Define the BIM Scope Before You Price the Model

Agree what the recipient will receive

A useful building information modelling (BIM) scope states what models, drawings and data will be produced, how they will be checked and what the recipient may use them for. A quotation for modelling alone leaves room for different expectations about coordination, meetings, revisions and handover data.

This article recommends a technical scoping method. It does not interpret contract rights or replace advice from the parties responsible for the agreement. Commercial allowances and change procedures should be settled in the actual appointment.

Separate the work into deliverable groups

List model creation, multidisciplinary coordination, drawing production, quantity extraction and asset data as separate activities where required. Coordination means checking how the different disciplines fit and work together. State which activities are included, excluded or dependent on another party. A model prepared for spatial coordination should not silently become a deliverable for manufacturing components.

For each deliverable, identify its systems, zones, issue format, required stage and recipient. Include the supporting evidence needed for acceptance. A quantity schedule, for example, needs agreed inclusion rules and source revisions; a coordinated drawing needs a defined review route. This is more informative than quoting solely by floor area or model detail.

Make inputs and dependencies explicit

Record who supplies the design basis, architectural and structural references, supplier information and engineering decisions. Identify the expected condition of those inputs. A drawing set available on day one is not necessarily complete enough to start every package.

Agree how queries are raised and who resolves them. If the modeller is expected to infer missing information, define the limits and required confirmation. Do not turn an authoring task into unacknowledged design responsibility. The programme should distinguish production duration from periods awaiting inputs or approvals.

Describe revisions and coordination effort

Define the review stages and how comments will be consolidated. Distinguish corrections to agreed requirements from changes to the underlying design or scope. Avoid assuming an unlimited number of meetings or revisions within an otherwise fixed package.

For an illustrative equipment change, identify which consequences the revised service includes: updating geometry, checking adjacent systems, revising drawings, rerunning quantity schedules and updating asset attributes. These are related tasks, but they are not automatically the same task. Recording them prevents a small visible change from hiding a larger delivery obligation.

Prove the exchange on a sample package

Before full production, test a small representative package to confirm formats, field naming and acceptance expectations. Industry Foundation Classes (IFC) is a standard for exchanging building information between applications. buildingSMART's Information Delivery Specification (IDS) can express selected IFC data requirements for automated checking [1]. It supports part of a data specification, not the complete scope or agreement between parties.

Use the trial to identify misunderstandings before repeating the work. Record the agreed output and apply it consistently. A sample demonstrates the agreed method; it does not verify every later package or create undocumented additional requirements.

A scope review checklist

• Deliverables and their permitted uses are named.
• System and zone boundaries are identifiable.
• Inputs and engineering decisions have assigned providers.
• Review stages and acceptance responsibilities are stated.
• Meetings, revisions and change handling are addressed.
• Formats and information fields have been tested on a sample.

SmartBuild Tech's BIM and advisory services can help organise these technical boundaries before mobilisation. A clear scope gives both the delivery team and the client a more useful basis for planning the work and discussing its price.