Describe the premises, patrol schedule, and checkpoints. Makeform creates a mobile-friendly security check form for times, locations, status, photos, incidents, and follow-up.
Send records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adjust it for your site, or send it to the builder. The field outline shows an example structure.
Audience
Guards checking offices after business hours
Format
Checkpoint patrol form with exceptions
Prompt size
294 chars
Example form structure
Checkpoint patrol form with exceptions
Guard, shift, and round times
Which checkpoint are you inspecting?
Checkpoint status
Photo of an exception
Action taken and follow-up
Suggested routing tags
Round complete
Follow-up needed
Incident reported
Require a result at each named checkpoint so a missed location is visible.
Step 1
Identify
guard, site, shift, and patrol round
Step 2
Inspect
each checkpoint gets a recorded result
Step 3
Escalate
exceptions capture evidence and actions
Step 4
Handover
open items reach the next responsible person
Routine checks, usable records
Guide guards through checkpoints and highlight exceptions.
Give doors, alarms, cameras, lighting, rooms, and perimeter points a clear status.
Ask for location, notes, photo, action, and escalation only when there is an exception.
Show the incoming shift which observations are closed and which still need attention.
Adapt to the site
Replace the sample checkpoints, results, and escalation contacts with your procedure.
Check lobbies, plant rooms, server areas, stairs, parking, and perimeter doors.
Check fences, gates, loading bays, restricted inventory, alarms, and keys.
Structure opening, closing, occupancy, cash-area, service-entry, and exterior checks.
Log gates, common areas, parking, amenities, lighting, and vacant units.
Build the patrol workflow
Define normal results, then add focused questions for exceptions.
Name the building, shifts, patrol frequency, checkpoints, and escalation contacts.
Use concise statuses, then require evidence and actions for exceptions.
Walk the route, clarify checkpoint names, and remove unnecessary fields.
Send checks to operations and notify contacts when follow-up is needed.
Form vs logbook vs chat
Compare how each approach records checkpoints, evidence, and handover status.
Field guide
Use these six sections to keep routine answers short and exception records useful.
Guard and assignment
Capture guard, site, post, shift, and round. Use lists for stable names so records group cleanly.
Timing and route
Capture start and finish times. Let the selected route control which checkpoints appear.
Checkpoint results
Use repeatable statuses such as secure, issue found, or unable to inspect. Tailor labels to each item.
Exception evidence
Show detail fields after an exception. Ask for location, observation, photo, and any blocked access.
Action and escalation
Record the guard's immediate action and the person notified, with notes for extra context.
Follow-up and handover
Record whether follow-up is required, its owner, review time, and any related report reference.
Related tools
Connect checks to related site workflows.
Capture events, evidence, notifications, and actions after an incident.
Open toolReport events needing more detail than a checkpoint exception.
Open toolPass open observations and follow-up to the incoming team.
Open toolRoute failed lights, locks, gates, and cameras to facilities.
Open toolInspect workplace hazards beyond the security patrol scope.
Open toolReview temporary, visitor, contractor, or restricted-area access requests.
Open toolFAQ
Practical answers for security and facilities managers replacing inconsistent patrol notes.
A security check form records a patrol, opening, closing, or fixed-post inspection. It identifies the guard, site, route, and time, then captures checkpoint results. Exception fields record what happened next.
Include guard, shift, site, route, round times, checkpoints, result options, and completion status. For exceptions, add location, description, photo, immediate action, person notified, follow-up owner, and any incident or work-order reference.
Yes. Generate separate versions when routes differ, or use conditional sections. Opening checks might cover signs of entry and alarm status; closing forms can cover occupancy, restricted rooms, locks, alarm activation, and an exterior walk.
Use conditional logic so an exception opens required questions for location, observation, photo, immediate action, escalation contact, and follow-up. Align choices with your site procedure; your organization defines the response and review process.
Yes. Share a form link guards can open on a phone. Use dropdowns, multiple choice, checkboxes, and short labels. Test the form while walking the route, including photo uploads and long checkpoint lists.
They serve different purposes. The check form records the routine round and first response. An incident report can capture the timeline, people, statements, evidence, and later actions. Link them with the incident report reference.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge. Replace the sample checkpoints with your premises and revise the form before sharing it.
Add follow-up status, responsible team, review time, and related record number. Route submissions to an inbox or sheet and filter for open items. The incoming shift can then see what is closed, monitored, or awaiting action.
Make each patrol round easier to review.
