Craig Stanley
Home / Decisions / Decision models

Act, ask a person, or stop

Three routes for every case a decision model scores, and how to decide which cases take which route.

10 October 2026 · 2 min read · Craig Stanley
In short, explained

When the helper is very sure, it can go ahead. When it's not sure, it asks a person. When something looks wrong, it stops and doesn't do anything.

Every case a model scores goes one of three ways. It acts on its own, it hands the case to a person, or it stops because something's wrong. Deciding the rules for each route in advance is what makes the system safe.

Define three routes: autonomous action above a calibrated threshold, human review in the uncertain band or for high-stakes cases, and a hard stop when inputs are out of distribution, data is missing or a policy rule fires. Log every route taken.

Act

The model acts on its own when three things are true: its score is above the action threshold, the stakes for this case are within agreed limits, and nothing unusual has been flagged. A routine £40 expense with a receipt and a known supplier is a typical example.

Log every automatic action so it can be sampled and checked later.

Ask a person

The case goes to a person when the score falls in the uncertain band, when the stakes are above a set limit whatever the score, or when the case belongs to a category you've decided people always handle.

Give the person what they need to decide quickly: the facts, the model's suggestion and score, and why it was sent to them. Record what they decided. Those records are the best training data you'll get.

Stop

Some cases shouldn't be scored at all. Stop and raise an alert when:

  • required data is missing or malformed
  • the case looks unlike anything the model has seen before
  • a policy rule fires, such as a sanctioned supplier or an amount over a hard limit
  • the model's recent behaviour has drifted, for example a sudden jump in approvals

Stopping isn't a failure. It's the system knowing the edge of what it can safely do.

Keeping the routes honest

Check the split every week. If the share going to people climbs, the model or the data may have changed. If it falls to almost nothing, check that the threshold hasn't been loosened without anyone agreeing. The nudges in the Risk section can watch these numbers for you.

Read next

A question to take awayWhich repeated decision would you trust a cheap model to score first, with a person checking the close calls?

About me

Craig Stanley

Microsoft AI consultant and technical architect, based in Whitley Bay. Over the last few years I've delivered Microsoft 365 Copilot, Copilot Studio agents, Azure AI Foundry work and governance for UK public sector and financial services organisations.

What interests me is the decision underneath the tool: what it costs, what it risks, and whether a small, transparent model can make it better. I write the methods up here and on Substack so anyone can use them.

Find me