Reputifly editorial · Reviewed 27 September 2026 · 2 min read
A reusable briefing format that separates confirmed facts, proposed work and unanswered questions.
Prepare the source notes
Start with the client’s actual request, relevant existing pages and confirmed business facts. Remove unnecessary personal information before using an AI tool. Keep a reference to the original notes so a reviewer can check where each requirement came from.
Use a brief with six fields
- Objective: the business or visitor problem to solve.
- Audience: the people and situations the work must support.
- Confirmed facts: offers, prices, dates and constraints supplied by an authorised source.
- Deliverables: the pages, assets or actions required.
- Open questions: missing information that changes the work.
- Acceptance checks: observable conditions that define completion.
A prompt that exposes uncertainty
Turn these notes into the six-field brief above. Preserve confirmed facts exactly. Mark assumptions as assumptions. Do not invent prices, results, testimonials or deadlines. Quote the source note beside any requirement that could be ambiguous. Finish with the decisions a person must make.
This is a drafting aid, not authority to approve a scope. Ask the project owner to resolve contradictory notes before production begins.
Check one realistic example
If the notes say “make the proof images readable on mobile”, the deliverable is not automatically a new homepage. A useful acceptance check is that each full image can be opened, inspected and closed on a phone without losing position. Record the existing header and unrelated sections as constraints.
Keep the human approval visible
Assign an owner, version and review date. Compare the final brief against the notes, then remove requirements that were guessed. Use the approved brief for handoff; keep the source material in the appropriate private project record. AI can organise a request, but it cannot establish that a business claim is true.
