The Precedent handbook
Record an exception
An exception is a time-boxed departure from a standard, policy or decision. It names what it waives, why, what makes the risk acceptable meanwhile, and the date it ends.
Security and platform teams track exceptions so an auditor can see who waived which control, for whom, with what compensating controls, and until when. Precedent records them as decisions of the Exception Type, so they appear in the same lists, searches and assistant context as the standards they depart from.
What an exception needs
| Field | What to record |
|---|---|
| Exception (the title) | What is waived and for whom, in one sentence. In AR-118, Acme Robotics keeps raw inspection images for 30 days instead of the seven days AR-097 allows. |
| Summary | The scope of the waiver: which systems, teams or data it covers, and until when. |
| Rationale | The justification. Why the standard cannot be met here, and what meeting it would cost. |
| Compensating controls | What reduces the risk while the exception is open, and the risk accepted. |
| Departs-from link | A departs-from link to the standard, policy or decision being waived. The target decision lists the exception under Exceptions to this decision. |
| Expires on | The expiry. The exception stands through this date and shows as Expired from the next day. The editor offers a date only, because a review condition does not count. |
The Exception Type requires rationale, compensating controls, an expiry date and a departs-from link before it can be approved, and it always needs approval from someone other than its owner. A draft can be saved without any of them. The checklist names each missing item, in the editor, on the decision page and in the confirmBlockers an assistant receives.
Record one
- Choose New decision and pick Exception under Type. Write the waiver in the summary, the justification in the rationale and what reduces the risk in the compensating controls.
- Fill in the title, summary, rationale and compensating controls. Set Expires on to the day the exception ends. Choose an owner and the areas it applies in, then Save as draft.
- On the draft's Record tab, choose Add link, select departs from and enter the reference of the decision being waived.
- Attach evidence such as the risk assessment, then choose Ask for approval. See Approve decisions.
- The exception becomes Decided when someone other than its owner, the person who asked and the person who last changed it has approved, and every Area's rule is met.
An assistant can do the same with propose_decision, passing type: "exception", a reviewAt date and a departs_from link in links, or adding the link later with link_decisions. The owner asks for approval in the web app, or asks the assistant to do it with ask_for_approval and accepts the prompt their assistant's app shows. Another person approves it in the web app, from its post in Slack, or with approve_decision; the same rules apply either way.
What Expired means
On the day after its expiry date, a decided exception shows an Expired badge on its page, in list rows, in search results and in assistant responses: search_decisions and get_decision return expired: true with expiresAt, and get_area_context lists it under Expired rather than among current guidance. The decision it departs from applies again in full.
Expired is derived from the date; nothing is rewritten. The status stays Decided, the revisions and events stay as they were, and the record keeps showing why the exception was granted. An exception with a date in the future is open and waives its target.
| Where | What you see |
|---|---|
| Decision page | An Expired badge beside the status and a banner naming the date and the decisions that apply again. |
| Target decision | Exceptions to this decision, with open and expired counts, so a reader of a policy sees who is currently exempt. |
| Inbox | The review item reads Expired, with the date. Exceptions due to expire within 30 days appear under expiring soon. |
| Owner reminders | The owner gets a direct message or email 30 and 7 days before the expiry date, on the date, and the day it shows as Expired. Each one names the decision it departs from. |
| Weekly digest and Slack | Expired and expiring exceptions are grouped under their own headings. In an Area channel's review post 30 and 7 days before the date, each expiring exception is its own row, with its expiry date, and on the date its row reads Expires today. |
| Search, areas and impact map | An Expired badge on the row. |
Reaffirm, supersede or let it lapse
| Action | Use it when | Result |
|---|---|---|
| Reaffirm with a new date | The exception is still needed. | Say why it is still needed; the note is required. Once the reaffirmation is approved, the expiry moves to the new date. The revision history and event log record the move from the old date to the new one. The dialog asks for a new Expires on date only, because a condition is not accepted for an Exception. |
| Revise | The scope or compensating controls changed. | A new revision with a change note, in force once it is approved. A decided Exception keeps its date and its departs-from link. |
| Supersede | A different waiver replaces this one. | A successor of the same Type, which needs its own date, link and approvals before it is decided. |
| Reverse | The exception ends early. | Once the reversal is approved, the record stays, with Reversed status and the reason. |
| Do nothing | The exception has served its purpose. | It shows as Expired and the standard applies again. The record remains for the audit trail. |
Reaffirming, revising, reversing and archiving a decided exception are proposed changes. Each waits until every Area's rule is met and someone other than the exception's owner and the person who proposed it has approved, so the person who proposed it can never apply it alone. Until it is approved, the exception stays as it is, with its current expiry date. A draft that supersedes a decided exception, or stages a change to one, also needs approval from someone other than the draft's owner, the exception's owner, the person who asked and the person who last changed the draft.
Once a reaffirmation of an expired exception is approved, the badge clears from the next page load. The old date, the new date and who reaffirmed it stay in the Revisions and Event log tabs.