Describe the service boundary
Separate site capture, point-cloud processing, model production, drawing extraction, and coordination support in the scope. Some commissions include the full sequence; others begin with an existing dataset. If a point cloud is supplied, establish who checks its coverage, date, coordinate reference, and suitability before modeling begins.
List included buildings, floors, external areas, and disciplines. Define whether equipment is represented as an approximate envelope, recognizable component, or information-bearing asset. Record exclusions such as concealed services or inaccessible roof areas. This makes the quoted work understandable and creates a clear basis for later changes.
Specify quality at the level of the decision
Avoid using a single label as the entire definition of quality. State which elements matter, how their geometry should be interpreted, and how they will be checked. A model suitable for room planning may need additional investigation before it supports a tightly constrained equipment installation.
Ask the provider to distinguish survey quality from model representation. The measuring instrument, registration process, site conditions, and modeling choices all influence the final result. A scanner specification alone does not describe the delivered model. Agree how uncertainty, simplification, and deviations will be reported in the areas that influence design.
Use a sample to settle practical questions
A representative sample is useful when the project includes repeated rooms, complex services, or irregular existing construction. Choose an area that exposes the difficult decisions rather than the easiest area to model. Review its object categories, naming, geometry, properties, and performance in the intended application.
Approve the sample with written comments that become production rules. For example, decide whether insulation is included in service envelopes and how unverified elements are identified. This early agreement reduces the chance of receiving a complete model that follows technically consistent rules but fails the recipient's actual needs.
Compare deliverables and dependencies
Confirm native model versions, exchange formats, point-cloud packaging, drawing outputs, and the review information supplied with each issue. Autodesk documents RCP as a project that groups RCS files, so a receiving team must check the complete point-cloud package rather than assume that the project file contains every dependency.
Include access arrangements in the comparison. Who organizes keys, escorts, safe access, and return visits? What happens if an area cannot be scanned? Ask how new site information affects the agreed fee and programme. A transparent proposal explains both the deliverables and the conditions needed to produce them.
Agree acceptance before the final issue
Create a short acceptance checklist with the people who will use the files. It should cover opening the package, checking positioning, confirming required content, reviewing sample geometry, and resolving outstanding comments. buildingSMART's Information Delivery Specification supports machine-readable information requirements where the project's tools and workflow make that useful.
Automated information checking does not remove the need for visual and geometric review. Give review comments an owner and a resolution date. Close the commission with an accepted issue register and an explicit list of remaining limitations, so later users understand the agreed basis of the delivery.
Common questions
What should a client provide when requesting a quotation?
Provide available plans, site extent, access constraints, required outputs, intended uses, and important deadlines. Identify uncertain areas so the provider can explain assumptions rather than price an incomplete brief.
Can an existing point cloud be reused?
Often, but its condition must be assessed. Check coverage, currency, registration evidence, permissions, and compatibility. Missing or outdated areas may require targeted new capture before they can support the proposed work.
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.