Translate model uses into survey requests
Ask each discipline which decisions depend on measured information. An architect may need opening dimensions and floor relationships, while a services designer needs clear routes and equipment interfaces. Convert those needs into a survey scope with named areas, required evidence, delivery dates, and known access constraints.
Avoid treating the survey as one undifferentiated background file. Identify which deliverables support planning, coordination, setting out, or final records. Each use may require a different review and authorization. The execution plan should make those boundaries visible so data is not reused beyond its agreed purpose.
Assign responsibility at the handoffs
Name the roles responsible for survey control, registration, model positioning, interpretation, and acceptance. Specify who provides access and who answers questions about inaccessible areas. The author of a model should know where to send a survey query without relying on informal personal contacts.
At every handoff, state what the receiver checks. The survey team may supply a processed dataset and quality record; the BIM team must still verify that it is positioned correctly in the project. Review responsibility should follow the task, rather than being assumed to transfer automatically with the file.
Control coordinates and revisions together
Maintain a coordinate note covering units, horizontal and vertical references, orientation, and the agreed relationship between survey and model space. Identify the authoritative source and the person who may approve changes. Autodesk's shared-coordinate guidance recommends one source for the coordinate relationship among linked Revit files.
Pair that setup with revision control. A new survey issue should identify changed areas, capture dates, and any change to positioning. Do not silently replace a background file while several teams are modeling against it. Announce the issue, check the links, and record which model revisions incorporate it.
Give survey questions a trackable route
Create a common issue process for missing coverage, conflicting evidence, doubtful geometry, and required return visits. Each issue needs a location, clear question, owner, supporting view, and decision deadline. A screenshot without a location or request is difficult to resolve when many teams are involved.
buildingSMART's BIM Collaboration Format supports model-based issue exchange. Use it where the project tools support the workflow, or use another agreed register. The essential discipline is to preserve the question, evidence, response, and outcome so a later reviewer can understand why a modeling decision was made.
Schedule checks before dependent decisions
Place review gates ahead of the work that depends on the data. Check a representative area before full production, resolve critical interfaces before fabrication decisions, and verify changed conditions before final records are accepted. Schedule access around these decisions instead of discovering the need for another visit after a package is issued.
Define what happens when a gate cannot be completed. The team may restrict the affected use, commission additional capture, or accept a stated limitation through the proper project role. Record the decision and affected areas. This keeps uncertainty attached to the work it influences.
Common questions
Who should own the project's coordinate setup?
The project should designate an accountable role with suitable survey and coordination input. What matters is one approved reference, clear change authority, and checks in each receiving model.
When should the survey team join BIM planning?
Before capture and model production are committed. Early involvement allows the team to connect access, evidence requirements, coordinate control, and delivery dates to actual design and construction decisions.
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.