framework · cross business
One-page workflow brief
Write a one-page workflow brief covering the task, inputs, owner, permissions, baseline, success criteria, and stopping rule. Print it without an account.
On this page
Purpose
Use this brief to describe one task before choosing tools. A useful brief makes the desired result and the limits equally clear. It should help another person explain what will happen, what will remain manual, and who can stop the work.
When to use it
Fill it in before a first experiment, when a task changes, or when handing a process to someone else. If you cannot name the input owner or describe a correct result, record the gap. Do not conceal uncertainty with a guessed number.
Printable worksheet
The editable worksheet follows this guide. Fields stay in this page’s memory; refresh clears them. Use the browser’s Print or Save as PDF to keep a copy. No account or email is required. Avoid putting private records, passwords, or API keys into the worksheet.
Filled synthetic example
| Field | Example, not an observed business result |
|---|---|
| Task | Prepare support-email categories and draft replies for review. |
| Trigger | A new synthetic message in a dedicated test mailbox. |
| Inputs | Message ID, message text, approved sample FAQ with an owner and revision date. |
| Current steps | Read request, look up FAQ, draft response, review, send manually. |
| Volume | Unknown; owner will measure eligible messages before a pilot. |
| Owner | Assign a real owner and backup before building. |
| Desired output | A pending review row with category, FAQ reference, draft, and escalation reason. |
| Simpler alternative | A manual reply template or fixed category rules. |
| Permissions | Read test mail; write the test review sheet; no email sending. |
| Baseline | Measure handling and correction time for comparable requests. |
| Success criteria | Every duplicate fixture produces no additional row; unsupported requests escalate; a person approves draft quality. |
| Stopping rule | Stop on unexpected access, repeated duplicate writes, unsupported drafts, or an unreviewed backlog. |
Instructions
Start with the task, not a product name. Use a verb and an object: “prepare a review row” is more useful than “add AI to support.” Define what starts the task and what marks it complete.
Describe the inputs as fields and approved sources, rather than copying records. Name their owner and permission constraints. State which information the workflow must never access.
Write the current steps before proposing changes. A missing step often reveals work that would otherwise be forgotten, such as checking access or resolving conflicting information. Keep your first scope small enough to test with representative examples.
For baseline and volume, write “unknown” if you have not measured them. Describe how and over what period you will obtain the numbers. Success criteria should include wrong-result and failure behavior, not just an expected time saving.
Make the stopping rule actionable: who switches the workflow off, how they identify affected items, and how the task continues manually. A general intention to “monitor it” is not a stopping rule.
How to interpret the brief
Review it with the person who does the work. If they cannot recognize the task or agree on a correct result, revise it. If ordinary rules meet the need, that may be the best implementation. If permissions, review capacity, or recovery are unresolved, prepare those before connecting tools.
Use the readiness assessment as a second planning check. It does not certify that a workflow is safe or worthwhile.
Limitations
This is a planning artifact, not a security approval, vendor assessment, contract, or proof of return on investment. The example contains no measured results. A completed form does not replace execution tests or a decision by the actual process owner.
Sources and next step
This worksheet is an original editorial resource. Put the brief beside the support triage playbook and check that each proposed action stays inside the permissions you wrote down.
Your workflow brief
Fields stay in this page's memory. Refresh clears them. Print or save to PDF to keep a copy.
Change notes
Foundation draft prepared October 20, 2026. No public publication or successful live-tool test is claimed.
Next learning step: Triage support emails and draft replies for review