Information delivery under ISO 19650 is planned at two levels.
TIDP — task information delivery plan
Each task team (for example the structural engineers) writes a TIDP. It lists the information containers the team will produce — models, drawings, schedules, reports — with:
- a container name or number following the project naming convention
- the person responsible
- the milestone or date for delivery
- dependencies on other teams’ information
- the expected level of information need
MIDP — master information delivery plan
The lead appointed party combines all the TIDPs into the MIDP. It is the delivery team’s master schedule of information, aligned with the project programme. Building it reveals dependencies and conflicts: the MEP model at stage 4 depends on the architectural model being shared first; two teams cannot both wait for each other.
Requirements flow from the client’s needs into the EIR; the delivery team answers with the BEP and delivery plans.
Why coordinators should care
- Coordination cycles depend on models being shared on time. The MIDP shows whether a model is actually late.
- Clash issues often need information from another team. The MIDP shows when it is planned.
- Comparing planned and actual delivery is a simple, honest measure of project health.
Keep the MIDP live. A delivery plan written once at the start and never updated quickly becomes fiction.