document-a-process-exception

name	document-a-process-exception
category	start
description	Document a process exception with scope, reason, authority, risk, compensating controls, duration, review, and closure. Use when an approved rule cannot be followed for a bounded case.

document-a-process-exception

An exception is temporary and explicit, not a silent alternate process.

When to use

• Use for urgent, unusual, inaccessible, technically blocked, or transition cases.
• Do not use an exception to bypass legal, safety, consent, or authority requirements that cannot be waived.

Procedure

1. Identify the rule, process version, requestor, affected cases, dates, and business reason.
2. Explain why the normal path cannot work and which alternatives were considered.
3. Assess operational, financial, security, privacy, safety, legal, and fairness risks.
4. Define the minimum exception scope and compensating controls.
5. Obtain the authorized approver and any independent specialist approval.
6. Set start, expiry, review, monitoring, evidence, rollback, and owner.
7. Close, renew, or convert through a new decision; verify temporary access and controls are removed.

Done

• An exception record documents rule, scope, reason, risks, controls, approvals, owner, dates, monitoring, and closure
• Authority, minimum-scope, expiry, compensating-control, monitoring, removal, and recurrence checks verify bounded use