Handling client content approval for AI-written pages: a workflow that gets a clear yes

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: Get a clear yes on AI-written pages with seven steps: your editor fact-checks each page against the client's own documents, the client names one approver, you send pages in small batches with a deadline, the approver marks each fact and claim, you fix and resend only what changed, and the approver signs off in writing before anything goes live. Keep the record. AI drafts are fast, so the bottleneck is no longer writing. It is the client's review, and a clear process is what stops it dragging on.

Ranjit Bhinge

Your AI tool can write 20 pages in an afternoon, and the client has not yet replied about the first five.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Content approval is the step where a client confirms that the words on their site are accurate and say what they want to say. With AI-written pages, the approval has a second job: someone who is accountable has to confirm the facts, because the tool writes smoothly whether it is right or wrong. Google's own page on generative AI content warns that outputs may contain inaccuracies, which it calls hallucinations, and says to manually fact-check and review all AI-generated content before publishing. Its helpful-content guidance asks "who, how and why" questions about who created a page and how. A written approval from a named person on the client side is how you prove the facts were checked.

This page gives you the whole workflow: who does what, the steps, the tools, a message template, a sign-off record, and a worked example. It sits next to the general guides on client approval workflows and the content approval process. What is new here is the AI part: pages arrive faster than reviewers can read them, and the errors are fluent ones.

Why approval breaks down with AI drafts

  • Volume. Twenty pages arrive at once and the client reads two, then goes quiet.
  • Everything looks finished. Smooth text hides a wrong price, a service the client does not offer, or a made-up credential.
  • Too many reviewers. Three people send three sets of comments that contradict each other.
  • No deadline. A silent client is treated as a "yes", or the project stalls for weeks.
  • No record. Someone later says they never approved that line, and nothing shows otherwise.

Each step below fixes one of these.

The seven steps

Step 1: name the approver and the deadline in the kickoff

Ask the client for one person who can say yes, and one backup. Put both names and the review window in the kickoff message and in the contract. A typical window is three working days per batch. State what happens when the window passes: either you send one reminder and then pause the project clock, or the page moves to "approved with no changes" only if the contract says that in plain words. Do not assume silence means yes. The contract language is covered in contracts for website work in the AI era.

Step 2: collect the facts before the AI writes

Ask the client to supply a facts sheet: services, prices or price ranges, service areas, hours, licences, years in business, staff names, claims they can prove. Give this to the AI as the only source of facts. That moves the review from "is this true" to "does this match our sheet", which is much quicker.

Step 3: your editor reviews before the client sees anything

A named person on your side reads every AI-written page against the facts sheet. Check the numbers, names, places, claims and any statement about the law or health. Cut anything unprovable. Google's position, set out in its search guidance, is that it judges quality and helpfulness, not how the text was made, and it says to fact-check and review AI content before publishing. Your review is the one that counts for Google. The client's is the one that counts for accuracy.

Step 4: send in batches, with a short cover note

Send three to five pages at a time, in priority order: home, main service pages, contact, then the rest. Each batch gets a cover note saying what is in it, what you want checked, and the deadline. Do not send raw drafts with AI notes or comments left in.

Step 5: make the client mark facts, not style

Give the approver a short list of questions per page: Are all facts correct? Is anything missing that customers always ask? Is there any claim you cannot prove? Is any sentence something you would never say? Ask for comments in one place only. If three people review, one person collects and sends a single set.

Step 6: resend only what changed

Fix the comments and send back only the changed lines or pages, with changes marked. Do not resend the whole batch. Count the rounds. Put the number of included rounds in the contract, for example two per page, and a charge for more. See getting written approval when a client changes the scope.

Step 7: written sign-off, then lock

The approver replies "approved" or signs a form for the batch. Save it. Then change the status of those pages to locked: later edits go through a change request. This is the same idea as creative approval sign-off, applied to words.

What to check on an AI-written page

CheckWhoWhy
Prices, hours, address, phoneClientThe AI may guess or reuse a sample
Services and service areasClientPages may add services the firm does not offer
Licences, awards, years, numbersClient, with proofUnproven claims can mislead customers and may draw regulator attention. Check local advertising law
Testimonials and reviewsClientMust be real and used with permission. The US Federal Trade Commission (FTC), the advertising regulator, bans fake or AI-generated reviews under a rule effective October 2024. Check local law
Legal, health, money or safety statementsClient, and a qualified adviser if neededHigh-risk topics need a human expert
Brand voice and words to avoidYour editor, then clientKeeps the site sounding like the client
Repeated or near-identical pagesYour editorGoogle's spam policies target pages made mainly to manipulate search rankings, however they are made
Author and "how this was made" lineBothGoogle advises bylines where readers expect them, and a short note on how content was made where readers would ask. Never invent an author, name or credential

Tools: simple first, then built

You do not need a special product to start. Choose the lightest setup that gives you three things: one place for comments, a status per page, and a saved sign-off.

  • Shared document with comments. A cloud word processor such as Google Docs, which lets several people comment on one file, works for small sites. Use a suggestion mode so changes are visible.
  • A tracking sheet. One spreadsheet row per page with columns for status (draft, with editor, with client, changes, approved, locked), owner, batch, sent date, due date and approval link.
  • Your project tool. A task board with one card per page and a rule that a card cannot move to Live without the approval attached.
  • Proofing and approval software. Review the options in content approval software if you have many clients at once.
  • Staging link. For the real look, send the page on a private preview address. See approving a real version, not a mockup.

Whatever you use, test it with a client who is not technical. If they cannot find where to comment in the first two minutes, change the tool.

A custom approval portal

If you run many client sites, a custom portal may be worth building: one login per client, pages shown with the facts sheet beside them, a yes, comment or no button per page, automatic reminders as the deadline nears, a locked state after sign-off, and a dated record you can export. Blur Studio builds this kind of portal, as part of its custom build and care work, for agencies that outgrow shared documents and sheets. It is only worth it when the manual process costs you more than the build, so count the hours first. See how to build a client approval portal for what it involves, and what Blur Studio builds.

Copy-ready templates

Kickoff note. "To keep your site on schedule, please name one person who can approve pages and one backup. We will send pages in batches of about five. Each batch has a three working day review window. We will send one reminder. If the window passes with no reply, the schedule moves by the days we waited. Each page needs a written approval before it goes live."

Batch cover note. "Attached: Home, Services, Plumbing repair, Water heaters, Contact (batch 1 of 4). Please check: facts and numbers, anything missing that customers ask about, any claim you cannot prove, any sentence you would not say. Reply by [date]. Reply in one message with all comments."

Sign-off line. "I, [name], confirm that the pages listed below are accurate and approved for publishing. Date: [date]. Pages: [list]."

Tracking sheet columns. Page, status, owner, batch, sent, due, round number, approver, approval date, link to the saved sign-off.

A worked example with made-up numbers

An agency builds 18 pages for a heating firm in a morning. The numbers are invented to show the method.

The editor checks each page against the facts sheet and cuts five lines: a "family owned since 1985" claim the sheet does not support, an invented award, and three services the firm does not offer. Pages go to the client in four batches of four or five. The approver, the owner's office manager, has a three working day window per batch. Batch 1 comes back in two days with six comments, mostly a wrong service area and a missing phone number. The editor fixes them and resends only the changed lines. Round two is approved the next morning. Batches 2 to 4 follow the same pattern, and the whole approval takes about two weeks, against the three or four weeks of "any chance you could look at this" emails it often takes without a process. The record is 18 rows, each with a date and the approver's name. The saving here is a model, not a promise: your time depends on how fast your client replies.

When this is too much

For a one-page site and a client who answers in an hour, one message with "reply yes to approve" and a saved copy of the reply is enough. Keep the record, skip the batches. Use the full workflow when there are many pages, several reviewers, regulated topics such as health, law or money, or a client with a history of changing their mind.

How I'd approach this

I would treat approval as part of the build, not an afterthought, and price it into the project: a set number of batches and rounds, and a clear charge beyond that. The record matters more than the tool. A dated "approved" from a named person protects both sides.

First week: write the facts-sheet request and the kickoff note from the templates above, and send them to your next client before the AI writes a word. Set up the tracking sheet with the status column. Name your editor, the person who checks every AI page before the client sees it. At the end of the first batch, count how long the client took and how many comments were about facts. If most are about facts, improve the facts sheet. If most are about voice, improve the brief. Pair this with the 20-point QA checklist for AI-built websites at launch.

Related guide: AI disclosure on websites and in outreach.

You may also want Ploy vs Jasper and Copy.ai.

Related guide: getting on-brand copy with no brand guide.

Questions people ask

Who should approve AI-written pages on the client side?

One named person who knows the business and can say yes, such as the owner or office manager, plus one backup. Many reviewers give conflicting comments. If several people must review, one of them collects the comments and sends a single set.

What if the client never replies?

Agree the rule in the kickoff note and the contract. A common rule is one reminder, then the schedule moves by the days you waited. Do not treat silence as approval unless the contract allows it in plain words. Check local law for how silence is treated in contracts.

Do I have to tell the client the pages were written with AI?

No general law requires it that I know of, but clients increasingly ask and some have policies about it. Saying which parts are AI-assisted and that a person reviewed them builds trust. For contract wording, see the AI clause for an agency contract.

Should the website say that AI helped write a page?

Google's helpful-content guidance says to add bylines where readers would expect them, never to use made-up names or false credentials, and to add an AI or automation disclosure where readers might think "how was this created?". Whether to add a line depends on the page and the client. Check Google's current guidance and local law.

How many revision rounds should I include?

Two per page is a common starting point, and a stated charge or hourly rate for more. Say what counts as a round in the contract. See agency scope creep for how extra rounds creep in.

What is the best tool for client content approval?

The simplest one the client will actually use: shared documents with comments plus a tracking sheet is enough for small sites. See content approval software for dedicated tools, and test any option with a non-technical client first.

How do I stop the client rewriting everything in their own style?

Agree the brand voice in the kickoff, give examples of sentences they like and dislike, and ask reviewers to mark facts first and style second. Style comments beyond the included rounds go through a change request.

Is a written approval enough if something on the page is wrong later?

It shows the client checked and accepted the page, which helps in a dispute, but it does not replace your own review or remove duties under local advertising or consumer law. Cut claims that cannot be proven, whoever approved them. This is information, not legal advice.

More in this topic: Websites: agency delivery, quality control and margins (10 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…