Security Guard Schedule Template
Download a simple weekly schedule for planned guard coverage. The Excel workbook has a Blank Schedule worksheet and a Fictional Example worksheet. The two-page landscape PDF contains the matching printable forms. No signup, email address or payment is required.
Plan one coverage segment per row
Enter the week starting date, then the date, site or post, guard, start and end time for each assignment. Use the date on which that segment starts. Keep times in the site's local time and use the same time zone throughout a sheet. The blank worksheet provides 12 rows; use a separate copy for another week.
Planned Hours calculates elapsed clock hours for each valid segment. It does not deduct breaks or calculate pay. Split uncovered breaks into separate segments. Check assignments against the approved site requirements before sharing the schedule.
Day and overnight shifts
Enter Excel times such as 08:00 and 16:00 for an eight-hour day shift. Enter 22:00 and 06:00 for eight hours ending the following day. An end earlier than the start is interpreted as next day; one row must be shorter than 24 hours.
Equal start and end times display Check inputs, not 24 hours. Completely unused rows stay blank. Partly completed rows, missing dates or guard/post names, and invalid times also display Check inputs. The total stays at Check inputs until those rows are corrected. These are local clock-hour calculations; daylight-saving changes need a separate duration review.
Represent relief without counting the same coverage twice
When a replacement takes over, end the outgoing guard's segment at the handover time and start a separate row for the incoming guard. Do not leave the original full shift in place and add replacement hours on top. If an overlap is deliberately planned, record its purpose; the total counts both guards' planned time during that overlap.
The fictional example splits Tuesday reception coverage into 08:00-12:00 for Example Guard A and 12:00-16:00 for Example Guard C. Those two rows total eight hours. Together with Monday's day and overnight rows, the example totals 24 planned hours.
Fictional schedule example
Harbor Point Offices - Fictional Example. Week starting 12 January 2026. All names and assignments are invented; they are not customer records or a recommended staffing level.
| Date | Site/Post | Guard | Start | End | Planned Hours | Relief/Replacement | Notes |
|---|---|---|---|---|---|---|---|
| 2026-01-12 | Harbor Point / Reception | Example Guard A | 08:00 | 16:00 | 8 | None planned | Day coverage |
| 2026-01-12 | Harbor Point / Exterior | Example Guard B | 22:00 | 06:00 | 8 | None planned | Ends 13 January |
| 2026-01-13 | Harbor Point / Reception | Example Guard A | 08:00 | 12:00 | 4 | Relieved by Guard C at 12:00 | First segment only |
| 2026-01-13 | Harbor Point / Reception | Example Guard C | 12:00 | 16:00 | 4 | Replaces Guard A from 12:00 | Second segment only |
Planned coverage and actual attendance are different records
A schedule records who is expected to cover a post and when. It does not prove that a guard attended or worked those hours. Keep actual attendance, changes, missed coverage and supervisor review separately. A checkpoint scan records an interaction, not completion of a whole shift or every assigned task.
This template has no macros, external connections, payroll rates or statutory calculations. It does not import assignments into CheckpointGuard or automatically check availability, overlapping assignments or site staffing requirements.
Move from a worksheet to operational scheduling
When several supervisors need to maintain assignments, explore CheckpointGuard's scheduling and attendance workflow. Review the roster alongside recorded attendance and workforce-cost preparation, with the appropriate plan and permissions. CheckpointGuard is not presented as a statutory payroll processor.
Carry the plan into handover
Use the shift handover checklist to pass on open issues and changes when the incoming guard takes over. Keep the planned roster and the handover record identifiable as separate documents.