A decision log helps when someone asks, “Why did we choose this?” Write down the choice, the reason, who owns it and when it should be reviewed. A Markdown file is a simple place to keep that record alongside your project notes.
You can create and preview the file locally in Ulet. Start with decisions.md, then give each decision a short, stable ID.

Keep enough context to understand the choice after the meeting is over.
Use this entry as a starting point
## DEC-014 — Review small changes weekly
Status — Active
Date — 2026-11-05
Owner — Maya
### Decision
Review small changes every Thursday for the next month.
### Why
Small changes are waiting too long for a monthly review.
### Alternatives considered
- Keep the monthly review.
- Hold a short weekly review.
### Consequences
The review lead needs a reserved weekly time slot.
### Review trigger
Revisit after four review cycles.
### Evidence
[Notes from the scheduling discussion](review-notes.md)
The people and situation here are sample content. Replace the reasoning with what your group actually discussed. If you keep the example link, create review-notes.md beside the log or replace it with an existing source.
Record the reason while it is still fresh
“We chose option B” will be hard to interpret later. “We chose weekly reviews because small changes were waiting for the monthly meeting” explains the trade-off. Include the constraint that mattered most and the alternative you set aside.
You rarely need a transcript. A few accurate sentences are more useful than a long discussion summary that leaves the choice unclear.

The alternatives and review trigger help a future reader reassess the choice.
Keep decisions and actions separate
A decision might be to hold weekly reviews. An action is for Maya to book the room by Tuesday. Put the action in your task list and link to it if needed. The decision entry explains the ongoing choice, so it should still make sense after that booking is done.
When a decision changes
Add a new entry explaining the replacement choice.
Link the new entry to the earlier decision.
Mark the earlier entry as superseded and point to the replacement.
Keep the original reason, so readers can follow what changed.
For example, a weekly review could become a twice-monthly review after the queue gets smaller. That is easier to understand when both entries retain their dates and reasoning.
Review the log with the project
Choose review triggers you can recognize, such as a milestone, a change in constraints or four completed review cycles. During the review, check which active decisions still fit the situation and which need an update.
Markdown headings and links make a short log easy to navigate. Ulet's source and preview views let you check the structure while the file stays in your local project folder. Write and preview Markdown in Ulet.
New to the syntax? The local Markdown writing guide explains headings, links and preview checks.



