Can document automation use custom instructions without creating a template for every sender?

Direct answer

Custom instructions are useful when most documents share the same business fields but some senders phrase, label, or position those fields differently.

Instead of creating a completely separate template for every sender, the workflow can use one core schema and add instructions for edge cases, special labels, or validation rules.

What the workflow should include

Custom instructions should be specific enough to improve extraction but organized enough that they do not become an unmaintainable rule dump.

When a document type truly has different required fields or downstream routing, create a separate extractor or workflow branch rather than overloading one configuration.

How Lido helps

Lido supports configurable extraction columns and instructions, plus workflow branching when different document types need different extractors.

That gives teams flexibility for many sender formats without forcing every variation into its own brittle OCR template.

Example workflow

1. Create a stable extraction schema for the document type.
2. Add custom instructions only for known sender-specific variations or business rules.
3. Use separate extractors when the required fields are truly different.
4. Review new failures and decide whether to update instructions or route the document elsewhere.