How do I set rules for specific senders without making the workflow cumbersome?

Direct answer

Sender-specific rules become cumbersome when every small variation turns into a separate template, script, or long unmanaged instruction list.

The better pattern is to keep one shared output schema and add targeted rules only when a sender consistently expresses a field differently or requires a different validation rule.

How to keep rules maintainable

Group rules by document type, sender, and field. Remove or consolidate rules that are no longer needed, and create a separate workflow branch when the document is no longer truly the same type.

Measure whether each rule improves accuracy or reduces review work; otherwise it may just add maintenance burden.

How Lido helps

Lido supports custom instructions and workflow branching, so teams can handle sender-specific differences without turning every variation into a new OCR template.

That keeps extraction flexible while still controlled enough for production use.

Example workflow

1. Start with a shared schema for the document type.
2. Add sender-specific instructions only for recurring extraction differences.
3. Use validation and review to catch edge cases instead of overfitting rules.
4. Split into a separate extractor when the sender's document requires materially different fields.