A strong source list is more than a collection of links: it is a working map of the people, records, studies, and observations that can support every important claim in a reporting project. This guide explains how to build one from the first idea through publication.
Define the reporting question first
Before searching for sources, write down what you are trying to establish. A broad topic such as “rising housing costs” can produce thousands of possible sources, while a focused question gives you a useful filter.
Write a short reporting brief that includes:
- The central question you want to answer.
- The location or community involved.
- The time period being examined.
- The people, institutions, or systems affected.
- The claims you expect to investigate.
- The deadline and publishing format.
For example, instead of starting with “investigate local housing,” define the project as: “How have rent increases affected tenants in one city since 2022, and what policies or market changes contributed to them?”
Break the main question into smaller reporting questions. You might need to determine how rents changed, which neighborhoods were most affected, what landlords or officials say, whether public assistance changed, and how individual tenants experienced the change. Each subquestion will require different kinds of sources.
Create a preliminary claim list as well. Mark each claim as either a fact you need to verify, a question that needs an answer, or context that will help readers understand the issue. This prevents you from collecting interesting material that does not actually serve the story.
Start with a source map
A source map is a simple plan for the kinds of evidence you need. Do not rely on one category, such as online articles or interviews. Good reporting usually combines several source types because each has different strengths and weaknesses.
Consider including:
- Primary documents: budgets, court filings, inspection reports, contracts, meeting minutes, public records, datasets, and official correspondence.
- Direct witnesses: people who experienced the event or are directly affected by the issue.
- Decision-makers: officials, company representatives, administrators, lawyers, or organizers who can explain actions and policies.
- Independent experts: researchers or practitioners who can interpret evidence without being directly responsible for the outcome.
- Historical and contextual sources: earlier reporting, books, academic papers, archives, and institutional histories.
- On-the-ground observations: visits, public meetings, facilities, neighborhoods, and events you personally observe.
- Opposing or alternative perspectives: credible sources that challenge your initial assumptions or offer a different explanation.
A source map also reveals gaps. If your list contains ten advocacy groups but no government records, affected residents, or independent analysis, it is not yet balanced. Balance does not mean giving every claim equal credibility; it means understanding the relevant evidence and allowing significant parties a fair opportunity to respond.
Build the source-list spreadsheet
A spreadsheet is often the most flexible tool for a reporting project. A notes app can work for a small assignment, but a spreadsheet makes it easier to sort by source type, follow-up status, and relevance.
Use one row per source or contact. Add columns such as these:
| Column | What to record |
|---|---|
| Source ID | A short label such as S-001 or DOC-04 |
| Name or title | Person, organization, document, or dataset |
| Source type | Interview, record, study, observation, or other category |
| Contact or URL | Email, phone, office, archive location, or direct link |
| Key information | What this source may establish |
| Reliability notes | Expertise, firsthand knowledge, conflicts, or limitations |
| Status | Not contacted, requested, scheduled, received, reviewed, or used |
| Follow-up | Your next action and due date |
| Citation details | Publisher, date, author, page, file name, or access date |
Assign each source an ID as soon as you add it. Use the ID in your interview notes and drafts so you can quickly trace a statement back to its origin. For documents, include page numbers or section names. For datasets, record the table, field, date range, and any definitions that affect interpretation.
Keep the source list separate from raw notes, but connect them clearly. A source row should tell you where evidence came from; your reporting notes should preserve the actual quotation, statistic, observation, or document passage. Avoid putting important evidence only in a browser bookmark or a memory-based note.
Find sources systematically
Search in stages rather than entering the same broad phrase repeatedly. Begin with orientation searches to learn the vocabulary of the issue. Identify the agencies, laws, companies, researchers, programs, neighborhoods, and technical terms that appear repeatedly.
Then search for original material. Useful search patterns include:
- A person or organization plus “report,” “budget,” “audit,” or “minutes.”
- A policy name plus “full text,” “implementation,” or “evaluation.”
- A company or agency plus “contract,” “complaint,” “inspection,” or “lawsuit.”
- A dataset name plus “methodology,” “codebook,” or “data dictionary.”
- A study title or author in a scholarly database.
- A local government department plus the relevant year and subject.
Search beyond the first page of results. Official repositories, public libraries, court databases, university archives, and meeting portals may be less polished than commercial websites but can contain more useful evidence.
When you find a valuable document, examine its references, footnotes, authors, cited organizations, and named participants. This “citation chaining” can produce better sources than starting a completely new search. Also search for the document title in quotation marks to locate revised editions, corrections, or archived copies.
Record a source immediately. Save the direct URL, title, author, publication date, and the reason it matters. Web pages can change, move, or disappear, so download permitted documents and note the access date. Do not assume that a search-result snippet is an adequate source.
Evaluate every source before relying on it
A source can be useful without being neutral, and a source can be official without being complete. Evaluate evidence on several dimensions instead of assigning a vague label such as “good” or “bad.”
Ask these questions:
- What does the source know firsthand? A resident may describe a personal experience but not the full policy history. A data analyst may explain a dataset but not what happened to one individual.
- How close is the source to the event? Consider timing, access, and whether the source directly observed what it describes.
- What expertise or authority does the source have? Check the person’s role, qualifications, publication history, or responsibility for the relevant record.
- What interest or incentive might shape the account? Funding, political goals, employment, litigation, reputation, and personal conflict can all matter.
- Can the claim be independently verified? Look for records, additional witnesses, data, or contemporaneous evidence.
- Is the material current enough? A reliable older report may not describe present conditions.
- Are the methods visible? For surveys, studies, and datasets, look for sample size, definitions, collection methods, exclusions, and uncertainty.
Add these observations to the reliability-notes column. For example: “Direct witness to the incident; remembers approximate date; account should be checked against meeting video and minutes.” This is more useful than simply writing “credible.”
Manage interviews and source relationships
A source list should track relationships, not just names. Before contacting someone, note why they are relevant and what you need to learn. Prepare open-ended questions first, then specific verification questions.
A practical contact record includes:
- Date and method of contact.
- What you requested.
- Whether the source agreed to speak or provide records.
- Any deadline or preferred communication method.
- Promises made about confidentiality or attribution.
- Important follow-up questions.
- Whether the source has reviewed or supplied documents.
Be precise about the ground rules. “Off the record,” “background,” “not for attribution,” and “on the record” can mean different things to different people. Explain how you understand the arrangement before substantive information is shared, and record the agreement in your notes.
Do not promise anonymity casually. Before offering it, consider whether you can protect the source, whether the information can be verified elsewhere, and whether the public interest justifies the risk. If anonymity is necessary, document the reason and discuss with an editor how the source will be described without exposing them.
Give people a fair chance to respond to significant allegations. Send specific questions, relevant dates, and a reasonable deadline. Keep copies of your request and any response, including a statement that the person declined to comment.
Connect sources to claims
As reporting develops, build a claim-evidence matrix. List each important statement you may publish and identify the supporting source, the exact passage or data point, and any remaining uncertainty.
For each claim, record:
- The proposed wording.
- The source ID or IDs supporting it.
- The precise page, timestamp, row, or quotation.
- Whether the support is direct or inferential.
- What opposing or qualifying evidence exists.
- Whether the claim needs an editor’s review.
Prefer two independent forms of support for major claims when practical. A public record may establish that a decision occurred, while an interview may explain its consequences. Two sources that repeat the same press release are not truly independent confirmation.
Separate fact from interpretation. “The agency reduced the program budget by 18 percent” is a factual claim that should be tied to budget documents and a clearly defined comparison. “The reduction harmed access” is an interpretation that may require service data, interviews, or expert analysis. Keep the wording proportional to the evidence.
Keep the list current during reporting
Source lists become unreliable when they are treated as finished documents. Set aside a short period at the end of each reporting session to update statuses and next actions.
Useful statuses include:
- Identified
- Contact information needed
- Contacted
- Waiting for reply
- Interview scheduled
- Records requested
- Records received
- Evidence reviewed
- Needs verification
- Used in draft
- Not used
Add dates to follow-up tasks. A row that says “follow up” is easy to ignore; “email records office on Thursday” is actionable. Use filters to see all unanswered requests, all sources related to one claim, or all documents missing citation details.
Save versioned copies if the project is important. A dated backup can help you reconstruct when a source was added or when a document changed. Protect personal information and limit access to sensitive notes, especially when they contain private contact details or confidential reporting material.
Troubleshoot common problems
The list is too short. Revisit the source map and identify which evidence category is missing. Search the names and terms found in your strongest document, then look for records rather than more commentary.
The list is too large. Add a relevance score or priority field. Rank sources by how directly they address the reporting question, how difficult they are to replace, and how much independent verification they provide. Archive low-value links instead of deleting them immediately.
Several sources repeat the same claim. Trace the claim backward to its original document or data. Repetition can create the appearance of confirmation without adding new evidence.
A key source will not respond. Send a concise follow-up, try an alternate official contact method, search for public records, and identify another person who can address the same factual question. Record your attempts so the reporting history is clear.
A document is inaccessible or disappears. Look for an official archive, library copy, meeting packet, court filing, or permitted archived version. Preserve the citation and describe any access limitation rather than presenting an unverified summary.
The source gives useful information but has a conflict of interest. Do not automatically discard the material. Identify the conflict, seek corroboration, and explain the source’s role accurately in your notes and, when relevant, in the published story.
A statistic does not make sense. Check the definition, denominator, date range, geographic scope, missing values, and whether the comparison is like-for-like. Ask the data provider for a methodology document before interpreting the number.
Final pre-publication check
Before filing or publishing, scan the source list alongside the draft. Every consequential factual claim should have a traceable source. Every quotation should be accurate and attributed to the correct person. Every number should have a defined source, date, unit, and comparison.
Check that:
- Names, titles, organizations, and dates are spelled correctly.
- Links work or the document can otherwise be located.
- Citations identify the relevant page, table, or timestamp.
- Allegations include evidence and a documented response request.
- Anonymous sources have a recorded justification and editor approval where required.
- Your wording does not claim more than the evidence shows.
- Important gaps and limitations are visible in your notes.
A well-maintained source list saves time at every stage: it improves research, makes follow-up easier, exposes weak evidence, and gives editors a clear path to verify the work. Most importantly, it helps you build a story where each important statement can be traced back to evidence rather than memory, assumption, or an attractive but unreliable link.