HOW THE ASSESSMENT IS BUILT

The ProcessScout Methodology

For technical evaluators and skeptical operators: how we collect evidence, score confidence, and keep humans accountable for every finding that reaches your board.

Every claim in a ProcessScout report traces back to a source you can inspect.

01 — EVIDENCE-FIRST PIPELINE

Findings start with evidence, not opinions.

An assessment begins by building an evidence base, not by filling in a template. We collect the raw material of how your business actually operates:

Documents & exports
SOPs, policies, reports, and system exports that show how work is defined on paper.
Screenshots & workflow recordings
Captures of real workflows as they happen — the difference between the documented process and the actual one is often where the opportunity lives.
Stakeholder input
Structured intake with the people who do the work, capturing context, exceptions, and pain points that never make it into documentation.
Structured & linked
Each item is catalogued and tagged, and every finding in the report links to the specific evidence supporting it. If we can't trace a claim to a source, it doesn't ship.
The report clock starts when evidence collection is complete: your report is delivered within 7 business days of that point, backed by the refund policy in our Terms.
02 — CONFIDENCE SCORING

Every finding tells you how sure we are — and why.

Findings carry a confidence level driven by three things:

Evidence quality
Is the finding backed by primary sources — recordings, exports, artifacts — or only by secondhand description?
Coverage
How much of the relevant process the evidence actually observes, versus what had to be inferred around the edges.
Corroboration
Whether independent sources — different people, different systems, different artifacts — point to the same conclusion.
Low-confidence findings are labeled as such, not hidden. If something looks like a real opportunity but the evidence is thin, we say so explicitly — and tell you what additional evidence would firm it up.
03 — HUMAN-IN-THE-LOOP

AI prepares. A human analyst signs off.

Sarah, our AI intake assistant, runs the evidence-gathering conversation: she asks follow-up questions, organizes what you share, and assembles the context an analyst needs. That's where her job ends.

What Sarah does
Structures intake, requests missing evidence, links artifacts to the processes they describe, and drafts the working material for review.
What the analyst does
Reviews every finding against its evidence, prioritizes opportunities by impact and feasibility, rejects anything that doesn't hold up, and signs off on the final report.
AI output is never shipped unreviewed. A named human analyst is accountable for every report we deliver.
04 — PROVENANCE & INTEGRITY

You can verify the evidence trail yourself.

Evidence is only worth anything if you can trust it hasn't quietly changed between upload and report. So we make the trail checkable:

  • • Every upload and exchange is timestamped at the moment it enters the system.
  • • Files are hash-verified on receipt, so any later change to an artifact is detectable.
  • • Findings reference the specific evidence version they were drawn from.
This doesn't make evidence infallible — a bad export is still a bad export. What it does is make the chain from source to finding auditable, so disagreements can be settled by looking at the record rather than arguing about memory.
05 — WHERE AI IS USED, AND WHERE IT ISN'T

An honest split, because the split is the point.

AI DOES THIS
  • • Extracting structure from documents, recordings, and exports
  • • Clustering related evidence across sources so patterns surface
  • • Drafting findings and summaries for analyst review
  • • Flagging gaps and inconsistencies in the evidence base
HUMANS DO THIS
  • • Judgment calls about what a pattern actually means for your business
  • • Prioritization: which opportunities are worth pursuing, in what order
  • • Deciding what makes it into the report — and what gets cut
  • • Final signoff on every deliverable
We use AI where it's genuinely better than people — reading everything, missing nothing, working fast. We keep people where AI is genuinely worse — knowing what matters, and being accountable for the answer.
06 — SECURITY POSTURE

Your evidence is business-sensitive. We treat it that way.

Assessment evidence often includes internal documents, system exports, and recordings of real work. How we handle access, storage, and retention is documented on its own page, kept current as our practices evolve.

Read the security overview →

See what the method produces.

The fastest way to evaluate the methodology is to read a report built with it — then start Foothill with a paid Trail Map.