Evidence standard

No savings or revenue outcome is claimed here. This model shows the baseline, controls and acceptance evidence that should exist before a result is reported.

How a claim becomes evidence

UnknownThe current result is asserted, not evidenced.
MeasuredA baseline exists and terms are defined.
ControlledThe change is bounded with exceptions and review.
AcceptedThe result survives a commercial review of the evidence.

A result is reported only after it reaches Accepted. Everything before that is work in progress.

What is measured

This is not a savings claim. It shows how repeated tasks can be compared without pretending every saved minute becomes cash.

Each workflow is scored for frequency, active effort, delay, rework, rule clarity, data quality, reversibility and owner readiness. High-value but low-readiness work is redesigned before automation.

What control changes

  • A ranked workflow inventory with evidence links.
  • A realistic range for recoverable capacity.
  • A minimum useful automation scope.
  • Exception, access, logging and recovery controls.
  • A plan for how recovered capacity will be used.

What proves acceptance

The first workflow is suitable when the team can explain the trigger, input, decision rules, output, exceptions, owner and fallback without relying on undocumented judgement.

Replace with permissioned evidenceOnce Advery has confirmed source data, scope, dates and client approval, this model can be replaced by a named or appropriately anonymised result page.