Back to app
Decisions

Decisions

Calls your company made, recorded with the reasoning behind them and who made them.

Reviewed AdminVertiqa 1.46+

A decision record answers a question that gets asked months later: why did we do it that way, and who decided?

What a decision needs

Five fields are required, and the shape is deliberate:

  • Title — the question that was settled, short enough to scan.
  • Decision — what was actually chosen.
  • Rationale — why. This is the field the record exists for. A decision without its reasoning is just a fact you'll re-argue later.
  • Decided by — picked from your team, not typed.
  • Decided at — when it was settled, which can be backdated to when the call was really made.

Description is optional, for context that isn't the reasoning itself.

Two statuses

  • Decided — the call stands.
  • Closed — it no longer needs active review.

Closing is not reversing. A closed decision is still on the record with its rationale intact; closing just takes it off the list of things anyone is still watching. Use Close decision on the detail page, which lets you add a reason.

If a decision was genuinely overturned, record the new decision as its own record and close the old one. The pair is the history.

Finding one

Search matches title and decided-by. The status filter and the owner field narrow the list — note that the owner box wants a user ID pasted from a record, not a name.