A proof belongs to a saved draft revision and its dependencies. Activation is a separate reviewer decision. Neither an authoring proposal nor a successful earlier proof is authority to change production.
Choose evidence before reading the result
For a policy change, prepare cases that establish the intended outcome independently. Include a normal permitted movement, a boundary quantity, an ineligible condition and any changed destination or allocation choice. Record the expected outcome from the business requirement rather than copying what the candidate produces.
For example, if a policy should send a particular family to an approved bin, check a matching material, a different family and a missing or unavailable destination. These are review ideas, not a ready-made policy: use the actual supported fields and valid site records.
Prove the saved draft
In Retained drafts, choose Open this draft, check the kind and revision, then Prove this exact draft. Review the proof and, for a policy, its current operational impact. Inspect affected demand and allocations rather than checking only a pass indicator.
A change to the draft, active dependency or operational facts can make the proof stale. Reopen current information, rerun proof and review the new result. Do not treat an identifier retained from yesterday as current evidence.
Activate with the correct person
A reviewer enters Reason for release and chooses Activate this proved release with recent Accounts verification. Where distinct review is required, the last editor must hand over to another reviewer. Where self-review is permitted, the warning and recorded self-review remain part of the release evidence.
The activation checks the exact content, proof, dependencies and impact again. Refusal leaves the proposed change unactivated. Investigate the stated reason, especially stale evidence, identity compatibility or changed allocation impact.
Check additional Automation reviews
When a draft or the policy workflow is enrolled in SmartFACT Automation, its separately retained example set must have current independent approval. A candidate and proof are tied to that exact set. Release submission and approval are additional requirements, and the person activating cannot be one of the recorded contributors. The local self-review setting does not waive these controls. Follow the linked Automation handbook and resolve its specific review refusal before trying native activation again.
Roll back deliberately
Prepare the selected retained release as a rollback copy and state the reason. Its content cannot be edited. Prove it against current conditions and obtain reviewer activation as for a new release. A rollback is not erasure: historical movements retain the releases used at the time, and the rollback source remains recorded.
After activation, tell the supervisor which operational decision changed and which items need attention. Do not imply that releasing a policy moves stock or corrects an earlier physical recording.