Website Design OutsourcePowered by StealthAgents

How to Set AI Copy Rules for an Outsourced Website Build

A practical rule set for AI-assisted copy in an outsourced website build, covering permitted uses, client confidentiality, factual sourcing, originality checks, brand voice, regulated claims, and handoff records.

Visual guide for How to Set AI Copy Rules for an Outsourced Website Build
On this page
  1. Decide which copy tasks may use AI
  2. Write a disclosure rule the client can accept
  3. Keep confidential material out of public tools
  4. Require a source note for every factual claim
  5. Check originality before the copy enters the CMS
  6. Teach voice with samples instead of adjectives
  7. Route regulated claims to a named reviewer
  8. Record prompts, versions, and edits
  9. Test the rule on one live template
  10. Related reading

Decide which copy tasks may use AI

A website build contains several kinds of writing, and they do not carry the same risk. A meta description is not the same risk as a privacy notice, a medical claim, or a testimonial. Start the rule by listing the tasks the vendor may draft with AI assistance and the tasks that must be written or approved by a person. Put the list in the statement of work so the boundary is agreed before production begins.

The list should name the deliverable rather than the tool. Naming a specific product creates a rule that expires when the vendor changes software, while naming the deliverable survives a tool change. A useful entry might permit first drafts of non-regulated service page copy and require alt text to be checked against the image. Ambiguity at this level becomes an argument during review, when the page is already in staging.

Write a disclosure rule the client can accept

Some clients want to know when AI touched a deliverable, while others care only about quality. Ask which position applies before the first draft and record the answer in the handoff. A simple three-level rule works: AI is free for internal planning, disclosed for client-facing drafts, and prohibited for named case studies or attributed quotations. The levels give the vendor room to work without hiding the practice.

Disclosure does not need to be a label on the live page. In most builds it belongs in the content handoff record, beside the draft version and the editor who accepted it. That record lets the client answer a later question about how a page was produced. If the client does want a public statement, agree the wording and placement before launch.

Keep confidential material out of public tools

Client briefs often contain unreleased product names, pricing, customer lists, and internal process notes. A public AI tool may retain prompts or use them for training, depending on its terms and settings. Before the project starts, agree which material may never be pasted into an external tool and provide a redaction step for the rest. A shared safe-to-draft folder containing only approved background gives designers and writers a bounded source, while tasks that cannot be redacted stay with a person who has access under the contract.

Require a source note for every factual claim

AI tools produce fluent sentences that can contain a wrong number, a missing qualifier, or an invented study. The fix is not a stronger warning but a required source note for every factual sentence. The writer attaches the URL, the retrieval date, and the exact claim the source supports. A reviewer can then check the note without re-reading the whole page or trusting the model's confidence.

Set the rule for numbers, dates, rankings, certifications, and comparisons. A sentence such as "most clients see results in six weeks" needs a source or it gets removed. The same applies to claims about a competitor, a guarantee, or a regulation. The source note can live in the draft document or the CMS revision field, but it must reach the reviewer before the page is approved. Pages without notes do not move to staging.

Check originality before the copy enters the CMS

AI-assisted drafts can resemble existing web copy even when no source was copied deliberately. Run a similarity check on every client-facing page before it enters the CMS, and keep the report with the draft. Review the flagged passages rather than accepting a percentage score, because a high score can come from a shared product description and a low score can hide a paraphrased paragraph. Treat a close match as a writing problem, not a score to explain away.

The check should include the vendor's own earlier pages. Reusing a paragraph from another client site is a serious problem even when the words were generated fresh for this project. Add a rule that no sentence from another client's deliverable may be reused without written permission. When a match appears, rewrite from the approved brief and record the change.

Teach voice with samples instead of adjectives

A brief that says "friendly but professional" gives a model and a human writer nothing to test. Replace the adjectives with three approved samples: one page the client likes, one page the client dislikes, and one paragraph written by the client. Annotate each sample with the traits that matter, such as sentence length, use of contractions, and how directly the page names a price. The samples become the reference for every draft.

Ask the writer to produce a short voice test before the full batch. Two paragraphs on the same topic, one in the proposed voice and one in a deliberately wrong voice, show whether the rule is working. The client picks a direction and the annotation is updated. This step costs less than rewriting ten pages, and it gives the reviewer a concrete basis for rejecting a weak draft.

Route regulated claims to a named reviewer

Some copy cannot be approved by a designer or a general editor. Health claims, financial promises, legal statements, accessibility commitments, and data-processing descriptions need a named reviewer with the right authority. List those categories in the rule, name the reviewer for each, and state what evidence the reviewer needs. The vendor should not publish a regulated sentence because the client did not object at review.

The reviewer's approval belongs in the record, with a date and the exact version reviewed. If the reviewer changes a sentence, the change is recorded like any other revision. When no reviewer is available, the page holds rather than shipping with an unreviewed claim. The record shows the claim had an owner.

Record prompts, versions, and edits

A handoff that says "copy was AI-assisted" cannot be audited. Keep a lightweight record for each deliverable: the tool and model version, the prompt or brief used, the draft version, the editor who revised it, and the source notes. The record does not need to include every intermediate attempt. It needs enough detail for a second reviewer to see how the text was produced and what changed.

Store the record with the content handoff rather than in a personal chat history. When the client moves to another vendor, the new team should be able to tell which pages had AI involvement and where the supporting sources live. This is the same discipline used for image rights and font licenses, applied to text. The record also makes a later correction faster, because the original claim and its source are already linked.

Test the rule on one live template

Choose one low-risk template, such as a service page or a team bio, and run it through the full rule before applying the process to the rest of the site. Draft the page, attach the source notes, run the similarity check, and send it to the named reviewer. Inspect what the reviewer actually received, because missing notes and unclear ownership show up quickly on a single page. After the test, update the rule, add the examples that helped, and confirm the client accepts the revision before the remaining templates follow.

Turn the guidance into a reviewable handoff

Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.

Plan a website production handoff

Move one website project from backlog to a reviewed handoff.

Share the pages, platform, current assets, deadline, and approval owner. We will help determine the right production lane and the decisions your team should keep.

Plan the handoff