*
en | de
Pro User
  • All of Microsoft
  • My Role
    • All in My Role
    • Pro User
    • Administrator
  • Focus
    • All in Focus
    • Microsoft Build 2026
    • Microsoft Copilot
    • All about AI
    • M365 Admin
    • What's Hot
    • M365 Release
Timespan
explore our new search
Project
Oct 26, 2026 9:04 PM

RAID Log Ownership Is Shared Across the Project

by HubSite 365 about Tech Tweedie

As we go beyond the low code, welcome to Tech Tweedie. Hosted by Ian Tweedie, this channel explores the Power Platform and other related technologies to extend the capabilities beyond the out of the b

Pro UserProjectLearning Selection

Tech Tweedie’s short highlights that a project manager may run the RAID process, while item owners and sponsors handle their own responsibilities.

Key insights

  • RAID commonly stands for Risks, Assumptions, Issues, and Dependencies.
  • The project manager typically maintains the process but does not own every entry.
  • Each log item should have a named owner responsible for progressing and updating it.
  • Sponsors or governance groups may own decisions beyond the project manager’s authority.
  • Some organizations use D for Decisions rather than Dependencies.

Tech Tweedie published a 22-second YouTube Short titled “Who REALLY Owns The RAID Log? It’s NOT Just The PM!” The available Short description contains no transcript, so its specific spoken wording and examples cannot be verified. The topic points to a useful distinction for project teams: a project manager can coordinate the log without being accountable for resolving every risk, issue, or dependency in it.

What's new

The Short frames RAID log ownership as broader than the project manager alone. RAID commonly refers to Risks, Assumptions, Issues, and Dependencies: a register that makes uncertainties, current problems, and cross-team handoffs visible.

That distinction separates three kinds of accountability. The project manager or delivery lead typically looks after the process, each entry has its own owner, and decisions requiring authority beyond the project manager may belong to a sponsor or governance group.

Why it matters

For project managers, process ownership means keeping the log accessible, setting up regular reviews, recording updates, and flagging overdue or escalating items. It does not mean personally carrying every action or being able to approve every response.

For makers, technical leads, business representatives, and functional managers, the approach makes responsibility more specific: an item should be assigned to someone positioned to take its next meaningful action. A sponsor or steering committee may need to decide matters such as scope, funding, deadlines, or accepting a risk.

This division can also clarify supplier dependencies. A provider may deliver the work, but the project should still have an internal person monitoring the dependency and raising a delay when needed. The research notes describe these as general project-management practices, not as a Microsoft product feature or a change to project software.

How it works

A RAID entry commonly records its category, description, impact, named owner, next action, due date, status, and review date. Teams can use those fields to see who is moving an item forward and what needs attention.

  1. Agree on what each RAID category means; in some organizations, D means Decisions instead of Dependencies.
  2. Assign a named owner to each item, choosing someone able to take the next meaningful action.
  3. Have the owner update the status, coordinate actions, and escalate when necessary.
  4. Use the project manager’s review process to surface overdue items and decisions that need higher authority.

Limitations and open questions

The source is a short clip, and its published description provides no transcript or operational details. The broader ownership explanation comes from the supplied research notes; the clip itself cannot be checked for specific examples or a step-by-step demonstration.

No software, template, licensing requirement, or rollout information is specified. The meaning of D can vary, so teams should confirm their own definition rather than assume every RAID log tracks the same categories.

Sources

Frequently asked questions

Does the project manager own every item in the RAID log?

Not necessarily. The project manager typically owns the process, while each entry should have its own named owner.

Who should own a decision the project manager cannot approve?

The research notes say decisions involving matters such as scope, funding, deadlines, or risk acceptance may require a sponsor, steering committee, or other governance body.

Does the D in RAID always mean Dependencies?

No. Some organizations use D for Decisions, so the project team should agree on the definition.