BuildBuild: Month seven…
Due
The parts list says when the valve chamber drawing was due: week 28.
Stage 5 · Build it · Stop 7 of 13 · The right way
Late, not extra
The back alley's bill so far: 117 weeks · See the bill
The right way
Arrived
The drawing arrives on the shared table three weeks late. The Site Office trail records exactly when, and who shared it.
BuildBuild: The claim…
Agreed
Kofi builds the delay claim from those two dates, in an afternoon. The client checks the same trail and agrees the time.
Kofi: Due 28, arrived 31. That's three weeks.
Six inboxesSix answers, two empty folders, and a claim that failed.
The trailTwo dates, one afternoon, and time agreed.
Now there is: The trail (the CDE audit trail): release dates on the parts list, arrival dates on the record, and a delay agreed.
What's going on here
When information is late, the cost is real, but it has to be proved. A parts list that says when each piece was due, and a Site Office that records when it actually arrived, turn an argument into two dates. Email can't do that: it scatters the proof across inboxes.
New at this stop
- The trail
- The record the Site Office keeps of who shared what, and when. (The audit trail.)
In the town See it in the town: Two dates settle an argument. Where do you keep them?
The parts list said when the valve chamber drawing was due: week 28. The trail in the Site Office says when it really reached the shared table, week 31, and who shared it. Put side by side, the two dates do Kofi's arguing for him. Email scatters the same facts across six inboxes and two emptied folders, and a fact nobody can find can't prove anything.
Fix it Arguing about a delay? Find the two dates first.
- Find the late item's due date on the parts list.
- Find its arrival on the Site Office trail, not in anyone's inbox.
- Ask every designer to share through the Site Office, not by email.
A note for the information manager: Keep the parts list dates current, because the trail can only prove lateness against a due date someone wrote down.
Try it on your job
Pick one drawing that arrived late on your job. Can you show the day it was due and the day it arrived?
ISO 19650 From the parts list to the trail
| ISO 19650 says | Means | In the town |
|---|---|---|
| Master information delivery plan (MIDP) | The plan of every piece of information the job will deliver, who delivers it and when | The parts list, with week 28 on it |
| Task information delivery plan (TIDP) | Each team's own share of that plan, with its dates | The designer's lines on the parts list |
| Common data environment (CDE) | The shared store, which keeps a record of each revision, its status, who changed it and when | The trail |
| Not from ISO 19650: the delay claim (extension of time) | A contract claim for more time, which needs proof of what was late and by how much | Kofi's afternoon with two dates |
Based on the ISO 19650 series: the ideas come from the standard; the plain-English wording, examples and advice are InfoTown's. ISO 19650 and its UK National Annex are © 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.