Free guide · Context before drafting
Your AI Working Brief
Give AI the context a capable colleague would need.
You’ll leave with a short, reviewed brief for 1 real task: an email, proposal, presentation or team update. Use the brief to guide your first draft and check the result.
Start with 1 piece of work
Choose something you need to write. “Help with my work” is too broad. “Write an email asking our CFO to approve temporary reporting support” gives the interview a purpose.
Open a conversation in your workplace-approved AI tool. Use details you’re allowed to share. Replace sensitive names and figures with placeholders where needed. Keep a private mapping so you restore the right details later.
Follow this sequence: interview → working brief → your review → first draft.
Copy the interview prompt
Replace the opening placeholder. Paste the whole prompt into your conversation. Answer each question with specific details. “I don’t know yet” is a useful answer.
I need help with this piece of work: [describe the email, proposal, presentation or update]. Before writing, interview me to build a short working brief. Ask 1 focused question at a time and wait for my answer. Start with the outcome I need. Skip questions I’ve already answered. Follow up when an answer is too vague to guide the work. Cover my role and team, the audience and their priorities, the decision or action I need, the relevant background, confirmed facts and sources, constraints, tone, output format and what a good result looks like. Use only information I supply. Don’t invent facts, deadlines, approvals or audience preferences. If I don’t know an answer, mark the gap as “To confirm.” Label suggestions separately from confirmed details. If my answers conflict, ask me to resolve the conflict. Aim for 6–8 questions, then summarize what you have. Don’t keep interviewing to fill every field. If a missing detail would change the decision, cost, scope, deadline or requested action, flag the gap as blocking. Mark other gaps as non-blocking. Ask me to confirm your assessment. Summarize the brief under these headings: 1. Role and team 2. Audience and priorities 3. Deliverable 4. Desired decision or action 5. Background 6. Confirmed facts and sources 7. Constraints and boundaries 8. Voice and tone 9. Output requirements 10. Success criteria 11. Open questions 12. Review status Keep the brief around 300–450 words. In Open questions, separate blocking gaps from non-blocking gaps. Set Review status to “Awaiting my review.” Ask me to correct the brief and resolve blocking gaps. Stop there. Don’t write the deliverable until I approve the brief and ask for a draft.
Give useful answers. Instead of “Keep the CFO happy,” try “The CFO needs the total cost, the consequence of waiting and a clear approval request.” Instead of “Make the email professional,” try “Lead with the decision. Use short paragraphs. Skip the warm-up.”
If you already have the details, fill in the template below and ask AI to identify missing or conflicting information, 1 question at a time.
Save your reusable brief template
Copy this into a document you control. Keep stable context, such as your role and writing preferences, separate from facts you’ll refresh for each task. Aim for 1 page of concise notes.
WORKING BRIEF
Task: [short name]
Version / reviewed date: [version and date]
REUSABLE CONTEXT, recheck for each task
1. Role and team: [my responsibility; who’s involved]
2. Audience and priorities: [who will read this; what they know; what matters to them]
8. Voice and tone: [how I’d say this; phrases to avoid; optional short writing sample]
THIS TASK, update before reuse
3. Deliverable: [what I need written and why now]
4. Desired decision or action: [who needs to do what, by when]
5. Background: [why this matters; what’s already happened]
6. Confirmed facts and sources: [facts, figures and dates; source or owner for each]
7. Constraints and boundaries: [budget, scope, timing; what isn’t approved or promised]
9. Output requirements: [format, length, structure and required points]
10. Success criteria: [2–3 observable checks for a useful result]
11. Open questions:
Blocking: [missing details which change the decision, cost, scope, deadline or action]
Non-blocking: [details to omit or leave as labelled placeholders]
12. Review status: [Awaiting my review / Needs changes / Approved for drafting]
Reviewed by: [name and date]Save the corrected version after your review. In a new conversation, paste your brief again and refresh the audience, dates, figures, sources and open questions. Don’t rely on the tool to remember your previous conversation.
See a completed workplace example
Fictional example: an operations manager needs a CFO decision on temporary reporting support. Every person, figure, date and source below is invented for practice.
Notice the difference between “Write a professional email asking for help” and a brief which makes the decision clear.
WORKING BRIEF Task: Temporary reporting support approval Version / reviewed date: v1 / 2 October 2026 1. Role and team I’m Morgan, Operations Manager. I coordinate monthly service reporting with a team of 4 analysts. I own delivery of the reporting pack and the request for extra support. 2. Audience and priorities Priya, our CFO, approves unbudgeted spending. She knows we have a vacancy but hasn’t seen the options. She needs cost, timing and the consequence of waiting. 3. Deliverable An email requesting a decision on temporary support for the November reporting cycle. 4. Desired decision or action Ask Priya to approve up to $4,800 CAD by 9 October 2026 so I’m able to start procurement. Approval would authorize the spend, not confirm a contractor booking. 5. Background An analyst vacancy has reduced reporting capacity. We considered temporary support or moving the internal pack deadline from 6 November to 13 November. The later date needs separate agreement. 6. Confirmed facts and sources • 4 analysts on the team; 1 additional role vacant: staffing plan, owned by Morgan, checked 2 October. • Support estimate: 40 hours × $120 CAD = $4,800 CAD, all-in ceiling including applicable taxes and fees: procurement estimate, owned by Alex, dated 1 October. • Target support period: 26 October–6 November; pack due 6 November: reporting calendar, owned by Morgan, checked 2 October. • Without support, Morgan forecasts a 13 November delivery date. This is an estimate, not a guaranteed outcome. 7. Constraints and boundaries No spending or booking before approval. Procurement must confirm availability and access arrangements before work starts. Don’t promise the original delivery date or imply a contractor is secured. 8. Voice and tone Direct, calm and accountable. Lead with the decision. No apology-heavy opening or exaggerated urgency. 9. Output requirements Subject line plus an email body of 150–180 words. Include the request, cost, trade-off, procurement condition and next step. Sign as Morgan. 10. Success criteria Priya sees the spending ceiling and decision deadline immediately. She understands the delay estimate and booking uncertainty. The email makes approval or a discussion of the later deadline easy to request. 11. Open questions Blocking: none for requesting budget approval. Non-blocking: contractor identity and availability. State availability as a procurement condition; don’t invent a name or confirmed start. 12. Review status Approved for drafting by Morgan, 2 October 2026, for this fictional practice exercise.
Why this brief helps: the writer has a specific request, a calculation, a fallback and limits on what to promise. An uncertain contractor booking doesn’t disappear behind polished wording.
Review before you draft
Read the AI’s summary against your own information. A fluent summary still needs your judgment.
If a check fails, paste this correction prompt:
Revise the working brief with these corrections: [list corrections]. Preserve confirmed details elsewhere. Flag any conflicts created by my changes. Show the updated brief and unresolved questions. Keep the status as “Awaiting my review” and stop before drafting.
You’re ready to draft when the requested action is clear, the facts are checked and no blocking questions remain. For a non-blocking gap, choose an explicit treatment: omit the detail, state the uncertainty or use a labelled placeholder.
Copy the next-step drafting prompt
Use this in the same conversation after your review. Replace every bracketed field. If you’ve edited the brief outside the conversation, paste the corrected version first.
I’ve reviewed and approved working brief [task name, version and date]. Use that version to write [deliverable]. Follow its audience, desired action, voice, constraints and output requirements. Use only the confirmed facts and clearly labelled estimates in the approved brief. Don’t invent sources, figures, approvals, dates or promises. Treat remaining non-blocking gaps as follows: [list each gap and whether to omit, state uncertainty or use a labelled placeholder; write “None” if there are no gaps]. If you find a conflict or a blocking gap, stop and ask me 1 focused question before drafting. Otherwise, provide the draft, then a short “Review notes” section outside the deliverable. In those notes, check each success criterion and list any remaining uncertainties or placeholders. Don’t call a criterion met if you lack the evidence.
For the example: fill in “Temporary reporting support approval, v1, 2 October 2026” and “a CFO approval email.” For the remaining gap, write “State contractor availability as a procurement condition. Omit the contractor’s identity.”
Read the draft before using or sending the result. Check the requested action, facts, tone and commitments against the approved brief. Remove or resolve any remaining placeholders.
Keep the brief useful
For your next piece of work, reuse the role and voice context, then update the task details. If the audience, decision or facts change, review the brief again before drafting.
Your finished output from this guide is a brief you’ve checked, a draft grounded in your work and a saved template for next time.