BIM on NEC Projects: Information and Coordination Scope

On a project using an NEC contract, BIM support starts by understanding what information must be delivered, by whom and for what use. A model-production plan should connect to the project's actual requirements, review process and delivery dates.

NEC's practice note explains how information modelling under NEC4 Option X10 relates to requirements included in the Scope. It provides a route for incorporating an information protocol. That does not establish which provisions apply to your particular project: the contract team should identify the selected form, edition, options and amendments. NEC's practice note on BIM.

What this guide covers

This is a practical BIM/VDC delivery checklist for project teams. It addresses models, information exchanges and coordination records. It does not interpret entitlement, allocate legal liability or replace review of the executed agreement.

Documents to bring to the BIM kickoff

• The applicable information requirements and deliverable schedule identified by the project team.
• The project BIM Execution Plan or other agreed information-execution documents.
• The discipline and responsibility list, including reviewers and acceptance roles.
• Current models, drawings, schedules and the register of their revisions.
• The agreed platform, access rules and process for formal communications.

Ask the team to resolve contradictory instructions before production starts. For example, a model deadline and a design-input deadline may leave no time for checking. The useful output of kickoff is a recorded decision about that dependency, not just a meeting attendance list.

Build a requirement-to-deliverable register

For every required output, record its purpose, author, source information, format, delivery date, reviewer and acceptance check. Add a reference to the governing requirement so the team can trace why the deliverable exists.

Illustrative example: a package requires coordinated services in a plant room. The register should identify the relevant discipline submissions, the coordination review and the evidence of issue resolution. “Revit model delivered” does not by itself demonstrate that those coordination activities occurred.

Use the register to expose missing decisions. If an export format is named but the receiving software and acceptance test are undefined, agree a sample exchange before the full package is due.

Keep model issues and formal communications connected

A model issue should identify the location, affected elements, source revision, question and responsible person. It can support the project team's review, but teams should agree how that issue relates to formal communications under their project procedures.

Do not assume that a comment in a coordination platform has completed a separate communication requirement. Equally, a formal response may require a subsequent model update and check. Keep references between the records so the team can follow both actions.

Make revisions visible

When inputs change, record which deliverables are affected, what needs rechecking and who confirms the next release. Preserve the issue and revision history. A newer file date is not enough to show what changed or whether the change was reviewed.

For handover, provide the agreed outputs, delivery register and open-item list. Record the status of the package accurately; avoid presenting incomplete coordination as accepted construction information.

Questions for your first working session

1. 1Which requirements govern the model and information exchanges?
2. 2Who supplies and reviews each input, and when?
3. 3What decisions need model coordination or a 4D sequence review?
4. 4Where are issues recorded, and how do they connect to formal project communications?
5. 5What evidence is required to accept each deliverable?

EZ-VDC provides BIM/VDC support for projects using NEC contracts. To define a suitable scope, share the project stage, information requirements and required deliverables with our BIM and VDC consulting team. For broader scoping questions, use the BIM proposal checklist.