Many projects have a design programme and a construction programme but no specific plan for producing, reviewing and accepting information. Files emerge when somebody asks for them, dependencies are discovered late, and delivery dates are coordinated through emails, messages and meetings.
An MIDP and its supporting TIDPs address that gap. They do not replace the overall project programme. They organise the information production needed for that programme to operate through traceable decisions.
What is the difference between a TIDP and an MIDP?
A Task Information Delivery Plan (TIDP) is prepared for a task team. It records the information containers that team must produce, together with responsibilities, dates, dependencies and review arrangements.
The Master Information Delivery Plan (MIDP) compiles and coordinates the task teams' TIDPs. Its purpose is not simply to copy every list into a larger spreadsheet. It should expose duplicated deliverables, impractical sequences, unresolved dependencies and conflicting dates.
The basic logic is straightforward:
- each task team declares what it must and can produce;
- the lead delivery team coordinates those commitments;
- the master plan is checked against information requirements and project milestones;
- actual dates and acceptance decisions keep the plan current.
Why a document schedule is not enough
A useful information delivery plan needs more than filenames. Every deliverable should answer at least eight questions:
- Which requirement or use does it satisfy?
- Which task team produces it?
- Who checks it and who approves it?
- Which information must exist before work begins?
- When must it be available?
- At which CDE state or project milestone will it be exchanged?
- Which revision and suitability code apply?
- Has it been accepted, rejected or rescheduled?
Without those relationships, a date is merely an expectation. With them, it becomes a testable commitment.
Alignment with ISO 19650
ISO 19650-2 defines an information management process for the delivery phase and its information exchanges. ISO 19650-4 provides criteria for executing exchanges and protecting the quality of the resulting information model. UK BIM Framework guidance identifies responsibility matrices, TIDPs and the MIDP as resources supporting information delivery planning.
The SORA workbook translates those principles into a practical starting point. It does not reproduce the standards or certify compliance. It must be adapted to the contractually applicable edition, BEP, information standard, CDE and actual appointment structure.
Two concepts must also remain distinct. WIP, Shared and Published describe states or areas within a CDE workflow; Commissioning and Handover are project milestones. The workbook uses both as configurable control points but does not treat them as equivalent concepts.
Supporting technical continuity
Within the SORA ecosystem, the MIDP/TIDP has a clear role:
- the Information Requirements Matrix defines what information is needed;
- the RACI matrix clarifies who participates and with what authority;
- each TIDP commits what a task team will produce and when;
- the MIDP coordinates the overall delivery sequence;
- naming rules preserve the identity of each information container;
- QA/QC determines whether a delivery complies before acceptance.
Together, these controls support SORA's technical-continuity model: Engineering → Information → Coordination → Construction → Commissioning → Handover.
What the workbook contains
The current spreadsheet interface is in Spanish; an English interface has not been published yet. The download includes:
- project and exchange configuration;
- editable catalogues;
- a TIDP expandable to 95 deliverables;
- an automatically consolidated MIDP;
- 20 starter deliverables covering information management, BIM, coordination, documentation, electrical, BMS/BAS, EPMS, construction, commissioning and handover;
- production, checking and approval roles;
- dependencies, planned dates and actual dates;
- CDE state, suitability, revision and workflow status;
- day-variance calculations;
- completeness, delay, rejection, cancellation and acceptance controls;
- checks for duplicate IDs, missing dependencies, self-dependencies and reversed dates;
- a dashboard and decision gate;
- usage guidance, references and limitations.
How to implement it
Configure the project first and review every starter row; examples should never be adopted automatically. Each task team then prepares a realistic TIDP. The lead delivery team compiles the plans, resolves dependencies and verifies that every information requirement has an associated delivery.
Update the plan whenever a date changes, an information container is rejected or cancelled, or a new dependency appears. A cancelled item remains visible for traceability but is removed from the gate's current scope. Without controlled updates, the MIDP quickly becomes an obsolete snapshot.
A well-maintained delivery plan does not remove a project's surprises, but it stops them from piling up unnoticed.
Sources
Does your organization need a tool adapted to its processes?
Tell us about the context, roles, deliverables and controls you need. SORA can help structure a tailored technical solution and define the right scope.
Discuss a tailored tool →Tags