Appointing-party information delivery planning — ISO 19650-2

Client decisions, not models, drive information requirements.

• Tie each information requirement to a decision the client must make (§5.1)
• Set the project information standard and production methods once, for all appointments
• Procure reference information (surveys, existing-asset data) before appointing designers

What tenders omit, variations supply — expensively.

• Issue exchange information requirements with every invitation (§5.2)
• Require pre-appointment BEPs and judge them on capability evidence
• Keep requirement language testable: a bidder should know what acceptance means

Each appointment plans its own delivery; only the appointing party sees the whole.

• Review MIDPs together: sequencing, shared dependencies, common milestones (§5.4)
• Make inter-appointment information dependencies explicit and owned
• Synchronise milestone calendars before mobilisation completes

Acceptance discipline early sets the cost of quality for the whole project.

• Review against the exchange information requirements, clause by clause (§5.7)
• Reject precisely — name the requirement, not the feeling
• Track acceptance metrics per appointment as a leading indicator

The project ends; the information does not.

• Map accepted deliverables to asset information requirements (ISO 19650-3 handshake)
• Archive the project information record with provenance intact (§5.8)
• Debrief appointments on information performance, not just programme