コンテンツにスキップ

Registers overview

このコンテンツはまだ日本語訳がありません。

A register is a list of one kind of project record — for example the risk register or the decision register. Each entry in a register is an artefact: a single item (one risk, one decision, one action) extracted from a communication. See the Glossary for these terms.

Every project has these registers:

RegisterWhat it holds
ActionsTasks someone owns, with an owner and status
RisksThings that might go wrong
IssuesThings that have gone wrong and need handling
DecisionsChoices that were made, with their context
MeetingsMeeting notes, with their actions and decisions extracted
StakeholdersPeople and organisations involved in the project
FinancialsInvoices, payments, change orders, commitments, budget updates and forecasts

In the project sidebar these all sit together as a flat list under Knowledge.

You don’t fill registers in by hand. Whenever a connected source brings in a communication — an email, a meeting transcript, a Slack message, a document — ddx PMO reads it and pulls out any register-worthy items. One message can produce several: a single email might add a stakeholder, record a decision, and raise an action all at once. Each item is routed to its own register.

When the system is confident enough, the item is added to its register straight away. When it’s less sure, the item waits in the project Inbox under Needs attention, where you confirm or correct it before it’s added.

Registers don’t just stack up rows. When a later communication updates an earlier one, the new entry supersedes the old; near-identical entries are flagged as duplicates. By default a register shows the current version of each item, with superseded versions and duplicates grouped underneath — expand a row to see its history, or switch the view from Current to All to list every version. Each entry also links back to the source it was extracted from.