Define the coordination question
Set out which systems, areas, and interfaces are included. A plant-room refurbishment needs different attention from a broad record of distribution routes. Define whether the model will support spatial planning, design coordination, installation planning, or final asset records. Do not assume that one scope automatically covers all four.
Describe the geometry needed for each task. Agree whether service envelopes include insulation, fittings, supports, equipment access zones, and other relevant allowances. Identify who supplies these requirements and who approves them. A model can be internally consistent while omitting the space that real installation and maintenance need.
Establish the basis for existing services
Use measured information to locate visible services and relate them to structure and architecture. Combine it with appropriate drawings, photographs, labels, and site observations. Record the evidence supporting system identification; shape and proximity alone may not establish which system a pipe or cable tray belongs to.
Separate observed routes from assumed continuations through concealed areas. Mark unresolved connections and inaccessible zones so the design team can decide where investigation is necessary. A model should not create a false impression of complete knowledge just because a continuous route is easier to display.
Check intersections and required space separately
Clash review should reflect the type of problem being investigated. Autodesk's Navisworks guidance distinguishes hard clashes, which check geometric intersections, from clearance tests, which check whether objects fall within a specified distance. Choose test rules that match the project's coordination requirements.
A geometric intersection is only part of constructability. Review access to valves and panels, equipment removal paths, installation sequence, and the spaces required around retained assets. These checks need relevant manufacturer information and discipline input. A clear model view cannot establish that all operational and installation requirements have been met.
Turn findings into decisions
Group related findings into issues that a person can resolve. Give each issue a location, affected systems, current evidence, owner, and required decision. Avoid measuring coordination progress only by the number of reported clashes, because duplicate or low-value results can distract from a critical unresolved interface.
Track the proposed solution through the responsible designers and installers. Record approval, update the model, and recheck the affected area. buildingSMART's BIM Collaboration Format supports exchanging model-based issues where the team uses compatible tools. Whatever system is chosen, preserve the resolution and its supporting context.
Release a coordinated package with defined limits
Before release, confirm model revisions, coordinates, referenced backgrounds, and the status of significant issues. Provide the required drawings, model files, schedules, and issue record. Explain whether the work represents existing conditions, coordinated design intent, or a more detailed installation deliverable.
Coordinate a final site check for interfaces whose condition or accessibility may have changed. Modeling does not replace discipline design, equipment selection, fabrication requirements, or necessary field verification. The service adds value by making relevant constraints and decisions available before work is committed, while keeping outstanding questions explicit.
Common questions
Does a clash-free model guarantee a workable installation?
No. The result depends on modeled content and test rules. Installation sequence, access, maintenance requirements, concealed conditions, and design decisions still need appropriate review and verification.
Can existing services be modeled from scanning alone?
Visible geometry can often be interpreted from suitable capture. System identity, hidden connections, condition, and performance may require labels, records, inspections, or specialist input beyond the point cloud.
Further reading
This article was rewritten in October 2026 around the subject of the original Geobiro post. The original publication date is retained; the update date identifies the current text.

