Page 05 / 08 · Classify first

Why the first step is classification

You could try to extract fields immediately. But then someone — or something — would first need to know which model belongs to which document. That is exactly the information classification creates, and it creates it in a form the machine can process further.

content_cut

Documents emerge from a stack

What arrives at intake is rarely a document — it is a scan stack. Classification recognizes the boundaries and writes each subdocument with its own pages out as a separate file. Everything after that works on a cleanly delimited single document.

key

The category is the routing key

Recognition models are configured per document type. Without a category, there is no deterministic path to the right model — with it, model selection becomes a lookup the machine can perform without asking.

savings

The cheap step comes before the expensive one

Only the first pages are classified. The costly field extraction then runs exactly once, with exactly one model, on exactly the matching subdocument — instead of trying “all models against every document.”

speed

Confidence comes free with it

Every category comes with a confidence score. This makes it possible to decide before analysis whether a document may continue automatically — an uncertain assignment never creates wrong metadata in the target system, but instead a review case.

What the step leaves behind
SPEAKING PATH
Classifier model and document type are in the storage location — the storage is then sorted automatically.
CATEGORY METADATA
The document type is attached to the blob itself — readable independently of intermediate storage.
CONFIDENCE
Basis of the first quality gate and every later evaluation.
JOURNAL RUN
The output path becomes the document key that accompanies the case all the way to the target system.
Without classification first
A person would have to separate stacks and assign document types — automation ends at the inbox.
Or every document would have to run against multiple models: more cost, ambiguous hits, no clear result.
Error cases would not be assignable: without a category, there is no reference point at which “processed incorrectly” can even be determined.
With classification first
The intake may remain arbitrarily mixed — sorting emerges during the run, not before.
A new document type means: train category, assign model. No intervention in the processing code.
Every automatic decision is justified and traceable: category, confidence, selected model are in the journal.