Give the brief a clear progression.
Organize the document so a reader can move from the business problem to the workflow, its controls and the evidence needed to accept it.
1. Business objective
Explain the current problem, who it affects and why it is worth solving. State the desired improvement and any measured baseline. Keep proposed technology separate from the outcome.
2. Current workflow and examples
Describe the trigger, the steps people take and the final handoff. Include a representative input, an acceptable output and at least one exception. Identify the systems and records involved.
3. Proposed responsibility
Define what the automated workflow should prepare or perform. Specify which decisions remain with people and what authority each role has. Identify the owner of day-to-day operation.
4. Context and integrations
List required information sources, business definitions and permissions. For each integration, identify the system of record, the direction of the handoff and the team responsible for access. Mark version or licensing questions that still need investigation.
5. Review and recovery
Explain how a reviewer accepts or rejects a result. Define what happens when input is missing, a tool fails or a request is repeated. State how an operator can identify the affected job and resume safely.
6. Acceptance and delivery
Describe observable acceptance criteria, representative evaluation cases and the people who sign off. Include the documentation, training, source access and operational handoff required for the engagement.
Keep decisions traceable. When scope changes, record what changed, who agreed and which acceptance criteria are affected.
What are you
working on?
Looking for a course, help with a difficult problem, or someone to build a solution? Tell us where you are and what you'd like to do next.