Design Pattern · September 2026
Work Unit record
Describe one piece of work by its purpose, evidence, authority, risk, handoffs, and accepted outcome.
Under the pillar Labor as Code™
Inputs
Observed cases, source records, policies, staff accounts, exceptions, and outcome measures.
Method
Write the purpose, trigger, inputs, source priority, decisions, actions, outputs, authority, risks, dependencies, handoffs, timing, failure modes, rights, and acceptance test.
Output
A versioned record another person can inspect and test.
Boundary
A description of intended process is not evidence of actual work.
Stop
Stop when the unit is too broad to observe or too narrow to own a meaningful result.
Put this to work
Work Unit record application record
Apply Work Unit record to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A work unit record application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
Do not infer that a task can move merely because it can be described.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.