Unblockd

RAID log: create, maintain, and use for sponsor governance

A clear, copy‑paste RAID log template and step‑by‑step playbook for project and delivery leads to raise sponsor asks, keep items current, and record auditable decisions.

By the Unblockd team, edited by Patrick SaulPublished

A RAID log is the single register project leads use to track Risks, Assumptions, Issues, and Decisions or Dependencies and to prepare sponsor asks that are auditable. Use the RAID log as your source of truth for sponsor‑visible asks and status reports, and keep one canonical shared log the sponsor can view. (https://www.atlassian.com/agile/project-management/raid-log)

What is a RAID log?

A RAID log is the project register that groups Risks, Assumptions, Issues, and Decisions or Dependencies so a project lead can rank work that needs sponsor attention and prepare auditable approvals. Use the RAID log to present short sponsor asks and to link each ask back to evidence and a Decision ID for traceability. (https://www.atlassian.com/agile/project-management/raid-log)

What to do, say, and check:

Quick start, two actions to do now

Create a shared copy of the CSV template below and give sponsors view access, then before your next triage raise items using a short cause‑and‑effect description and assign Owner and Sponsor. Paste the template into your sheet, set view access for sponsors, and use the phrasing shown when you raise the first items. (https://thedigitalprojectmanager.com/project-management/risk-management-project-management/raid-log/)

Copy these two actions verbatim:

  1. "Paste the CSV RAID template below into a shared sheet and give sponsors view access." (https://thedigitalprojectmanager.com/project-management/risk-management-project-management/raid-log/)
  2. "Before the next triage, raise items using the description: Because [cause], the result could be [effect], and assign Owner and Sponsor." (https://asana.com/resources/raid-log)

Templates, paste-ready

The templates below are ready to paste into a sheet or document; every variable uses [bracketed placeholders] so you can copy and begin raising items immediately. (https://asana.com/resources/raid-log)

CSV (paste into a sheet)

ID,Category,Title,Description,Owner,Sponsor,Status,Likelihood,Impact,Score,Mitigation or action,Next review,Last Updated,Link to task,Decision ID,Notes
[ID-PLACEHOLDER],[Category],[Title],[Because ... result ...],[Owner Name],[Sponsor Name],[Status],[Likelihood],[Impact],[Score],[Mitigation action description],[YYYY-MM-DD],[YYYY-MM-DD],[https://...task-url],[Decision-ID],[Notes]

Markdown table (paste into docs)

ID Category Title Description Owner Sponsor Status Likelihood Impact Score Mitigation Next review Last Updated Link Decision ID Notes
[ID-PLACEHOLDER] [Category] [Title] [Because ... result ...] [Owner] [Sponsor] [Status] [Likelihood] [Impact] [Score] [Mitigation] [YYYY-MM-DD] [YYYY-MM-DD] [https://...task-url] [Decision-ID] [Notes]

Decision register CSV (paste into a sheet)

Decision ID,Date,Approver (name / role),Rationale,Scope,Consequences,Sign-off method,Linked RAID IDs,Linked deliverables,Notes
[DEC-PLACEHOLDER],[YYYY-MM-DD],[Approver Name / Role],[Short rationale],[Scope description],[Consequences summary],[Email / In-meeting / Board minutes],[ID-1; ID-2],[Deliverable-IDs],[Notes]

Decision register Markdown table (paste into docs)

Decision ID Date Approver (name / role) Rationale Scope Consequences Sign-off method Linked RAID IDs Linked deliverables Notes
[DEC-PLACEHOLDER] [YYYY-MM-DD] [Approver Name / Role] [Short rationale] [Scope description] [Consequences summary] [Email / In-meeting / Board minutes] [ID-1; ID-2] [Deliverable-IDs] [Notes]

Note: If your field values contain commas, enclose that cell in double quotes before pasting into Excel or Google Sheets.

What to change at kickoff?

At kickoff confirm the likelihood and impact scales, set escalation and monitor thresholds, and confirm sponsor view access for the shared RAID log so governance produces consistent sponsor asks and exports. Record these agreements in the Decision register and share them with owners to keep triage and escalation consistent. (https://www.atlassian.com/agile/project-management/raid-log)

Kickoff checklist to paste:

What should go in a RAID log?

A RAID log should include ID, Category, concise Title, a one‑sentence Description with cause and effect, one accountable Owner, Sponsor, Status, Mitigation or Next action, Next review, Last Updated, links to evidence or tasks, and an optional Decision ID for sign‑off traceability. Use these fields so your export columns match the governance pack. (https://asana.com/resources/raid-log)

How to fill fields and exact wording to paste:

  • ID: [ID-PLACEHOLDER]
  • Category: [Risk / Assumption / Issue / Decision or Dependency]
  • Title: [Short title]
  • Description: start with: "Because [cause], the result could be [effect]." (https://asana.com/resources/raid-log)
  • Owner: [Owner Name]
  • Sponsor: [Sponsor Name]
  • Status: use the exact values listed in the triage section below. (https://asana.com/resources/raid-log)
  • Mitigation or action: [Concrete next action and who will do it]
  • Next review: [YYYY-MM-DD]
  • Last Updated: [YYYY-MM-DD]
  • Links: [https://...task-url]
  • Decision ID: [Decision-ID]

Who owns RAID items and how should ownership work?

Each RAID item must have exactly one accountable owner who updates status, drives mitigation, attaches evidence, and prepares the short update the project lead will present at triage; the project lead enforces the single‑owner rule and logs any reassignment in Notes. Clear ownership keeps sponsor asks auditable and reduces confusion about who will deliver the next action. (https://asana.com/resources/raid-log)

Copy‑paste phrasing for owner assignment and reassignment:

How often should the RAID log be reviewed and who attends?

Review the RAID log on a fixed cadence tied to your existing meetings so owners update rows before triage and sponsors see only current asks; use a weekly tactical triage for owner updates and your governance meeting for sponsor approvals. Require owners to set Last Updated before the tactical triage so the project lead can present current items. (https://www.atlassian.com/agile/project-management/raid-log)

Cadence rules to paste:

How to present a sponsor snapshot?

Present a one‑line snapshot for each item requiring sponsor action that includes ID, Category, Owner, Status, Ask, Next review, and a link so the sponsor can approve quickly and your governance notes remain auditable. Send the snapshot by email before the governance meeting so the sponsor can prepare and the Ask wording matches the governance pack. (https://www.atlassian.com/agile/project-management/raid-log)

Copy‑paste email-ready sponsor snapshot:

[ID-PLACEHOLDER]: [Category] - [Title]
Owner: [Owner]
Status: [Status]
Ask: [Exact approval or sign-off needed]
Next review: [YYYY-MM-DD]
Link: [https://...task-url]

How do you score and triage RAID entries?

Score items with Likelihood and Impact and use a Score to rank items for sponsor review; agree the scales and escalation thresholds at kickoff so everyone applies the same rules when you decide which items escalate to the sponsor. Use the Score formula and thresholds you agreed at kickoff to set Status values for escalation and monitoring. (https://www.atlassian.com/agile/project-management/raid-log)

Scoring rule to paste:

Status field exact copy‑paste values and definitions (use these words verbatim in tools and exports):

Exact triage rules to paste:

Decision vs Dependency?

Use Decision for approvals, vendor or sponsor sign-offs, and policy choices that change scope; use Dependency for sequencing or external delivery constraints that must finish before your work begins. Record Decisions that require sign‑off in the Decision register so approvals are auditable and linked back to RAID rows. (https://www.atlassian.com/agile/project-management/raid-log)

What to do, say, and check:

How should decisions be recorded for audit and traceability?

Record decisions in a Decision register with Decision ID, Date, Approver, Rationale, Scope, Consequences, Sign-off method, and linked RAID IDs so approvals are traceable back to evidence and sponsor sign‑off is auditable. Link Decision IDs from RAID rows when you raise an Ask to the sponsor so governance notes the approver and method. (https://www.atlassian.com/agile/project-management/raid-log)

How to keep the RAID log from going stale?

Prevent staleness by enforcing owner updates before triage, requiring a Last Updated timestamp and attached evidence, and archiving closed rows so the active log stays focused on current sponsor asks; the project lead enforces these rules at the weekly triage. Require owners to confirm updates before the weekly tactical meeting so the sponsor sees only live asks. (https://asana.com/resources/raid-log)

How to archive (copy‑paste):

How to integrate a RAID log with your tools and status reports?

Add a custom field [RAID ID] to related tickets and populate it so you can filter and export the top items into a sponsor pack; link RAID IDs to tasks, change requests, and Decision IDs so updates flow into the log and the governance pack matches the source evidence. (https://asana.com/resources/raid-log)

One-line integration note to paste:

"Sign-up, workspaces, projects with deliverables, activities, tasks, evidence, blockers, risks, decisions"

How to use the template in five repeatable steps?

Create the RAID log in a shared location, raise items early with cause‑and‑effect descriptions, assign an owner, review on cadence, and close items with evidence attached so sponsor asks are traceable and auditable; repeat these steps before each sponsor meeting to keep governance consistent. Use the phrasing and templates above to make asks auditable. (https://www.atlassian.com/agile/project-management/raid-log)

Exact steps and phrasing to paste:

  1. "Create the RAID log in your shared project doc or sheet and give sponsors view access." (https://thedigitalprojectmanager.com/project-management/risk-management-project-management/raid-log/)
  2. "When raising an item, write the description as 'Because [cause], the result could be [effect]' and assign Owner and Sponsor." (https://asana.com/resources/raid-log)
  3. "Owners attach evidence and set Last Updated before triage." (https://asana.com/resources/raid-log)
  4. "PM sorts by Score and presents the top items with a single Ask for each to the sponsor." (https://www.atlassian.com/agile/project-management/raid-log)
  5. "On closure, the owner attaches evidence, sets Status = Closed, sets Last Updated, and the PM archives the row to the historical sheet with an archive note." (https://wisegrid.co/blog/raid-log/)

Questions people ask

What is the minimum info to raise a RAID item?

Raise a RAID item with an ID, Category, one‑line Title, a one‑sentence Description that follows 'Because [cause], the result could be [effect]', an accountable Owner, a Sponsor, Status, and a clear next action. (https://asana.com/resources/raid-log)

How long should closed RAID items be kept before archive?

Keep Closed items in the active sheet only while they are still relevant, then move Closed rows to a historical archive sheet on a regular cadence such as monthly; include an archive note showing who archived and a link to evidence. (https://wisegrid.co/blog/raid-log/)

How should I record sponsor backup or escalation contacts?

Record the sponsor and a named backup in the RAID or governance contact field and include an escalation note in Notes describing the backup contact method so you can escalate approvals when a sponsor does not respond. (https://www.atlassian.com/agile/project-management/raid-log)

Patrick Saul · Co-founder, Unblockd

Patrick Saul is a co-founder of Unblockd, AI-native project tracking and reporting built at Conversint Consulting in Austin, Texas.

Get the sponsor ask checklist

One screen to check before you send an ask: the decision, the options, the date, and what waits on it. Then one email a week with new guides.