Client flagged an issue on your deliverable? Here's what happens next.

A flag is the client's button for saying: this part needs work. It is specific, it is written, and it is attached to the deliverable itself, not buried in an email thread. Read it, fix what it names, re-deliver on the same record, and the client accepts the corrected version. The flag is how a handover handles a problem without becoming an argument.

What a flag actually is

On a Zambo handover, the client does not just accept or reject. They can flag an issue: a short written note pinned to the exact delivered item, saying what is wrong or missing. The flag is part of the record. Anyone reading the handover later sees the work, the flag, your fix, and the final acceptance in one chain, in order. Nothing depends on who remembers which email said what.

That changes the conversation. A complaint in chat is vague and easy to escalate. A flag has to name the problem, which means most flags are fixable items: a wrong figure, a missing file, a section that needs another pass. You answer the flag, not the mood.

The five steps after a flag

Read the flag on the record. It names the item and the problem. If it is unclear, ask on the record, not in a side channel.
Acknowledge it in writing. One line: what you will change and when. The client sees the flag is being handled.
Fix the work. Do the correction the flag names. If you disagree, say why on the record and show the evidence; the record carries both sides.
Re-deliver on the same handover. The updated deliverable joins the same record. The client sees the original, the flag, and the corrected version together.
The client accepts the corrected version. Acceptance closes the flag and stamps the final state. The payment conversation now has a complete, agreed history.

Why this beats the email argument

Without a record, a flagged problem turns into competing memories: the client says the work was never right, you say the fix was sent Tuesday. With a handover, the flag, the fix, and the acceptance are one timeline that either side can open. Most disputes die at the flag stage because the flag forces the specific complaint into the open while it is still small and fixable.

It also protects the client, which is why clients use it. Flagging is safer than paying and hoping, so clients accept deliveries faster when they know a flag costs them nothing and stays attached to the work.

Set it up before you deliver

The flag only works if the delivery itself runs through a record. Send the work as a Zambo handover from the start: the client opens one link, sees the deliverables, and can accept or flag each one. The Day Pass at $0.99 covers a full day of handovers for the job you are delivering today, and every handover page carries the same accept and flag flow. See how to hand off AI work to a client and the client approval page for the full setup.

Frequently asked questions

What does it mean when a client flags an issue on a deliverable?

It means the client used the flag option on the handover record to attach a written note to the exact item, naming what is wrong or missing. The flag becomes part of the delivery record alongside the work itself, so the problem, your fix, and the final acceptance all sit in one timeline.

Is a flag the same as rejecting the work?

No. A rejection ends the delivery. A flag is a request for a specific correction while the delivery stays open. You fix what the flag names, re-deliver the corrected version on the same record, and the client accepts it there.

What should I do first when a client flags my work?

Read the flag on the record, acknowledge it in writing with what you will change and when, then make the fix and re-deliver on the same handover. Answering on the record matters: your response becomes part of the same timeline the client will check before paying.

What if I disagree with the flag?

Say so on the record and show your evidence, for example the brief line the work follows or the source the figure came from. The record carries both sides in order, which is exactly what settles the question later if it ever becomes a payment dispute.

Does the client pay before or after flags are resolved?

That is the client's call, and the record supports both. Many clients accept and pay once the flags are closed, and the closed flag history is their proof the issues were handled. If a client later refuses to pay, the same record, flags and fixes included, is your evidence of what was delivered and agreed.

Zambo is the verifiable work layer for AI: handover, verify a receipt, Day Pass.