ISO 19650 Checklist: A Practical Guide for European Consultants

The tender pack arrives with a 40 page Exchange Information Requirements document, a file naming standard you have never used, a common data environment you do not control, and a line saying all deliverables shall be produced "in line with EN ISO 19650." Your team knows Revit and knows the design. What it does not always know is which documents the client expects back, when, and in what state.

That gap costs consultants time at the worst moments: a pre-appointment BEP written in a rush, a mobilization stage that never happens, and models rejected at the first information exchange because the naming, status codes or metadata were wrong. This ISO 19650 checklist turns the standard into the steps an architecture, structural or MEP consultancy actually has to complete on a European project.

What ISO 19650 Covers Today

ISO 19650 is a series of international standards for managing information over the life of a built asset using BIM. It is published across Europe as EN ISO 19650, with national versions such as BS EN ISO 19650 in the UK and DIN EN ISO 19650 in Germany. The parts most consultants deal with are:

Parts 1 and 2 are under revision, and ISO has published draft versions (ISO/DIS) for comment. The draft changes some terms and adds a "submitted" state to the CDE workflow. Until the new editions are published and named in your appointment, work to the edition your contract cites.

ISO 19650 for Consultants: Who Does What

The standard talks about parties, not job titles. On most European projects the client is the appointing party, the lead designer or main contractor is the lead appointed party, and each consultancy is an appointed party. A structural or MEP consultant is usually a task team inside a delivery team. That matters because your obligations flow down from the lead appointed party's BEP and master plan, not straight from the client.

EIR and BEP Requirements: The Documents You Must Read and Write

• Exchange Information Requirements (EIR): what the client wants, when, at what level of information need and for what purpose. Read it first and list every requirement that touches your discipline.
• Project information standard and production methods: naming, classification, units, coordinates, status and revision codes, and file formats such as IFC. These are where most rejections come from.
• Pre-appointment BEP: your proposed approach, team and software, submitted with the tender.
• Post-appointment BEP: the confirmed version after award, with the agreed responsibility matrix.
• Level of information need: often defined with reference to EN ISO 7817-1, which replaced the older LOD style tables on many European projects.

MIDP and TIDP Planning

Each task team writes a Task Information Delivery Plan (TIDP): every model, drawing, schedule and report your team will produce, with an owner, a due date and the exchange it belongs to. The lead appointed party combines all TIDPs into the Master Information Delivery Plan (MIDP). If your TIDP is vague, your deadlines are set for you by someone else's MIDP. Keep it at container level: one line per file, named exactly as it will appear in the CDE.

Common Data Environment Workflow

Under the 2018 editions, every information container moves through four states: work in progress, shared, published and archived. Status codes tell other teams whether a file is fit for coordination, for review or for construction. Common mistakes we see:

• Sharing work in progress models directly by email or file transfer, outside the CDE.
• Using revision codes for shared files that the information standard reserves for published ones.
• Missing metadata fields, so the CDE cannot route the file for review.

The 8-Step ISO 19650 Information Delivery Checklist

These steps follow the delivery process in ISO 19650-2, written from the appointed party's side.

1. Assess the requirements. Read the EIR, information standard, production methods and any shared reference information. Log questions for the tender clarification window.
2. Check your capability. Confirm your team, software versions, IFC export settings and capacity against what the EIR asks for.
3. Write the pre-appointment BEP input. Describe your approach, modeling responsibilities and any exceptions to the information standard.
4. Agree the appointment. Make sure the EIR, the BEP and the responsibility matrix are named in your appointment documents, together with the information protocol.
5. Mobilize. Get CDE access, set up templates with the right naming, coordinates and parameters, and test one full exchange before production starts.
6. Produce information collaboratively. Model to the agreed level of information need, run self checks and clash checks, and share through the CDE on the agreed cycle.
7. Deliver the information model. Check every container against the acceptance criteria, then submit it for review and authorization by the lead appointed party.
8. Close out. Archive the project information and record lessons learned for the next appointment.

For how these rules sit alongside wider European BIM requirements, see our post on BIM and MEP rules in Europe.

Quick Pre-Exchange Checklist

• File names follow the project information standard, field by field.
• Status and revision codes match the CDE state.
• Shared coordinates and project base point match the federated model.
• Classification and required properties are filled in, including any IFC property sets.
• The IFC export opens cleanly in a free viewer and in the client's checking tool.
• Clashes in your area are resolved or logged with an owner.
• The TIDP line for each container is updated with the actual issue date.

BIM365 works as the production and coordination team behind architecture, structural and MEP consultancies. Your firm keeps design responsibility and sign-off. We build the models and drawings to your project information standard, so what you upload to the CDE passes review the first time.

• Revit MEP modeling and architectural and structural modeling set up to the EIR, naming convention and level of information need.
• Clash detection and coordination with issues tracked in BCF so every clash has an owner and a status.
• TIDP and BEP support: container lists, delivery dates and the modeling sections of your BEP drafted for your review.
• IFC export checks before every information exchange.

We support consultants across Europe, working to your CDE, your templates and your time zone.

Send us your EIR and one set of drawings. We reply with a scope, a schedule and a fixed price within 24 hours.

WhatsApp or call: +91 94618 36037
Email: info@bim365.in
Website: bim365.in