# Computer-Vision Feasibility Checklist

Twelve questions to answer in writing before building image recognition.
Source: VisionRoute — "Computer-vision feasibility checklist" (published 2026-08-31).
Free to copy and adapt. Vague answers count as unchecked — the checklist works
by refusing to be hand-waved.

## The decision (1–3)

- [ ] **1. The visual decision fits in one sentence.**
  "Given [image], decide [answer], and the product does [action]."
  If the sentence needs "and also…", you have two use cases — run the checklist twice.

- [ ] **2. Both failure directions have a named cost and owner.**
  What happens on a false accept, what happens on a false reject, and who feels each.
  If nobody can price the failures, nobody can set the accuracy bar.

- [ ] **3. A person can make this decision from the image alone.**
  Show ten images to two domain experts separately. If they disagree, the project has
  a definition problem before it has a model problem.

## The data (4–6)

- [ ] **4. You have — or can collect — 100+ representative images.**
  Including hard cases and true negatives, from the real capture conditions.
  Screenshots of other people's datasets do not count as your distribution.

- [ ] **5. Every example has a recorded expected answer.**
  Ground truth written down before testing, not recalled during it.
  Disagreements surfaced by item 3 get resolved here.

- [ ] **6. Variability is bounded and rare-but-costly cases are listed.**
  Camera sources, lighting, resolution, occlusion — and the specific rare inputs whose
  failure would be expensive. If you cannot list them, collect until you can.

## The constraints (7–9)

- [ ] **7. The accuracy bar is stated per failure direction.**
  For example: "false accepts under 2%; false rejects may go to review."
  A single overall accuracy number hides the direction that hurts.

- [ ] **8. The latency budget is known — and where it binds.**
  Synchronous user flow or asynchronous batch? The same model can be right for one
  and disqualified for the other.

- [ ] **9. Volume is projected and priced at 12 months.**
  Images per day now and at 12 months, and the per-image budget at that volume.
  Approaches that work at 1,000/day can stop making sense at 50,000/day.

## The operations (10–12)

- [ ] **10. Privacy and residency constraints are decided.**
  May images transit a third-party API at all? Under which retention and
  training-use terms? This answer removes or admits entire solution families.

- [ ] **11. The abstention path is designed.**
  When the system is unsure: human queue, safe default, or block?
  "It will always be sure" is not a design.

- [ ] **12. Someone owns correctness over time.**
  Models, providers, and your own product drift. Name who re-checks the decision
  when they do, and what triggers the re-check.

## Scoring rule

| Checks passing | Reading | Next step |
| --- | --- | --- |
| 10–12 | Ready to evaluate. Remaining gaps are known and small. | Run a controlled test on your representative set — the checklist answers become the evaluation design. |
| 7–9 | Promising, but an evaluation now would be built on guesses. | Close the specific open items first — usually data collection (4–6) or an unpriced failure direction (2, 7). |
| 0–6 | Not a modeling problem yet. The use case is underdefined. | Work items 1–3 with the domain owner. This costs days and saves the quarter a premature build would spend. |

Passing the checklist does not mean the use case is feasible — it means you can
now find out, cheaply and defensibly. Feasibility itself is settled by testing on
representative data, and the honest outcomes include "not yet feasible" and
"not enough evidence".
