A home for project information

What you will understand

• Distinguish baseline information, evolving records and reports.
• Explain the purpose of management approaches and initiation documentation.
• Identify proportionate controls for digital tools and data across their lifecycle.

The idea

Project information should help people decide and act. A folder full of disconnected files can be less useful than a small, well-controlled shared workspace. The important questions are what the information means, who owns it, whether it is current and who has authority to change it. Digital tools support those arrangements; installing a tool does not establish them automatically.

Management products describe information used to manage the project, rather than the specialist products the project exists to create. They can establish an agreed reference, maintain an evolving record or communicate a particular view. For example, an approved plan provides a baseline, risk information evolves as uncertainty is assessed and a progress report communicates the position to a particular audience at a point in time.

A baseline is an agreed reference against which work and change can be assessed. It does not mean information can never change; it means changes follow the agreed authority and controls. Records such as risks, issues and lessons need active maintenance. A report draws on relevant information to support a decision or oversight. A report’s polished appearance does not prove its underlying figures are accurate.

Project initiation documentation brings together the foundations for managing the project and gives a basis for authorisation and control. It can be linked information rather than one enormous document. Management approaches explain the agreed way of working: responsibilities, procedures and techniques. The concerns include benefits, change, commercial arrangements, communication, digital and data, issues, quality, risk and sustainability. Live records show what has happened within those arrangements.

Digital and data management considers both the tools and the information those tools handle. Identify required data, its source, quality needs, ownership, access, storage and protection. Consider how it is shared with suppliers, how versions remain traceable and what happens after closure. A non-digital product still generates project information, while a digital product may also depend on specialist operational data that needs its own controls.

Use proportionate arrangements for accuracy, availability and security. Define who updates forecasts, when data is refreshed and how conflicting versions are resolved. Validate important assumptions before relying on an automated dashboard. Retain or dispose of information in accordance with relevant organisational and legal requirements, with clear ownership after handover. More data is not always better when it is unnecessary, unreliable or inaccessible to the people who need it.

Find the right information home

Points to remember

• Management information may be held in tools or linked records, not only documents.
• A baseline can change through authorised control.
• Data ownership and lifecycle arrangements matter beyond project closure.

Your takeaway

Organise information by purpose and decision need. Make approved references, changing records and reports distinguishable, and control the digital tools and data that connect them.