QA an Outsourced Revit Model: 7 Red Flags (2026)

The biggest objection to outsourcing BIM isn’t cost, and it isn’t communication. It’s the fear of paying for a model that looks fine in a screenshot and turns out to be a landmine — doubled-up elements, junk families, schedules that are 20% off. Fair fear. I’ve reviewed those models. I’ve also rejected them, and this is the process I used.

Quick answer: before paying for any outsourced Revit model, run a structured 10-minute health check — worksets, view range discipline, family hygiene, open connectors, warnings count, quantity spot-check against a known area, and file performance. Write that checklist into your engagement as acceptance criteria so “done” is defined before modelling starts, and stage payments against it.

This checklist is one part of our full BIM outsourcing guide for Australian & NZ firms — worth reading if you’re still deciding whether to outsource at all.

The deeper background on why these particular failures happen is in 5 Revit MEP modelling mistakes that cost you dozens of hours — the same standards we hold our own team to. This article is the buyer’s-side version: what to check, in order, before money moves.

The 10-minute health check: 7 red flags

Open the model. No tools needed beyond Revit itself.

1. One giant workset (or default worksets only)

Collaborate → Worksets. If everything lives in “Workset1”, the modeller either doesn’t know worksharing or didn’t care. You should see discipline-based worksets (MEP_HVAC_Ducts, MEP_Plumbing_Pipes, links on their own worksets) that let you unload what you don’t need.

Why it matters: you can’t manage load or ownership on a real project, and it signals every other shortcut probably got taken too.

2. Warnings count through the roof

Manage → Warnings. A working model carries some warnings; a 500MB model carrying 4,000 is a rework bill. Duplicate instances, overlapping walls, elements slightly off-axis — each one is minutes of somebody’s time later.

Rule of thumb: flag anything over ~1 warning per 10 elements for explanation before acceptance.

3. Elements that vanish between views

Pick three elements in 3D, find them on plan. If things show in 3D but not on documentation views — or vice versa — you’re looking at View Range abuse or wrong-level hosting: devices hosted to Level 1 with a 3,800mm offset instead of Level 2. That’s how duplicated elements (and doubled quantities) are born.

4. Junk families

Manage → Purge (look at the list before purging) and check a few family sizes. Downloaded manufacturer families with modelled threads and bolts, 8MB valves, families named Family1 - Copy (3) — all signs the library was Googled, not managed. Naming should follow a convention you recognise (Manufacturer_Type_Code or your office standard).

5. Open connectors everywhere (MEP models)

Analyze → Show Disconnects for each discipline. Yellow flags scattered through the model mean systems were drawn, not built: Revit can’t calculate flow, pressure, or produce trustworthy system schedules. A handful at package boundaries is normal; hundreds is a fail.

6. Quantities that don’t survive a spot-check

Pick one area you know — one plant room, one level of pipework — and take off a couple of quantities manually against the model schedule. If duct area or pipe length is off by more than a few percent in a contained area, extrapolate that error across the project and reconsider the invoice. This catches the “modelled for looks, not data” problem that plagues cheap outsourcing.

7. The file fights you

Slow opens, constant “not responding”, 10 minutes to sync. Check file size against project scale, purge state, and how many views/sheets carry no view template. A bloated, undisciplined file costs your team hours every week for the life of the project.

Turn the checklist into a contract

The health check protects you after delivery. Acceptance criteria protect you before. Write into the engagement:

1. Standards up front: template, worksets, naming convention, units, LOD per element category — reference your BEP or office standard.
2. Defined “done”: “Model passes the attached health check: warnings under X, zero disconnects outside package boundaries, quantities within 3% on nominated spot-check areas.”
3. Staged payments: per package or milestone, with the check as the gate. Never 100% up front.
4. First-package review: review the first delivery hard — 30 minutes per sheet/level, written feedback. Quality on package two onward is set by how seriously you review package one.

A provider who pushes back on written acceptance criteria has told you everything you need to know. A good one will hand you their internal checklist before you ask — because they run one anyway. (That difference matters more than which country they’re in — see Vietnam vs India vs the Philippines.)

---

Work with us

This checklist isn’t theory — it’s our internal release gate. Every model my Vietnam-based team ships to Australian and NZ clients passes it before you ever see the file, reviewed under standards set on WestConnex and Sunshine Coast University Hospital.

🧪 See it for yourself: run a fixed-price test package via Fiverr and put the delivery through this exact checklist.