Working with Documents

What You'll Need

⏱ Time: 15 minutes  |  📋 Tasks:

• Open your preferred chatbot: chatgpt.com, claude.ai, or gemini.google.com
• Find a short PDF or document you've already read thoroughly — a contract, an article, a report you know well
• Keep this lesson open in a second tab to follow along

Did It Skim My Upload?

You upload a contract PDF and ask a simple question — "What's the termination clause?" The model gives you a clear, confident answer. It sounds right. But when you scroll back to check, it missed a key exception buried in a footnote. The clause exists, but the model simplified it past the point of accuracy.

Or you take a photo of a whiteboard after a meeting and ask the model to transcribe it. It reads most of the text correctly but scrambles the most important note — the one with the deadline and the dollar amount — because your handwriting was messiest right there.

Documents give the model raw material to work from, but they're not magic. A clean digital PDF with clear headings extracts beautifully. A scanned 50-page contract with dense columns loses information regardless of which model you use. Knowing the limits is what separates useful document analysis from quietly wrong answers.

Concept — What Models Actually See

When you upload a document, the model doesn't "see" it the way you do. It receives an extraction — a translation of your file into text. That translation is lossy in predictable ways.

• PDFs with selectable text (not scanned): extracted well, but layout is lost. Tables arrive as a stream of numbers separated by spaces. Columns mix together. A two-column page reads as one long paragraph, not two parallel sections.
• Scanned PDFs and images: the model uses optical character recognition (OCR) to read text from the image. Handwriting, small fonts, low contrast, and watermarks all produce errors. A clean typed document works reasonably well. A photo of a handwritten meeting note is a gamble.
• Spreadsheets: only the first several dozen rows are reliably visible. The rest depends on the model's context window. Asking for "the average of column C" works; asking for "the value in row 300" may not — the model may not have seen that far.
• Context windows: every model has a limit on how much text it can process at once. ChatGPT handles roughly 128K tokens (about 100 pages), Claude ~200K, Gemini ~1M. But quality degrades before you hit the hard limit — the model gets worse at recalling details from earlier in the document as it fills up.

Key insight: a well-formatted 2-page proposal with clear headings will be extracted accurately by any model. A scanned 50-page contract with dense columns and fine print will lose information in every one. The document itself determines the ceiling on accuracy — not the model.

Walkthrough — Upload a Document and Ask Questions

Follow these steps with a document you've already read. The goal isn't to learn something new — it's to test what the model catches and what it misses when you already know the answers.

Step 1: Find your test document

Pick a short PDF you know well. A contract you signed, an article you studied, a report you wrote. The key requirement: you already know the key facts, numbers, and dates in it. You're testing, not reading.

Step 2: Upload and ask for a summary

Upload the file to your chatbot (click the paperclip or + button, or drag and drop). Then ask:

Summarize this in 3 bullet points. Capture the key facts, not the general topic.

Step 3: Ask for specifics

Paste this follow-up:

What are the key numbers or dates mentioned in this document? List them exactly as written.

Compare the list against what you know. Notice any dates slightly off? Numbers rounded? Details merged from different sections? Those are the extraction limits in action.

Step 4: Ask what you might have missed

This is the most useful question. Ask:

Is there anything here that I might have missed on a quick read? Look for details that are easy to overlook — exceptions, footnotes, conditional language.

This often surfaces things your eyes skipped. Models are good at finding patterns; they're bad at deciding what matters. Use them as a second pass, not a first reader.

Step 5: Cross-reference with a second model

Upload the same document to a different chatbot and ask the same three questions. Compare the two sets of answers. Chances are, each model caught different details and missed different ones. The gaps between them tell you what to go read yourself.

Your Takeaway — Document Analysis Checklist

Before you upload a document and trust the output, run through these questions to calibrate your confidence:

[ ] Is the text clean digital text or scanned/handwritten?
    (scanned = less reliable)
[ ] Are there tables or columns?
    (layout will arrive scrambled — ask about specific cells)
[ ] Is the document longer than 50 pages?
    (may hit context limits — try section by section)
[ ] Do I need exact numbers from a specific section?
    (ask directly, don't rely on the summary — summaries round)
[ ] Would uploading in sections give better results?
    (chapter by chapter beats all-at-once for recall)
[ ] Am I asking about a detail the model might have skipped?
    (ask follow-ups targeting specific sections)

Try It

This week, upload a document you've already read thoroughly — something where you know the key facts cold. Ask the model three questions you already know the answers to. Check which answers it got right and which it got wrong. That's your personal calibration: you'll develop a sense for what this model catches reliably and where it tends to miss, and you'll adjust your trust accordingly for every document you upload after.

Then try the same document in a second model. Compare. The differences between the two outputs are more valuable than either one alone — they map the edges of what these tools can and can't do with your kind of documents.