Open And Inspect Sources
Source inspection is the main trust step in Document.Bot. AI answers are useful only when you can check where they came from.
Why Source Inspection Matters
You should inspect the original file when:
- a PDF page layout affects meaning
- a spreadsheet row or formula matters
- a Word document has comments, tracked changes, or surrounding context
- an answer cites a clause, requirement, policy, or decision
- a proposed edit depends on specific evidence
How To Inspect A Source
- Search or ask a question.
- Open the cited file from the answer or file tree.
- Navigate to the relevant page, line, heading, row, or section.
- Compare the answer with the source.
- Ask a follow-up question if the evidence is incomplete.
Supported Source Views
Depending on file type and app build, Document.Bot can show:
- PDFs with page navigation, text, outlines, and password handling
- Word and office documents in a viewer or converted form
- spreadsheets and CSV files
- Markdown with headings and links
- text and code files with search and line navigation
- HTML files
- images
- graceful fallback actions for unknown or binary files
Treat Derived Text Carefully
Some workflows use extracted text or converted documents to help the AI read a source. That text is useful for search and drafting, but the original file is still the authority when layout, tables, signatures, comments, or formatting matter.
For PDF forms, inspect the saved PDF after a fill or edit. Form-field labels, visual layout, flattened outputs, and signature requirements can affect whether the result is usable outside the app.