Skip to main content
An instruction tells anyformat how to extract one field. Write it in plain English. It covers:
  • What to look for
  • Where the value usually appears
  • How to read an ambiguous case
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 and assumptions.
2

Describe intent, not format

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

Explain edge cases when needed

If a value can appear in several forms, say which one to prefer.
4

Avoid copying document text verbatim

Guide the extraction. Do not mirror the source.
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.”Why it fails: it does not say which total to use, 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