Decision Log in Confluence: Record Project Decisions
Keep a decision log in Confluence so the team never argues about the same thing twice: the date, the decision, why, and who owns it. Add a new decision to a real project page.
Step by step
Why a decision log
- Decision log. 3 weeks after a meeting, people forget what was decided and why. A decision log fixes that. Here we add a new decision to a project's log in Confluence.
- Four columns. The log is a table on a Confluence page. Each decision gets 1 row, and there are 4 columns: the date, the decision, why it was made and who owns it.
Add a decision
- Edit. Click Edit to open the page in the editor.
- New row. Click inside the last row of the table. Then press Ctrl+Alt+Down arrow. Confluence adds an empty row below it, ready for the new decision.
- The date. In the date cell, type the day the decision was made: 10 Oct 2026.
- The decision. In the decision cell, write the decision as 1 sentence: Saving to a wish list needs a signed in shopper.
- Why. In the why cell, give the reason: A list must belong to an account. This is the column people will be grateful for later, when someone asks to change the decision.
- Owner. In the owner cell, name the person who made the call: Product owner.
Share it
- Update. Click Update to save the page, so everyone on the team can see the change.
- In the log. The new decision now sits in the log. Link to this page from your meeting notes, so every decision has 1 home.
Recap
- Date, decision, why, owner. Keep 1 row per decision with 4 parts: the date, the decision in 1 sentence, why, and who owns it. Add the row on the same day you decide.
Common mistakes
- Leaving the why column empty. Without the reason, people argue the same point again a few weeks later. Write 1 short sentence on why, like A list must belong to an account.
- Adding decisions days later. By then the date and the reason are already fuzzy. Add the row on the same day, straight after the meeting.
- Decisions spread across meeting notes. When decisions sit on many different pages, nobody can find the final answer. Keep them all in 1 log page, and link to it from each set of meeting notes.
- An owner like the team. If nobody in particular owns the decision, nobody can confirm or change it. Name 1 role or person, such as Product owner.
When a business analyst uses this
In a requirements workshop, the stakeholders agree that only signed-in shoppers can save to a wish list. The BA adds that row to the decision log the same day and links it from the workshop notes. When someone asks for guest wish lists before sign-off, the why column shows the reason and the owner shows who to ask.
Questions people ask
How do I create a decision log in Confluence?
Make a page with a table that has 4 columns: date, decision, why and owner. Add 1 row for each decision, then click Update to save it for the team.
What should a decision log include?
The date the decision was made, the decision in 1 sentence, the reason for it, and the person who owns it. The reason matters most, because it stops the same debate from starting again.
Is a decision register the same as a decision log?
Yes. They are 2 names for the same thing: 1 place that lists each project decision with its date, reason and owner.
