Review policy exceptions

Use Inbox → Exceptions to review requests for a limited departure from policy. A recorded violation describes a policy result; an exception request asks for a decision. The list includes requests awaiting a decision and approved exceptions that need further review.

Work the list

1. Choose Open to focus on work that still needs a decision.
2. Filter by urgency, application, or item type when you need a smaller list.
3. Group by application or rule to review related requests together.
4. Open an item in the side panel and inspect its policy and session evidence.
5. Record the decision and explain why it is appropriate.

Use Closed to review approved, denied, expired, and revoked exceptions without adding them back to the open queue.

Choose an available decision

• Approve a pending request only when its scope, duration, and evidence support the exception.
• Deny a pending request when it should not be granted. Enter the required decision note.
• Extend an approved exception when its review is due and the panel offers that action. Set the new expiry and review the evidence again.

An approaching expiry does not by itself make every action available. The panel shows actions permitted for the exception’s current state and your access. Approving an exception is not confirmation that an application executed an action.

Write a useful decision note

State what you decided and the evidence that supported it. Keep the note short enough to scan, but specific enough that a future reviewer does not have to rebuild the context.

For example:

Approve the exception for the claims application through the requested expiry. The attached sample supports the limited scope. The application owner will review results before renewal.

Use the actual application, evidence, and owner from the request. A note explains the decision; it does not change the saved scope or expiry.