Off-campus strong-arm robbery September 2016 with update
AI-generated · every claim is source-linkedSyracuse University DPS published a public safety notice. Full text is preserved from the official DPS page.
- Alerts
- 2
- Response
- —
- Killed
- 0
- Injured
- 0
Alert Sequence
2 messages in sequence · 2 verified verbatim
Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.
How the first alert is built
To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.
For the protection and safety of SU students, faculty, staff and neighbors, the Department of Public Safety releases the following alert: OFF CAMPUS STRONG-ARM ROBBERY (Date Issued: September 18, 2016 SPD Case # 16-463374) Sunday, September 18, 2016 at approximately 8:57 p.m. - 500 block Stratford Street. An alumni reported a strong arm robbery that occurred off campus. The alumni reported she was walking in the 500 block of Stratford Street. when she was approached by three unknown males who exited a vehicle and approached her. The suspects used physical force to forcibly steal the alumni's purse. The suspects fled the scene in a vehicle. The alumni sustained no injuries and refused medical attention. There was no threat of a weapon. DPS asks your help in identifying the suspects if you were in the vicinity at the time of the incident. For this purpose, the following is the description of the suspects: 3 Males, 12 to 14 years of age, One male possibly wearing a white T-shirt, were last seen in a white vehicle. For an interactive map of the incident location, refer to the Google Map link at: https://www.google.com/maps/d/edit?hl=en&authuser=0&mid=1uzS6goH3aX9H7S_wyzccWKv5x3s If anyone has any information regarding this incident or others, please contact the Syracuse Police Department at (315) 442-5222 or the Syracuse University Department of Public Safety at (315) 443-2224. If you would like to anonymously report NON-EMERGENCY information for DPS, you can use the Silent Witness tool, available at http://publicsafety.syr.edu/html/silent_witness.html. FOR YOUR SAFETY, PLEASE REMEMBER: • After dark, take advantage of the free safety escort services available through the Department of Public Safety. Both walking and shuttle services are available to students, staff, and faculty at SU or SUNY-ESF. Call 443-SAFE (7233) for more information about these services. • Take advantage of the CENTRO and Birnie Bus services. Taxi services are also available. • Walk, bike or jog in groups of three or more, away from bushes, cars, and other objects a suspect could hide behind. • Plan your walking travel times by avoiding late to early morning hours. • Be aware of your surroundings: look and listen. Headphones and cell phones can create tunnel vision. • Travel in well-lit and populated areas. Keep porch lights on at night. • Download the LiveSafe app on your Android or iOS smart phone. The app provides a virtual escort feature you can use with friends and quick links to important public safety information. Set the app to Syracuse University and sign up with your syr.edu email address! • Don't approach strangers or let them get close to you. • If you think someone is following you, switch directions or cross the street. Go toward an open business or lighted house. • Have your house or car keys in hand before you reach your door. • Know where campus blue light alarms are and how to use them. • If someone tries to rob you, don't resist. Give up your property, not your life. • If you are in a safe place to do so, attempt to get a description of the suspect(s) and any associated vehicles or license plate numbers. IMMEDIATELY report emergencies or suspicious activities, persons and vehicles. For Public Safety dial 443-2224 or #78 (from a cell phone); if you are in a situation where you cannot safely make a phone call, send a text message to 711@syr.edu; for Syracuse Police dial 911. Your quick reporting may help prevent others from becoming victims. This public safety information is issued for your safety in compliance with the Jeanne Clery Act
Sourcepresent25/25
Final assessment
DPS or Public Safety branding identifies the sender.
Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.
See all 25 individual reads
- present: DPS or Public Safety branding identifies the sender Independent review agrees.
- present: Source present via Syracuse University DPS Confirmed on re-read.
- present: Public safety notice is attributed to DPS Based solely on the alert text.
- present: Issuing authority is campus public safety From the full message only.
- present: Source cue is DPS language No outside context used.
- present: Department of Public Safety is named Strict rubric application.
- present: Sender identity is clear Element coded from wording alone.
- present: Agency attribution is present Same conclusion on second look.
- present: Syracuse DPS is the named issuer Matches the public-warning test.
- present: Institutional public-safety sender is stated Wording is decisive here.
- present: DPS or Public Safety branding identifies the sender Clear cut for this element.
- present: Source present via Syracuse University DPS Borderline language still codes this way.
- present: Public safety notice is attributed to DPS Standard pattern for this element.
- present: Issuing authority is campus public safety Consistent with prior passes.
- present: Source cue is DPS language Re-checked against the full text.
- present: Department of Public Safety is named Pass applies the same bar as peers.
- present: Sender identity is clear Text support is adequate.
- present: Agency attribution is present Rubric threshold met.
- present: Syracuse DPS is the named issuer Second independent look agrees.
- present: Institutional public-safety sender is stated Coding rests only on transmitted text.
- present: DPS or Public Safety branding identifies the sender No inference beyond the notice.
- present: Source present via Syracuse University DPS Present or absent is unambiguous.
- present: Public safety notice is attributed to DPS Element decision is stable.
- present: Issuing authority is campus public safety Full-message pass confirms.
- present: Source cue is DPS language Final pass agrees with the set.
Hazardpresent25/25
Final assessment
Hazard is the named crime or emergency event.
What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.
See all 25 individual reads
- present: Hazard is the named crime or emergency event Independent review agrees.
- present: Offense type is stated as the hazard Confirmed on re-read.
- present: Crime or hazard under investigation is explicit Based solely on the alert text.
- present: Alert names the threat or incident type From the full message only.
- present: Hazard element is the reported offense No outside context used.
- present: Incident category is clear from the wording Strict rubric application.
- present: Named emergency condition is the hazard Element coded from wording alone.
- present: The public-safety threat is specified Same conclusion on second look.
- present: Hazard is the named crime or emergency event Matches the public-warning test.
- present: Offense type is stated as the hazard Wording is decisive here.
- present: Crime or hazard under investigation is explicit Clear cut for this element.
- present: Alert names the threat or incident type Borderline language still codes this way.
- present: Hazard element is the reported offense Standard pattern for this element.
- present: Incident category is clear from the wording Consistent with prior passes.
- present: Named emergency condition is the hazard Re-checked against the full text.
- present: The public-safety threat is specified Pass applies the same bar as peers.
- present: Hazard is the named crime or emergency event Text support is adequate.
- present: Offense type is stated as the hazard Rubric threshold met.
- present: Crime or hazard under investigation is explicit Second independent look agrees.
- present: Alert names the threat or incident type Coding rests only on transmitted text.
- present: Hazard element is the reported offense No inference beyond the notice.
- present: Incident category is clear from the wording Present or absent is unambiguous.
- present: Named emergency condition is the hazard Element decision is stable.
- present: The public-safety threat is specified Full-message pass confirms.
- present: Hazard is the named crime or emergency event Final pass agrees with the set.
Locationpresent25/25
Final assessment
A street, building, or campus area is specified.
Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.
See all 25 individual reads
- present: A street, building, or campus area is specified Independent review agrees.
- present: Location is given as a named place near campus Confirmed on re-read.
- present: Geographic detail anchors the incident Based solely on the alert text.
- present: Address or landmark appears in the notice From the full message only.
- present: Where it happened is stated for the community No outside context used.
- present: Place name or block is present Strict rubric application.
- present: Campus-area location cue is clear Element coded from wording alone.
- present: A street, building, or campus area is specified Same conclusion on second look.
- present: Location is given as a named place near campus Matches the public-warning test.
- present: Geographic detail anchors the incident Wording is decisive here.
- present: Address or landmark appears in the notice Clear cut for this element.
- present: Where it happened is stated for the community Borderline language still codes this way.
- present: Place name or block is present Standard pattern for this element.
- present: Campus-area location cue is clear Consistent with prior passes.
- present: A street, building, or campus area is specified Re-checked against the full text.
- present: Location is given as a named place near campus Pass applies the same bar as peers.
- present: Geographic detail anchors the incident Text support is adequate.
- present: Address or landmark appears in the notice Rubric threshold met.
- present: Where it happened is stated for the community Second independent look agrees.
- present: Place name or block is present Coding rests only on transmitted text.
- present: Campus-area location cue is clear No inference beyond the notice.
- present: A street, building, or campus area is specified Present or absent is unambiguous.
- present: Location is given as a named place near campus Element decision is stable.
- present: Geographic detail anchors the incident Full-message pass confirms.
- present: Address or landmark appears in the notice Final pass agrees with the set.
Guidancepresent25/25
Final assessment
Guidance is contact DPS or local police.
The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.
See all 25 individual reads
- present: Guidance is contact DPS or local police Independent review agrees.
- present: Protective advice or contact instructions appear Confirmed on re-read.
- present: Community is told what to do next Based solely on the alert text.
- present: Safety tips or reporting steps are present From the full message only.
- present: Stay-away or lock-up guidance is given No outside context used.
- present: Call-to-action for the audience is clear Strict rubric application.
- present: Resource or reporting guidance is included Element coded from wording alone.
- present: Guidance is contact DPS or local police Same conclusion on second look.
- present: Protective advice or contact instructions appear Matches the public-warning test.
- present: Community is told what to do next Wording is decisive here.
- present: Safety tips or reporting steps are present Clear cut for this element.
- present: Stay-away or lock-up guidance is given Borderline language still codes this way.
- present: Call-to-action for the audience is clear Standard pattern for this element.
- present: Resource or reporting guidance is included Consistent with prior passes.
- present: Guidance is contact DPS or local police Re-checked against the full text.
- present: Protective advice or contact instructions appear Pass applies the same bar as peers.
- present: Community is told what to do next Text support is adequate.
- present: Safety tips or reporting steps are present Rubric threshold met.
- present: Stay-away or lock-up guidance is given Second independent look agrees.
- present: Call-to-action for the audience is clear Coding rests only on transmitted text.
- present: Resource or reporting guidance is included No inference beyond the notice.
- present: Guidance is contact DPS or local police Present or absent is unambiguous.
- present: Protective advice or contact instructions appear Element decision is stable.
- present: Community is told what to do next Full-message pass confirms.
- present: Safety tips or reporting steps are present Final pass agrees with the set.
Timepresent25/25
Final assessment
A clock time or calendar date is stated.
When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.
See all 25 individual reads
- present: A clock time or calendar date is stated Independent review agrees.
- present: When the incident occurred is explicit Confirmed on re-read.
- present: Temporal detail appears in the notice Based solely on the alert text.
- present: Date or approximate time is provided From the full message only.
- present: Time cue supports the narrative No outside context used.
- present: Day and time markers are present Strict rubric application.
- present: A clock time or calendar date is stated Element coded from wording alone.
- present: When the incident occurred is explicit Same conclusion on second look.
- present: Temporal detail appears in the notice Matches the public-warning test.
- present: Date or approximate time is provided Wording is decisive here.
- present: Time cue supports the narrative Clear cut for this element.
- present: Day and time markers are present Borderline language still codes this way.
- present: A clock time or calendar date is stated Standard pattern for this element.
- present: When the incident occurred is explicit Consistent with prior passes.
- present: Temporal detail appears in the notice Re-checked against the full text.
- present: Date or approximate time is provided Pass applies the same bar as peers.
- present: Time cue supports the narrative Text support is adequate.
- present: Day and time markers are present Rubric threshold met.
- present: A clock time or calendar date is stated Second independent look agrees.
- present: When the incident occurred is explicit Coding rests only on transmitted text.
- present: Temporal detail appears in the notice No inference beyond the notice.
- present: Date or approximate time is provided Present or absent is unambiguous.
- present: Time cue supports the narrative Element decision is stable.
- present: Day and time markers are present Full-message pass confirms.
- present: A clock time or calendar date is stated Final pass agrees with the set.
Impactpresent25/25
Final assessment
Impact includes injury, custody, or outcome status.
What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.
See all 25 individual reads
- present: Impact includes injury, custody, or outcome status Independent review agrees.
- present: Consequence for people or property is stated Confirmed on re-read.
- present: Investigation result or harm detail appears Based solely on the alert text.
- present: Outcome language codes impact From the full message only.
- present: Arrest, injury, or all-clear status is impact No outside context used.
- present: What happened to people or operations is noted Strict rubric application.
- present: Impact includes injury, custody, or outcome status Element coded from wording alone.
- present: Consequence for people or property is stated Same conclusion on second look.
- present: Investigation result or harm detail appears Matches the public-warning test.
- present: Outcome language codes impact Wording is decisive here.
- present: Arrest, injury, or all-clear status is impact Clear cut for this element.
- present: What happened to people or operations is noted Borderline language still codes this way.
- present: Impact includes injury, custody, or outcome status Standard pattern for this element.
- present: Consequence for people or property is stated Consistent with prior passes.
- present: Investigation result or harm detail appears Re-checked against the full text.
- present: Outcome language codes impact Pass applies the same bar as peers.
- present: Arrest, injury, or all-clear status is impact Text support is adequate.
- present: What happened to people or operations is noted Rubric threshold met.
- present: Impact includes injury, custody, or outcome status Second independent look agrees.
- present: Consequence for people or property is stated Coding rests only on transmitted text.
- present: Investigation result or harm detail appears No inference beyond the notice.
- present: Outcome language codes impact Present or absent is unambiguous.
- present: Arrest, injury, or all-clear status is impact Element decision is stable.
- present: What happened to people or operations is noted Full-message pass confirms.
- present: Impact includes injury, custody, or outcome status Final pass agrees with the set.
Systematic AI judgments with visible reasoning, not human-validated codings.
About this analysisBackground
Key Findings
Sources
Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.
- Official
Campus Alert Archive. "Syracuse University: Off-campus strong-arm robbery September 2016 with update." Incident of September 19, 2016. Added July 2026. https://campusalertarchive.com/case/syracuse-university-off-campus-strong-arm-robbery-september-2016-with--2016-09-19/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.