456
Prompt

Document Extraction Schema Prompt

Designs the schema and validation rules before you build extraction.

1 min readupdated 2026-08-01

/ quick answer

Run first when automating any document intake process. Designs the schema and validation rules before you build extraction.

Designs the schema and validation rules before you build extraction. Run first when automating any document intake process. Copy the prompt below, swap the bracketed variables for your own context, and run it in any capable model. This prompt node is part of the Onexial knowledge graph and links to related concepts, workflows and tools below.
Context
Run first when automating any document intake process.
Prompt
Act as a data engineer designing document extraction. For the document type below, return:

1. SCHEMA — every field with type, required/optional, and normalisation rule (dates, currency, IDs).
2. VALIDATION RULES — arithmetic checks, cross-field consistency, external lookups.
3. AMBIGUITY CASES — the 5 places extraction most often goes wrong for this document type.
4. HUMAN QUEUE CRITERIA — exactly which failures a human must review.
5. TEST SET — 8 document variations to test against, including 3 malformed ones.

Document type: {{DOC_TYPE}}
Downstream system: {{SYSTEM}}
Volume: {{VOLUME}}
Example Output
1. SCHEMA — supplier_name (string, required), vat_id (string, optional, uppercase no spaces), total (decimal, required)...
Related Workflow
Related Tool Stacks
/ frequently asked

What does the Document Extraction Schema Prompt prompt do?

Run first when automating any document intake process.

Which AI models work with this prompt?

It is model-agnostic: it works with any capable general model. Replace the bracketed variables with your own context before running it.

What output should I expect?

1. SCHEMA — supplier_name (string, required), vat_id (string, optional, uppercase no spaces), total (decimal, required)...