An approval request should stop authorising new execution after its defined expiry. Resolve approval and timeout races in trusted state so a late click cannot unexpectedly activate stale work.
Expiry is a decision-state transition
Approval expiry closes the window for a person to authorise a specific proposal. It is distinct from a deadline for already authorised execution. The business must define what happens if approval arrives just before expiry but work starts later.
For a proposed state model, use pending, approved, denied, expired, and cancelled decisions with explicit timestamps and revision binding. Apply one atomic transition from pending so approval and expiry cannot both win independently.
Use a trusted time source and store the expiry instant unambiguously. Display the reviewer’s local representation clearly without allowing browser time or a language model’s interpretation to control the boundary.
Reproduce a fictional late approval
A manager receives a proposal to release a temporarily held appointment slot. The request expires at 15:00. The manager clicks at 15:01 after the hold has already been released. The system should show the expired status and require a fresh proposal rather than execute the old action.
A boundary fixture submits approval and expiry simultaneously. The final stored decision must be singular and explainable. If approval wins under the defined policy, execution still checks the current resource and permitted start deadline.
| Timed fixture | Expected result |
|---|---|
| Valid approval before expiry | Current proposal enters approved state |
| Approval after expiry | No new authorisation |
| Simultaneous timeout and click | One atomic terminal decision |
| Proposal edited during waiting | Prior request invalidated |
| Repeated approval callback | Same disposition, no duplicate effect |
Use a simulated clock for deterministic tests. Waiting through real deadlines makes the race difficult to reproduce and slows the suite without improving the assertion.
Expired does not mean all work vanished
A proposal may have preparatory reservations or notifications. Define their cleanup and ownership. If an external action already began under a valid approval, expiry alone may not cancel it; reconcile through the execution state.
Expiry protects against stale permission but can frustrate reviewers when deadlines are too short. Choose durations from actual operational needs and provide a clear renewal path. Do not silently extend the same approval whenever an agent asks for more time.
This timed workflow is proposed. The voice integration case study describes relevant backend work without claiming this approval controller. Pair it with external approval queues.
Approval expiry FAQ
Should a late click create a new approval automatically?
No. A fresh proposal should reflect current facts and receive the required decision.
Does expiry cancel an external effect already running?
Not necessarily. Decision state and execution state need separate handling.
What should the reviewer see?
The current decision, expiry meaning, affected proposal revision, and supported way to request renewed review.