This video explains what a Master Information Delivery Plan (MIDP) is and why it is one of the most important coordination tools in ISO 19650. The written guide below covers how the MIDP brings together all task information delivery plans into a single framework, why dependencies and deadlines matter, how quality assurance procedures are built into the plan, and how collaborative planning tools make it practical to build, manage, and track the MIDP throughout the project.
Why the master information delivery plan coordinates everything
The Master Information Delivery Plan consolidates all of the task-level delivery plans into a single framework. It is the document that answers the question every project manager, information manager, and appointing party needs answered: what information is being delivered, by whom, when, and in what order? The MIDP covers every type of deliverable on the project — 3D models, drawings, schedules, programmes, approvals, documents, certificates — and makes sure they are all assigned to the right teams or team members and aligned with the project or Exchange Information Requirements.
The MIDP does far more than list tasks. A critical purpose is defining dependencies and deadlines to map out how deliverables interact with each other. For instance, an architectural concept model might need to be validated before structural design can proceed, or a fire strategy report might be required before MEP coordination begins. By aligning these dependencies, the MIDP avoids bottlenecks and keeps tasks flowing smoothly. The MIDP also strengthens quality assurance by setting clear validation and approval processes. It specifies exactly who reviews each deliverable, what standards must be met, and how compliance with ISO 19650 requirements like naming conventions and metadata is ensured before information is shared with the wider team.
The challenge most teams face is not understanding why the MIDP matters, but actually creating and maintaining one. When a new project starts, the natural instinct is to jump straight into execution. But the time invested in planning is critical. Without proper planning, projects are set up to struggle. Developing a comprehensive MIDP enables teams to understand interdisciplinary workflows, develop parallel planning strategies, and identify when work is intersecting. This proactive approach supports not just reactive clash detection but a process built around clash avoidance, where teams avoid clashes as they model because they understand how each discipline will proceed and where their work overlaps.
Building the MIDP starts with listing each team’s deliverables at every project stage, involving the teams themselves because they are the experts in what they need to produce. One effective method is collaborative pull planning, where teams use structured workshops to map out their deliverables and dependencies together. Once the list is complete, deliverables are classified by discipline — architectural, structural, MEP — or by project phase such as concept, design, or construction. This classification makes it easier to track and manage at scale. Clear deadlines are set for each deliverable, with identified dependencies ensuring that sequencing is accounted for. All individual Task Information Delivery Plans (TIDPs) are then consolidated into the single MIDP using a database-driven collaborative planning approach. The timeline view allows teams to visualise deliverables, dependencies, and phases together, while filters let each team focus on their own responsibilities while staying aligned with the overall project schedule.
How to build and manage the MIDP
- List all deliverables by team and stage – Work with each task team to document every deliverable they will produce, including models, drawings, documents, schedules, approvals, and certificates. Include deliverables from every project stage, from concept through to handover.
- Classify deliverables by discipline or phase – Organise the list by discipline (architectural, structural, MEP, project management) or by project phase (concept, design, construction, operations) to create a structure that is easy to navigate and filter.
- Set deadlines and identify dependencies – Assign clear deadlines for each deliverable and map the dependencies between them. Use the scheduling tools to ensure that sequencing is correct and that no deliverable is scheduled before its dependencies are complete.
- Consolidate TIDPs into the MIDP – Bring all individual task team plans together into a single Master Information Delivery Plan that provides a comprehensive view of all deliverables across the project.
- Assign responsibility and track status – Use the quick assign tools to allocate teams and team members to each deliverable, define statuses (proposed, approved, pending, complete), and track acceptance of accountability before commitments are formalised in contracts.
- Define quality assurance procedures – For each deliverable, specify who reviews it, what standards must be met, and what compliance checks are required. Include naming conventions, metadata requirements, and security protocols as defined in the BIM Execution Plan.
- Visualise in timeline and compact views – Use the timeline, grid, and compact views to see the broad schedule, drill down into specific teams or deliverables, and identify clashes or resource conflicts across the programme.
- Keep the MIDP live and actionable – Treat the MIDP as a dynamic document that is updated as deliverables progress, new requirements emerge, and dependencies shift. Use filters to focus on pending items, overdue tasks, or specific team responsibilities at any point during delivery.
What you’ll learn
- What a MIDP is – How the Master Information Delivery Plan consolidates all task-level delivery plans into a single coordinated framework that manages every deliverable across the project.
- Dependencies and deadlines – Why mapping how deliverables interact with each other and setting clear sequencing prevents bottlenecks and keeps tasks flowing smoothly between teams and disciplines.
- Quality assurance built into the plan – How defining validation processes, review responsibilities, and compliance checks within the MIDP ensures that information meets the required standards before it is shared.
- Clash avoidance through better planning – How understanding interdisciplinary workflows and parallel planning strategies enables teams to avoid clashes during modelling rather than detecting them after the fact.
- Collaborative planning approaches – Why involving task teams in defining their own deliverables and dependencies produces a more accurate and achievable plan than top-down scheduling.
- Dynamic tracking and filtering – How database-driven planning tools with milestone tracking, status filters, and dependency views keep the MIDP actionable throughout the project lifecycle.
Common questions
What is the difference between the TIDP and the MIDP?
The TIDP (Task Information Delivery Plan) is created by each individual task team and documents the specific deliverables they will produce, including timelines, formats, and dependencies. The MIDP combines all TIDPs into a single master plan that gives the lead appointed party and the appointing party a comprehensive view of every deliverable across the entire project. The TIDP is the team-level plan; the MIDP is the project-level coordination tool.
How does the MIDP support clash avoidance?
By mapping dependencies between disciplines and defining when each team’s deliverables intersect, the MIDP enables teams to coordinate their work proactively. Instead of modelling in isolation and then running clash detection after the fact, teams can see where their work overlaps and plan their modelling sequence to avoid clashes from being created in the first place. This proactive approach saves significant time and reduces rework.
How often should the MIDP be updated?
The MIDP should be treated as a live document and updated regularly throughout the project. As deliverables progress, new requirements emerge, or dependencies change, the plan must reflect the current state of the project. Regular reviews — typically aligned with project milestones or reporting cycles — ensure the MIDP remains an accurate and actionable coordination tool rather than a static document that quickly becomes outdated.
How does the MIDP connect to the BEP?
The BIM Execution Plan defines the overall information management strategy, standards, and procedures. The MIDP translates that strategy into a detailed delivery schedule, specifying exactly what will be delivered, by whom, and when. The BEP says how information will be managed; the MIDP says what will be delivered and in what sequence. Together with the responsibility matrix, they form a complete accountability framework for the project.
Explore further
- Creating the MIDP and TIDP – The full expert course lesson covering how to build and manage the Master Information Delivery Plan in detail.
- How to create a MIDP in Plannerly – Step-by-step guide to building the Master Information Delivery Plan using the Scope module.
- EIR, PIR, and BEP documents with Plannerly – How the complete set of information requirement and delivery documents connects across the project lifecycle.
- ISO 19650 concepts and workflows – The full help centre collection covering how each component of ISO 19650 works together in practice.