What Drives the Cost of VDC Services

If “VDC services” is sitting in an RFP or a scope of work you’re pricing, here’s the plain answer: it means coordination of the building — clash detection, coordination meetings, trade sign-offs, RFI resolution, model QA, and managing the common data environment the project team works out of. I also build 4D construction animations and print physical construction models off the same underlying models, but those are separate deliverables with their own cost drivers — I cover the animation side in what drives the cost of a 4D construction animation — and the coordination cost story below is what you’re actually pricing when a scope says “VDC services.”

I’ve written before about how “VDC services” and “BIM coordination” describe the same purchase once your need is a single coordination job. I’ve spent 10+ years in construction and VDC, about four of them on-site, and read enough coordination proposals — mine and other providers’ — to know exactly where a competitive-looking quote tends to leave its own number behind.

How VDC coordination actually gets priced

Coordination proposals aren’t built off one format. Three structures show up most often, and knowing which one you’re looking at changes what question to ask next.

The weekly line-item stack

Every scope item — coordination meetings, clash detection and RFI leadership, recording trade sign-offs, managing the common data environment, model QA, enforcing the collaboration strategy — priced separately and billed per week. It reads granular and fair on paper. The catch is structural, not a trick: if every line bills weekly, every week the schedule runs past its planned end date, the whole stack bills again. A coordination effort quoted to close in three months that actually runs five pays two extra months of every line on the sheet, not just one fee.

The fixed fee with defined scope

A set number of weeks, a set number of coordination meetings, sign-off documentation for a defined list of buildings or areas, quoted as one number. This looks like the safer structure, and often is — but the real terms live in what happens outside that defined scope. Extra meetings, extra clash reports, or sign-off revisions beyond the count usually convert to hourly billing, sometimes pre-agreed right in the proposal so no separate signed change order is ever required to trigger it.

The retainer or resourcing model

An upfront retainer locks in staff, sometimes paired with an offer to add resources and compress the timeline. Worth noticing what’s called out as free — unlimited coordination calls, for instance — since a provider advertising a normal deliverable as free is usually a sign the market bills for it elsewhere.

The real reason costs run past the quote

Every structure above gets quoted against two estimates: a coordination duration, and a meeting count — nobody can know at kickoff exactly how many weeks trade coordination will take. But coordination schedules push on almost every real project, for reasons that have nothing to do with the coordinator: design changes, trade RFI turnaround, procurement timelines, owner decisions. When that happens, the extras are where the final number leaves the original quote behind — meetings beyond the estimated count, additional clash reports, sign-off revisions, RFI posting, billed on top, sometimes pre-agreed so no new signed change order is needed to authorize it.

One term worth reading closely in any proposal: sign-off recording listed as “whenever required,” with no defined count. Paired with a low initial meeting-count estimate, that’s exactly the structure that turns a competitive-looking quote into a much larger final number once the schedule does what coordination schedules almost always do. It’s less bad faith than market incentive — a lower headline number wins the bid, and the real economics show up later, in the schedule. I go deeper on why the schedule is the single biggest risk to a coordination budget in what drives the cost of BIM coordination, including how I track overdue items so they don’t quietly roll from week to week.

The best protection is simple: get more than one proposal, and normalize them before you compare — same meeting count, same sign-off count, same terms for the extras. I’ve compared two proposals for the same coordination scope where one estimated 15 meetings and the other 38. The 38 wasn’t the expensive quote — it was the honest one, calculated from the actual coordination schedule. The 15 was a lower number built to win the job, with the difference set to show up later, billed meeting by meeting past the estimate. Apples to apples, the “cheaper” proposal wasn’t cheaper at all.

“

The number that wins the bid is rarely the number on the final invoice. The gap lives in what happens once the schedule pushes — which it almost always does.

The quieter costs worth checking for

Beyond the schedule mechanic above, a handful of line items are easy to miss on a first read of a proposal:

• Software and platform fees. A base coordination platform is usually included, but cloud coordination or model-review platforms beyond that are often billed case-by-case, not folded into the headline number.
• Sign-off scope. A defined count of sign-off documents per building or area prices very differently than sign-offs “whenever required” — worth confirming which one you’re actually being quoted.
• RFI posting and change-order billing. Some proposals bill RFI posting hourly, separate from the coordination fee, with a pre-agreed change-order rate that doesn’t require new signed authorization.
• Mobilization terms. How fast coordination can actually start once documents are in hand, and what a retainer locks in versus what it doesn’t.
• Exclusions that become change orders. Scope like gap modeling or on-site trade liaison work is often explicitly excluded from the base fee — worth knowing before it shows up as a mid-project add-on.

What you hand over still sets the pace

One driver holds regardless of which pricing structure you’re looking at: most coordination proposals only start the clock once they receive a usable architecture and structure base model. A clean, coordination-grade model handed over at kickoff means federating and running clashes can start immediately. An incomplete or early-stage model means real setup work before coordination begins at all — time that shows up in the schedule, and depending on the structure, in the invoice too.

What to ask before you compare VDC quotes

Two proposals that both say “VDC services” — or “BIM coordination” — can hide very different terms once the schedule moves. Ask every provider these same questions so you’re actually comparing like to like:

• What’s the exact meeting count and deliverable count included, and what does anything beyond that cost?
• What happens to the quote specifically when the schedule pushes — is that spelled out, or silent?
• Is sign-off recording a defined count, or “whenever required”?
• Which software or platform fees are included, and which are billed separately?
• Is RFI posting and change-order work billed hourly, and does that billing require new signed authorization or not?
• What’s explicitly excluded from the base fee?

The cheapest coordination isn’t the lowest quote

I quote coordination against a defined meeting cadence and a defined deliverable set, and I name the per-extra terms up front, not as a mid-project surprise. But the terms on paper aren’t the part I actually control — the schedule is. Every set of coordination minutes I run names the overdue clashes, the trade responsible, and the date they’re due, so an open item doesn’t quietly roll to next week unnoticed. The weekly report itself is AI-leveraged, which keeps that tracking consistent and detailed without slowing the turnaround, and I review every line before it goes out.

The cheapest VDC coordination quote isn’t the one with the lowest number at the bottom. It’s the one that tells you up front what happens when the schedule pushes, and then runs tight enough that it mostly doesn’t have to.