Who this is for, and what changes
Useful when a website lists broad capabilities but does not explain suitability, constraints, implementation or purchasing decisions. Begin with the questions an actual buyer must resolve rather than a target number of pages.
Possible work includes service detail pages, comparison criteria, procurement questions and specialist articles. Give a direct answer, explain conditions and link the facts that support it. Do not manufacture awards, customer endorsements or results to fill a page.
What we need before drafting
- Priority audiences and buying questions, existing URLs, target languages and the actual service or product scope.
- An approved fact ledger or source materials, subject-matter input and a list of statements that require further confirmation.
- Brand terminology, an author or reviewer, and the person authorised to approve customer-facing wording.
- A publishing owner and agreed website or platform permissions. Delivery of text does not itself authorise access to a CMS or publication on an external account.
Deliverables to agree
| Deliverable | What it contains |
|---|---|
| Content plan and briefs | Question, audience, purpose, page structure, supporting facts, internal links and an acceptance checklist for each agreed item. |
| Reviewable drafts | Service explanations, buyer answers or articles, with source references, conditions, unresolved claims and proposed titles and descriptions. |
| Version and approval record | Immutable text-and-source versions, reviewer decisions, customer feedback and the revisions made in response. |
| Publication handover | Approved text and a destination checklist. A real publication requires its own live URL, time and inspection record; a draft is not a publication receipt. |
How the schedule is established
Use the following as a planning sequence, not a promised delivery duration. Quantities, languages, review rounds and publisher availability determine the schedule after the agreed contract and funding conditions are met.
| Stage | Completion condition | What affects timing |
|---|---|---|
| Brief approval | Questions, page purpose and evidence requirements agreed. | Unclear audiences or missing facts. |
| Drafting | Scoped items ready for subject-matter review. | Technical depth, translation and source availability. |
| Review and revision | Claims resolved and the current version approved. | Reviewer response and agreed revision scope. |
| Handover or separately authorised publication | Delivery acknowledged; if publishing is included, live evidence checked. | CMS permissions, customer approval and release windows. |
Acceptance and the current capability boundary
- Check that the agreed buyer question is answered, important claims are supported, names and units are consistent, and limitations are visible. A source link should support the statement beside it.
- Approve the latest version and its sources. If live publication is in scope, inspect the actual destination, public access, language, links and agreed metadata; an internal approval is not proof of external publication.
- The current commercial workflow supports versioned text, human review and protected customer feedback. Automated content production, external-platform publishing and controlled file delivery have not completed full production implementation and acceptance.
- No particular AI citation, index inclusion, ranking or inquiry volume is guaranteed. Distribution, source outreach and outcome measurement require separate permissions, evidence and scope.