Skip to main content
Instructions tell anyformat how to extract a field. They are written in plain English and can include:
  • What to look for
  • Where it usually appears
  • How to interpret ambiguous cases
Example:
“Extract the total amount charged, including taxes. Ignore subtotals.”

​
Why instructions matter

Good instructions

  • Reduce ambiguity
  • Improve accuracy
  • Lower review time

Bad instructions

  • Are vague
  • Repeat the field name
  • Try to encode logic unnecessarily

​
Instruction best practices

1

Be explicit, not clever

Say exactly what you mean. Avoid shortcuts or assumptions.
2

Describe intent, not format

Focus on what you want, not where it appears on the page.
3

Explain edge cases when needed

If a value can appear in multiple forms, clarify which one to prefer.
4

Avoid copying document text verbatim

Instructions should guide processing, not mirror the source.
You don’t need to over-instruct. Clear intent beats long explanations.

​
Examples

Field: total_amountInstruction: “Extract the final total amount including taxes. If multiple totals appear, use the one labeled ‘Grand Total’ or ‘Amount Due’.”
Field: total_amountInstruction: “The total amount.” (Too vague — doesn’t clarify which total or whether to include taxes.)

​
What’s next?

annie

Let annie suggest fields and write instructions for you

Workflows

Put your schema to work with repeatable workflows