Write exception branches
See this course’s project requirements
A versioned equipment-loan procedure, matching checklist, and walkthrough test log that a beginner can follow.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A one-paragraph scope with reader, trigger, allowed endings, and evidence.
- A five-step normal-path procedure and sample confirmation.
- A three-row exception table with return points and owners.
- A five-item checklist with evidence fields and a recorded correction.
- A two-case test log with one defect, an edit, and retest evidence.
- A versioned final procedure packet with change and review records.
Review and revise
Use these criteria to check your work and choose what to improve.
- Every required section is present and traceable to the supplied case facts.
- Decisions separate known facts, assumptions, and unresolved questions.
- Records, calculations, and instructions agree with each other and the stated rules.
- The final revision addresses a changed case and explains what someone should do next.
Want more background?
The idea in everyday life
Fictional date-counting rule: duration equals return date minus pickup date, using elapsed calendar days. June 3 to June 8 is 5 days; June 3 to June 10 is 7 days and passes the duration limit; June 3 to June 11 is 8 days and goes to Lee. Policy: missing fields go to requester clarification, excessive quantity/duration goes to Lee, insufficient availability goes to Lee. No reservation is created until all checks pass. R3 lacks a return date. R4 has all fields but quantity 4. R5 requests 2 stands when only 1 is free. Pending requests are rechecked from the first check after new information arrives.
An exception needs a condition, an action, and a return point.
Write exception branches — guided practice
Make missing information and supervisor decisions explicit.
Fictional date-counting rule: duration equals return date minus pickup date, using elapsed calendar days. June 3 to June 8 is 5 days; June 3 to June 10 is 7 days and passes the duration limit; June 3 to June 11 is 8 days and goes to Lee. Use a text editor, a free document editor, or paper. Start from the following fictional records; they reset this lesson even if your earlier answer differed. Policy: missing fields go to requester clarification, excessive quantity/duration goes to Lee, insufficient availability goes to Lee. No reservation is created until all checks pass. R3 lacks a return date. R4 has all fields but quantity 4. R5 requests 2 stands when only 1 is free. Pending requests are rechecked from the first check after new information arrives.
1. Separate exception types
Create a row for missing data, policy excess and unavailable stock.
You should see: Three distinct conditions, with one specified next action each.
Different reasons need different decision-makers.
2. Write the missing-data branch
State what Jo records and asks about R3.
You should see: Pending—return date missing; requester owns reply; no reservation.
A focused clarification is easier to answer than a vague rejection.
3. Write supervisor branches
Send R4 and R5 to Lee with the relevant numbers.
You should see: R4: 4 requested versus maximum 3. R5: 2 requested versus 1 available.
Evidence lets the authorized owner decide without reconstructing the case.
4. Define re-entry
Specify where an updated request returns to the procedure.
You should see: Restart at field check after a correction or authorized revised request.
Changed dates or quantities can invalidate earlier checks.
What to finish
A three-row exception table with return points and owners.
Watch for this
Using an “otherwise approve” branch that bypasses availability or authority.
How can I tell I understand it?
Check your result against the worked example, then explain the changed case without using an unstated assumption.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
7 Steps to Write Standard Operating Procedures that ACTUALLY Work
From Layla at ProcessDriven. Watch here or open it on YouTube .
Optional course overview. Follow the written steps below at your own pace.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-12
Inspected sections 2 and 4.2 on preparation, testing, document control and administrative procedures. April 2007 methodological guidance, not a current compliance standard.
Access: Public page inspected without an account.
Reuse: Reference link only. Course prose and practice data are original; no third-party text, figures, or templates are reproduced.
Source & access notes · checked 2026-09-12
Inspected audience, writing, design and testing guidance overview.
Access: Public page inspected without an account.
Reuse: Reference link only. Course prose and practice data are original; no third-party text, figures, or templates are reproduced.
Source & access notes · checked 2026-09-12
Inspected instructions on numbered steps, conditions, optional actions and visible results.
Access: Public page inspected without an account.
Reuse: Reference link only. Google guide has its own content license; original examples and prose are used here.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.