# Decision Log

## 1. Project details

**Project:** \[Project name\]  

**Project manager:** \[Name\]  

**PMO / register owner:** \[Name\]  

**Review frequency:** \[e.g. weekly\]  

**Escalation route:** \[Committee / responsible body\]  

**Last updated:** \[Date\]

## 2. Decision overview – the master Decision Log

**This is the single working register.** Each decision has **one row**; its status, decision-maker, deadline and short outcome are maintained **here only**. Most decisions need no additional page.

| ID | Decision required / question | Decision-maker | Required by | Status | Impact of delay | Decision / outcome | Reference / link |
| --- | --- | --- | --- | --- | --- | --- | --- |
| DEC-001 | Approve the pilot at site A? | Steering committee | \[Date\] | Open | Pilot start may slip | – | – |
| DEC-002 | Use centralised or local testing? | Project manager | \[Date\] | Under review | Testing plan depends on it | – | \[Optional detail page DEC-002\] |
| DEC-003 | Approve additional testing resources? | Department head | \[Date\] | Decided | Testing schedule affected | Two testers approved | – |

**Status definitions**

- **Open:** Decision need recorded; active clarification has not yet started.
- **Under review:** Options, input or approval are being considered.
- **Decided:** Decision made; record the short outcome and, where useful, its date.
- **Deferred:** Decision deliberately postponed; set a new review date.

**How to use it:** Add one row for each decision → name the decision-maker, date and impact → review the status regularly → record the outcome and link any resulting actions. For extensive supporting material, use the reference column.

## 3. Optional: detailed decision record on a child page

> **Use only when needed.** For larger, more complex or consequential decisions, create a **child page** under the Decision Log page. Copy the block below into that child page and replace the placeholders. Link the page from the relevant row in the register under **“Reference / link.”**
> 
> **Important:** The overview in section 2 remains the **single source of truth for status, owner, due date and short outcome**. A detail page adds background, options, evaluation and decision rationale. Do not maintain the same operational fields in two places. **No automatic synchronisation** is configured.

### Child-page copy template: DEC-XXX – \[Decision title\]

**Decision ID:** DEC-XXX  

**Decision question:** \[What exactly needs to be decided?\]  

**Background / context:** \[Why is the decision needed?\]

**Options and assessment**

| Option | Advantages | Disadvantages / risks | Effort / impact |
| --- | --- | --- | --- |
| A – \[Label\] | \[Benefits\] | \[Drawbacks\] | \[Impact\] |
| B – \[Label\] | \[Benefits\] | \[Drawbacks\] | \[Impact\] |

**Project team's recommendation:** \[Recommended option and rationale\]

**Supporting information:** \[Links to documents, risks, Jira issues and approvals\]

**Decision rationale / supporting record:** \[Why was this option chosen? Where is the formal approval recorded?\]

**Consequences and follow-up actions:** \[Impacts, action items and links to their main tracking location\]

**Back to the master register:** \[Link to Decision Log overview\]

*Keep current status, decision-maker, due date and short outcome in the main register only. This detail page provides supporting context.*

## 4. Using the template in Confluence

1. **Copy** this page into your project space and replace the fictional entries in section 2.
2. Add one new register row for each decision.
3. **Optional:** For complex decisions, create a child page, copy only the section 3 record into it and link it from the register.
4. Remove or collapse the example template block on your project page if preferred; it is **not a second register**.
5. Confluence status macros and Jira links may be added as required; this template includes **no automated metrics or Jira integration**.

## 5. How it differs from Excel

Both formats provide the same core register. The Excel version adds dropdowns, due-date calculations and summary metrics. Confluence provides a shared project page and optional linked detail pages. The two versions **do not synchronise automatically**.