Completix

Contact
RAID Logs

Every risk, action, issue, and decision, on the record and owned

Four logs, one for each kind of record, kept current on the project. Every item has an owner, a date, and a status, so nothing lives in meeting minutes, chat threads, or someone's inbox.

Get started Talk to us
Decision Log CRM Replacement Program
Risks Actions Issues Decisions
Phase 2 modules moved to post go-live Steering Committee · 03 Jun
Logged
Approve vendor for data migration A. Lindqvist · 21 May
Logged
Adopt a phased cutover over big bang Steering Committee · 14 May
Logged
Freeze scope ahead of UAT M. Rossi · 28 Apr
Logged
The discipline

Four logs, one for each kind of record

In Completix, RAID brings risks, actions, issues and decisions into one connected project record, not four scattered spreadsheets. Each record type tracks a different part of the project, kept in one place, owned and current, instead of buried in minutes, chat, and email.

Risks

What might go wrong, before it does. Logged, owned, and given a mitigation plan as part of project risk management, while you still have time to act.

Actions

The work that has to happen, and who owns it. Assigned with a due date and tracked to done, not lost when the meeting ends.

Issues

What has already gone wrong and needs resolving now. Logged with an owner and tracked until it is closed.

Decisions

The calls you made and why. Recorded with the rationale and what was considered, so they hold up when someone asks later.

Scenario one

Six weeks later, the sponsor asks why you descoped it

The steering committee agreed to push two modules to post go-live, a call made within the program's portfolio governance. The reasoning made sense in the room. Now a sponsor wants the justification, and the minutes are buried in someone's inbox.

When the decision is logged with its rationale and the options that were weighed, the answer is one record away. Not a memory, not a forwarded email thread.

  • Who decided, and on what date
  • The rationale in plain language
  • The alternatives that were considered
Decision Logged

Phase 2 modules moved to post go-live

Decided bySteering Committee
Date03 Jun 2026
Rationale

Vendor API limits put the full scope at risk for the go-live date. Deferring reporting and bulk export protects the launch window without affecting core migration.

Alternatives considered
  • Hold full scope and move the go-live date
  • Add a second integration vendor mid-project
System of record

A log lists what happened. A system of record proves it.

The difference is not the list. It is what each item carries with it, and where it connects. In Completix a RAID log is not a side document, it is part of the project.

Owned and dated

Every item has an owner, a date, a status, and a full history of what changed. Accountability is built in, not added later.

In one place

The log lives on the project, not in minutes, chat threads, and inboxes. One source the whole team works from.

Defensible

Decisions are recorded with their rationale and the options weighed, so the call holds up when someone asks months later.

Issue Open

Legacy export failing on custom fields

OwnerD. Okafor
SeverityHigh
Raised06 Jun 2026
Target12 Jun 2026
Activity
06 Jun, raised from standup, assigned to D. Okafor
08 Jun, vendor confirmed a field mapping bug
09 Jun, fix scheduled for the next data sync
Scenario two

The blocker everyone mentioned but nobody owned

The legacy export keeps failing on custom fields. It came up in standup, again on a vendor call, and across three chat threads. Everyone knows about it. No one is clearly on the hook to fix it.

Logged as an issue, it gets a single owner, a severity, and a running record of every update until it is closed. The blocker stops living in conversations and starts moving toward done.

  • A named owner, so it is clear who is driving it
  • Severity and status visible to everyone on the project
  • A running update trail from raised to resolved
Scenario three

Eleven actions came out of the gate review. Now what?

Every governance review ends with a list of things to do. Two weeks later the real question is simple, which ones are done, which are overdue, and who is stuck. The answer should not require chasing people for updates.

Actions logged against their source carry an owner, a due date, and a status you can see at a glance. Overdue items stand out, so follow-up is a decision you make, not a surprise you discover.

  • Filtered to the source that created them
  • Overdue items visible without a status meeting
  • Owner and due date on every single one
Actions From: Gate 2 review
ActionOwnerDueStatus
Sign off data mappingM. RossiJun 04 Done
Refresh UAT environmentA. LindqvistJun 14 Overdue
Confirm cutover windowD. OkaforJun 18 In progress
Draft rollback planP. SinghJun 21 In progress
Brief support on Phase 2 scopeS. HaddadJun 25 Not started
What every record carries

The detail that makes the log worth keeping

Owner and accountability

Every risk, action, issue, and decision has a named owner. No orphaned items.

Due dates and overdue visibility

Dates on every item, with overdue status surfaced so nothing slips quietly.

Color-coded at a glance

Type and status are color-coded across the log, so the state of the project reads in seconds.

Full activity history

Every change is recorded, so you can see how an item moved over time.

Filtered views

Slice the log by type, owner, status, or source to focus on what matters now.

Export for governance

Pull the log for a gate review or an audit without rebuilding it by hand, and feed the same records into project status reporting instead of updating two places.

Because RAID records stay connected to the project, the same delivery context can surface in portfolio reporting without rebuilding the story in another spreadsheet.

RAID Logs

Keep one honest record of the project

See how Completix keeps risks, actions, issues, and decisions connected, owned, and ready when someone asks.

Get started

Recommended Resources

user adoption

Why User Adoption Beats Features in PPM Software

Most PPM rollouts don’t fail from missing features, they fail because updating the tool takes longer than the workaround. Here’s what actually drives adoption, and how Completix keeps status reporting fast enough that people use it.