Shift identity
Tie the record to an assignment.
Identify who completed the checklist, the covered post, and the scheduled and actual shift times.
- Guard identifier and supervisor.
- Site, post, zone, and shift type.
- Scheduled and actual shift time.
Describe the site, post orders, and shift stage. Makeform creates a form for equipment checks, patrols, access control, exceptions, and handoff notes.
Route completed checklists to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a shift pattern, edit the details, and send the prompt to the builder. The field list is an example structure.
Audience
Guards taking over a fixed security post
Format
Opening checklist with exception routing
Prompt size
325 chars
Example form structure
Opening checklist with exception routing
Guard, shift, post, and handoff details
Equipment present and working?
Open incidents or expected visitors
Which item needs follow-up?
Attach a photo of the exception
Suggested routing tags
Start shift
End shift
Needs follow-up
Ask for an exception note whenever a duty is marked incomplete, so a checked box never hides an open task.
Step 1
Identify
guard, post, shift, and handoff
Step 2
Confirm
equipment, access, patrols, and logs
Step 3
Explain
exceptions, evidence, and action taken
Step 4
Route
handoff and supervisor follow-up
Why use a shift checklist
Connect every duty to a guard, post, time, exception, and next owner so the incoming team can see what needs attention.
Show post-specific checks for the lobby, gatehouse, warehouse, control room, or mobile patrol.
Request a reason, location, photo, action, and notification only when a guard reports a fault.
Tag unresolved work and route the handoff to the incoming guard or supervisor.
Common shift patterns
Separate readiness checks from closeout records, or combine them when one guard owns the full record.
Confirm the post, equipment, systems, alerts, visitors, contractors, and incoming handoff.
Record patrols, keys, badges, access events, incidents, pending tasks, and outgoing handoff.
Organize post-specific equipment and duties for each staffed location.
Capture each site, visit window, checkpoint, observation, and escalation for the route.
Checklist workflow
Keep routine checks quick and request detail only when someone needs to act.
Describe the assignment, stage, equipment, patrol points, access duties, and handoff information.
Use clear statuses and require notes or evidence only for answers needing explanation.
Send routine records to the shared log and route exceptions to the supervisor.
Check for a clear next action and owner, then refine confusing prompts.
Form vs paper vs free text
Keep routine confirmations and exceptions together.
Field guide
Adapt these six field groups to the site's post orders and each guard's assignment.
Shift identity
Identify who completed the checklist, the covered post, and the scheduled and actual shift times.
Post readiness
List post-specific items and pair every failed status with fault and reporting details.
Access control
Record security-relevant access exceptions and anything that remains active for the incoming shift.
Patrol duties
Match checkpoints to patrol orders and explain every delayed, interrupted, or missed round.
Incidents and exceptions
Reference the detailed incident report with its number, status, immediate action, and escalation.
Handoff and ownership
Separate information-only notes from open work, then name its next owner and follow-up point.
Related tools
Connect handover, inspection, and incident forms with live Makeform tools.
Record pending work, system status, and next-shift priorities.
Open toolRecord follow-up and closure status for incidents.
Open toolCheck issued equipment with structured condition fields.
Open toolFAQ
Answers for security operations managers improving shift handoffs.
A security shift checklist is a form a guard completes at the start or end of a shift. It records the post, equipment, systems, access duties, patrols, incidents, open work, and handoff. Adapt it to the site's post orders and escalation process.
Record the guard, post, and shift time, then check keys, radio, access devices, equipment, cameras, alarms, gates, and communications. Include the outgoing handoff, restrictions, visitors, incidents, and open tasks. Failed checks should request details and notification.
Record patrols, door and gate checks, badge and key transfers, equipment, access events, incidents, and incomplete duties. For each open item, name the impact, next action, owner, and person notified.
Either works. Separate forms keep readiness and closeout distinct. One form suits a guard who opens and closes the same record. When combining them, use a shift-stage question and show only relevant fields.
Use statuses such as complete, incomplete, not applicable, and follow-up needed. Failed answers should request a note, location, action, notified person, and useful attachment. Keep urgent communication instructions in the post orders.
Yes. Use a site or post selector to show conditional groups for each location or route. Give every group its own equipment, checkpoint, and access questions, avoiding long lists of not-applicable checks.
Yes. Makeform provides unlimited free forms and responses. You can generate, edit, publish, and use the checklist without a response cap; the paid tier removes the Makeform badge. Review it against current post orders before rollout.
Route routine submissions to a shared destination such as Google Sheets, then tag or notify supervisors about missed patrols, faults, and unresolved incidents. Filter by post, date, shift, or follow-up status to find notes, attachments, incident references, and owners.
Make every guard handoff easier to act on.