Coulter BIM Information Management

When working in the world of BIM and information management, one of the most common misconceptions I come across is the misuse of the Task Information Delivery Plan (TIDP). It’s often promoted—or worse, implemented—as a document register or issue sheet. While it may look like one on the surface, this fundamentally misses the point of what a TIDP is meant to do.

A TIDP is a delivery plan, not a record of what’s been issued.

Its core purpose is to outline what will be delivered, by whom, and when, to support the overall project milestones. It’s a forward-looking tool—one that helps teams plan, coordinate, and manage their contributions to the project information model. In contrast, a document register is a backward-looking tool, recording what has already been published or issued. Confusing the two can quickly create problems with accountability, coordination, and clarity of scope.

Another common misunderstanding is the obsession with individual file-based listings. Many assume that a TIDP must include every single drawing, model file, or document separately. While this level of granularity may be appropriate in some cases, TIDPs can also be package-based, grouping multiple deliverables into manageable units. This can drastically reduce administrative burden, especially on large or fast-paced projects. It also better reflects how information is often created, reviewed, and delivered in real-world design and construction workflows.

An additional layer of confusion comes from the terminology of “files” versus “information containers.” In line with ISO 19650, the emphasis should be on information containers, not just “documents” or “drawings.” An information container could be a model, a schedule, a specification, or a drawing sheet—essentially anything that carries project information in a structured, exchangeable form. Focusing solely on traditional document formats (like PDFs) risks overlooking valuable structured data that is just as important, if not more so, in a digital delivery process.

To sum up:

A TIDP is not a record of issued files—it’s a plan for what will be delivered.

It can be structured by packages, not just individual files.

It should reflect information containers, not just documents.

And crucially, it plays a key role in coordinating responsibilities and planning project information delivery.

Clarity on these points makes for more effective information management and helps ensure that teams are aligned with the intent and structure of ISO 19650 processes.