Project and program registers and the importance of linking

Most project professionals are familiar with RAID - Risks, Assumptions, Issues and Dependencies are fundamental controls. A well-managed RAID log helps project teams identify uncertainty, surface problems early and understand what may affect delivery.

But on complex projects, RAID alone is rarely enough. A risk register may identify a threat. An issue log may record that the threat has occurred. An action register may list what needs to happen next. A change request may capture the impact on scope, schedule or cost. A communications plan may identify who needs to know.

The problem is that these records are often managed separately. The result is fragmented project control. Information exists, but the story is difficult to follow. Sponsors receive updates without seeing the connection between an early assumption, an emerging risk, a realised issue, a decision, a change and the eventual impact on benefits.

That is where B-RADICAL provides a more complete approach.

team collaboration session

RAID is a starting point, not the whole control system

RAID remains useful. It provides a practical foundation for identifying and managing the immediate factors that may affect delivery. However, projects do not succeed merely by recording risks and issues.

They succeed when leaders can make timely decisions, teams complete agreed actions, stakeholders understand what is changing, and benefits remain visible from the business case through to post-implementation review.

B-RADICAL extends the RAID concept by connecting ten essential project controls:

• Benefits

• Risks

• Actions

• Dependencies

• Decisions

• Issues

• Communications

• Changes

• Assumptions

• Lessons

And yes you could write this as B-RADDICCAL however there may be other lists such as a schedule that could be included so we have kept it as B-RADICAL. The real value is not in creating ten more registers it is linking them.

From lists of information to a connected delivery narrative

A project register should not be a static list that is updated before a governance meeting and then forgotten.

Each item should help tell the delivery story, consider a simple example.

A business case may include an assumption that users will adopt a new system within six weeks of go-live. That assumption supports an expected benefit, such as reduced processing time, lower operating costs or improved customer experience.

However, a capability gap in training or business readiness may create a risk that adoption will be slower than expected. If that risk occurs, it becomes an issue.

The issue may require actions such as additional training, revised communications, local champions or extended hypercare support. It may also require a decision from the sponsor, a change request to approve additional funding or time, and an updated benefits forecast.

Once resolved, the experience should inform lessons learned for future projects.

Without linked controls, these events may sit across multiple documents, owned by different people and reviewed in isolation.

With B-RADICAL, they become one connected management story which enables the project team and sponsor to answer important questions quickly:

• What assumption did this issue challenge?

• Which benefit is now at risk?

• What decision is required, by whom and by when?

• Which actions are overdue?

• Does the issue require an approved change?

• Who needs to be informed?

• What should we learn and apply elsewhere?

woman writing notes

Why this matters for project sponsors and governance boards

Senior leaders do not need more project paperwork. They need clearer line of sight.

A connected B-RADICAL approach improves governance because it helps sponsors move beyond high-level status reporting and ask more meaningful questions, for example:

• Which benefits are most exposed to current risks and dependencies?

• Which assumptions remain unvalidated and could materially affect the business case?

• Which decisions are overdue and creating delay or uncertainty?

• Which changes have been approved, and what is their cumulative impact on scope, cost, schedule and benefits?

• Are recurring issues revealing a systemic problem in capability, governance, supplier performance or stakeholder engagement?

• What lessons are being embedded now, rather than simply recorded at project closure?

This is particularly important where a project appears green on a dashboard but underlying assumptions are weakening, decisions are being deferred or benefits are becoming less achievable. As bad news does not get better over time, a connected control system helps bring emerging concerns into view early enough for leaders to act.

business meeting group

B-RADICAL should be proportionate, not bureaucratic

The purpose of B-RADICAL is not to create administrative burden.

A small project may manage its controls in a disciplined Excel workbook. A major program may require integrated workflows, dashboards, escalation rules and automated reporting.

The principle remains the same: capture information once, maintain clear ownership, and link related items. At a minimum, each B-RADICAL record should include:

• A unique reference number

• Clear description and context

• Accountable owner

• Status and target date

• Impact on objectives, benefits, scope, schedule, cost, risk or stakeholder confidence

• Links to related B-RADICAL items

• Decision, action or escalation required

• Review date and governance forum

The links are critical because a risk should be able to link to relevant assumptions, dependencies, benefits and mitigation actions. If the risk occurs, the resulting issue should be linked back to the original risk. Any required decision, change, communications activity and lesson learned should then remain connected to that same delivery thread.

This creates traceability from the earliest business case assumptions through to benefits realisation and post-project evaluation.

filling checklist form

Moving from spreadsheets to intelligent workflows

Excel remains an effective starting point for many organisations. It is accessible, flexible and familiar to project teams.

However, as projects become more complex, manually maintaining multiple registers can become inefficient and unreliable.

Digital platforms can help organisations create a single source of truth. For example, Jira or SharePoint Lists, Power Apps, project portfolio management tools and approved workflow platforms can be used to manage B-RADICAL items, notify owners, track overdue actions, escalate decisions and provide live reporting via PowerBI.

Artificial intelligence can also assist by summarising trends, identifying recurring themes and preparing draft governance reports however, human judgement remains essential.

Project leaders need to validate the outputs, understand the context and ensure that the most material information is not missed. A concise automated summary is only useful when it reflects the real condition of the project.

Technology should improve visibility and reduce administration. It should not replace informed leadership, accountability or professional judgement.

business team discussion

Benefits should sit at the centre

One of the most important differences between RAID and B-RADICAL is the explicit inclusion of benefits. Projects are not undertaken simply to deliver outputs. They are undertaken to create value.

A new system, building, process, policy or operating model may be delivered on time and within budget, but still fail to generate the intended outcomes, by linking benefits to assumptions, risks, dependencies, issues and changes, project leaders can see whether the original value proposition remains credible.

This helps organisations avoid a common failure: treating benefits as something to review only at project closure because benefits should be actively managed throughout the lifecycle.

rising bar chart

B-RADICAL is a way of thinking

B-RADICAL is not simply an expanded acronym. It is a way of thinking about project control as an integrated system. It encourages project teams to connect decisions with consequences, risks with benefits, issues with actions, changes with communications and lessons with future practice.

When controls are connected, leaders gain a clearer picture of what is really happening, what matters most and where intervention is needed.

RAID remains valuable but for organisations seeking stronger governance, better traceability and greater confidence that projects will deliver their intended benefits, B-RADICAL provides the more complete framework.

office meeting discussion

At PMLogic, we help organisations strengthen governance, project controls, benefits realisation and delivery capability through practical frameworks, assurance and capability uplift.

The question is not whether your project has a RAID log, but the question should be if your project controls are connected strongly enough to support confident decisions and sustainable outcomes.

---

The PMLogic team have supported many organisations improve their transformation, portfolio, program and project performance but improving project controls.

We do this by facilitating discussion, coaching, training, establishing new practices, and contributing to strategy implementation practices, such as captured within PMLogic’s CEO’s book; The Strategy Implementation Gap.

Reach out to find out more.

Get in touch