Owner Project Knowledge Mandate

# Owner Project Knowledge Mandate

Owners should define how project knowledge will be governed before design and construction information becomes fragmented. This model language can be adapted for an owner directive, procurement package, project charter or contract exhibit with advice from the owner’s procurement and legal teams.

Purpose

The project will maintain one owner-governed source of verified project knowledge from authorization through design, construction, commissioning, turnover and operations.

Core requirements

1. Owner control

The owner will retain control of the project record, including access, roles, permissions, retention standards and final disposition. No contractor or consultant platform will be the owner’s only means of retrieving required records.

2. One governed point of entry

Required project information will be submitted through a defined process. Email, meetings and other systems may support the work, but required records must be captured in the governed owner record.

3. Verification and accountability

Each required record will include, as applicable:

• Originator and responsible organization
• Date and time received
• Document type, status and revision
• Related contract, asset, room, system or decision
• Review, approval and distribution history
• Outstanding action, responsible party and due date

4. Independent administration

The owner may appoint an independent project-information governance provider to administer standards, verify completeness and report exceptions. This role does not replace the contractual responsibilities of the designer, contractor, commissioning provider or other participants.

5. Decision traceability

Changes, RFIs, submittals, meeting actions, schedule updates, payment support and field records must be connected to the evidence required to understand what changed, who acted and what remains unresolved.

6. Commissioning and turnover from Day One

Turnover will be treated as an ongoing process. Operations, maintenance, warranty, training and commissioning knowledge will be collected and reviewed throughout delivery—not reconstructed at project close.

7. Owner acceptance

The owner will define measurable knowledge-completeness criteria. Physical completion or file delivery alone will not constitute acceptance of the project record.

8. Long-term usability

The final record will be organized for future facility teams, renovations, audits and lifecycle decisions. The owner will receive access in a usable form consistent with agreed security and retention requirements.

Five decisions the owner should make now

• Who governs the record independently of the parties performing the work?
• Which documents and data are required, and when?
• How will completeness, accuracy and timeliness be measured?
• Who can see, change, approve and export each category of information?
• What must be proven before payment, substantial completion and final acceptance?

Recommended next action

Use this mandate as a starting framework—not legal advice. Align it with applicable contracts, procurement rules, cybersecurity requirements and records policies before adoption.

Want to turn this framework into a project-specific knowledge mandate? Talk to Shelley.