Scan-to-BIM Modeling Exclusions Schedule

An exclusions schedule should say what a deliverable intentionally leaves out, where that boundary applies and who agreed it. It should not disguise missing evidence as agreed scope or make an uncertain item appear verified.

Use separate columns for scope, representation and evidence. A single label such as “approximate” cannot explain all three.

Define boundaries by location and intended use

Start with the agreed brief and model-use statement. Describe exclusions precisely enough that a recipient can locate them: a named zone, element group or information field is more useful than “minor items excluded.”

Autodesk's point-cloud documentation distinguishes linked reference data from the Revit model. Make exclusions clear for the authored deliverable rather than assuming the source and model contain identical information.

Use independent fields instead of a misleading status

This is our proposed worksheet, not an official classification system. Keep related assumptions in the existing-conditions assumptions register.

A specialist provider's workflow description includes documenting exclusions and logging ambiguous geometry. That is a useful attributed example; it does not make its contract language or procedures applicable to your project.

Hypothetical example: decorative loose objects are outside the assignment

In this fictional room-planning package, the agreed brief excludes decorative objects on reception shelving. The schedule identifies the room and object group, records “omitted” for representation and links the scope decision.

This does not mean the shelves themselves are excluded. If their geometry is required but insufficiently supported, record a separate evidence question instead of placing the entire area in the decorative-object exclusion.

If a later visualization request needs those decorative objects, reopen the scope discussion. Do not silently add guessed items or assume an earlier exclusion grants permission for a different use.

Make limitations visible to recipients

Identify which model, drawing and exchange outputs carry each limitation. Check that the receiving package includes the schedule or a clear reference to it. A note hidden in an internal working folder will not help a recipient who never receives it.

If a proposed exclusion would undermine the intended task, ask the designated project lead to decide whether to obtain more evidence, alter the deliverable or change the use. Recording an exclusion alone does not make a model suitable.

Reconcile exclusions before acceptance

Compare the schedule with the current brief and actual output. Resolve required items that were omitted without a recorded decision, and correct exclusions that no longer describe the delivered revision.

Use the scan-to-BIM acceptance checklist to retain those findings. Nest's scan-to-BIM briefing guide and scan-to-BIM services offer context for agreeing a bounded production task with explicit inputs and limitations.