Platform

Don't just store the decision. Preserve its story.

A decision, a commitment and an action are three different kinds of record, each with its own lifecycle - because "what did we decide," "who agreed to do it" and "is it actually happening" are three different questions.

What a decision actually requires

A decision has to rest on something

Confirming a decision requires support: a specific piece of validated evidence, or a stated institutional judgement with a reason attached. An institution that records a decision nobody can trace to anything has recorded a preference.

Superseded and reversed are different

A decision moves from proposed to confirmed, then either superseded - a later decision replaced it, and it was right at the time - or reversed - the institution changed its mind and says so. Neither deletes anything.

Commitments can be owned by a team

A commitment names a responsible party in plain language - "the housing team", "Council's transport unit" - not only a person with a login. Most commitments in a session belong to a role, not an individual.

Actions carry progress, not just a checkbox

An action records a progress note and a percent complete, and can move from in progress to blocked and back - work that stalls and resumes is the normal case, not an exception to paper over.

Illustrative example

A decision, its commitment, and the action tracing it.

Decision

Confirmed

Adopt revised complaints process

Rests on: validated evidence from Community consultation #14

Commitment

Active

Owned by Council's complaints unit

Due
30 days

See what a decision in your own organisation would rest on.