Canonical page: https://tellenze.com/work-templates/clear-work-brief [All templates](https://tellenze.com/work-templates) A free writing template # Clear work brief Turn a broad request into an outcome someone can act on and check. Use it when you are about to hand work to a person or an agent and need to agree what a useful result looks like. [Start with the blank template](#blank-template)[Read the filled example](#filled-example) No account or email needed. Downloads work without JavaScript. Make the structure useful ## Current facts. A clear next step. Replace the prompts with your own context. Keep an unanswered question visible when the facts are missing. Agree the people and decisions rather than copying them from the example. The blank and filled versions are portable Markdown. They do not install native Tellenze templates or create workspace work. [Define clear work](https://tellenze.com/guides/define-clear-work) - 01 Name the change someone should be able to observe, then explain who needs it and why. - 02 Keep the scope small. Add current sources, limits and questions that could change the approach. - 03 Write acceptance checks a reviewer can try. Agree who reviews the result before work begins. - 04 Replace every placeholder, then read the brief with the contributor. Update it when a decision changes the scope. 01 / Your starting point ## Begin with the real work. Copy or download this version. Replace the placeholders, then review the definition with the people who will use it. Portable Markdown ## Blank template [Download blank template](https://tellenze.com/work-templates/clear-work-brief/download?version=blank) Use the preview below, then copy the text or download a .md file. ### Clear work brief #### Outcome [What should be different when this work is finished?] #### Why this matters - Who needs the result: [person or group] - Current problem: [what happens today] - Useful change: [why the result helps] #### Scope - Included: [the work covered by this brief] - Outside this request: [what can wait] #### Context and sources - Current facts: [facts the contributor needs] - Sources: [link or location, version or date, and why it matters] - Access check: [confirm the contributor and reviewer can open each source] #### Constraints and open questions - Constraints: [formats, agreed decisions, technical or operational limits] - Open questions: [what needs an answer before work proceeds] - Dependencies: [what must happen first, and the next action] #### Deliverables [Code, document, design or other output, and where it will be saved] #### Acceptance checks - [An observable successful result] - [A relevant failure or access case] - [Evidence a reviewer can inspect] #### Review and handoff - Contributor: [agree a person or agent] - Reviewer: [agree who checks the result] - Required approval or external action: [state it, or write none] - Handoff: [link the output, verification results and any remaining step] View blank template Markdown source Markdown source — blank template# Clear work brief ## Outcome [What should be different when this work is finished?] ## Why this matters - Who needs the result: [person or group] - Current problem: [what happens today] - Useful change: [why the result helps] ## Scope - Included: [the work covered by this brief] - Outside this request: [what can wait] ## Context and sources - Current facts: [facts the contributor needs] - Sources: [link or location, version or date, and why it matters] - Access check: [confirm the contributor and reviewer can open each source] ## Constraints and open questions - Constraints: [formats, agreed decisions, technical or operational limits] - Open questions: [what needs an answer before work proceeds] - Dependencies: [what must happen first, and the next action] ## Deliverables [Code, document, design or other output, and where it will be saved] ## Acceptance checks - [ ] [An observable successful result] - [ ] [A relevant failure or access case] - [ ] [Evidence a reviewer can inspect] ## Review and handoff - Contributor: [agree a person or agent] - Reviewer: [agree who checks the result] - Required approval or external action: [state it, or write none] - Handoff: [link the output, verification results and any remaining step] 02 / A fictional example ## See how the sections connect. The Northstar customer portal is fictional. Its receipt-download scenario shows a writing approach, with assumptions, unfinished checks and required decisions kept visible. Use the structure with your own facts. Example text is not evidence of a shipped feature or approval for an action. Portable Markdown ## Filled example [Download filled example](https://tellenze.com/work-templates/clear-work-brief/download?version=example) Use the preview below, then copy the text or download a .md file. ### Customers can download a receipt Fictional example: Northstar customer portal. Names, work and results are illustrative. #### Outcome A signed-in customer can download a PDF receipt for their own completed order from the order page. #### Why this matters - Who needs the result: customers who need a record of payment. - Current problem: they ask Support to prepare a receipt. - Useful change: they can retrieve the same agreed payment information themselves. #### Scope - Included: one receipt download action on completed orders, using the approved receipt fields. - Outside this request: refund receipts, bulk downloads and email delivery. #### Context and sources - Current facts: the order page already identifies the signed-in customer and the order payment state. - Sources: the agreed receipt-format document and the order-page design, linked in the real work item. - Access check: the contributor and reviewer must open both current sources before starting. The example supplies no private links. #### Constraints and open questions - Constraints: use the existing access check and PDF approach; add no new dependency without approval. - Open questions: confirm the displayed payment-date timezone before implementing the PDF. - Dependencies: the reviewer must confirm the receipt fields and timezone first. #### Deliverables A reviewed code change, tests for download and access behavior, and a short verification note linked from the work item. #### Acceptance checks - A completed order shows a PDF download action; the PDF has the correct order number, payment date and paid amount. - A customer cannot download another customer's receipt; incomplete orders offer no receipt. - A failed download shows a clear message and lets the customer try again. - The reviewer can find the output and verification evidence. #### Review and handoff - Contributor: a developer or connected agent chosen by the team. - Reviewer: the portal product owner checks the receipt fields; a second developer checks access and failure behavior. - Required approval or external action: review the change before deployment; deployment is a separate authorized step. - Handoff: link the code, test results and any unresolved check. Keep the work in review while a required check remains. View filled example Markdown source Markdown source — filled example# Customers can download a receipt Fictional example: Northstar customer portal. Names, work and results are illustrative. ## Outcome A signed-in customer can download a PDF receipt for their own completed order from the order page. ## Why this matters - Who needs the result: customers who need a record of payment. - Current problem: they ask Support to prepare a receipt. - Useful change: they can retrieve the same agreed payment information themselves. ## Scope - Included: one receipt download action on completed orders, using the approved receipt fields. - Outside this request: refund receipts, bulk downloads and email delivery. ## Context and sources - Current facts: the order page already identifies the signed-in customer and the order payment state. - Sources: the agreed receipt-format document and the order-page design, linked in the real work item. - Access check: the contributor and reviewer must open both current sources before starting. The example supplies no private links. ## Constraints and open questions - Constraints: use the existing access check and PDF approach; add no new dependency without approval. - Open questions: confirm the displayed payment-date timezone before implementing the PDF. - Dependencies: the reviewer must confirm the receipt fields and timezone first. ## Deliverables A reviewed code change, tests for download and access behavior, and a short verification note linked from the work item. ## Acceptance checks - [ ] A completed order shows a PDF download action; the PDF has the correct order number, payment date and paid amount. - [ ] A customer cannot download another customer's receipt; incomplete orders offer no receipt. - [ ] A failed download shows a clear message and lets the customer try again. - [ ] The reviewer can find the output and verification evidence. ## Review and handoff - Contributor: a developer or connected agent chosen by the team. - Reviewer: the portal product owner checks the receipt fields; a second developer checks access and failure behavior. - Required approval or external action: review the change before deployment; deployment is a separate authorized step. - Handoff: link the code, test results and any unresolved check. Keep the work in review while a required check remains. Check before you share ## A useful file. A result you can trust. - Replace placeholders and fictional facts. - Check that readers can open every source. - State what is verified and what remains unfinished. - Agree the next action and any required approval. ### Put the template to work. [Define clear work](https://tellenze.com/guides/define-clear-work)[Build an agent brief](https://tellenze.com/agent-brief-builder)[Follow a complete workflow](https://tellenze.com/examples/release-notes)[Use native work templates](https://tellenze.com/guides/work-templates) Another useful starting point ## Keep the next conversation clear. COME TAKE A LOOK ## A little less busy. A lot more together. Curious? Join the waitlist and see how we welcome your team. Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace. [Join waitlist](https://tellenze.com/waitlist)Start with your email. No payment needed to join.