How to Compare BIM Service Proposals: A Scope Checklist

Before comparing BIM fees, make sure the proposals describe the same work. A modeling-only scope, a clash-reporting scope and a coordination service with meetings and issue follow-up can all be presented as “BIM services.” Their prices are not directly comparable.

This checklist is for owners, contractors and design teams preparing a service brief. It helps you expose scope differences and decide what to ask next. It is not a price benchmark or a contract template.

Start with the decision you need to make

Write one sentence describing the desired outcome: “We need coordinated ceiling zones before releasing this fit-out package,” or “We need existing architectural conditions documented for renovation design.” These are illustrative briefs, not descriptions of completed projects.

Then identify the service that supports the outcome. New model production, coordination of supplied models, 4D planning and Scan to BIM require different inputs. If you are still deciding, the BIM fundamentals guide explains their uses.

A project brief you can copy

• Project and location: building type, site location and remote or on-site needs.
• Purpose: decision, project stage and intended use of each output.
• Area and boundaries: levels, zones, disciplines, systems and exclusions.
• Available inputs: drawings, models, point clouds, schedules and their revision dates.
• Information required: elements, properties, tolerances where applicable and level of development by use.
• Deliverables: native models, exchange formats, drawing list, reports and meeting records.
• Milestones: first sample, review dates, final handover and dependency on other teams.
• Responsibilities: who supplies inputs, resolves design questions and accepts work.
• Revisions: included review rounds, update frequency and treatment of changed inputs.
• Acceptance: checks, receiving software and how outstanding issues are documented.

For a formal information-management approach, the UK BIM Framework provides guidance on defining information requirements. The checklist above is a practical scoping aid, not a claim of compliance with that framework. Guidance on information requirements.

Compare each proposal against the same questions

What is included, excluded or conditional?

Ask each provider to respond to your brief line by line. Mark a requirement as included, excluded, conditional or unanswered. A vague “BIM coordination included” should prompt questions about model federation, clash rules, meetings, issue ownership and verification after revisions.

Who makes design decisions?

Distinguish recording an issue from resolving the design. Name the responsible designers or trade partners and the route for escalation. A service provider cannot close a coordination issue simply because its report has been delivered.

Which changes create additional work?

Ask about revised design information, added disciplines, extra zones and additional review rounds. Identify the baseline inputs for the fee. Agree how changes are assessed before they are undertaken so the final scope does not depend on conflicting assumptions.

What will your team actually receive?

Request a sample deliverable or a demonstration using material the provider is authorized to share. Evaluate clarity, issue traceability and usability in your receiving workflow. For Revit work, use the model and drawing handover guide.

Why floor-area prices can be misleading

Area is one input to effort, not a complete description of it. Repetition, MEP density, source quality, model properties, drawing production and decision cycles matter too. Ask what assumptions sit behind a quoted unit rate and what changes that rate.

Illustrative comparison: Proposal A includes a model and one clash report. Proposal B includes the same model plus recurring meetings, issue tracking and checks of revised submissions. Before deciding that B costs more for the same service, normalize the deliverables and duration. Neither scope is inherently right; the project may only need one of them.

Additional questions by service

• Scan to BIM: is site capture included, where is coverage available, who registers the cloud, and how are inaccessible areas and model tolerances recorded?
• 4D planning: who provides the schedule, which scenarios are included, and are you receiving an animation, an editable linked model or both?
• Coordination: who updates each discipline model, how often are issues reviewed, and what evidence is required to close an item?
• Digital twins: which operating question, asset records and system connections are included, and who maintains them after handover?

These questions help avoid purchasing a model when the real need is a recurring management service, or purchasing ongoing support for a one-time deliverable.

A first milestone before the full package

Where appropriate, agree on a representative sample area or deliverable. Review it against the acceptance checklist, record the changes and confirm how the agreed approach extends to the remaining work. The sample should be representative of the difficult work, not only the easiest area.

Make the selection traceable

Keep the brief, clarifications and final deliverable list together. Compare scope coverage, relevant evidence, available capacity, communication and total cost on the same basis. Do not treat a short promised duration or an impressive model image as proof that the full scope is covered.

To scope work with EZ-VDC, review the service overview and send your project requirements. Start with the brief above; identify missing inputs explicitly so they can be assessed.