Skip to main content

Our Team

  • Lindsay Smith, CTO - Enterprise software veteran, 20+ years FinTech, former CTO at Telrock
  • Robbie MacIntosh, Operations Director - Crisis management and operational transformation specialist
  • Spencer Thursfield, Chief Marketing Officer - Brand development, commercial strategy, and cross-sector pattern recognition

Proven Results

  • 150% conversion increase: same leads, seven figures in new annual revenue
  • 95% faster processing: 3 hours of senior time reduced to 9 minutes
  • £200K+ hidden costs uncovered in a single 48-hour engagement
  • £15M procurement decision delivered in 48 hours from 1,200 pages
  • Live with paying clients since October 2024

Using AI to Review Completed Checklists for Accuracy

·4 min read·730 words
Context EngineeringSASHAContour MethodologyPrivate AI

AI can review completed checklists for accuracy, but only if it knows what a correct one looks like in your firm. Where it works, where it fails, and how to set it up.

Yes, AI can review completed checklists for accuracy. It can also review them badly. The difference is not the model. It is whether the AI knows what a correct checklist looks like in your firm.

That part is fixable.

What "accuracy" means on a checklist

A completed checklist can be wrong in four different ways. Each needs a different kind of check.

  • Incomplete. A box is blank, or a required field has no entry.
  • Inconsistent. Two answers contradict each other, or an answer contradicts the source document it refers to.
  • Unsupported. A box is ticked, but there is no evidence attached to show the step was done.
  • Technically complete, substantively wrong. Every box is filled in and the answers are plausible, but a senior person would not accept them.

Most off-the-shelf AI handles the first two reasonably well. The last two are where the risk sits, and where generic tools fall down.

Where AI helps

Checklist review is repetitive, rule-based and high volume. That is the work senior people should not be doing. AI is well suited to:

  • Flagging missing, blank or placeholder answers across a whole batch.
  • Comparing each answer against the document it cites and highlighting mismatches.
  • Checking that evidence exists for each ticked item.
  • Sorting completed checklists into "clean", "needs a look" and "send back", so a reviewer starts with the ones that matter.

Where it fails

A general-purpose model reviewing a checklist has no idea what your firm treats as an acceptable answer. It will read "reviewed with client" and accept it. Your senior partner would ask who, when and what was decided.

It will also sound sure of itself. Confidence is not accuracy, and a reviewer that approves a wrong checklist is worse than no reviewer, because people stop looking. We cover that cost in The Verification Debt Nobody Budgeted For.

How to set it up so the review can be trusted

  1. Write down what a pass looks like. For each item, state what counts as acceptable evidence and what does not. This is your methodology, and it is the most valuable input you have.
  2. Give the AI the standard, not just the checklist. It needs the criteria, worked examples of good and bad answers, and the source documents each answer should match. This is context engineering. See What Context Engineering Actually Means.
  3. Do the deterministic checks in code. Blank fields, missing attachments and mismatched figures do not need a language model's opinion. Let code check them and let the model handle judgement calls.
  4. Keep a human on the exceptions. The AI sorts and flags. A named person signs off anything it marks as doubtful.
  5. Test it before you trust it. Run it on a batch you have already reviewed by hand. Count what it caught and what it missed. Agree an acceptance threshold before go-live. See Acceptance Criteria for AI Projects.

Keep the checklists inside your firewall

Completed checklists often contain client names, figures and internal judgements. Pasting them into a public AI tool is a data problem before it is an accuracy problem. Our SASHA platform runs inside your own infrastructure, on AWS Bedrock or an internal LLM, so the checklists never leave your firewall. It is encoded with your methodology under our Contour Methodology, so it reviews against your standard, not a generic one.

The point

The aim is not to remove people from checklist review. It is to stop your senior people reading every checklist to find the few that need them. Let's look at the numbers for your process.

Talk to us about reviewing your own checklists with SASHA.

Related Articles

What happens next?

Talk to us. We'll tell you honestly whether AI makes sense for your situation.

If it does, we'd love to work with you. If it doesn't, we'll tell you that too.

Start a Conversation
Skip to main content

Our Team

  • Lindsay Smith, CTO - Enterprise software veteran, 20+ years FinTech, former CTO at Telrock
  • Robbie MacIntosh, Operations Director - Crisis management and operational transformation specialist
  • Spencer Thursfield, Chief Marketing Officer - Brand development, commercial strategy, and cross-sector pattern recognition

Proven Results

  • 150% conversion increase: same leads, seven figures in new annual revenue
  • 95% faster processing: 3 hours of senior time reduced to 9 minutes
  • £200K+ hidden costs uncovered in a single 48-hour engagement
  • £15M procurement decision delivered in 48 hours from 1,200 pages
  • Live with paying clients since October 2024

Using AI to Review Completed Checklists for Accuracy

·4 min read·350 words
Context EngineeringSASHAContour MethodologyPrivate AI

What the phrase means when a firm puts AI to work, why generic AI misses it, and how SASHA encodes your own methodology inside your firewall.

Yes, AI can review completed checklists for accuracy. It can also review them badly. The difference is not the model. It is whether the AI knows what a correct checklist looks like in your firm.

That part is fixable.

What "accuracy" means on a checklist

A completed checklist can be wrong in four different ways. Each needs a different kind of check.

  • Incomplete. A box is blank, or a required field has no entry.
  • Inconsistent. Two answers contradict each other, or an answer contradicts the source document it refers to.
  • Unsupported. A box is ticked, but there is no evidence attached to show the step was done.
  • Technically complete, substantively wrong. Every box is filled in and the answers are plausible, but a senior person would not accept them.

Most off-the-shelf AI handles the first two reasonably well. The last two are where the risk sits, and where generic tools fall down.

Where AI helps

Checklist review is repetitive, rule-based and high volume. That is the work senior people should not be doing. AI is well suited to:

  • Flagging missing, blank or placeholder answers across a whole batch.
  • Comparing each answer against the document it cites and highlighting mismatches.
  • Checking that evidence exists for each ticked item.
  • Sorting completed checklists into "clean", "needs a look" and "send back", so a reviewer starts with the ones that matter.

Where it fails

A general-purpose model reviewing a checklist has no idea what your firm treats as an acceptable answer. It will read "reviewed with client" and accept it. Your senior partner would ask who, when and what was decided.

It will also sound sure of itself. Confidence is not accuracy, and a reviewer that approves a wrong checklist is worse than no reviewer, because people stop looking. We cover that cost in The Verification Debt Nobody Budgeted For.

How to set it up so the review can be trusted

  1. Write down what a pass looks like. For each item, state what counts as acceptable evidence and what does not. This is your methodology, and it is the most valuable input you have.
  2. Give the AI the standard, not just the checklist. It needs the criteria, worked examples of good and bad answers, and the source documents each answer should match. This is context engineering. See What Context Engineering Actually Means.
  3. Do the deterministic checks in code. Blank fields, missing attachments and mismatched figures do not need a language model's opinion. Let code check them and let the model handle judgement calls.
  4. Keep a human on the exceptions. The AI sorts and flags. A named person signs off anything it marks as doubtful.
  5. Test it before you trust it. Run it on a batch you have already reviewed by hand. Count what it caught and what it missed. Agree an acceptance threshold before go-live. See Acceptance Criteria for AI Projects.

Keep the checklists inside your firewall

Completed checklists often contain client names, figures and internal judgements. Pasting them into a public AI tool is a data problem before it is an accuracy problem. Our SASHA platform runs inside your own infrastructure, on AWS Bedrock or an internal LLM, so the checklists never leave your firewall. It is encoded with your methodology under our Contour Methodology, so it reviews against your standard, not a generic one.

The point

The aim is not to remove people from checklist review. It is to stop your senior people reading every checklist to find the few that need them. Let's look at the numbers for your process.

Talk to us about reviewing your own checklists with SASHA.

Related Articles

What happens next?

Talk to us. We'll tell you honestly whether AI makes sense for your situation.

If it does, we'd love to work with you. If it doesn't, we'll tell you that too.

Start a Conversation
Built with BernardCookie settings