A business-rule change after approval can alter whether the action remains permitted. Record the rule version used for the decision and define whether execution must re-evaluate current policy before committing.
Approval does not freeze every rule
A post-approval rule audit checks which policy justified a proposal, which version the reviewer saw, and which rules governed execution. Historical evidence and current authority can have different roles.
For a proposed design, link the proposal to relevant policy identifiers and versions. Record effective times, owner, and decision categories. At execution, enforce the actual business rule for revalidation, grandfathering, or renewed approval.
Do not assume that preserving the old policy automatically permits execution under it. Conversely, do not silently rewrite the historical audit to say the reviewer approved under a rule that did not yet exist.
Test a fictional cancellation-policy change
A manager approves cancelling an appointment under the policy current on Friday. Before the worker executes on Monday, the business changes a consequential condition. The business must define whether the earlier authorisation remains valid or needs review.
The workflow should expose that choice and retain both the approval context and execution policy. If current policy prohibits the action, the application must not bypass the rule because a stale approval event arrives.
| Policy transition | Evidence and action |
|---|---|
| Unchanged rule | Normal current execution checks |
| Material condition changed | Apply defined revalidation policy |
| Explicit authorised exception | Record scope and responsible authority |
| Unknown rule version | Safe unresolved state |
| Historical replay | Preserve original decision meaning and current effect rules |
Use a simulated timeline with changes just before approval, just after approval, and immediately before execution. Assert both audit history and actual business effect.
Keep policy ownership distinct from implementation
A developer can deploy an expression without authority to redefine the business rule. Changes should have an approved meaning and traceable implementation. Reviewers need a concise explanation of material differences, not only a configuration hash.
Versioning adds maintenance and can create too much ceremony for trivial presentation changes. Focus on rules that change eligibility, authority, commitments, consequences, or staff action. Keep the audit minimal but sufficient to reconstruct those decisions.
This policy-audit design is proposed. The voice integration case study describes related backend work without claiming this approval system. Pair it with business-rule versioning.
Post-approval rule FAQ
Does approval always preserve the old rule indefinitely?
No. The business must define execution and exception semantics explicitly.
Should old audit entries be updated to the new policy?
Preserve historical truth and link any later re-evaluation rather than rewriting the original decision.
What should staff see when a rule changes?
Show the material difference, current action status, required review, and accountable policy owner.