|

Policy & Document Management guide

Review and version documents

Initiate scheduled or manual reviews, classify changes as major or minor and preserve a complete version history.

Document Owner, Policy Manager or Approver Approximately 10–20 minutes Updated 9 September 2026

Start a review

PurpleWASP calculates the next review date from the organisation's configured review period and can send reminders before the document becomes due. An owner can also begin a review at any time.

1

Open the published document

Select the document and choose Review.

2

Make the required changes

Edit content, record the approver and describe what changed and why.

The review workflow captures the revised content, change description, approver and change scope.

Choose the version impact

Minor changeUse for limited changes that do not materially alter purpose or requirements. Version 1.0 becomes 1.1.
Major changeUse for material changes to scope, obligations or intent. Version 1.0 becomes 2.0.

Submit the review for approval. The approver sees the document marked as a review and can approve, reject or request changes.

Republish the approved revision

After approval, publish the new version using the standard audience and date workflow. The revised version replaces the active content while previous versions remain available in history.

Understand version history

Version history records the document version, author, approver, dates and reason for the change.

The history preserves the recorded version, author, approval and change context so reviewers can understand how the document evolved.

Common problems

The next review date is unexpected

Ask an administrator to verify the configured document review period and reminder intervals.

A small wording change created a major version

Review the change scope selected during submission. The major or minor choice determines the automatic version increment.