Public clients across the UK are increasingly asking contractors to deliver “information management using BIM” in line with the UK BIM Framework and ISO 19650. In practice, that means aligning your programme, procurement and QA with structured information requirements, a working common data environment, and clear responsibilities for who creates, checks and approves data and models. It’s not just a designer’s problem and it doesn’t stop at drawings: it runs from tender queries to asset registers at handover.
TL;DR
/>
– Treat the IM mandate as a delivery framework: align ISO 19650 roles, CDE controls and asset data with your programme and supply chain.
– Interrogate EIRs early, close gaps, and propose pragmatic standards (naming, Uniclass, LoIN) the team can actually follow.
– Resource an IM lead with authority, and include information deliverables in subcontracts with acceptance criteria and dates.
– Stand up a CDE with robust permissions, review workflows and metadata; link it with site QA, RFIs and change control.
– Start asset data and handover packs on day one; verify fields progressively, not in a panicked month before PC.
A contractor’s IM mandate playbook: from tender to handover
# Start at tender: interrogate the brief and close the gaps
/> Read the Exchange Information Requirements (EIR) and any Asset Information Requirements (AIR) like a contract. Identify formats (IFC, PDFs, COBie or equivalent), classification expectations (often Uniclass 2015), security needs and the approval process. If anything is vague, issue clarifications and propose a practical approach: a draft Responsibility Matrix, Level of Information Need (LoIN) for key systems, and the data exchange timetable tied to milestones. Flag deliverables you can’t achieve without client decisions (e.g. asset ID conventions) and secure agreement before award.
# Appoint and empower the IM lead
/> Name an Information Manager or Digital Engineering Lead with time and authority to enforce process, not just “keep the CDE tidy”. Map responsibilities using a RACI that covers design, temporary works, MEP, civils, commercial and handover. Give the IM lead a budget for supply chain onboarding and tools, and make them a standing item in pre-start, design coordination and progress meetings. Ensure they can stop an issue or withhold “Published” status when acceptance criteria aren’t met.
# Publish a project information standard and methods
/> Issue a concise, site-readable Information Standard and Information Production Methods and Procedures in line with ISO 19650. Pin down naming conventions, revision and status codes, classification, attribute pick-lists, and drawing/model sheet templates. Define WIP/Shared/Published/Archive workflow, who can move information between states, and the evidential trail required for acceptance. Keep it short, visual and practical; one-page quick guides for site teams outperform 80-page manuals nobody reads.
# Configure a fit-for-purpose CDE
/> Stand up the CDE early with work areas by discipline and package, and metadata fields that match your standard (project, system, level, status, revision, suitability, classification). Build review and approval steps with checkers and approvers named by role, and make transmittals part of the audit trail. Set permissions tightly; WIP is private to authors, Shared is controlled, Published is read-only to the project. Connect site QA, RFIs and change notices so issues are closed with traceability, not lost in inboxes.
# Plan information production to the programme
/> Write the Master Information Delivery Plan (MIDP) with Task Information Delivery Plans (TIDPs) for each trade, linking every deliverable to programme milestones and procurement gates. Include who produces what, acceptance criteria, and when it is needed to let packages, pour concrete or place orders. Ring-fence float for asset data capture and verification ahead of commissioning. Publish a rolling 4–6 week IM lookahead so supers, planners and commercial teams can see what’s due and what’s at risk.
# Run assurance and change control, not after-the-fact chasing
/> Operate a clean checker/approver regime; no self-approval. Make status and revision meaningful so people know whether something can be built, procured or is simply shared for coordination. Tie RFIs and design change to information updates and asset data impacts; if a valve size changes, its attributes, tag and O&M must follow. Keep an exceptions log and review it weekly; stop the line on information debt before it buries the job.
# Prepare handover from day one
/> Agree the asset breakdown structure and tagging convention with the client early, and map it to Uniclass and your asset register fields. Capture barcodes/QRs on install if required, and verify attributes progressively (manufacturer, model, serials, spares) rather than dumping it on the MEP subbie at PC. Build O&M, test certificates and commissioning records into the CDE structure so handover packs assemble themselves. Schedule a dry-run data drop before commissioning to flush gaps while people are still on site.
# Common mistakes
/>
– Treating IM as a software problem instead of a delivery process. The CDE is only as good as the roles, rules and time you give people to use it.
– Dumping IM obligations onto subcontractors without templates, training or time allowances. If you want structured data, provide the structure and pay for the effort.
– Writing an over-engineered standard nobody can follow on a live site. Keep conventions simple, aligned to programme, and supported by quick guides.
– Leaving asset data until the month before practical completion. Start tags and attributes with first fix and verify at each inspection/test stage.
A live UK site scenario: IM pressure under programme heat
/> A tier one is upgrading a coastal water treatment works under a public framework. The EIR asks for ISO 19650 alignment, Uniclass classification and a structured asset register at handover that can slot into the client’s maintenance system. Early on, the civils team focuses on pours while the M&E subcontractor waits on late RFIs; the CDE fills up with “Shared” drawings but few are actually approved. When the pumping station kit lands, the tags don’t match the client’s asset IDs, and commissioning is three weeks away. The QS flags risk to completion bonuses due to incomplete O&Ms and missing certificates. The contractor’s IM lead steps in: they run a mini-workshop to fix the asset ID mapping, stand up a weekly data drop review, and tie asset attribute checks to the MEP inspection/test plan. Two weeks later, the commissioning pack compiles without a scramble, and the client signs off the interim data drop with only minor snags.
On-site IM readiness checklist
/>
– Extract the top 20 asset types critical to operation and lock down Level of Information Need and tag formats with the client before design freeze.
– Configure CDE metadata to capture package, system, level, status and classification, and make those fields mandatory at upload.
– Map the client’s asset ID convention to your tagging and labelling plan, including barcodes/QRs if required, and brief installers.
– Build a 6-week rolling IM lookahead linked to procurement and install dates, not just design milestones.
– Train supervisors and foremen on mobile CDE use for snagging, test records and photo evidence; keep it to a 30-minute site-friendly session.
– Bake information deliverables and attribute lists into subcontracts with clear acceptance criteria and dates; price the effort.
– Run a mid-project dry-run data drop to surface gaps before commissioning and handover.
Bottom line for contractors working under the IM mandate
/> The mandate is simply formalising what good contractors already do: get the right information to the right people at the right time, and hand over an asset the client can operate. Start early, keep standards simple, enforce the workflow, and treat asset data as part of the build, not an afterthought. For your next project meeting, ask: Do we have a signed-off LoIN and asset ID plan? Is our MIDP genuinely linked to the construction programme? Who has authority to stop a publish if acceptance criteria aren’t met?
FAQ
# What is the UK “IM mandate” asking of contractors?
/> Public sector clients are increasingly requiring information management aligned with the UK BIM Framework and ISO 19650 on their projects. For contractors, that means proving you can plan, produce, assure and deliver structured information, not just drawings, across the job. It covers roles, workflows, CDE use, and asset information at handover.
# Do we have to buy a particular CDE to comply?
/> No single platform is mandated across the UK market. What matters is that your CDE supports controlled WIP/Shared/Published states, metadata, review/approval workflows, audit trails and secure access. Choose a tool that your team and supply chain can use confidently, then configure it to your project standard.
# How do we onboard subcontractors without overwhelming them?
/> Give them only what they need to succeed: a one-page naming guide, attribute templates, simple upload rules and a brief training session. Put information deliverables and acceptance criteria in the subcontract, and allow time in the programme for checks and corrections. Pair smaller trades with a digital champion on your team for the first cycles.
# Who owns the information in the CDE and at handover?
/> Ownership is defined by your contract and appointments, but typically the client expects a licence to use project information for operation and maintenance. Contractors should retain evidence and records for their obligations, while ensuring the client can access agreed deliverables in open or agreed formats. Clarify rights, retention and export needs at tender.
# What does good asset information look like at practical completion?
/> It’s structured, consistent, verified and aligned with the client’s asset breakdown and ID conventions. You should be able to filter by system or space, find certificates and test results quickly, and see attributes that matter for maintenance (make, model, spares, warranty). Aim for a clean, navigable deliverable that your client’s FM team can pick up on day one without a translation exercise.
