This video covers how to track BIM deliverables and project progress using connected ISO 19650 workflows. The written guide below explains why progress tracking breaks down after contracts are signed, how TIDPs and MIDPs should remain connected to live delivery, and how centralized Kanban boards, timeline views, and filtered task updates replace the chasing of emails, spreadsheets, and disconnected to-do lists.

Why connected progress tracking changes project outcomes

Setting clear requirements and getting them into a contract is essential, but it is only the beginning. The real challenge starts the moment the contract is signed and multiple teams go off to deliver. In most projects, that is exactly where visibility breaks down. Architects maintain one list, contractors maintain another, consultants track their own deliverables somewhere else, and none of those lists are clearly connected back to the TIDPs, MIDPs, or the contract requirements that everyone agreed to. The result is that teams work in silos, deadlines are missed without warning, and updating the project plan feels like detective work.

The root cause is not a lack of discipline. It is that traditional progress management relies on disconnected tools. When each team maintains their own spreadsheet or to-do list, there is no single source of truth for the project. Status updates travel through emails, meeting minutes, and chat threads, and by the time someone compiles them into a report, the information is already out of date. That disconnect between what was contractually agreed and what is actually being tracked creates confusion, duplicate effort, and disputes that could have been avoided with better visibility.

A connected tracking workflow solves this by keeping the master information delivery plan at the centre of project delivery. The MIDP brings together the task information delivery plans from all teams into a unified view of what needs to be delivered, by whom, and by when. In Plannerly, this is not a static document that gets filed away after signing. It remains a live, interactive view where teams can update their own progress, attach deliverables to tasks, and move items through statuses as work progresses. Because every task is linked back to the original contract requirement, teams are not just updating random lists. They are proving that they have fulfilled their contractual obligations.

The timeline view adds another layer of clarity by showing dates, dependencies, and handoffs between teams. When one team’s output is a dependency for another team’s start date, that relationship is visible to everyone. There is no ambiguity about who is waiting on whom, and reforecasting becomes possible before a missed deadline cascades into a larger problem. The Kanban board provides a complementary view where teams can see their filtered tasks and drag them through statuses, from proposed to in progress to completed to verified, with each update visible to everyone on the project in real time.

How to set up connected delivery tracking

1. Keep the MIDP live after contract signing – Rather than filing the master information delivery plan as a static document, use it as the live tracking backbone where all team deliverables are monitored against the agreed requirements.
2. Connect TIDPs to the master plan – Ensure that each team’s task information delivery plan feeds into the MIDP, creating one unified view of all deliverables across the project.
3. Add dates and dependencies – Schedule your scope by assigning start and end dates and connecting dependent tasks so that handoffs between teams are visible and delays can be identified early.
4. Set up filtered views for each team – Use grid, timeline, and Kanban views with filters so that each team sees only their own deliverables while project managers retain the full picture.
5. Enable live status updates – Let teams update their own task statuses directly, reducing the need for email chasing and manual progress reports. Each status change is timestamped and visible to all stakeholders.
6. Attach deliverables to tasks – When a task is completed, attach the actual deliverable to the task record so that the output is connected to the requirement, the assignment, and the contract in a single traceable chain.
7. Review progress against milestones – Use the information exchange milestones to check whether deliverables are on track, and reforecast early when dependencies shift.

What you’ll learn

• Why tracking breaks down – How disconnected team lists and siloed progress management create confusion, missed deadlines, and duplicate effort after contracts are signed.
• Live MIDP tracking – How keeping the master information delivery plan connected to live task updates creates a single source of truth for the entire project.
• Timeline and dependency management – How visualising dates, handoffs, and dependencies in a timeline view helps teams plan, track, and reforecast delivery.
• Kanban-based progress updates – How a centralized Kanban board with filtered views simplifies status tracking and eliminates manual reporting.
• Contract-connected deliverables – How linking every completed task back to the original contract requirement improves accountability, reduces disputes, and supports on-time payment.

Common questions

Explore further

• The truth about CDEs and BIM tracking – Why traditional common data environments alone are not enough for effective delivery tracking.
• ISO 19650 information production schedule (IPS) – How the information production schedule connects to TIDPs and MIDPs in ISO 19650 delivery.
• Information verification, project tracking, compliance and lessons learned – Expert-level lesson on tracking compliance and capturing lessons across the delivery lifecycle.
• Part 5: Model verification and quality assurance – Continue to the next lesson on building confidence through automated model checking and QA workflows.