Published

After an acquisition, a procurement department has twenty-four signed agreements awaiting registration in its governed records system. An internal policy requires registration within two working days. The authorised owner approves a temporary exception for that identified backlog. Near the end date, six agreements are still outstanding. Does moving the date forward preserve the same permission?
A policy exception should end under the terms of its approval, with any continuation requiring an authorised decision. Set the scope, end date, temporary controls and review conditions when approving it. Keep the expiry of permission separate from verification that the underlying work is finished.
Identify the requirement that cannot be met, why the departure is needed and which records, team or activity it covers. Confirm that the named authority can approve that departure. If the policy already permits an alternative route, use and record that route rather than calling every variation an exception.
Choose the duration from the stated need, remaining exposure and credible plan to remove the exception. Record the temporary controls and who will check them. Agree what happens at the end date and which events require an earlier review or stop. An unfinished task does not by itself extend the approval.
Identify the requirement, affected scope, owner, controls and limit of the approval.
Inspect current evidence before expiry and whenever an agreed review condition occurs.
Record the authorised outcome and keep unresolved work assigned.
| Event | Decision needed | Evidence to retain |
|---|---|---|
| The approved end date arrives | End reliance under those terms unless a further approval is already in force. Keep unfinished work visible. | Original approval, expiry, current position and any separately authorised continuation. |
| The policy, scope or responsible owner changes | Reassess the exception under its agreed change rules. Confirm what remains permitted and who is accountable. | Changed facts, affected requirement and the decision to continue, amend or end the exception. |
| A required temporary control fails | Follow the approved stop or escalation rule and obtain the authority needed for further handling. | Failed check, affected scope, immediate action, owner and subsequent decision. |
| The work removing the exception is complete | Verify the result and approve closure, including any remaining action. | Completion evidence, verification result and the recorded closure decision. |
These events have different effects. A new policy version may remove the original issue, leave it unchanged or introduce a different requirement. A change in owner needs a confirmed handover. State whether an event ends permission immediately or calls for reassessment; do not rely on an ambiguous “expires on change” label.
Before considering more time, inspect the current requirement, remaining work, temporary-control results and reasons the original plan was not completed. Consider whether the scope can be reduced or the normal process can now be used. The authority needed for a repeated or changed exception may differ under the organisation's procedure.
Retain the earlier decision and create a linked renewal or amendment with its own approver, terms and effective period. Show a requested extension as awaiting a decision until it is accepted. If approval is absent at expiry, route the affected work through the agreed handling process rather than quietly treating the request as permission.
Repeated renewals also give the policy owner useful evidence. The operating process, capacity or requirement may need a separate review. Revising the general policy remains a controlled change; it should not happen through an indefinitely extended exception.
In this fictional process, the exception covers twenty-four previously signed supplier agreements for one procurement department, for ten working days. New agreements must follow the normal registration rule. The approved temporary controls require retained originals in the authorised repository, an outstanding-item list and an owned daily progress check. These durations and controls are example terms, not universal requirements.
The owner records the applicable policy version and registration requirement, the twenty-four agreements, the reason, end date and temporary controls. Other departments and new agreements remain outside that approval.
The review finds eighteen agreements registered and six outstanding. It retains the registration evidence, checks the temporary controls and records why those six remain. A progress percentage alone does not settle whether more time should be allowed.
The department proposes a shorter continuation for the six named agreements, with a revised completion plan. The reviewer assesses current facts and the applicable policy. The earlier twenty-four-item approval remains in the history; the extension is still a request.
If approved before the original permission ends, the new decision states its six-item scope, controls and end date. If it is refused or still undecided, the team follows the agreed handling route at expiry and escalates the unfinished work. It does not assume the requested date is effective.
The owner supplies evidence that the remaining agreements are registered. The authorised reviewer checks it and records closure. The original approval, any later decision and actual completion evidence remain connected to the policy and affected records.
A reminder helps the owner act; it does not renew the exception. An expired approval can still have unresolved work, and a completed task still needs the agreed verification. The reminder and notification guide explains why delivery and business completion need their own evidence.
Give the exception and affected records the intended access controls. Reviewers may span departments or business processes; customer tenants can add another boundary. A policy audience does not automatically need access to every exception's sensitive supporting documents.
For decisions requiring a committee, the board-pack example connects a time-limited acceptance to its issued paper, conditions and later test. The policy-management guide covers the wider released-policy lifecycle.
An exception needs a defined limit and an accountable path beyond it. Agree what ends permission, what prompts review and what evidence can support closure or a further approval. Retain the original terms so staff can explain both the temporary departure and what happened afterwards.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.