Canonical page: https://tellenze.com/work-templates/stakeholder-review [All templates](https://tellenze.com/work-templates) A free writing template # Stakeholder review Show the result, evidence and next decision in a review someone can use. Use it when you need to share a work update with selected readers or ask for a concrete decision. [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. [Review and share results](https://tellenze.com/guides/review-and-share-results) - 01 Choose the readers and the question the review should answer. Check access to every linked source. - 02 Lead with the actual state of the outcome. Separate verified results from expectations and unfinished checks. - 03 Show the deliverable and evidence, then explain meaningful limits, blockers and decisions needed. - 04 Review the content and recipients before sharing. A Markdown file does not grant access to its sources. 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/stakeholder-review/download?version=blank) Use the preview below, then copy the text or download a .md file. ### Review: [outcome or work] #### Readers and purpose - Intended readers: [people or group agreed for this review] - Purpose: [inform, review a result or decide a next step] - Work covered: [period or scope, with work links] #### Outcome and current state - Intended outcome: [what should change] - Current state: [what is complete, in review or unfinished] - Main result: [what the evidence actually supports] #### Deliverables and evidence - Output: [link or file location and useful explanation] - Checks performed: [test, review or observation and its result] - Limits: [what was not checked or remains uncertain] - Source access: [confirm the selected readers can open each link] #### Decisions and next actions - Decision needed: [specific question, or write none] - Decision maker: [agree who can decide] - Next action: [what happens next, who agreed to do it and the work link] - Blocker or dependency: [cause and exact next step, or write none] #### Before sharing - Facts and links are current. - Unfinished checks and limits remain visible. - The readers and source access were reviewed. - Sharing or publishing is explicitly authorized where required. View blank template Markdown source Markdown source — blank template# Review: [outcome or work] ## Readers and purpose - Intended readers: [people or group agreed for this review] - Purpose: [inform, review a result or decide a next step] - Work covered: [period or scope, with work links] ## Outcome and current state - Intended outcome: [what should change] - Current state: [what is complete, in review or unfinished] - Main result: [what the evidence actually supports] ## Deliverables and evidence - Output: [link or file location and useful explanation] - Checks performed: [test, review or observation and its result] - Limits: [what was not checked or remains uncertain] - Source access: [confirm the selected readers can open each link] ## Decisions and next actions - Decision needed: [specific question, or write none] - Decision maker: [agree who can decide] - Next action: [what happens next, who agreed to do it and the work link] - Blocker or dependency: [cause and exact next step, or write none] ## Before sharing - [ ] Facts and links are current. - [ ] Unfinished checks and limits remain visible. - [ ] The readers and source access were reviewed. - [ ] Sharing or publishing is explicitly authorized where required. 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/stakeholder-review/download?version=example) Use the preview below, then copy the text or download a .md file. ### Review: receipt download ready for review Fictional example: Northstar customer portal. This is an illustrative review, not a claim about a shipped customer feature. #### Readers and purpose - Intended readers: the portal product owner, developer and reviewer. - Purpose: inspect the proposed receipt download and decide whether it is ready for the next authorized step. - Work covered: the first receipt-download change; link the actual work item in a real review. #### Outcome and current state - Intended outcome: a customer can download a PDF receipt for their own completed order. - Current state: prepared for review; deployment remains outside this review. - Main result: the fictional contributor has prepared the download, a sample PDF and verification evidence. A real review must link those outputs before making this statement. #### Deliverables and evidence - Output: the reviewed code proposal and a sample receipt; insert actual accessible links. - Checks performed: in the real work, record results for a completed order, another customer's order, an incomplete order and a failed download with retry. - Limits: production behavior has not been verified in this example. Refund receipts, bulk downloads and email delivery are outside the scope. - Source access: check that all selected readers can open the brief, output and test evidence. #### Decisions and next actions - Decision needed: does the PDF match the agreed fields and timezone, and is the implementation acceptable? - Decision maker: the product owner confirms the output; the developer reviewer checks the change. - Next action: finish review and record its result in the work item. Any deployment needs its own authorization and verification. - Blocker or dependency: keep the item in review while any required check remains unresolved. #### Before sharing - Replace example references with current facts and real output links. - Show any missing or failed check without describing it as passed. - Confirm the readers can open the sources. - Confirm sharing is authorized; this file grants no workspace access. View filled example Markdown source Markdown source — filled example# Review: receipt download ready for review Fictional example: Northstar customer portal. This is an illustrative review, not a claim about a shipped customer feature. ## Readers and purpose - Intended readers: the portal product owner, developer and reviewer. - Purpose: inspect the proposed receipt download and decide whether it is ready for the next authorized step. - Work covered: the first receipt-download change; link the actual work item in a real review. ## Outcome and current state - Intended outcome: a customer can download a PDF receipt for their own completed order. - Current state: prepared for review; deployment remains outside this review. - Main result: the fictional contributor has prepared the download, a sample PDF and verification evidence. A real review must link those outputs before making this statement. ## Deliverables and evidence - Output: the reviewed code proposal and a sample receipt; insert actual accessible links. - Checks performed: in the real work, record results for a completed order, another customer's order, an incomplete order and a failed download with retry. - Limits: production behavior has not been verified in this example. Refund receipts, bulk downloads and email delivery are outside the scope. - Source access: check that all selected readers can open the brief, output and test evidence. ## Decisions and next actions - Decision needed: does the PDF match the agreed fields and timezone, and is the implementation acceptable? - Decision maker: the product owner confirms the output; the developer reviewer checks the change. - Next action: finish review and record its result in the work item. Any deployment needs its own authorization and verification. - Blocker or dependency: keep the item in review while any required check remains unresolved. ## Before sharing - [ ] Replace example references with current facts and real output links. - [ ] Show any missing or failed check without describing it as passed. - [ ] Confirm the readers can open the sources. - [ ] Confirm sharing is authorized; this file grants no workspace access. 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. [Review and share results](https://tellenze.com/guides/review-and-share-results)[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.