These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Document Management System
- Process
- Revision and review
Revision and review
A review begins with a controlled parent document. The Document Controller identifies the organization, category and owner, then records the incoming version under that parent. The source reference matters: a reviewer must inspect the item that the decision will name.
Step by step
-
Draft document Document Controller
The controller registers the document and confirms the owner and classification.
- Establish identity, category and owner
- Updates Documents, Document categories
-
Record version Document Controller
The controller links the candidate version and source ID to the parent.
- Link the source item to its parent
- Updates Document versions, Documents
-
Validate revision Document Controller
The controller checks the selected revision; the upload operation records its run and step trace and marks the document reviewed.
- Trace the check and reviewed state
- Updates Operation runs, Operation steps, State history
-
Review revision Document Reviewer
The independent reviewer records a decision and reason against the source revision.
- Preserve decision, reviewer and evidence
- Updates Review decisions, Evidence documents
ApprovalA person approves before the work moves on. -
Resolve review return Document Controller
The controller uses a returned reason to prepare a correction and another review.
- Keep the reason and prepare a successor
- Updates Document versions, Review decisions
Who does what
Roles and permissions- Document Controller
- Prepares; Document Reviewer decides; Publishing Manager checks the approved revision before publication.
Set up Document Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.