Information management during delivery — ISO 19650-2

Everything downstream prices and plans against this baseline.

• Derive project information requirements from organisational and asset information requirements (§5.1)
• Set the project information standard, methods and procedures
• Fix reference information and shared resources the teams will rely on

The tender response is where information management is priced — vagueness here becomes variation later.

• Require a pre-appointment BEP per §5.3 content headings
• Assess task-team capability and capacity with evidence, not assertion (§5.3.2)
• Surface the proposed federation strategy and mobilisation plan

The confirmed BEP turns tender intent into contractual commitment.

• Confirm the delivery team's BEP and the high-level responsibility matrix
• Embed the exchange information requirements in each appointment
• Cascade the information standard into every sub-appointment

Mobilisation is rehearsal, not paperwork: prove the CDE, the exchange formats and the people before production starts.

• Each task team owns a Task Information Delivery Plan
• Aggregate TIDPs into the Master Information Delivery Plan (§5.4.1)
• Test the CDE workflow end-to-end with a pilot exchange

Production quality is checked continuously, not at the milestone.

• Hold work-in-progress / shared / published container states (§5.6)
• Run quality assurance against the information standard before each shared transition
• Track delivery against the MIDP and surface slippage early

Acceptance is against requirements; close-out feeds the asset phase.

• Review deliverables requirement-by-requirement (§5.7)
• Transfer accepted containers toward the asset information model (ISO 19650-3 handshake)
• Archive and capture lessons learned (§5.8)