Reviewed and updated: 21 July 2026.
A process exception is a case where the standard method could not or should not be followed. A short voice note can preserve the circumstances while work is still fresh, but the approved register must distinguish an authorised exception from an uncontrolled workaround, a process defect or a formal change.
Define the boundary before recording
State the process, step, case or location affected. Record only the information needed to explain the deviation. Avoid adding unrelated personal, customer or security details to a temporary voice note.
Use a complete exception record
| Field | Required content |
|---|---|
| Process reference | Procedure, workflow or control affected |
| Expected standard | What should normally happen |
| Actual variation | What happened instead |
| Reason | Evidence-supported cause or constraint |
| Immediate impact | Customer, safety, quality, cost or compliance effect |
| Control | Temporary safeguard applied |
| Authority | Person permitted to approve the variation |
| Duration | Expiry, review date or return-to-standard trigger |
Classify the exception correctly
- Customer-specific: a justified variation for one case.
- System failure: the normal route was unavailable.
- Safety response: immediate protection required a different action.
- Capacity constraint: resources prevented the standard step.
- Approved experiment: a controlled trial with defined measures.
- Policy gap: the standard did not address the situation.
An issue already causing harm may also need an issue record. A permanent process alteration needs formal change control rather than an endlessly renewed exception.
Verify authority and conditions
Repeat who approved the variation, what evidence they considered and any limits attached. An AI summary can easily turn “allowed for this case until Friday” into a general approval. The final register must preserve the exact boundary.
Analyse repeated workarounds
Review exceptions by process, team, reason and outcome. Repeated entries may show that the documented procedure is unrealistic, training is weak, a system is unreliable or staff are bypassing a necessary control. Frequency alone does not prove the standard should change; assess impact and evidence.
Close the exception deliberately
- Confirm whether the process returned to normal.
- Verify that temporary controls were removed or replaced.
- Record any customer or operational follow-up.
- Link an approved change, issue or risk where required.
- Document the closure owner and evidence.
How NERALVO Halo fits
NERALVO Halo can capture short, structured exception notes while staff are mobile. DOWAY can draft a transcript or summary, but the checked record should be transferred into the controlled process register.
Bottom line
A good exception register reveals where work differs from design while preventing temporary deviations from becoming invisible permanent practice.
Ready to capture meetings properly?
View the NERALVO Halo AI voice recorder with 64GB local storage, meeting capture, compatible phone-call recording workflows and one year of DOWAY Max included.
View NERALVO Halo