The fabrication release just moved up. The coordination lead is already carrying the current mechanical, electrical and plumbing (MEP) zone, the weekly coordination meeting and the questions coming back from the shop. Bringing in help is the obvious answer. The risk is that the same lead then spends the next several days explaining the work instead of finishing it.
Under schedule pressure, it is tempting to hand over the area causing the most pain: the congested corridor with open requests for information (RFIs) and a design decision still pending. That area hurts because it is unresolved, and unresolved work is the hardest to transfer. The likely result is a second person waiting on the same missing decision.
We recommend the opposite starting point. Hand off what is most separable, not what is most painful, and make the first delivery small enough to check quickly.
Test the assignment before you hand it over
We recommend four tests before assigning outside help to building information modeling (BIM) and virtual design and construction (VDC) work. If an assignment fails one, fix that gap or pick a different assignment.
Can the result be written down? A few sentences should name the output, the area it covers and the conditions for accepting it. If nobody can write that, the work is not ready to hand off.
Do the inputs exist? An open design question does not always rule out outside support, but every assumption and pending decision must be visible. Each one needs a single owner with the authority to close it.
Does the recipient have the skills and the time? These are separate questions. The International Organization for Standardization's 19650 series (ISO 19650) sets out how to manage information on projects that use BIM. The UK BIM Framework's guidance on that series describes assessing a task team's skills and its capacity separately, along with the technology the work needs.[1]
Who reviews it, and when? Name the reviewer before production starts. Agree on a first delivery small enough to produce and review within the first few working days, so a misunderstanding is corrected before it spreads through the whole package.
Good and poor first assignments
A strong first assignment has a visible output that the reviewer can check against something that already exists. A weak one depends on decisions, history or relationships the newcomer does not have yet.
| First assignment | Good first step? | Why |
|---|---|---|
| Sheets from a coordinated, approved area | Yes | Inputs are settled, and the output can be checked against the model |
| One zone updated to an approved submittal at a named revision | Yes | Clear source, clear boundary, small review |
| A parameter and naming audit against the project standard | Yes | Visible output that also exposes access and template problems early |
| Spool drawings for one system run in a coordinated zone | Yes, with the shop standard supplied | Fabrication conventions must be written down, not assumed |
| A layout point export for one area | Yes, with care | Coordinate system, units and release authority must be confirmed; a simple-looking file carries real consequences |
| The most congested area, with open RFIs | No | The output depends on decisions nobody has made yet |
| General help with coordination across the whole job | No | No boundary, no acceptance condition and no first delivery |
| Running the weekly coordination meeting | Not first | Attending helps from day one; running it depends on the job's history and working relationships |
Draw the boundary and name the source
A useful boundary might be a level, a zone, a system or a release package. State what is included, what is excluded and which adjacent scopes the recipient must coordinate with, together with the owner of each.
Name the source model, its revision and the authoritative file location. Then state what the output is for. BIMForum's Level of Development (LOD) Specification gives teams a common language for how far a model element has been developed and how much others may rely on it, and it describes LOD 350 as supporting construction-level coordination.[2] It does not tell you what your handoff must contain. The project's own requirements do, and the handoff should point to them.
A model fit for coordination is not automatically fit for fabrication. Fabrication detailing typically adds shop standards, tolerances, connections, hanger and support requirements, installation access and product constraints. Those can require specialist judgment. Treating the step as a simple conversion hides the decisions the receiving team needs to see.
The handoff checklist
We recommend completing this checklist before the recipient's first day. Anything left blank becomes a question the coordination lead answers later, under more pressure.
| Item | Have ready | If it is missing |
|---|---|---|
| Boundary | Area or system, exclusions, adjacent scopes and their owners | Two people edit the same area, or nobody owns the edge |
| Source | Model files, revision or date, authoritative location | Work starts from a superseded file |
| Intended use | Coordination, shop drawings, spools or layout, plus the project's model requirements | The output suits the wrong purpose |
| Open decisions | Every assumption and pending decision, each with one owner | The recipient waits, or guesses |
| Standards and access | Templates, naming rules, software versions and file permissions | The first days go to setup instead of output |
| Reviewer | Named person, acceptance conditions and a review date | Delivery is mistaken for acceptance |
| First delivery | One small, representative piece of the scope | The same error repeats across the package |
| Release authority | Who authorizes the output for fabrication or field use | The preparer is assumed to be the approver |
| Support time | Named person and planned hours for orientation, questions and review | The support comes out of the lead's week unplanned |
Budget for the handoff itself
Someone has to grant access, explain conventions, answer questions and review the first result. That effort is real, and it comes out of someone's week. Put it in the plan with a name beside it.
If the coordination lead has no time at all, identify another qualified owner for the support role, or reduce the first assignment until it fits the time that exists.
The guidance does not prescribe a first delivery. On a compressed job, we recommend one as an early, practical check of file exchange, standards and review.
How to measure your team's coordination effort and test an improvement describes one way to keep that record without double counting.
When the work will not separate
Some work cannot be packaged yet: frequent design changes, shifting release priorities, decisions made in the meeting room. That work may suit an embedded role, where the person joins the team's decision cycle instead of receiving a package that is supposed to be settled. Embedded help and an outsourced package solve different problems covers that choice in more detail.
Keep release authority explicit in either arrangement. The person preparing the output and the person authorizing it for fabrication may carry different responsibilities.
The practical first step is a real, bounded package with a named source revision, a decision owner, a reviewer and a review date. It gives the added capacity useful work on the first day, and it gives both teams an early check on whether the arrangement works.
Sources
- UK BIM Framework, Guidance Part 2: Parties, teams and processes for the delivery phase of assets, edition 6, 2021, PDF pp. 24, 41, 43 and 58–62. Guidance (PDF). Supports assessing a task team's skills and capacity separately, with the technology the work needs, and planning mobilization with tests of exchanges and procedures. It does not prescribe a commercial arrangement or measure handoff effort.
- BIMForum, 2025 Level of Development Specification, Part I, 2025, introduction and LOD 350 definition, printed p. 17. Official specification (PDF). Supports the distinction between model development, reliance and intended use, and LOD 350's role in construction-level coordination. It does not define a project's handoff deliverable or promise any saving.
SCOPE
Atlas Construction Consultants is a construction technology consultancy offering staff augmentation; BIM and VDC design; project, model, trade and fabrication coordination; and technology consulting, implementation and training. This article describes a proposed way to choose and prepare a first assignment. It is not a measured client outcome, and Atlas does not provide licensed engineering, licensed construction management, trade supervision or installation.