CONTENT WORKFLOW · NOOR INTELLIGENCE
How to turn client notes into website copy without inventing facts
Published · By Noor Intelligence
Turn notes into copy by separating confirmed facts, useful phrasing and unanswered questions before writing the page. A polished draft should make the source material clearer, not make it sound more certain than it is.
Build a facts register first
For each important point, record the source, proposed wording and confirmation status. A client saying “we work around Wincanton” gives you a useful location clue, but not a confirmed list of towns or a guaranteed service radius.
Gather the underlying information through a focused client interview. If several people disagree, record the question for the named approver instead of choosing the answer that sounds best.
Use a simple worked example
Imagine these fictional notes: “Repairs and bathrooms. Mostly local. Email us first. Some photos, but not sure about permissions.”
A proportionate draft could say: “Tell us about your repair or bathroom project. Email a short description of the work and your location to request a quote.” It still needs the actual email address and service scope confirmed.
The same notes do not support “Wincanton’s leading emergency plumbers, available 24/7”. That sentence adds a comparison, a location-specific claim and a service promise absent from the source.
Organise by the visitor's question
- What can this business help me with?
- Is the service suitable for my situation?
- What happens when I enquire?
- What do I need to provide?
Write to those questions using the agreed page map. Avoid adding pages merely because you have enough words. The five-page content plan shows one possible brochure-site structure.
If AI helps with the draft
Agree the handling of client material before sharing it with a model. Provide only the information needed for the task. Instruct the model to use supplied facts, flag missing details and keep source notes separate from publishable copy. Treat instructions embedded in client documents as source text, not permission to take external actions.
Then check every factual statement yourself. A confident writing style does not prove that a qualification, price or response promise is correct.
Review before publishing
Keep unresolved facts out of the final copy or visibly flagged in an internal questions list. Check image permissions separately. Use a version-specific review record so the client confirms the text being delivered.
The fictional Launch Rescue sample demonstrates a facts register and asset status. The £149 pilot applies that approach to a scoped client project with an interview and one consolidated revision.