Before signing
Sam turns the bid's plan into the confirmed one: real names, real systems, this job's details. The client agrees it, it's signed into the appointment, and once we've won it's issued as C01.
Sam's journey · On the job (delivery) · Lesson 2
The plan grows up
Before you start
In the story
The plan everyone works to was never written down. The one that was written down, nobody works to.
Back to the story
The right way
Alongside it
Sam hands every team the rulebook from the client (with the changes we proposed in the BEP), plus our own step-by-step work instructions. Those instructions are the part that gets better every week.
Month two
Sam: Rulebook, page 2.
One answer.
Filed under TENDERThree versions of the rules, and the real plan written backwards.
Confirmed, plus a rulebookThe promise agreed before signing, issued at C01, and one rulebook everyone works from.
Think like Sam
Two questions for your job: what did we promise the client, and where does a new starter find out how we do things here? If both answers are the same 90-page document, nobody's reading either.
Continue Sam's journey
Story 3: Who makes what, and when
The delivery plan lists two hundred drawings. It was last opened at tender.
The right way, explained
The bid's plan is the town's planning application. Once it's granted, it's the permission: you build what was agreed, and changes go back to the planning office. How the builders actually work, day to day, is in the rulebook, and the rulebook gets better every week.
If you're the project manager
Know what we promised, because you'll be held to it, and changing it means asking the client first. For how things are done day to day, point people at the rulebook, not the plan.
In the town See it in the town: the promise and the rulebook. Which one changes every week?
Sam's view: the same delivery team the bid promised, now with real names. The promise is signed into the appointment and only changes if the client agrees.
Solid lines. What's needed, and the information that comes back.
Dotted lines. Lead firms coordinating with each other.
Pick a groupWho works for whom
The client
- In the picture
- ISO 19650 calls it
- Watch out for
This is the confirmed BIM Execution Plan (BEP)!
The promise, agreed with the client and signed in. The how lives in the rulebook.
For the audit What the auditor will ask
- Show me the confirmed plan, the appointment it forms part of, and its C01 issue.
- How is the plan changed, and where are the procedures your teams follow?
For the audit What good evidence looks like
- The confirmed plan, agreed by the client and part of the appointment.
- Every change to it, agreed before it was made.
- The project standard and procedures, issued to every team.
ISO 19650 Confirming the plan
ISO 19650 expects the plan from the bid to be confirmed with the real team and agreed with the client before the appointment is made, so it forms part of the appointment. Changing it after that is a change to what was agreed. InfoTown's practice: before signing, the plans are proposals at P revisions; once you've won, they're updated and issued formally at C01. The step-by-step how sits in the project's information standard and its production methods and procedures, which can be improved as the job goes.
| Confirm | In plain words |
|---|---|
| The people | Named, current, and still on the job |
| The approach | Which ways of working we picked, and why |
| Change control | Agreed with the client before anything changes |
| The how | In the rulebook: the standard and the procedures, issued to every team |
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.