design-a-document-review-workflow

# design-a-document-review-workflow Review the exact version and purpose assigned to each reviewer. ## When to use - Use for policies, contracts, reports, filings, specifications, publications, or executive materials. - Do not give reviewers broader sensitive access than their role requires. ## Procedure 1. Define document type, owner, audience, risk, sensitivity, deadline, publication route, and authoritative repository. 2. Assign author, evidence owner, subject reviewers, legal or privacy, accessibility, copy, approver, publisher, and backup roles. 3. Set stages, entry criteria, review scope, response time, sequence, quorum, and decision rights. 4. Use one controlled master with immutable versions, comment identity, timestamps, and comparison. 5. Classify comments as factual, required, risk, editorial, question, preference, or out of scope. 6. Route conflicts to accountable adjudication and preserve material dissent. 7. Bind approval to exact content, attachments, and evidence; material change reopens required review. 8. Verify final files, links, accessibility, signatures, metadata, publication, archive, and access removal. ## Done - A document review workflow and log record versions, roles, stages, comments, evidence, conflicts, approvals, deadlines, and publication - Access, version, scope, comment-resolution, dissent, approval-binding, accessibility, link, archive, and publication checks verify control