Start with the document's actual text
Run OCR and inspect the pages containing likely answers. A model cannot reliably distinguish a missing fact from a badly recognized one unless the source is checked.
For a long document, a short summary can help identify the relevant section before you ask a detailed question.
Write a bounded question
Ask 'What payment deadline is stated, and on which page?' instead of 'Tell me everything important.' Include units, date range, party name, or section when those narrow the search.
Tell the system to say when the answer is not stated rather than infer it.
- One factual target per question
- Request the page reference
- Distinguish stated facts from explanation
- Ask for the exact wording when a clause matters
- Treat absence of an answer as something to verify manually
Review the answer
- 1
Read the answer
Identify every factual claim.
- 2
Open the referenced page
Compare wording, number, and context.
- 3
Check nearby text
Conditions and exceptions often sit in the next sentence.
- 4
Record only verified facts
Do not pass an unchecked answer into a consequential workflow.
Know when not to rely on document Q&A
Do not treat it as legal interpretation, medical diagnosis, tax guidance, or financial advice. It can help locate and explain text, but a qualified person remains responsible for professional judgment.
When the source is incomplete, handwritten, poorly scanned, or heavily tabular, manual reading may be faster and safer.
