Skip to content

Table · reads decision

Decision log

Choices + rationale.

Rows and columns, sortable and filterable.

Every row names what was turned down. That is what makes it worth reading later.
DecisionDateByRejected
Own delivery, not a courier14 JulCamille, TomasThird-party courier — cost per drop
Trade from 12 units2 AugCamille6 units — margin too thin
No Saturday opening yet19 AugAllSaturdays — staffing not there
Stay on one site through 20263 SepCamilleSecond site — revisit Q2

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Records what was rejected, which is the column people skip and the one that pays.

Stops the same option being re-proposed every six months by somebody who was not there.

Dated and attributed, so the context of a decision survives the people who made it.

How it works

  1. 1

    A decision is recorded when it is made, with the alternative that lost.

  2. 2

    The rejected column is required, because without it the same option is re-proposed every six months.

  3. 3

    Entries are immutable; a reversal is a new decision referring to the old one.

  4. 4

    The agent surfaces a relevant past decision when the same subject comes up.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
DecisionrequiredtextWhat was decided, stated as the thing now true.
DaterequireddateWhen. Without it the record cannot be read in order.
ByrequiredtextWho made it, so context survives the people who left.
RejectedrequiredlongtextWhat was turned down and why. The column people skip and the one that pays.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • No formal reversal link — a superseding decision has to say so in its own text.
  • Nothing enforces that a decision was actually followed.
  • No confidentiality levels, so a sensitive decision needs care about where it is recorded.
  • Records what was decided, not whether it was right.

Before it works

What you have to provide, if anything.

  • Nothing.
  • Record the rejected option even when it feels obvious. That is the entry future-you needs.

In practice

A team that had debated couriers three times in a year.

We are doing our own delivery, not a courier. Cost per drop is the reason.
What was said to the agent

What the agent built

A decision with the date, who made it and the rejected alternative.

What changed

It came up again in November and took two minutes instead of an afternoon, because the cost-per-drop reasoning was written down.

Questions

What data does the Decision log page use?

It reads decision records the agent has collected. Choices + rationale. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ