For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Revise a policy without overwriting its live content, then take the new version through the configured approval workflow.
Before you start
Confirm the policy, its current live version, the agreed change and who may approve publication. Have the approved source document or wording available. A policy can have one draft in progress at a time.
Prepare the revision
- Open the policy and its Policy Contents area. Check the version selector and the Live marker.
- Select New Version. If Draft Already in Progress appears, use Open Existing Draft and coordinate with its author.
- For a new draft, choose Minor or Major deliberately, set the effective date, describe the change and review Requires attestation. Select Create Version.
- Check which content source the draft uses. For document content, use Version Document to upload the approved replacement and complete its content-ingestion review. For editable text, select Edit and make the change.
- Wait for the content save to complete. Reopen the draft and confirm the latest wording. A failed save must be resolved before changing versions or using workflow actions.
- Open Changelog. Compare the deterministic difference with the previous version and check that the author summary accurately explains the change. An AI summary is not the authoritative comparison.
Review and publish
Use the draft's Content Approval workflow. The available transitions depend on your organisation's workflow and your role; do not expect a universal Publish button.
The reviewer should inspect the exact version, its source and changed obligations. Respond to requested corrections in an editable draft. Under-review, approved and published versions are locked against ordinary content editing.
After the authorised publication transition, reload and confirm which version is live. Check the effective date and any resulting attestation work separately.
Check it worked
Read the live version as an intended reader, not just as the author. Confirm the prior version remains in history and that any version-specific analysis still refers to the version actually reviewed.
If something goes wrong
| Problem | Next action |
|---|---|
| Edit is unavailable | Check the version state; create or reopen a draft rather than changing live content |
| Publication is blocked | Read the workflow/content readiness reason and resolve that prerequisite |
| A draft is no longer needed | Ask an Organisation Administrator to review the discard action; do not discard another author's work |
| A published error is found | Prepare a corrective version and coordinate any necessary reader communication |
Human judgement matters
A minor version label is not evidence that the change is unimportant. Choose versioning and attestation requirements according to the effect on readers.
What next?
For the wider context, see Manage policies, controls and frameworks.
Run the policy check-in task where a new acknowledgement is required, and keep approval and publication distinct from reader completion.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message, not confidential evidence or session details.