Decisions: proving your calls were right

1. Why decisions need a record

Most operational decisions — a renewal discount, a support staffing plan, a pricing change — are made in email and spreadsheets and never looked at again. Nobody can say afterwards what the decision was based on, who made it, or whether it worked. Flowcall records all three, so a team can learn which of its calls hold up.

The record starts with an approval step: the run pauses, the actual table goes to the inbox, and the approver's decision and comment are kept with the data they saw.

Do this: open the inbox's Decision log and read what it promises to hold.

Example used: Renewal review

2. Give a decision a value and an outcome

Two settings on an approval step turn a record into evidence. 'Value at stake' is the rough dollar impact. 'Check the outcome' names a pipeline to run some days later and a rule that says whether the decision worked — for the support staffing plan: SLA breaches stayed under 5%.

This example installs both pipelines already wired together, so you can see the whole loop.

Do this: install it, run the plan, approve it, then run the outcome check yourself and mark the decision in the log.

Example used: A decision that checks itself

3. Hit rate and cost per decision

Once decisions have outcomes, the Decision log shows a hit rate: what share of approved decisions worked. It also shows what each decision cost to produce — the machine time and AI tokens of the run behind it — against the value at stake, and how long decisions wait for a person.

That last number is often the most useful: a good plan approved six hours late is a worse plan.

Do this: approve two or three runs, mark one as didn't work, and read how the hit rate and wait time change.

Example used: A decision that checks itself

4. Receipts for audits and reviews

Every decision downloads as a receipt: the table the approver saw, who decided and when, their comment, the value at stake, what it cost to produce, and the outcome — with a fingerprint so it can be shown unchanged to finance or an auditor.

Do this: download one receipt from the Decision log and read it the way an auditor would.

Example used: A decision that checks itself