7 min reading · Practice at your pace
Write a Work Brief with Clear Inputs and Checks
Give Work an outcome, useful source material and a definition of done. Adapt a complete meeting brief and learn how to check the actual file it produces.
Make success observable before the task starts
Give Work an outcome, the inputs it may use and a way to check the finished result. A useful brief tells the assistant what to produce and tells you how to review it. Start with a task whose facts and requirements you understand.
A brief that led to a real editable proposal
Give Work the source facts, named sections and table columns you need. This workshop brief shows how those instructions become an editable document.
Checked values in the actual final Word table
| Item | Details |
|---|---|
| Scenario | Without optional printing. The proposal still needs approval. |
| Total cost | USD 370. |
| Proposed income | USD 480. |
| Remaining funds | USD 110, excluding unspecified tax and delivery. |
| Questions to resolve | What tax applies? What delivery terms apply? |
Name the result, sources and acceptance checks
Make requirements specific enough to inspect. Keep facts separate from preferences and unknowns.
How the actual document request defined success
| Item | Details |
|---|---|
| Audience and outcome | A small community group deciding whether to run a workshop; an actual editable Word brief, not only Chat prose. |
| Source facts | 24 proposed participants × USD 20 = USD 480; stated base costs total USD 370. Optional printing adds USD 25. |
| Deliverable | Cedar Workshop Brief, marked example, with Purpose, Source facts, Cost comparison and Decision to confirm. |
| Native structure | An editable Word table with named scenario/cost/income/remaining-funds columns. |
| Unknowns | Tax and delivery unspecified. No approval, date, venue or attendance guarantee. |
| Checks | Recompute the figures, preserve USD units and ask the two source questions separately. |
Read the initial request
This request is preserved from the earlier actual Work document task.
Create a real editable Word document named cedar-workshop-brief.docx from these notes. Use only these source facts, not personal memories, connected accounts or outside files. Deliver the actual document, not only chat prose.
Audience: a small community group deciding whether to run a workshop. Proposed participants 24, proposed fee USD 20 each, proposed income USD 480. Notebooks 24 at USD 5 = 120; marker packs 10 at USD 8 = 80; folders 20 at USD 3 = 60; room hire 1 at USD 110 = 110. Base cost is USD 370. Optional printing is USD 25, making total cost USD 395. Remaining funds are USD 110 without printing or USD 85 with printing. Tax and delivery are unspecified, so these remaining figures exclude them. No approval, date, venue or attendance guarantee exists.
Title: Cedar Workshop Brief. Mark it example. Include sections Purpose, Source facts, Cost comparison, and Decision to confirm. Include an editable native Word table comparing the two scenarios, with columns Scenario, Total cost (USD), Proposed income (USD), Remaining funds (USD). Ask exactly two separate questions under Decision to confirm: What tax applies? What delivery terms apply? Keep the event a proposal, not an approved plan. Check every figure and unknown before delivering.
Build a brief for your own task
Use this structure for the outcome, source authority, deliverable, scope and checks. Replace the brackets with facts you can verify. The complete practice brief below shows how those fields fit together.
Outcome: [The finished result and who will use it.]
Inputs: [Permitted notes/files, what each source supports and which is authoritative.]
Deliverable: [Actual file type, structure and required contents.]
Facts and unknowns: [Verified names/numbers/dates; missing information to leave explicit.]
Scope: [Allowed actions and any action requiring a decision.]
Preserve: [Correct facts, sections, interfaces or earlier versions.]
Checks: [Known totals, source comparisons, tests or other acceptance checks.]
Done means: [Delivered files, checks actually completed and anything incomplete.]Identify each source and what it may establish
Attach permitted files or paste the relevant notes. Say whether a file is factual authority, a style reference or an example. If sources disagree, name the authority or ask Work to flag the conflict. A filename or link alone does not establish that its content was read.
Describe allowed work and meaningful review points
Name what the task may change and what needs your decision before proceeding. A sentence in a brief does not grant access to a computer folder or connected account. Actual tools, client permissions and action review still apply. Check the task’s real questions and actions rather than assuming a pause occurred.
Check completeness and coherence
Inspect both the requested result and the surrounding explanation. In the document task, preserving Purpose during a narrow table revision left its old two-scenario wording. A later focused correction brought that paragraph into line with the new base-plan decision.
Try a meeting brief with known facts
Ask for an editable one-page document for the garden meeting. Keep the suggested agenda separate from supplied facts and preserve unknown date, address and contact information.
Revise only the agenda so introductions take 10 minutes. Preserve the supplied facts, keep the whole agenda at 45 minutes and leave the missing date, address and contact explicit.Work access and usage
Use Work with Plus for this exercise. See the Work reference for model usage, workspace access and task limits.
Work briefing questions
Keep the brief small enough to check.
What should I include in an AI Work brief?
State the outcome and audience, permitted sources, real deliverable, facts/unknowns, scope, preservation requirements and checks. Say what done means in inspectable terms.
Should I give Work every file I have?
Supply the files and passages the task needs, identify their role and avoid irrelevant or conflicting context. Tool access and model limits still apply.
Does an instruction to ask first guarantee that Work paused?
No. Read the actual task state and requested decisions. Action-review settings and tool permissions are separate from a sentence in the brief.
Guides and resources
Find more detail and choose your next step.
Your turn
Write a Work brief you can review.
Use the meeting brief below or replace its facts with your own permitted material. Inspect the delivered file against the requested sections, facts and agenda total.
Write a draft and review the checklist.
Your draft saves in this browser. You can leave and come back.
Take the brief into Work
Copy the brief, open Gab AI and choose Work before pasting and sending it. Open the delivered file and check it against the brief.
These buttons open the product and copy your draft. You choose the mode and send the request yourself.
Open Gab AI for WorkMake one change and check the whole result
Review the first answer, then send this follow-up in the same conversation.
Revise the meeting brief so introductions take 10 minutes. Adjust the other suggested agenda durations to keep the total at 45 minutes. Preserve Saturday at 10:30, 12 adult volunteers, the garden entrance and all missing details. Update any surrounding explanation that no longer agrees with the table. Return the complete revised file.Check that the requested change happened and the correct facts, format and missing details survived. For a file, open the revised artifact and inspect nearby paragraphs or formulas too.