Practical checklist
What this article covers
A sheet register comparison procedure covering numbers, names, included/excluded sheets and issue status.
Check a Revit sheet index against both the agreed issue scope and the actual delivered package. A row in an index, a sheet in the model and a page in a PDF are related records, not automatically the same inventory.
The worksheet below is a suggested reconciliation method. It deliberately avoids a universal rule that every index entry must be a local model sheet or that every model sheet must be issued.
Establish what the index is meant to represent
Autodesk describes sheet lists as indexes for construction document sets. First ask whether this project's index represents the full planned set, a specific issue, or a combination identified by the office convention.
Record the issue purpose, package revision and expected treatment of consultant sheets, future entries and intentionally excluded sheets. Do not invent an export command or assume a software filter equals an authorized exclusion.
Compare each row using a stable sheet reference
| Comparison | Check | Record a difference as |
|---|---|---|
| Number and title | Index versus the identified output | Naming or identity discrepancy |
| Package inclusion | Expected issue scope versus delivered files/pages | Missing output or documented exclusion |
| Source ownership | Local model or separately supplied content | Owner and delivery reference |
| Revision information | Project issue rules versus the actual output | Revision question requiring review |
| Extra output | Delivered page with no expected entry | Unexplained inclusion |
| Pending entry | Planned content not in this issue | Explicit status and responsible owner |
Preserve a copy of the inventory you checked. If the PDF is replaced, the earlier reconciliation does not automatically apply to the replacement.
Hypothetical example: a consultant entry has a separate delivery
In this fictional package, the overall index includes M-101 from a consultant and A-101 from the architecture team. The architecture PDF contains A-101 only, while the agreed manifest says the consultant PDF is supplied separately.
M-101 is not automatically a missing local Revit sheet. Check whether the separate PDF was received and whether the index communicates that arrangement correctly. If the separate delivery is absent, record the missing package and its owner rather than deleting its index entry.
The opposite case matters too: a delivered page that the agreed issue excludes needs a decision before distribution, even if the page looks complete.
Keep revision markings separate from issue status
Autodesk's revision-cloud documentation describes clouds as indicators of changed design areas. A visible cloud does not by itself prove a review item is still open.
Use the revision-cloud responsibility matrix to check project conventions. Record disagreements without removing historical marks or renumbering sheets solely to make a checklist pass.
Return a reconciliation result
List matched entries, explained differences and unresolved exceptions. State which files and issue scope were checked, who reviewed them and whether another decision is required.
Carry that result into the drawing issue checklist. Nest's outsourcing quality-control guide and construction documentation service page provide context for defining external production work and internal review responsibilities.
Related guides and services
Keep the production handoff connected to the wider workflow:
Need help with current production work?
Tell us which drawings, models, visualizations, or review packages need attention. We can review the assignment, confirm availability, and explain whether a project package or dedicated monthly support fits.
Book a project callSend a project brief