# Recording decisions (requirement calls and ADRs)

Decisions are recorded so that "why we decided that" can be checked later. There are two kinds of record.

## Requirement calls (hold for next time, out of scope this time)

**How far you build this time is settled on [Confirm scope](https://pmonrails.com/en/docs/scope.md).** These records
explain why the requirement cards that did not make it in were left out.

- There are two calls you can record: hold for next time, and out of scope this time. A reason is required.
- There is no "adopt" record. What went into this round is shown by the snapshot taken when the scope was confirmed.
- Open a requirement card and read its history tab to see who decided, when, and why.
- You can stack as many calls as you like on one card (held, then later ruled out), in order.
- A mistaken record is retracted rather than deleted, so the fact that it was taken back is kept too.

## ADR (architecture decision record)

![PM on Rails architecture decisions. Numbered decisions and their status. Before: why you chose it vanished in chat. After: you can follow the reason later.](https://pmonrails.com/docs-img/adr.png)

A record of the decisions made about design and technology: why this structure, why this technology.

- Keeps the reasoning in the shape "context, options, decision, consequences".
- When the direction changes, the old decision is superseded by a new one, and the history can be followed.
- Engineers can also create and update them from [Claude Web, Claude Code, and MCP integration](https://pmonrails.com/en/docs/mcp.md).

> Because the reasoning behind a decision is kept, people who join later can understand why things are the way they are. For the stakeholder, it also adds up to transparency.

---

https://pmonrails.com/en/docs/decisions