Build an Argument Map from a Course PDF: Evidence Template
An argument map helps you see what a reading claims, what supports the claim, and where the reasoning could fail. To build one from a course PDF, extract a small set of claims with page references, connect evidence to each claim, and label qualifications and unanswered questions. Check every connection in the original before using it in a seminar or essay plan.
This guide is for an argumentative reading or a paper you need to evaluate. It is not a general PDF summary, a diagram decoder, or a comparison of two studies. The map can be a plain table: you do not need a drawing tool to begin.
First decide whether the document makes an argument
UNC's argument guidance distinguishes presenting information from making a supported claim. Start by identifying what the author is trying to do.
A lab manual might mostly explain a procedure. A textbook section might describe an established concept. A research report presents a question, methods, and findings. These documents do not all need a single persuasive thesis. If no central argument is stated, label the document's purpose rather than forcing an invented claim into the map.
For a research article, distinguish the observed result from the author's interpretation of it. A result may support an interpretation without proving every implication the discussion suggests.
1. Create a source record
Record the title, author, year shown in the document, and the version you read. Note both the PDF viewer page and the printed page when they differ. This prevents “page 6” from becoming ambiguous later.
Choose a section that relates to your class question. You can use Notoo's PDF-to-notes workflow to generate a first-pass structured overview from a readable PDF and review the result against the original. The argument map below is a manual analytical template, not a tested automatic argument-map feature or promised output.
Keep the source PDF open. Generated headings and source references still need checking. Scans, tables, equations, and image-heavy pages require direct inspection when they carry evidence you intend to discuss.
2. Separate the author's claims from your reaction
Write one claim per row in your own words. Preserve the scope: which group, setting, time period, or condition is being discussed? Keep words such as “may,” “associated,” and “under these conditions” when they affect the meaning.
Add a short source location, then check that the row really represents the author's claim. “I disagree” belongs in your evaluation column; it should not replace the claim you are evaluating.
If you use exact wording, mark it as a quotation and record the source. Otherwise, paraphrase after understanding the passage. A page number alone does not make copied wording your own.
3. Connect evidence with a stated reason
Evidence can include data, a case, a quotation, an observation, or a reasoned example. Record what the document actually supplies. Then ask: why would this evidence support this particular claim?
UNC's evidence guidance emphasizes explaining how and why evidence supports an argument. Use that distinction to keep evidence and the connecting reasoning in separate fields.
An author may explain the connection explicitly. If you infer it, label the connection “my interpretation” and keep the passage you used. Do not promote your inference into a quotation or a stated author position.
Copyable evidence-and-argument table
| ID | Claim and scope | Evidence in this PDF | Why it supports the claim | Qualification or challenge | Source and status |
|---|---|---|---|---|---|
| C1 | Main claim | Evidence identifier E1 | Stated reasoning or labeled interpretation | Boundary, missing comparison, or alternative | Page / checked or unresolved |
| C2 | Supporting claim | Evidence identifier E2 | Link to C1, if supported | Limit on that link | Page / checked or unresolved |
Use relation labels such as “supports,” “qualifies,” “challenges,” and “depends on.” An arrow without a label can hide the question you need to answer.
DOCUMENT PURPOSE:
CLASS QUESTION:
SOURCE DETAILS:
CLAIM ID / PARAPHRASE:
SCOPE AND QUALIFYING WORDS:
EVIDENCE ID / WHAT IS ACTUALLY REPORTED:
PDF PAGE / PRINTED PAGE:
CONNECTION: AUTHOR-STATED or MY INTERPRETATION
QUALIFICATION OR ALTERNATIVE:
CHECK STATUS:
QUESTION TO ASK IN CLASS:
Fictional teaching example: support with a boundary
The following mini-reading is invented for this article. The page numbers are illustrative, and the example is not a study finding or a recorded Notoo output.
Illustrative page 2: “During one campus pilot, the evening library desk received more visits than the morning desk. The pilot coincided with exam week. The author proposes trying evening staffing in a second week before deciding on a permanent change.”
| Map element | Checked entry from the fictional reading |
|---|---|
| C1: proposal | Try evening staffing for a second week before making a permanent change |
| E1: observation | In one campus pilot, the evening desk received more visits than the morning desk |
| Connection | The observation motivates another trial; it does not establish year-round demand |
| Qualification | The pilot took place during exam week |
| Missing evidence | No counts, cost data, or ordinary-week comparison are supplied |
| Recall question | Why is a second trial different from a permanent staffing recommendation? |
Rejected map: “Evening staffing is cheaper and always increases access.” Neither assertion is supplied. A polished diagram would not repair that unsupported leap.
Simple relationship view: E1 supports C1's further-trial proposal; the exam-week condition qualifies the reach of E1. Leave the permanent-change conclusion unresolved.
4. Use AI to organize, then audit the links yourself
A generic prompt for a tool that accepts instructions is:
From the supplied passage only, list claims, evidence, and qualifications separately. Preserve scope and page references where provided. For each proposed connection, say whether the author states it or you inferred it. Do not invent missing data, citations, or objections. Mark absent information as not supplied.
This is a suggested instruction, not a claim about a particular product interface. Check every proposed row in the PDF. Remove evidence that came from general background knowledge rather than this reading. Keep an unresolved link when the passage does not settle the issue.
If a chart matters, use our research-paper figures and tables guide to inspect the visual source before adding its finding. If your task is comparing authors rather than evaluating one argument, use the two-paper comparison matrix.
5. Prepare a discussion contribution from the map
Close the PDF and explain the main claim, its strongest support, and one relevant boundary. Reopen the source and correct your explanation. Then prepare one question that points to a specific connection: “Does this observation support the full recommendation, or only another trial?”
For international students, keep a small reasoning-word list beside the map: “suggests” is weaker than “proves”; “however” may introduce a qualification; “because” may signal the connecting reason. Check those words in their sentence rather than translating each in isolation.
Use the map to plan your own reading and discussion. If you later write assessed work, follow your course's rules on AI use and citation, and return to the original for any claim you cite.
Start with one claim
Try Notoo for a first-pass overview of a permitted PDF, then fill one checked claim row. A useful argument map makes the support and the uncertainty visible. It does not need to make the author look more certain than the reading allows.