Describe the site, post orders, and reporting routine. Makeform turns them into a shift-ready security guard daily activity report form with timed patrol entries, incident details, observations, attachments, and a clear handoff for the next guard and supervisor.
Route shift reports to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adjust the post details, or send it to the Makeform builder. The field structure is an example you can edit.
Audience
Guards covering a commercial office property
Format
Shift report with repeatable patrol log
Prompt size
426 chars
Example form structure
Shift report with repeatable patrol log
Guard, post, and shift times
Patrol time and zone
What did you observe or do?
Does this require follow-up?
Handoff notes for the next shift
Suggested routing tags
Routine shift
Supervisor follow-up
Incident attached
Ask guards to enter each patrol as a separate timed log item. A single end-of-shift summary cannot show when a door, floor, or perimeter was checked.
Step 1
Start shift
identify guard, post, equipment, and briefing
Step 2
Log activity
record patrol time, place, observation, and action
Step 3
Flag exceptions
add incident facts, files, and notifications
Step 4
Hand off
summarize open items for relief and supervisor
A usable shift record
A guard report should distinguish routine patrols from exceptions, preserve the order of events, and make unfinished work obvious to the next shift. Structured fields do that without forcing every guard to invent a format.
Capture the time, checkpoint, condition, and action together so supervisors can review what was checked and when, rather than decoding one long narrative.
Conditional questions collect people, location, notifications, action, and attachments when something happens while keeping ordinary patrol entries short.
A required handoff section calls out broken access points, expected vendors, retained keys, and follow-up tasks before the guard submits the report.
Adapt it to each post
Keep the core shift, patrol, incident, and handoff fields consistent, then swap in checkpoints and activity categories that match the assignment.
Log lobby coverage, floor patrols, unlock and lock rounds, contractor access, elevators, and after-hours occupants.
Record gate activity, resident calls, parking observations, amenity checks, noise complaints, and mobile patrols.
Check docks, gates, trailers, fence lines, lights, restricted rooms, alarms, and after-hours truck movements.
Document briefing, assignment changes, entry issues, crowd observations, calls for assistance, lost property, and closeout.
Build the reporting workflow
Start with how the guard actually works: what begins the shift, which locations require checks, which exceptions need detail, and what the supervisor needs at handoff.
Name the post, shift pattern, required checkpoints, common activity categories, issued equipment, and supervisor routing so the generated draft reflects the job.
Use a consistent group for time, location, condition, observation, and action. Add dropdowns for checkpoints while preserving a narrative field for details that do not fit a list.
If a guard selects incident, damage, alarm, denied access, or follow-up required, reveal the relevant fact, notification, attachment, and escalation questions.
Route completed reports to a supervisor and tag submissions that contain an incident or unresolved issue, while routine reports remain available in the shared response record.
Form vs notebook vs generic document
A daily report is most useful when the same facts appear in the same place every shift. A generated online form creates that structure while leaving room for the guard's factual narrative.
Field guide
Build the form around the timeline of a shift. These six groups cover identity, patrol work, access activity, exceptions, communication, and the closing handoff without turning every routine entry into an essay.
Shift identity
Start with details that let a supervisor place the report without reading the narrative. Use controlled choices for site and post, then capture actual start, end, and relief times when they differ from the schedule.
Patrol timeline
Each patrol entry should stand on its own. A time and checkpoint paired with status and notes creates a readable sequence and prevents a vague end-of-shift statement from replacing the working log.
Access and site activity
Not every notable event is an incident. Separate routine access and service activity from emergencies so reviewers can find vendor arrivals, deliveries, key movements, and after-hours occupants without inflating incident counts.
Incident and exception facts
Use conditional logic to reveal an incident block after the guard flags an exception. Ask for observable facts, sequence, people involved, response, and notifications rather than forcing routine patrols through unused questions.
Notifications and follow-up
A note saying management notified is incomplete. Capture the person or team contacted, contact method, time, instructions received, current status, and named owner for the next step so follow-up can be assigned.
Equipment and handoff
End with issued equipment, outstanding site conditions, expected arrivals, and tasks passed to relief. A completion acknowledgment confirms the guard reviewed the entry before submitting without presenting the report as an official determination.
Related tools
Connect the shift log to incident detail, closure, handover, site observation, inspection, and maintenance intake using live Makeform tools.
Collect a fuller event narrative, people involved, actions, notifications, and attachments when a shift entry needs a separate report.
Open toolDocument investigation follow-up, corrective steps, ownership, and closure after the original shift report has been reviewed.
Open toolCreate a focused turnover checklist for keys, equipment, expected activity, open incidents, and post-specific instructions.
Open toolCapture an observed condition or behavior with location, supporting detail, immediate action, and recommended follow-up.
Open toolRun a structured inspection of entrances, shared areas, exterior conditions, lighting, and building components.
Open toolTurn a broken lock, failed light, damaged gate, leak, or other observed defect into a routed repair request.
Open toolFAQ
Practical answers for security supervisors replacing paper shift logs or inconsistent narrative reports.
It is a shift record guards use to identify their assignment and document patrols, access activity, calls, observations, incidents, actions, notifications, and handoff items. A structured form keeps recurring facts consistent while allowing a factual narrative for unusual events.
Include guard, site, post, supervisor, shift times, issued equipment, and repeatable activity entries with time, location, category, observation, and action. Add conditional incident details, people notified, supporting files, unresolved items, equipment return, and relief notes. Match checkpoints and terminology to the site's post orders.
A separate repeatable entry is usually easier to review because it keeps the time, location, status, observation, and action connected. Guards can add entries throughout the shift or transfer notes before submitting. Keep a final summary for patterns and handoff needs rather than using it as the only timeline.
Let the guard flag the activity as an incident or exception, then reveal fields for exact time and location, observable facts, people involved, action taken, notifications, reference numbers, and attachments. A separate incident report can collect additional detail when your operating process requires one.
Yes. Add file-upload fields to an incident, damage observation, access issue, or maintenance note. Include a short description of what each file shows so a supervisor can understand it without guessing, and follow the organization's rules for appropriate collection and retention.
Yes. Include a follow-up question and route the submission to the appropriate reviewer through your configured workflow. Record the issue, priority, assigned owner, and current status in the form so the handoff is specific instead of relying on a phrase such as supervisor notified.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and collect shift reports without a response cap. The paid tier removes the Makeform badge.
Yes. Start with site and post selectors, then use conditional logic to show the right checkpoints, equipment, activity categories, and supervisor path. Keep the shared identity, timeline, incident, notification, and handoff fields consistent so reports remain comparable across assignments.
Make every shift easier to review.
