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.

The registers

Every project has these registers:

Register	What it holds
Actions	Tasks someone owns, with an owner and status
Risks	Things that might go wrong
Issues	Things that have gone wrong and need handling
Decisions	Choices that were made, with their context
Meetings	Meeting notes, with their actions and decisions extracted
Stakeholders	People and organisations who bear on the project
Contacts	Everyone the project has come across, promoted into Stakeholders one by one
Financials	Invoices, payments, change orders, commitments, budget updates and forecasts

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

Note

Contacts and Stakeholders are two views of one set of people, not two lists — see Contacts. Newly-ingested people arrive as contacts; you promote the ones who are genuinely stakeholders.

Note

Register names follow your project’s methodology. An Agile project, for example, calls the issue register Impediments and the action register Tasks; an ISO 19650 project calls stakeholders Parties. Only the displayed wording changes — the underlying register is the same.

How items get into a register

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.

Versions and relationships

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.