Revit View Template Handover Checklist

A view-template handover should tell the receiving team which presentation reference to follow, what template relationship each checked view has and which exceptions have been agreed. “Template applied” is too ambiguous to serve as the whole record.

This is a recommended view-by-view review worksheet. It does not require a template on every view or establish a universal drawing standard.

Distinguish the template relationship

Autodesk's view-template demonstration distinguishes applying properties once from assigning a template that controls selected properties. The demonstration was recorded in Revit 2013, so check the current release documentation before using its interface instructions.

Record the actual relationship relevant to the checked view. A blank assignment alone is not proof that its graphics are wrong. Conversely, a named template does not by itself show that the output matches the project's intended reference.

View review worksheet

Keep the scope of the check explicit. If only two representative views were compared, say that; do not mark all project views verified.

The model handover checklist records the overall intake decision. Use this worksheet as supporting evidence for that decision.

Make the comparison reproducible

Ask the sender to identify the reference output and the model revision used to create it. Autodesk's eTransmit description identifies saved file versions as the packaging input. That makes revision identity part of a useful comparison record.

Have the responsible reviewer select the view and output checks for the receiving environment. Record observations, not presumed causes. If expected reference content is unavailable, open a dependency query using the linked-file handover register; do not invent external template or legend files.

An intended difference should have an identified owner and reason. An unexplained difference stays open until the appropriate person decides whether to change the view, change the reference or retain a documented exception.

Hypothetical example: a review view differs from the sample

In this fictional handover, a furniture review view has a different annotation presentation from the supplied sample. The worksheet records the view name, model revision, sample identifier and the specific difference.

The reviewer does not assume a missing template. The BIM lead checks the project setup and confirms that this view intentionally uses a presentation exception for client review. That decision and the accepted reference are recorded.

If the lead had instead requested a correction, the updated view and comparison evidence would be linked to the same row. Neither outcome requires changing unrelated views or applying a template across the whole model.

Finish with an explicit scope

State which views were checked, which references were used and what remains unresolved. Keep reviewed output separate from the authority to issue it. This handover record does not verify design accuracy, coordination completeness or construction suitability.

For the broader standards arrangement, see Nest's guide to external CAD/Revit support. The Revit documentation service page describes the related production-support offering.