Practical checklist
What this article covers
A model intake package with version, standards, references, issue log and acceptance responsibilities; focus on handover, not generic Revit outsourcing.
A Revit handover should tell the receiving team what package it has, what work that package supports and which questions remain open. Start with an intake record tied to the actual files, not a general statement that the model is “clean.”
The worksheet below is our suggested coordination method. Adapt the checks and decision roles to the project. It is not a model audit, survey certificate or authorization to issue construction information.
Define the handover before inspecting it
Record the sender, recipient, package identifier, delivery date, intended task and agreed software environment. Identify the source of the requirements: a dated brief, agreed deliverable list or written instruction. If two instructions disagree, record both and ask the designated project lead which applies.
Autodesk explains that eTransmit packages saved model and dependent-file versions. That makes the exact delivered revision worth recording; a packaging step is not a substitute for the recipient's acceptance decision.
Use Nest's guide to CAD/Revit standards for external support when agreeing the broader production brief. This article concerns receipt of one package.
Copyable intake register
Create one row for each agreed deliverable or check. “Not required” should have an agreed reason, not conceal a missing item.
| Check | Requirement reference | Evidence to record | Decision owner | Result |
|---|---|---|---|---|
| Main model | Deliverable list and intended task | Received file, stated release and revision | Named BIM lead | Checked, query or not checked |
| Dependencies | Agreed reference list | Included files and recipient access observations | Package coordinator | Complete for agreed scope or open item |
| Positioning | Project coordination instruction | Source reference and designated alignment review | Coordination lead | Confirmed for stated use or pending |
| Production conventions | Dated standards reference | Representative view, schedule or output comparison | Standards reviewer | Matches reference or exception |
| Unfinished work | Sender's issue list | Item IDs, affected scope and next decisions | Project lead | Assigned, resolved or held |
| Receipt decision | Intended task | Permitted next activity and remaining exclusions | Authorized recipient | Accepted for that activity or returned |
The result column describes an observation or decision; it does not certify the whole model. Record who checked it and when. Separate “file received” from “checked for the planned task.”
Route detailed checks to the right record
Use the linked-file handover checklist for dependency inventory. For positioning, Autodesk describes shared coordinates as relationships between files; keep the project's chosen reference and review observations in the coordinate handoff record.
A separately requested content library belongs in the family release checklist. View-specific presentation checks belong in the view-template handover worksheet. If the task includes drawing corrections, connect those instructions through the redline tracking register.
Do not mark these checks complete simply because files open. Equally, do not assume an external family library is missing merely because no separate library folder arrived.
Hypothetical example: an incomplete reference package
In this fictional example, package R4 is supplied for updating interior room labels. The agreed list includes a current reference PDF, but the recipient finds an older revision.
The intake row records the received filename, the required revision and the affected task. The package coordinator requests the intended reference. The project lead holds label changes dependent on that reference; other work proceeds only if separately authorized.
After the replacement arrives, the recipient checks its identity and records the new receipt decision. The original delivery record remains intact. Nobody infers that the Revit model is corrupted or changes its coordinates to address a document mismatch.
Close the intake with a bounded decision
Return a short receipt note naming the package, accepted task, unresolved items and their owners. Do not silently purge content, replace families or upgrade files as part of this checklist. Those are separate decisions requiring the project's actual instructions.
For a scoped production-support discussion, see Nest's Revit documentation service. Keep technical suitability, design review and final issue authorization separate from administrative receipt.
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