How We Review AI-Written and Staff-Written Content Before It Goes Live

The practical problem

Content rarely starts in one place. A team may have staff notes, a draft from an AI tool or a planning document. The risky approach is to treat any one of those sources as automatically ready for the public website.

What we built

We use one private draft process for different kinds of source material. It organises the draft, checks where it belongs, suggests useful links and records who should review it before the separate publishing step.

How the workflow works

1. Authorised staff choose or upload the source material.
2. The system turns it into a consistent private draft.
3. The draft is matched to an existing help area and useful website sources.
4. Staff can choose to use AI for rewriting or filling gaps, but that step is optional.
5. A person reviews the draft and marks it ready only when it is suitable.
6. Publishing remains a separate human-approved step.

Where AI is useful

AI can help rewrite, organise or fill gaps when staff ask for it. Text from an outside AI tool is treated as a draft, not as a trusted business fact.

Where AI is not allowed to decide

AI cannot publish by itself, create a hidden content area, overwrite an existing public page or bypass duplicate and safety checks.

Security, privacy and cost controls

Uploaded source files stay private. Public page choices are checked against allowed website locations, and important claims, links and wording are checked again before publication.

What another small business can take from this

Let people use the writing tools that suit them, but bring every draft into one consistent review process before it becomes public business information.

What this does not prove

This workflow handles the document structures it was designed for. Complicated layouts, unclear plans or unsupported page types still need staff editing.