Why every approval should cover one exact version
Why we think a client approval should cover one exact version of a website, email or invoice, and why it matters even more when an AI agent does the work.
Picture a message that everyone running a one-person AI agency has received in some form: "Looks great, go ahead!" It arrives on a Thursday, under a link to the draft home page. By the following Tuesday, that page has had a new photo, a shorter headline and a fixed typo. Then it goes live, and the owner asks why the headline changed.
Which version did "looks great" cover? The one she saw on Thursday. Nobody wrote that down, so the answer depends on who remembers better.
This note is about a rule we care about more than almost anything else in client work: an approval should cover one exact version, and any change after it needs a fresh yes. It sounds fussy. It's the opposite. It's what lets you and the client stop worrying about what was agreed.
What goes wrong with "looks good"?
"Looks good" is an approval of a moment, not of a thing. Websites, emails and quotes keep changing after someone glances at them. Each small change is reasonable on its own. Together, they drift away from what the client actually said yes to.
The trouble isn't dishonesty. Nobody in that story did anything wrong. The designer made sensible improvements; the owner approved what she saw. The gap is that the approval wasn't attached to anything you could open later and point at.
Once you see it, you notice it everywhere: an invoice changed after the client agreed the amount, a care plan email with one line edited after the client read it, a price on a page updated after sign-off.
What does approving an exact version mean?
It means the approval names one specific thing: this draft, this wording, going to this place. If any of that changes, the approval no longer covers it, and it comes back to the person who approved it. Approving one exact version has the short definition.
In practice it's small. Instead of "Here's the draft, any thoughts?", you send "Here's version 3 of the home page, shared today. If you're happy with this version, reply 'approved' and it goes live." If you then change the headline, you send version 4 and ask again. It adds one line to a message, and it turns every future question about what was agreed into something you can open and check.
Why this matters more with an AI agent
When you do all the work yourself, you at least know what you changed. When an AI agent drafts pages, writes emails and edits copy, changes can happen quickly, sometimes in places you didn't expect. An agent can improve a sentence after you read it, in good faith.
So the rule has to cover you as well as the client. What goes out under your name should be exactly what you read. That's the thinking behind the rule we recommend for AI agent approval: anything a client or customer will see waits for your yes, on that exact version.
The people who write the Model Context Protocol, the standard way many AI agents connect to other programs, reached for a similar idea. Its specification says users must explicitly consent to and understand all data access and operations, and that hosts must get explicit consent before invoking any tool. Consent there is tied to a specific action, not granted once for everything.
Why we built Volant around it
In designing Volant, we kept returning to one question: what would let a person working alone trust an agent with real client work? Better drafts help. Remembering the client between sessions helps; Claude Code context between sessions was about exactly that. But neither answers the worry that something will go out that you didn't mean.
Exact-version approval answers it. If nothing leaves without your yes on that exact version, you can let the agent work fast, because speed stops being a risk. You check what matters, once, at the moment it matters.
We think it's also the promise clients care about most. Owners of small businesses are rarely worried about the technology. They're worried about being surprised. "You'll see exactly what goes live, and nothing changes after you approve it without asking you again" is a promise they understand straight away.
If you keep notes for freelance web design time tracking, look for the hours that went on untangling: working out what had been agreed, then fixing the gap between that and what happened. That's the time a clear approval gives back.
How to start doing this tomorrow
You don't need special software:
- Give every draft a version number or a date in its name.
- When you ask for approval, name the version in the message.
- Keep the approved version, or a link to it, with the client's notes.
- If anything changes after approval, send the new version and ask again.
- Put only the approved version live.
If you're setting up a one-person agency now, build this habit before your first client, not after your first argument. Starting a one-person AI agency covers the other habits worth having from day one.
Where Volant fits
Volant sends, posts, publishes and invoices nothing until you approve that exact version, and a change after you approve comes back to you for a fresh yes. Tools your agent uses on its own, outside Volant, follow their own rules, so check those separately. If you want to know why we think this matters enough to build a whole product around it, why Volant exists tells the longer story.