Releasing a control plan revision
How control plan revisions are released and superseded, why only released revisions drive capture, and where the revision history lives.
Only a released control plan revision drives capture. Inspectors can never measure against a draft or a superseded snapshot, which is what makes every inspection record defensible: it names the exact released revision it was judged against. Releasing happens in the Plan area under VoraControl at /control/plan.
How a revision becomes released
In the app, generating a plan from the Plan library produces a released revision in one step: the new revision is created from the current source data, marked released, and the previously released revision is superseded at the same moment. There is never more than one released revision per plan, so Capture always has a single unambiguous plan to measure against.
What happens to the old revision
Superseding does not delete anything. Every revision, with its release note, effective date and recorded changes, stays in the plan History at /control/plan/history. Captures recorded against an older revision keep their snapshot of that revision, so historical measurements still read exactly as they were judged at the time.
After release
Once a revision is released it appears in the Capture plan picker, the printable export reflects it, and the signed approval document can be attached to it from the Plan library. If the approval is still outstanding, the library row offers Upload approval until the document is on file.
Releasing a control plan revision requires plan release access within the organization and site the plan belongs to. A user without that permission in the plan scope cannot release, regardless of their access elsewhere. Ask your administrator if a release you expect to make is refused.
Still stuck? Get support or contact the team. Support replies personally, typically within one business day.