Robbery Description and Witness Form
Document a robbery suspect description, direction of flight, and witness observations in one structured form before memories fade. Use it to capture facts quickly, consistently, and with a clear submission record.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Retail · Financial Services · Logistics · Hospitality
Overview
This Robbery Description and Witness Form template captures the facts people usually forget first: what the suspect looked like, what direction they fled, what was observed, and who can be contacted for follow-up. It is built for the first minutes after an incident, when a structured record is more useful than a freeform email chain.
The template includes a submission notice, incident details, suspect description, direction of flight, witness observations, and witness information. That structure helps separate firsthand observations from later discussion, which is important when multiple people are involved and memories can influence each other. It also gives you a cleaner record for internal review, insurance, or law-enforcement handoff.
Use this form when a robbery or attempted robbery has occurred and you need a consistent witness statement format. It is especially useful in retail, banking, hospitality, and logistics settings where staff may need to report quickly across shifts or locations. Do not use it as a general theft log or as a substitute for emergency response procedures.
When not to use it: if there was no robbery-related threat, if no witness has direct observations, or if your team only needs a simple property-loss record. Keep the form focused on observable facts, use optional fields for uncertain details, and avoid collecting unnecessary PII. A clear submission confirmation and follow-up note help set expectations after the report is sent.
Standards & compliance context
- If witness contact information is collected, limit it to what is necessary and disclose how it will be used to align with GDPR Article 5 data minimization.
- If the form is used in a workplace setting, keep the language neutral and avoid collecting unrelated personal details that could create unnecessary PII exposure.
- If your process may involve recorded statements, include a consent-to-record notice before any audio or video capture begins.
- For public-facing or shared intake use, ensure labels, focus order, and validation support WCAG 2.1 AA accessibility.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section sets expectations for consent, recording, and what happens after the report is submitted.
- I am completing this form based on my own observations and, if possible, before discussing the event with other witnesses.
-
Consent to record this witness statement
This form may be used for internal security review, incident documentation, and law-enforcement follow-up if needed.
-
Additional submission notes
Do not include unnecessary PII. Share only what you directly observed.
Incident Details
This section anchors the report with the date, time, location, and a short factual summary.
- Date of incident
- Approximate time of incident
- Location where the robbery occurred
-
Brief summary of what happened
Keep the summary factual and concise.
Suspect Description
This section captures only the observable traits that help identify the suspect without forcing guesses.
- Number of suspects observed
- Suspect gender presentation, if observed
- Approximate age range
- Height and build
- Clothing and visible accessories
- Distinguishing features
Direction of Flight
This section records where the suspect went and how they left so responders can act on the most useful details.
- Direction of flight
- How the suspect left the scene
- Vehicle description, if observed
- Last place the suspect was seen
Witness Observations
This section separates firsthand observations from assumptions and helps preserve the most reliable account.
- Observed actions
- Was a weapon observed?
- Weapon type observed
- Other witnesses present
- Additional observations
Witness Information
This section collects only the contact details needed for follow-up and keeps PII limited to what is necessary.
-
Witness name
Optional unless your organization requires identification for follow-up.
-
Witness contact information
Phone number or email for follow-up.
- Preferred contact method
How to use this template
- 1. Add the submission notice at the top so the witness understands what the form records, whether consent to record is needed, and what happens after submission.
- 2. Configure the incident details section with date and time pickers, a location field, and a short incident summary field that prompts for only observable facts.
- 3. Set the suspect description and flight sections to use conditional logic so witnesses can skip unknown details instead of guessing or filling every field.
- 4. Assign the form to the incident coordinator, security lead, or manager who will review the submission, preserve the audit trail, and route follow-up if needed.
- 5. Review the witness observations for completeness, then contact the witness only through the preferred method provided if clarification is necessary.
Best practices
- Use date and time pickers for the incident details so witnesses do not enter inconsistent timestamps.
- Mark witness contact fields optional unless your process truly requires follow-up, and explain why the information is being collected.
- Keep suspect description fields focused on observable traits such as clothing, build, and distinguishing features rather than assumptions about identity.
- Use progressive disclosure for weapon and vehicle questions so the form stays short when those details do not apply.
- Ask for the last seen location and direction of flight in separate fields so responders can act on both movement and place.
- Include a clear submission confirmation line that tells the witness who will receive the report and whether they may be contacted again.
- Avoid merging witness observations into a single narrative field if you need a reliable audit trail and easier comparison across statements.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this form be used?
Use it immediately after a robbery or attempted robbery, once people are safe and emergency services have been contacted if needed. It is designed to capture first-hand observations while details are still fresh. It should not replace a police report or internal incident escalation. It works best as a first-pass record before anyone starts comparing notes.
Who should complete the form?
A manager, security lead, HR representative, or other designated incident coordinator can collect the information, but each witness should provide their own observations separately when possible. The form is most useful when one person records the event and another reviews it for completeness. Avoid having one witness fill in details for everyone else. That can blur firsthand observations and reduce reliability.
Does this form need to be filled out for every theft incident?
No. This template is specifically for robbery or attempted robbery where there is a suspect description, flight details, or witness observations to capture. For routine theft without confrontation, a different incident or loss report is usually a better fit. Keeping the scope narrow helps avoid collecting unnecessary PII or unrelated details.
What information should be captured in the suspect description section?
Record only what the witness actually observed, such as approximate age range, height, build, clothing, and distinguishing features. Use conditional logic or optional fields so the form does not force guesses when a witness is unsure. Do not ask for overly sensitive or unnecessary details. The goal is a usable description, not speculation.
Should the form collect witness contact information?
Only if you need to follow up for an investigation, insurance claim, or law-enforcement request. If you collect contact details, include a brief disclosure about how the information will be used and who may access it. Mark those fields as optional unless contact is required for your process. This supports data minimization and reduces friction for witnesses.
How does this template help compared with an ad-hoc note or email?
A structured form keeps the same facts in the same order every time, which makes it easier to compare statements and preserve an audit trail. Ad-hoc notes often miss the direction of flight, last seen location, or witness observations. A template also makes it easier to use validation, required-vs-optional field labels, and progressive disclosure. That improves completeness without overwhelming the witness.
Can this template be customized for different locations or security workflows?
Yes. You can add site-specific location fields, incident routing, or internal reference numbers, and you can remove any fields you do not need. Many organizations also add conditional logic for weapon observed, vehicle description, or multiple witnesses. Keep the form focused on what your team will actually use after submission. That helps avoid collecting extra PII.
What should happen after the form is submitted?
The submission should route to the designated incident owner, security team, or manager, and the witness should see a clear confirmation that the report was received. If your process requires follow-up, note that the witness may be contacted for clarification. A visible submission notice helps set expectations and reduces duplicate reporting. It also supports a cleaner audit trail.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
Discover proven strategies to motivate retail employees—from recognition and communication to mobile-first training tools that drive engagement and reduce...
-
MangoApps is named a Leader in the IDC MarketScape for Content Management in Authenticated Digital Workspaces. See what sets our intranet platform apart.
Ready to use this template?
Get started with MangoApps and use Robbery Description and Witness Form with your team — pricing built for small business.
