Atlas
  • All-in-one
  • Solutions
  • Compare
  • Pricing
PricingGet started
  1. Atlas
  2. Guides
  3. A RAID Log People Actually Use
August 19, 2026·7 min read·Client Delivery, RAID, Risk Management

A RAID Log People Actually Use

A risk register that nobody reads is not a control. It is a document that makes everybody feel a control exists.

RAID stands for risks, assumptions, issues and dependencies, and most implementations of it are theatre. The register is populated in mobilisation, reviewed once, and produced at the end as evidence that risk was managed. Nothing in it changed a decision.

An owner is a person, not a workstream

A risk owned by "the delivery team" is owned by nobody. The single strongest predictor of a register being used is that every live entry has a named person and a review date, and that both are visible to whoever runs the weekly meeting.

Assumptions are the half everybody drops

Firms track risks and issues and quietly ignore assumptions, which is backwards: an assumption is a risk somebody has already decided not to test. Writing it down with a date to test it by is the cheapest control in the whole discipline.

The good ones are specific and falsifiable. "Client data is good enough" is not an assumption, it is a hope. "Client data is complete enough to answer the question, tested on a sample in week one" is one you can actually resolve.

The register has to reach the status report

Risks that never leave the register do not change anything. The weekly report should select its key risks from the live register rather than restating them, so the report and the register cannot disagree and the register earns a reason to be current.

Escalation before it is needed

Agree the escalation ladder at mobilisation, when nobody is defensive. Who hears about a risk at each severity, how quickly, and who can decide. An escalation path invented during an incident is negotiated rather than followed.

Starting from something rather than nothing

Atlas seeds a RAID register from the playbook an engagement starts from, so a technology implementation begins with the risks technology implementations actually have rather than an empty table. Those starters are a prompt rather than a substitute: the ones that matter on this engagement get added by the people doing it.

Keep reading

  • A Client Portal for Professional Services: What To Show, and What To Never Show
  • Engagement Change Control That Actually Protects Margin
  • The Engagement Closure Checklist: What Good Actually Looks Like
  • Engagement Management Software: What It Actually Has To Do
  • The RAID Register a Steering Committee Can Actually Read
  • Professional Services Automation: What To Look For, and What To Ignore
  • Free PDF tools
  • The all-in-one work OS

FAQ

Questions, answered.

What does RAID stand for in project management?
Risks, assumptions, issues and dependencies. A risk might happen, an issue already has, an assumption is something being relied on without testing, and a dependency is something outside the team control that the plan needs.
Why do RAID logs stop being used?
Usually because entries have no named owner and no review date, and because nothing in the register feeds anything anybody reads. A register whose risks are selected into the weekly status report has a reason to stay current; one that is only produced at the end does not.
What makes a good assumption entry?
It is specific, falsifiable, and carries a date by which it will be tested. "The client data is good enough" is a hope. "The client data is complete enough to answer the question, tested on a sample by the end of week one" is an assumption somebody can actually resolve.

Ready when you are

One workspace, not ten.

Atlas replaces the stack with one platform for tasks, projects, CRM, contracts, e-signature, PDF tools, and analytics. Start free.

Get started freeSee pricing
AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus