Use cases
Questions about identifying document types before extraction.
Classification
Lido helps teams classify document types before extracting data from them by combining AI extraction, review, validation, and clean exports to spreadsheets, CSVs, or business systems.
Healthcare documents
Lido helps teams route different healthcare document types to different extractors by combining AI extraction, review, validation, and clean exports to review workbooks or healthcare workflows.
Form classification
Lido helps teams classify forms before extracting fields by combining AI extraction, review, validation, and clean exports to spreadsheets, forms, or generated PDFs.
Templates vs AI
Lido helps teams choose templates for stable layouts and AI extraction for variable documents, with review and validation before export.
Mixed document types
Lido helps teams use one workflow to handle multiple document types by combining AI extraction, review, validation, and clean exports to spreadsheets, CSVs, or business systems.
Template reuse
Lido helps teams reuse an extraction template for similar documents by combining AI extraction, review, validation, and clean exports to spreadsheets, CSVs, or business systems.
Exception handling
Lido helps teams handle unreadable or unclassified documents in an extraction workflow by combining AI extraction, review, validation, and clean exports to spreadsheets, CSVs, or exception queues.
Variable formats
Use AI extraction and document classification around a consistent output schema so new sender layouts do not require a full OCR-template rebuild every time.
OCR replacement
Move from coordinate-only OCR templates to an AI extraction workflow that understands field meaning, supports review, and can be updated with instructions when formats change.
Inbox automation
Set up rules that forward or route relevant emails into a document automation workflow, then let classification and extraction decide what each attachment needs next.
Document routing
Yes. A document automation workflow can classify incoming files by type, then route each class to the extractor, validation rules, and export path built for that document.
Vendor evaluation
Ask vendors about intake channels, document classification, changing formats, missing fields, validation, review queues, exports, monitoring, implementation support, and build-versus-buy tradeoffs.
Custom instructions
Yes. Custom instructions can capture sender-specific rules and edge cases while preserving a common extraction schema, so teams do not need a separate template for every small variation.
Configuration control
Yes. Teams should track changes to extraction fields, instructions, validation rules, and workflow branches so production document automation remains controlled and reviewable.
Pre-extraction triage
Automate triage by identifying the intake source, classifying the document type, filtering irrelevant files, and routing each document to the right extraction path.
Insolvency variants
Yes, if the workflow separates shared fields from document-specific fields and routes personal and corporate insolvency documents through the right extraction and review rules.
New senders
Handle new senders by testing their documents against the existing schema, routing unknown formats to review, and updating instructions or workflows only when needed.
Post-extraction workflow
Yes. After extraction, a workflow can sort rows, merge outputs from different extractors, normalize formats, and prepare approved data for export.
Sender rules
Use a shared schema for the document type, then add sender-specific instructions only for recurring, meaningful differences that affect extraction or validation.
Extractor design
Use separate extractors when document types require different fields, validation, review rules, or downstream destinations; reuse one extractor when only the layout changes.