There is no honest universal BIM rate
A rate per square foot, square metre, drawing or model may be useful for an early internal allowance. It becomes misleading when it hides what must be modeled, documented, coordinated, checked, revised and issued.
The price should follow a visible scope: source information, intended model use, disciplines, outputs, standards, responsibilities, milestones, review cycles and acceptance criteria. The same floor area can represent a repetitive shell, a dense technical environment, a fragmented existing building or a documentation-heavy package.
Best first question: what decision, drawing set, coordination milestone or handover requirement must this BIM package support?
Four common ways to structure the commercial model
| Structure | Works well when | Define before award |
|---|---|---|
| Fixed package fee | Inputs, outputs, milestones and revision assumptions are stable | Deliverables, dependencies, exclusions, acceptance and change control |
| Time-based support | Requirements evolve or the team needs flexible production capacity | Roles, rates, approvals, reporting, limits and ownership of priorities |
| Milestone packages | A larger scope can be separated into testable stages | Entry criteria, review windows, issue status and acceptance for each stage |
| Dedicated team or retained capacity | Work is recurring and the client can maintain a prioritized pipeline | Team structure, overlap hours, utilization, governance and continuity |
Hybrid structures are often sensible: a paid discovery or sample package can reduce uncertainty before a fixed production scope, while approved changes can remain time-based.
The ten inputs that move BIM effort
- Source quality. Complete, current and coordinated inputs reduce interpretation and rework. Conflicting drawings, point-cloud gaps and unclear revisions increase discovery effort.
- Intended use. Concept comparison, documentation, coordination, fabrication support, quantities and handover require different geometry, information and checks.
- Disciplines and interfaces. Effort rises with the number and complexity of systems, links, trades, penetrations, zones and responsibility boundaries.
- Model development. Define required elements, geometry, information, tolerances and reliance instead of applying one LOD label to everything.
- Drawing and schedule density. Sheets, views, details, annotations, schedules and revision management can exceed the effort of model creation itself.
- Content requirements. Bespoke families, parameters, classification, formulas and manufacturer content need explicit rules and validation.
- Coordination cycles. Meeting cadence, clash rules, issue ownership, federated-model updates and close-out evidence all affect effort.
- QA and acceptance. Model health, coordinates, naming, parameters, drawings, exports and file-opening tests must be priced as work—not assumed to happen invisibly.
- Programme and access. Compressed dates, phased information, platform restrictions, time-zone overlap and software versions can change the delivery plan.
- Change assumptions. Included reviews, design development, client delays, rework boundaries and approval authority should be commercial terms, not informal expectations.
How to compare BIM proposals
Normalize the offers before comparing totals. One proposal may include coordination meetings, drawings, model QA and revisions while another prices only production geometry.
| Compare | Evidence to look for |
|---|---|
| Scope | Named elements, disciplines, outputs, formats, stages and exclusions |
| Assumptions | Source status, design responsibility, client inputs and dependencies |
| Programme | Mobilization, sample, reviews, milestones, issue dates and client response times |
| Quality | Checks, review roles, issue status, acceptance criteria and correction route |
| Coordination | Federation, clash rules, meetings, issue register, ownership and close-out |
| Commercial boundary | Included revisions, change process, taxes, software, travel and payment milestones |
Warning signs in a low quote
- No stated source revision or input assumptions.
- One LOD number with no intended use or element definition.
- No distinction between models, drawings, coordination and approvals.
- Unlimited revisions or an undefined “complete BIM model.”
- No client review time, design-decision owner or change process.
- No evidence of QA, issue status, exclusions or handover content.
A quote-ready BIM brief
You do not need a perfect BEP to begin. A useful first package contains:
- Project type, location, gross area and current stage
- Required service, disciplines and model purpose
- Representative model, drawing, scan or data sample with revision status
- Required native files, exports, sheets, schedules and issue records
- Software version, template, coordinates and naming requirements
- Target milestones, review windows and final issue date
- Known design gaps, coordination risks and approval responsibilities
- Expected review cycles and the route for approved changes
Use the complete BIM outsourcing scope checklist ↗
Pricing questions buyers ask
01 — Can BIM work be priced per square foot or square metre?
Area is a useful scale signal, but it is not a complete pricing basis. Two projects with the same area can require very different effort because of source quality, repetition, disciplines, model use, drawing density, coordination interfaces and review cycles.
02 — Is a fixed fee or an hourly model better?
A fixed fee works best when inputs, outputs, responsibilities, milestones and revision assumptions are stable. Time-based or capped-time arrangements can be more honest during discovery, changing design stages or uncertain existing-condition work.
03 — Does a higher LOD always cost more?
Usually it increases effort for the affected elements, but a single LOD label is not enough to price the work. The quote should define intended use, geometry, information, drawings, interfaces, tolerances and approval responsibility by scope.
04 — Can ZX Collabs review a project before all files are ready?
Yes. A short brief, representative input, sample output, software version and required date can support an initial fit and information-gap review. A committed proposal may still depend on access to the actual source package.
This guide explains commercial scoping principles. It is not a quotation, programme, cost plan or promise that a particular pricing structure fits every project.