RAID Log Roles and Responsibilities: Who Owns What

## The short answer

In a healthy RAID log, ownership operates at three levels: the **PMO** owns the *process and standard* (the template, cadence and quality), the **delivery or project manager** owns the *log itself* (keeping it current and driving reviews), and a **named individual** owns *each entry* (driving that specific risk, issue or dependency to resolution). The cardinal rule is that every single item has one human owner, never "the team", never "TBC". Unowned entries are where RAID logs go to die.

## Why ownership is the make-or-break factor

A RAID log fails for one reason more than any other: items get logged but nobody is accountable for moving them. Clear ownership turns the log from a list of worries into a set of commitments. When you can point at a name next to every red risk, reviews become short and decisive instead of circular.

## The three layers of ownership

### 1. The PMO: owner of the process

The PMO (or its equivalent) is responsible for:

- Providing a **consistent template** and definitions so every project's log looks and works the same way.

- Setting the **review cadence** and the rules for escalation.

- **Assuring quality**: spotting stale entries, vague descriptions, missing owners and risks scored as everything-is-critical.

- **Rolling up** the most significant items into portfolio or board reporting.

The PMO does *not* own the content. It owns the conditions that make good content possible.

### 2. The delivery manager: owner of the log

The delivery, project or programme manager keeps the log alive day to day:

- Runs the **regular review** and chases updates beforehand.

- Ensures **new items are captured promptly** rather than at the end of the project.

- Confirms **every entry has an owner, a status and a recent update date**.

- Decides what gets **escalated** and feeds the highlights into status reports.

- Closes items that are genuinely done, so the log doesn't bloat.

### 3. The item owner: owner of the entry

Each risk, assumption, issue or dependency needs a single accountable person who:

- **Understands** the item and can explain it.

- **Drives the action**, mitigation or resolution.

- **Updates** the entry honestly between reviews.

- **Raises a flag** when the situation changes or help is needed.

The item owner is the person best placed to act, which is often *not* the project manager. A technical dependency might be owned by a lead engineer; a budget risk by the finance partner.

## Where the sponsor and steering group fit

The **sponsor** and **steering group** are consumers and decision-makers, not maintainers. Their role is to:

- Review the **top risks and issues** at a summary level.

- **Make decisions and unblock** items the team cannot resolve alone, particularly escalated dependencies that cross organisational boundaries.

- **Accept residual risk** where appropriate, on behalf of the organisation.

Escalation exists precisely because some items are above the pay grade of the item owner. A working escalation path is part of good ownership design.

## A simple RACI for the RAID log

- **Responsible** (does the work): item owners, supported by the delivery manager.

- **Accountable** (answerable for outcome): delivery/project manager for the log; sponsor for the project overall.

- **Consulted**: subject-matter experts, the PMO, third parties named in dependencies.

- **Informed**: steering group, wider stakeholders via reporting.

## Common ownership anti-patterns

- **"Owned by the team."** Diffuse ownership is no ownership. Name a person.

- **The PM owns everything.** This overloads one person and removes accountability from those best placed to act.

- **The PMO writes the content.** The PMO can't realistically know the detail of every risk; pushing content ownership onto it produces shallow, generic entries.

- **Owners who can't act.** Assigning an item to someone with no authority to resolve it just delays the inevitable escalation.

- **No closure owner.** Someone must decide when an item is genuinely done and close it cleanly.

At neart.ai we build enterprise-grade delivery and PMO products, and across delivery teams the single strongest predictor of a useful RAID log is unambiguous, individual ownership of every entry, backed by a clear escalation route when an owner gets stuck.

## Practical takeaway

Assign ownership at three levels: PMO for the process, delivery manager for the log, and one named individual for every entry. Banish "team" and "TBC" from the owner column, make sure each owner can actually act, and define the escalation path before you need it.