Describe the sites and rounds your guards cover. Makeform builds a patrol report form with checkpoint times, observations, incident details, photos, and supervisor routing.
Route patrol submissions to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt the site details, or send it to the builder. The structure is an example, not a submitted report.
Audience
Guards completing interior and exterior rounds
Format
Mobile checkpoint report with conditional incident fields
Prompt size
257 chars
Example form structure
Mobile checkpoint report with conditional incident fields
Guard, site, and shift
Patrol start and finish
Checkpoint status and observation
Was an incident or hazard found?
Photos and supervisor follow-up
Suggested routing tags
Routine round
Incident review
Maintenance follow-up
Record the actual checkpoint visit time so supervisors can review when the route was completed.
Step 1
Identify
guard, site, shift, route, and patrol number
Step 2
Check
actual time and result at every checkpoint
Step 3
Escalate
incident details, actions, photos, and notifications
Step 4
Handoff
unresolved work routed to a supervisor or next shift
Why structured patrol reporting
Connect each observation to a checkpoint, time, response, and follow-up instead of collecting a row of unexplained checks.
Capture visit time, condition, and a concise observation for every stop.
Ask for location, urgency, action, notification, and evidence only when an issue is reported.
A follow-up owner and handoff note keep unresolved work visible.
Fits the assignment
Keep one reporting sequence while changing checkpoints and routing for each location.
Doors, loading bays, parking, alarms, and closing checks in walking order.
Gates, amenities, parking, resident contacts, mileage, and handoff notes.
Perimeters, restricted areas, materials, utilities, and hazards by zone.
Arrival, departure, route order, mileage, missed stops, and account follow-up.
Patrol reporting workflow
Define the route, refine the generated fields, and route each submission for review.
List shifts, checkpoints, issue categories, and report recipients.
Order checkpoints and show incident fields only for exceptions.
Send rounds to supervisors and flagged issues to the responsible team.
Filter by site, checkpoint, issue type, or follow-up status.
Form vs notebook vs generic checklist
The useful difference is whether each checkpoint result connects to its time, evidence, response, and next owner.
Field guide
Use these six sections as a starting point. Match checkpoints and notification paths to each site's instructions.
Assignment identity
Identify the submission before the narrative. Use controlled site and shift choices, plus a round number for repeated patrols.
Route and time
Order checkpoints by route. Capture actual visit time and require a reason when a point is not accessible.
Observations
Identify the exact place, condition, and context. Combine sortable categories with room for direct observations.
Incident and action
Open focused fields when a checkpoint is not normal. Record the issue, urgency, response, and condition when the guard left.
Notification and evidence
Capture notification recipient, method, and time. Pair uploads with captions explaining their location and purpose.
Follow-up and handoff
Separate completed actions from open ones. Give unfinished work a priority, owner, and clear next action.
Related tools
Connect routine rounds with dedicated incident, hazard, property inspection, shift handover, closure, and daily reporting forms.
Capture a fuller account when a patrol observation becomes a separate incident.
Open toolRoute unsafe conditions found during a round for assessment and corrective work.
Open toolRun a more detailed condition review of a building, unit, or shared area.
Open toolPass open issues, special instructions, keys, and equipment to the next guard.
Open toolDocument review, assigned actions, and closure after a security incident is investigated.
Open toolSummarize activity across patrols, posts, and shifts in one daily report.
Open toolFAQ
Practical answers for security supervisors replacing paper logs or inconsistent shift narratives.
It records a scheduled security round: guard, site, shift, route, times, checkpoint results, observations, incidents, actions, notifications, evidence, and follow-up.
Collect guard, site, date, shift, patrol number, start and finish, plus timed checkpoint results. For exceptions, add exact location, category, action, notification, photos, report reference, owner, and handoff notes.
Let the guard select the expected condition and capture visit time at every checkpoint. A final no incidents observed answer may summarize the round, but should not replace checkpoint results.
Yes. Conditional logic can open detail fields after an exception, hazard, alarm, damage, or suspicious activity answer while keeping routine entries short.
Yes. Add file uploads for visible conditions and a caption field so reviewers know the location and what each image shows.
Collect follow-up status, priority, owner, and requested action. Route flagged submissions appropriately, then filter consistent site, checkpoint, and issue categories during review.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your patrol report form. The paid tier removes the Makeform badge; it does not unlock a response allowance.
Yes. Use a required site selector and conditional sections for the correct route, checkpoints, contacts, and escalations. Separate forms may suit sites with very different post orders.
Make every patrol easier to review.
