An intake folder can contain several jobs: an application to review, a contract to file, or a form whose fields need extracting. Norml builds AI document classification for that first decision. We define the document classes with your team, test representative files and route the results to named queues. Files that do not meet the agreed routing checks stay available for a person to inspect.
The starting scope is a known set of document families and destinations. We retain the original file and make the routing decision traceable.
We define each class with examples and exclusions, including similar-looking documents that need different handling. Categories correspond to a business destination or next step. We test how the model handles unfamiliar material rather than assuming every unknown file will identify itself as unknown.
When an upload contains several documents, we assess whether classification should operate on the whole file, individual pages or detected document sections. Splitting behavior is configured deliberately and tested against packet examples. The original upload remains available while routing records point to the relevant pages.
Airtable can record the source, predicted class, checks and destination. Agreed thresholds and rule conflicts send a file to review. The processing record identifies which handoff completed, so a retry does not repeatedly notify an owner or submit the same pages to an extractor.
Supply representative samples, confusing pairs and documents outside the intended classes. A new category needs a definition and evaluation examples before it becomes a routing destination.
Identify which queue, team or extractor receives each class. Classification must not grant someone access to a source document they are not permitted to read.
Choose who reviews unclear files and how corrections are recorded. Agree when a file must remain manual, how long it is retained and who can approve a change to the class definitions.
We compare model output with checked examples and inspect confusing categories. This establishes routing rules and review conditions based on your document set, without promising a universal accuracy figure.
We build the classification call, page-range handling and routing ledger. Each destination receives the agreed file reference and context, with permission checks and a recorded handoff result.
We test mixed uploads, blank pages, unfamiliar types and duplicate delivery events. Your team reviews corrections and learns how to pause routing when a new document format starts arriving.