Document Revision History
Cornell’s document-control policy defines version control as tracking document versions, including revision history, modification dates and approval status, and requires changes to be documented. A revision history is therefore a governance/audit tool, not merely decorative front matter.
A document revision history records controlled changes across versions—typically enough information to identify the version, modification/revision date and what changed. Exact fields and numbering follow the organization’s document-control policy.
Key details
Important caveats
Scope Boundary
["Version numbering and approval rules are organization-specific; do not impose one numbering scheme as a universal standard."]
Further guidance
Fields
["Record the fields required by the governing process, commonly version/revision identifier, date and a concise change description; owner/approval fields may also be required."]
Practical Application
Use a revision history when readers or controllers need to trace approved changes across document versions. Record only the fields your document-control policy requires—commonly version, date, change summary, and responsible person or approval reference.
Purpose
["Use a revision history when readers or maintainers need an auditable record of document changes across controlled versions."]
Reader Check
Can a reader identify which version changed, when it changed, and what materially changed without reading every prior copy?
Worked Example
A compact row such as “v2.1 | 28 Sep 2026 | Clarified return procedure | KM” works when those are the organization’s required fields; add approval/status columns only if policy calls for them.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Document Development, Review, and Control Policy — Cornell Research Services (opens in a new tab)Cornell University Research Services · Institutional document-control policy covering version control, modification dates, approval status and revision history