InfoTown™
Sam's journey · On the job (delivery) · Lesson 3

Who makes what, and when

Before you start

In the story

Two hundred drawings planned, one fence nobody asked for, and the one that mattered on nobody's list.

Back to the story

The right way

Before signing

Before the contract is signed, each team writes its own plan: what it'll make, when, and who's doing it.

Before signing

Sam rolls them into one master plan, lined up with the build programme, with who produces each piece, and when, written down team by team. Both go into the appointment.

Month two

Issued at C01 after award, the plan stays live. When the programme moves, the plan moves. The inlet chamber drawing arrives a week early.

Opened at tenderA fence nobody asked for, and the drawing that mattered on nobody's list.
Kept liveEvery team's plan in one master, lined up with the programme.
Think like Sam

Pick the next three things site needs. Are they on the master plan, with a firm, a person and a date? If not, that's this week's job.

Continue Sam's journey

Story 4: Ready before day one

The bid had a mobilisation plan. Now somebody has to actually do it.
The right way, explained

The right way, explained

The parts list for the town: what's being made, by whom, and when it has to arrive. A parts list written at tender and never opened is a wish list, not a plan.

If you're the project manager

If you're the project manager

The master delivery plan should sit next to your programme. If one moves and the other doesn't, ask why.

In the town See it in the town: every team's page of the parts list. What happens when you join them up?

Sam's view: every team's page of the parts list, joined up into one, and lined up with the programme.

Show:
The need, travelling from the client to the design team and the site team On the left, the Client Town asks "What are we building?". The need travels to the project site. From there it splits: up to the Design System, where Alex plans 40 drawings and starts designing in the work-in-progress room, and down to the site cabin, where Dave lists detail drawings, RFIs and inspections to prove the work is right. CLIENT TOWN "What are we building?" THE NEED PROJECT SITE PROJECT CDE DESIGN SYSTEM WORK IN PROGRESS WE NEED: ☐ 40 drawings☐ 3 models☐ 1 design report Who · by when "OK, we need 40 drawings. Let's plan it." SITE CABIN WE NEED: ☐ 6 detail drawings☐ RFIs for any issues☐ 9 inspections to prove it's right "Details, RFIs and inspections to prove it."
The need, turned into a plan. Who makes what, and by when.

These are the Task and Master Information Delivery Plans!

Each team's page of the parts list, put together into one.

For the audit What the auditor will ask
  • Show me the master delivery plan, and how it lines up with the programme.
  • Show me who's responsible for one item, and how you know.
For the audit What good evidence looks like
  • Each team's delivery plan.
  • The master plan with dates.
  • The responsibility matrix.
  • Updates over time.
From the standard
ISO 19650 Delivery plans and who does what

ISO 19650 expects each team to plan what information it will produce and when, and the lead firm to roll those into one master plan, alongside a detailed matrix of who is responsible for what. All of it is done before the appointment is made, so it forms part of the appointment.

ExpectIn plain words
Team delivery plansEach team's list: what, when, who
The master delivery planAll of them together, lined up with the programme
The responsibility matrixWho produces each piece, and when (the procedures say who checks and approves)
Kept liveUpdated whenever the programme or the scope moves

Based on the ISO 19650 series: the ideas come from the standard; the plain-English wording, examples and advice are InfoTown's. ISO 19650 is © ISO and BSI. You'll hear the same language across the industry. Read more for free in the Information Management Initiative (IMI) Framework guidance from BSI and nima. For the full requirements, use the standard itself.