Reading the agreement report
The number that tells you whether an action is ready for more autonomy.
On this page
Reports → Agreement. It answers one question: when a digital worker proposed something, how often did a person change it?
What the columns mean
Proposed. How many times the worker suggested this action.
Accepted unchanged. A person approved it as written.
Edited. A person changed it before sending. The edit is the signal — read a sample of them rather than only the count.
Rejected. Discarded, with a reason.
Agreement rate. Accepted unchanged, divided by proposed.
Reading it honestly
A high agreement rate is necessary but not sufficient. Three ways it misleads:
Volume. Ninety per cent of ten is not evidence. Wait for a few hundred.
Rubber-stamping. If one person approves everything within two seconds, their agreement rate says nothing about the worker and quite a lot about the queue. The per-approver breakdown exists for this.
Selection. If the worker only proposes on the easy cases, its agreement rate describes the easy cases. Check the distribution of case types alongside the rate.
What good looks like
Teams that widen autonomy successfully tend to have, per action:
- Several hundred proposals
- Agreement above ninety per cent, stable over at least a month
- Edits that are stylistic rather than substantive
- Rejection reasons that cluster into a pattern you have already fixed
Using it
Filter to a single action, set the period to the last quarter, and read twenty edits. Then decide. The number tells you where to look; the edits tell you what to do.