Defining the prevention problem and work boundaries · Lesson 1

From reports to a defined prevention problem

9 min read

Lesson objectives

  • Apply From reports to a defined prevention problem to a fictional community case, documenting the decision and its limits in a reviewable work product.
Reading tools

Imagine a transit facility receiving three messages in one week: “There are thefts everywhere here,” “I no longer feel safe by the cycle parking,” and “My child's bicycle disappeared on Tuesday evening.” These messages matter, but they supply different kinds of information. The first is a broad judgment needing a defined scope and evidence. The second reports fear, which matters for design and evaluation, but is not an incident count. The third describes an event that can be checked. On its own, it does not establish a recurring problem or identify who took the bicycle. A prevention specialist separates these layers before deciding what to measure or change.

An event is a particular occurrence with a time, place, behavior, or harm, recorded in a facility log, official report, or account. A recurring problem is a pattern of sufficiently similar events and harms that warrants an organized prevention response. An indicator is a partial measure, such as the number of eligible reports in a month. It is not the pattern itself: reporting may rise when residents gain confidence in a reporting channel. A witness's use of the word “theft” is not a final legal finding. Legal definitions and procedures differ by jurisdiction; this program teaches prevention planning within the specialist's authority.

Build a problem card by naming the observed behavior before describing a group of people. Record the place, period, unit of count, affected people, source of each observation, and remaining unknowns. “The neighborhood is unsafe” gives no behavior to track, intervention site, or baseline. “Recorded bicycle losses near the station's east entrance between 18:00 and 22:00 over four weeks” is more useful. It remains incomplete until we know how duplicates were removed and how many bicycles were parked. A tight definition protects the decision: changing entrance lighting should not be evaluated against an unrelated neighborhood wide count.

In our fictional facility file there are 18 messages over four weeks. Six repeat earlier messages. Three describe fear without property loss, two describe bicycle scratches, and seven concern bicycle losses near the east entrance. The team checks the seven loss messages and finds six independent events because two accounts describe the same bicycle on the same day. The current count is six recorded loss events, not 18 confirmed crimes. Four of the six occurred between 18:00 and 22:00. That alone does not prove evenings are riskier: use of the entrance and the number of parked bicycles may differ by time. Obtain an exposure denominator before calculating or comparing rates.

A defensible provisional card reads: “The facility log records six independent bicycle loss events near the east entrance over four weeks; four occurred in the evening. Legal classification, the number of bicycles exposed, and changes in reporting remain unverified. The team will examine storage and entrance management and improve reporting without identifying a suspect.” Keep three fear reports outside the event count. They may support a separate measure of perceived safety if collected without exposing respondents. An account of an ongoing threat or immediate danger leaves routine pattern analysis and follows the facility's local emergency referral process.

Why write down unknowns? They can reverse the intervention choice. If losses involve bicycles left without secure storage, access to storage may be worth testing. If locked bicycles are lost inside an area controlled by the facility, inspect place management. If messages rose after a reporting campaign, the message series alone cannot demonstrate an increase in incidents. These are testable hypotheses, not blame assigned to people who experienced harm and not proof of a single cause. Problem oriented work moves from scanning to analysis, response, and assessment. Community participation helps set priorities, but it does not authorize a specialist to investigate individuals or publish personal accounts.

Before using the card, ask whether another person could reproduce the incident count from its inclusion rules, whether the place and period connect to an action the organization can take, and whether observed facts have been separated from hypotheses and referral needs. If any answer is no, revise the rule or collect the missing information. The output is a small working file: a behavioral definition, an account to event conversion table, a provisional indicator with limits, and a short list of data needs for the next lesson.

Now consider information arriving late. After the weekly count closes, a bicycle owner says that he sent his message from his brother's phone. A matching telephone number does not establish that two reports describe one event. Check the loss date, item description and location, then seek only the clarification needed. Retain the earlier decision and correction date so a colleague can explain why two report versions differ.

Create a short amendment log recording the change, its reason, the responsible role and its effect on the count. Use a functional description such as “separated two events after confirming different bicycles.” Keep identifying information in the system authorized to hold it. The analysis copy needs a local event identifier and verification status; the person contacting the reporter uses a separate secure channel. Separating these functions limits circulation while preserving a way to clarify information.

Another difficulty concerns events outside the scope. Suppose a message describes a bag lost inside a bus while your assignment concerns bicycle racks. Record the exclusion reason in the screening table and pass the report to the appropriate service where the local procedure allows. Exclusion from a narrowly defined indicator does not mean ignoring harm. Completing the reporting service and counting the selected prevention problem are distinct responsibilities.

A colleague's independent classification can reveal an unclear definition. Give the colleague four invented messages with identifying details removed and ask them to apply the inclusion rules alone. Compare decisions before comparing final totals. Equal totals may hide opposite errors: one person adds an event and drops another. Improve the ambiguous wording, then reclassify affected records.

Finish the review with a specific learning question: which fact, if changed, would alter inclusion? A fear-only message changes category if a described loss emerges. A reminder may become a separate event if clarification establishes a different item and date. This question teaches the reason for the rule instead of encouraging memorization of an answer count. Tomorrow, try the definition on a fresh record before using it in a routine report.

Lesson summary

Five new messages arrive after a poster encourages reporting.