Build a Useful Evidence Packet From a Long Report

A 146-page impact report arrives with a request for a 500-word authored article by tomorrow. Search finds 37 mentions of “access,” several tables use different populations and the executive wants a strong opening number. Sending the whole PDF to a writer technically provides the source. It does not make the evidence usable.

An evidence packet is a focused bridge between the report and the deliverable. It gathers the passages most relevant to proposed assertions, preserves enough context to interpret them and records what each passage can support. The full report remains available for inspection; the packet never replaces it.

Start with the article brief, intended audience and likely argument. List the questions a writer must answer: What changed? For whom? Over what period? How was it measured? What can the executive reasonably infer? Keep the brief in its own section. A request to lead with broad impact is an editorial goal, not evidence that broad impact occurred.

Turn likely sentences into atomic assertions. “The program expanded access and improved completion” contains at least two claims and may hide a third about cause. Search the report for each concept, including the report’s own terminology. A relevant keyword hit is a candidate. Read the page, section and notes before placing it in the packet.

Include contradictory or limiting passages. A regional result may sit beside a methodology note excluding certain participants. Omitting that note makes the packet faster to scan at the cost of changing the meaning. The writer needs the constraint early, not during final approval.

Proposed assertion

Write the claim in plain language and label its status as proposed. Identify the entity, population, period and comparison it concerns. If the wording contains two checkable ideas, split it into separate cards even when the final prose may combine them.

Source context

Record report title and version, page, section, table or figure, exact relevant passage and enough surrounding text to understand it. Include definitions and footnotes. For a chart, retain labels, units, legend and any note explaining missing or adjusted data.

Support decision and use decision

State what the passage supports, what it does not establish and any unresolved conflict. Name the reviewer and decision date. Separately record whether the information and wording may be used publicly, with its decision owner and conditions.

Imagine a fictional training charity whose report says 620 learners enrolled during the year. A results table shows 410 completed at least one module, while a footnote explains that completion data was unavailable for one partner site. Elsewhere, a survey of 180 respondents shows that 72 percent felt more confident applying for work. These invented figures are for demonstration only.

A proposed sentence says, “The program gave 620 people the confidence to find work.” The enrollment count does not establish a confidence outcome, the survey covers a smaller responding group and neither passage establishes that anyone found work. The packet should create separate cards for enrollment, module completion and the respondent-reported confidence result. It should retain the missing-site note and survey denominator.

A supportable proposal might say, subject to review and public clearance: “During the year, 620 learners enrolled. Among 180 survey respondents, 72 percent reported greater confidence in applying for work.” The writer can then offer the executive’s approved interpretation without converting it into an observed employment outcome.

Order cards according to the deliverable, not report pagination. Put the strongest relevant evidence near the section it informs and flag cards requiring a decision. Add a short source map showing where definitions, methodology and limitations live. Give the writer access to the complete original so they can inspect material beyond the extract.

A compact packet takes time to assemble. For a short reactive statement, prepare only the cards required for its few claims. For a long campaign, a broader packet can reduce repeated searching, while every reused card still receives a currency and permission check. The packet succeeds when another reviewer can reproduce each support decision from the cited original page.