Practical checklist
What this article covers
A manifest for linked models, CAD, images, paths and responsible owners; verify software claims against Autodesk.
A useful linked-file handover records what the host model is expected to reference and what the recipient can actually access. It does not diagnose every missing reference from a warning icon or prescribe one path format for all environments.
Use this recommended register for an agreed package and receiving environment. Keep a received copy unchanged while checking it; record proposed changes separately.
Establish the dependency baseline
Ask the sender to identify the host model, its revision, the intended task and the references required for that task. List linked files by their actual identifiers rather than a vague folder name.
Autodesk's eTransmit documentation says the process uses versions saved on disk and offers options for supporting files. Record the chosen package contents instead of assuming every useful reference was included automatically.
For the whole-package receipt decision, use the Revit model handover checklist. This worksheet covers the narrower dependency question.
Dependency register
| Field | What to enter | Why it matters to the handover |
|---|---|---|
| Reference ID | Stable row identifier | Connects follow-up messages to the same item |
| Host and revision | File needing the reference | Avoids checking against the wrong package |
| Reference identity | Filename, revision and file type as supplied | Distinguishes similarly named files |
| Intended use | What the reference supports | Identifies affected work if it is unavailable |
| Delivery arrangement | Included file or agreed access location | Makes the expected access route explicit |
| Recipient observation | Exact result and any displayed message | Separates evidence from a guessed cause |
| Owner and action | Person to clarify or provide the item | Makes the next step assignable |
| Closure evidence | Replacement identity or confirmed arrangement | Records what resolved the query |
Use separate rows for distinct required references. If something is intentionally excluded, identify the instruction authorizing that exclusion and any limitation it creates.
Check access without assuming alignment
Compare the delivered package with the agreed inventory. Record the receiving environment and the result of the project-approved check. “File present,” “accessible,” “loaded for this check” and “appropriate revision” answer different questions.
If a link is unavailable, preserve the observed message and ask the responsible person to investigate. Do not automatically bind, remove, rename or relink files. The register should not convert an unexplained symptom into a repair instruction.
Positioning is another check. Autodesk describes shared coordinates as establishing relative file positions. A file being accessible does not answer the project's positioning question; record that decision in the shared-coordinates handoff checklist.
Hypothetical example: the agreed reference is missing
A fictional package includes Host-R2 and a reference list naming Interior-Background-R5. The recipient finds only Interior-Background-R3.
The register records both identities and marks the intended room-layout update as pending. It does not claim a path failure: the immediate evidence is a revision mismatch.
The sender provides R5 through the agreed delivery route. The recipient records the replacement, repeats the agreed check and links the result to the same reference ID. If the sender instead confirms that R3 was intended, the designated project lead must resolve that conflict with the original requirement before dependent work proceeds.
Decide what can proceed
Use three plain outcomes: checked for the stated task, awaiting clarification, or excluded by an identified decision. Name the person authorized to accept an exception and the work it affects. Do not stop unrelated activities automatically, but do not treat silence as permission to continue affected work.
Nest's external-team standards guide provides broader handoff context. The Revit documentation service page is the place to discuss production scope. This register records references and receipt evidence; it does not certify model health or determine contractual responsibility.
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