New reusable worksheet draft • Birkan episode planning pack
Episode segment: 11:30–16:00
Purpose: Find the transition that needs explanation.
This worksheet starts empty. It contains no Birkan records or verified outcomes. Use actual approved records or clearly labelled demonstration data. It is not claimed to be an installed OpenAnalyst product template.
Fill in
- Order / process scope: fill in; keep unknown when unavailable
- Stage and accountable role: fill in; keep unknown when unavailable
- Input and entry condition: fill in; keep unknown when unavailable
- Work performed: fill in; keep unknown when unavailable
- Exit / acceptance condition: fill in; keep unknown when unavailable
- Next stage and receiving role: fill in; keep unknown when unavailable
- Record or event that proves handoff: fill in; keep unknown when unavailable
- Expected timestamp / time limit: fill in; keep unknown when unavailable
- Observed timestamp and source: fill in; keep unknown when unavailable
- Gap or disagreement: fill in; keep unknown when unavailable
- What the team confirms: fill in; keep unknown when unavailable
- Unresolved question and next check: fill in; keep unknown when unavailable
Fit into the existing workflow
- Existing routine and tool: describe where people already do this work
- Trigger to investigate: A recorded production, quality, or dispatch event enters the selected workflow. Record the actual demonstrated mode.
- Repeated manual effort before: lookups, copying, checking, chasing, or preparation
- AI task to investigate: Check handoff evidence and prepare the supported exception output. Confirm the actual supported behavior.
- Person and decision: who reviews, decides, or continues the task
- Working destination: The receiving role’s actual queue, record, or review location. Record the actual destination.
- What changes for the team: new habit, training, ownership, or data-entry requirement
- Completion evidence: source-backed result, accepted record, or execution receipt
- Next run and exception handling: how it repeats; who responds when it fails
State whether the captured example is manually started assistance, a saved repeatable procedure, scheduled automation, or event-triggered automation. Show its actual behavior and do not infer background execution from a generated answer.
Question to adapt
Map this order across the supplied production, quality, and dispatch events. Identify the first handoff that cannot be evidenced. Show expected and actual evidence, responsible roles, and unresolved questions. Do not infer that an unrecorded event never occurred.
Check the result
The physical workflow and record trail should be checked with the people responsible for both sides of a handoff.
Show on camera
Follow one task from its existing input through the AI step, the person’s decision, and the working destination. Explain what changed from the previous routine and show what proves completion.