2 Reporting and Story Development
Learn how to develop a promising story idea into a focused, evidence-based account by planning and combining observation with document research.
From idea to story
A story idea is a starting point, not yet a story. Reporting develops it into a focused, answerable account grounded in evidence and relevant to the public. Ideas may come from regular attention to a community or , everyday observations, public records, or gaps in existing coverage. A small, surprising detail can prompt a question, but further reporting determines whether that question supports a worthwhile story.
Choose an
An idea identifies a topic or possible event; an gives it a specific direction. A broad subject such as “public transit” is not yet focused enough. The question “Why have delays increased on the eastbound route since the schedule change?” identifies a direction and suggests what information to seek.
Use questions to test whether an idea can support a story:
Why does it matter to the community? Consider who is affected and what is at stake.
What is new, changing, unusual, or not yet understood? Look for a meaningful development or an unanswered question.
What evidence could answer the question? Identify observations, records, or other reporting needed.
Is the scope manageable? If not, narrow the place, time period, population, or issue.
Ideas may be prompted by recurring patterns, community concerns, meetings, earlier coverage, or a document that raises a new question. Public-records reporting can begin with a question that calls for specific records, or with records that reveal a story worth pursuing. An early explanation should remain a question to test, not a fact to prove.
Plan the reporting
Before gathering material, make a . State the working question and why it matters; summarize what is known and what remains uncertain; define the story’s boundaries; and list the evidence needed to answer the question. Identify possible places and events to observe, likely documents, a timeline, and practical limits such as access and deadlines. Change the plan when evidence challenges the initial idea.
For a possible story about bus delays, define a route and time period. A reporter might observe buses at several stops during the morning commute and examine schedules, service alerts, and available on-time-performance records. This plan is more useful than a vague assignment to “look into transit” because it identifies a question, a scope, and evidence that can support or complicate an answer.
Regular coverage can help reporters notice incremental changes and build knowledge over time. Effective coverage connects institutions and policies with their effects on people, rather than treating official activity as the whole story.
Observe firsthand
means going to a relevant place or event and recording what happens firsthand. Take clear notes on time, location, sequence, conditions, and details that help explain the scene. Distinguish what you directly witnessed from what you inferred or learned elsewhere.
For the bus example, a reporter might record scheduled and actual arrival times at selected stops. Notes should specify when and where each observation occurred and how many buses were observed. These details help readers understand what the observations show and what they do not show.
A single visit can describe that moment, but cannot by itself establish a trend; repeated observations or other evidence may be needed. adds detail and context, but does not by itself support claims about causes or patterns.
Research documents
Documents can reveal decisions, rules, spending, timelines, and patterns that may be difficult to see during a brief visit. Depending on the story, useful records might include meeting agendas and minutes, budgets, inspection reports, schedules, service alerts, or datasets. Identify records that could answer a specific question, then locate them through the relevant agency, archive, database, or public-records request process. Access rules and exemptions vary by jurisdiction.
Read records critically. Check who created them, when and why; understand their definitions and units; note missing information, exceptions, and limits; and compare records across time or against firsthand observations. A document is evidence, not an automatic explanation. For example, a transit performance report may count only certain kinds of delay or summarize a period that differs from the reporter’s observations. Explain how a record was obtained when that helps readers assess it.
Let evidence shape the story
Strong story development moves from a promising idea to an open, focused question. Choose an that matters, plan the scope and evidence, and gather information systematically. Observation shows what happened in a particular place and time; documents can reveal rules, decisions, and broader patterns. Use both carefully, recognize their limits, and let the evidence—not the initial hunch—shape the story.