How do I handle new document senders that enter the market?

Direct answer

When new organizations start sending documents, the automation workflow should not collapse just because the layout, labels, or section order changed.

A resilient process uses AI extraction around the desired output fields, then sends unfamiliar or low-confidence cases to review before deciding whether configuration changes are needed.

What to monitor

Track new senders, new document formats, missing required fields, confidence drops, and repeated manual corrections. Those signals tell you whether the workflow needs new instructions or a separate branch.

Avoid creating a new template for every sender unless the document truly has different fields or business logic.

How Lido helps

Lido helps teams maintain a common extraction schema while adding instructions, validation, and workflow branches for meaningful variations.

That makes it easier to support a changing sender ecosystem without returning to manual keying.

Example workflow

1. Route documents from unknown or new senders through review initially.
2. Compare extracted outputs against the existing schema.
3. Update instructions for small variations.
4. Create a separate extractor only when the document type or required output is truly different.