Scheduling a 6-guard company when the owner works a post

You gave yourself the 3 a.m. post again, didn't you? When you own a small security company and still work a guard shift, your schedule can quietly turn your own hours into the catch-all slot. But if you are the owner who covers posts, the schedule is the business. This post is for the owner-operator running a 6-guard company who needs a plan that protects your own shift instead of treating it as the default.

We will start with why your shift keeps becoming the fallback and the legal baseline before you build anything. Then we will build a repeating two-week template in six steps, name relief slots so gaps stop landing on you, and walk through an actual week: who is on which post. You will also see how a 5:40 a.m. call-off gets filled, what the owner sees on their phone, and how to choose an employee scheduling app for a 6-guard company. Finally, we will cover what to do this week. No fancy jargon. Just practical steps.

Why your own shift keeps becoming the fallback slot

Nineteen shifts a week across three client sites in southern Ontario. Seven nights at the plaza, seven days at the condo, five warehouse evenings. Six people to cover them, and you are one of the six.

The schedule gets built Thursday night in a WhatsApp group and a spreadsheet. Your name is the only one you can move without making a phone call, so you become the filler.

Three 12-hour nights in a row plus two day shifts pushes you past 60 hours with no full rest day. That is the same week a client complaint sits unanswered.

Here is the assumption most owner-operators never notice: if your own shift is not written on the template, it is not a shift. It is spare capacity, and spare capacity always gets spent.

A repeating two-week template with named relief slots, plus conflict detection, turns your shift into a planned shift that only gets touched as a last resort.

The legal baseline before you build the template

Before you write a single shift, spend ten minutes on the law.

The Canada Labour Code sets standard hours at 8 per day and 40 per week, allows averaging, and requires at least 8 consecutive hours of rest between shifts, with an emergency exception. It also sets two notice rules that shape how you publish: a written schedule at least 96 hours before a shift starts, and 24 hours' written notice of any change. Employees may refuse shifts that begin inside that 96-hour window.

Those are federal rules for federally regulated workplaces such as banks and telecoms. Most small guard companies are provincially regulated, so check your own province before you lock a template. Ontario is an example only: a Winter 2021 factsheet lists a 48-hour weekly maximum, overtime after 44 hours, and a 30-minute unpaid break per 5 hours worked. Verify current numbers before relying on them. Alberta and BC publish their own rules on breaks, daily hour limits, and weekly days off, and the specifics differ by province.

On owner-as-guard coverage: self-employed people are not covered by the Ontario ESA, and whether you are an employee of your own corporation is a question for an accountant or an employment lawyer, not a blog post.

One habit covers most of this, whether you run the roster on paper or on free vs. paid guard scheduling software: publish on a fixed day each week, so nobody is ever handed a schedule that starts tomorrow.

Build the repeating two-week template in six steps

Step 1: list slots, not people

List every client shift: 7 plaza nights (1900-0700), 7 condo days (0700-1900), 5 warehouse evenings Mon-Fri (1500-2300). 19 weekly, 38 per cycle.

Step 2: pick a publishing day and keep it

Publish both weeks every Thursday by 6 p.m. Week two's first shift is seven days out, past federal 96-hour written-notice baseline; guards plan childcare and second jobs.

Step 3: write your own shifts into the template

Two evening shifts weekly, same nights each cycle, on the roster like everyone else's. A template shift is protected; one in your head is not.

Step 4: cap consecutive nights at three

Never finish a 12-hour night at 07:00 and start a day shift at 15:00 that day. Exactly 8 hours, legal on paper, no room for late handover/cross-city drive.

Step 5: balance weekly hours between 32 and 40

Leave headroom so a call-off cannot push anyone past 44 hours (the Ontario overtime threshold) or 48, or onto a seventh straight day.

Step 6: rotate the two weeks

Share nights and weekends; publish both weeks together. Every guard gets one full weekend off per cycle, the top reason small-firm guards quit.

Name your relief slots so gaps stop landing on you

A relief slot is a shift on the template that is staffed by a named guard but is not locked to a post. Whoever holds it knows from publication day that they may be moved.

Plan two, one per week of the cycle. Week one, Tom holds it on 32 hours. Week two, Kayla holds it on 32 hours. Both are already on the clock, so moving them costs no extra hours and no awkward favour.

Write the rules down. Relief goes to the guard with the lowest hours that week. Never to anyone who would break the 8-hour rest rule. Never to anyone who would cross 44 hours without you approving the overtime first. That same fairness logic carries into Step 6: treat fair scheduling as a retention tool.

When a gap opens, the relief holder moves into it and the relief slot becomes the small open shift. You backfill an 8-hour evening, not a 12-hour day, on a night you chose.

Conflict detection does the checking: drag a shift onto a guard who is booked, short on rest, or at their cap, and the software flags it before you publish rather than at 5 a.m.

The first call on a gap goes to a named relief guard. You become option four.

The actual week: who is on which post

Now the cycle:

Week one, plaza nights (1900 to 0700): Sam Monday to Wednesday (36 hours), Denise Thursday to Sunday (48 hours). Denise is at the Ontario weekly maximum, so watch overtime after 44. Condo days (0700 to 1900): Ahmed Monday to Wednesday (36), Kayla Thursday and Friday (24), Tom Saturday and Sunday (24). Warehouse evenings (1500 to 2300): Kayla Monday and Tuesday, you on Wednesday and Thursday, Tom Friday as the named relief slot.

Week one totals: Sam 36, Denise 48, Ahmed 36, Kayla 40, Tom 32, owner 16. 208 hours of post coverage, every slot filled, nobody over the cap.

Week two rotates nights and weekends. Denise takes plaza Monday to Wednesday, Sam Thursday to Sunday. Tom covers condo days Monday to Wednesday, Ahmed Thursday and Friday, Kayla Saturday and Sunday. Warehouse evenings go to Kayla Monday and Tuesday, you Wednesday and Thursday, and Ahmed Friday as week two relief. Totals: Denise 36, Sam 48, Tom 36, Ahmed 32, Kayla 40, owner 16. Same shape, different names, so nobody gets the same bad weekend twice in a cycle.

If Sam finishes a plaza night at 07:00 Thursday and starts a warehouse evening at 15:00 the same day, that is 8 hours rest. Legal on paper, miserable in practice. Conflict detection catches it. Your two shifts sit in the same slot both weeks, so the family calendar works and the client sees a consistent face on Wednesday and Thursday evenings. Adding a guard? How to get new guards using your scheduling app on day one covers setup.

How a call-off at 5:40 a.m. gets filled

It is 5:40 a.m. on a Thursday. Your condo day guard texts that she is sick. The shift starts at 07:00, 80 minutes away.

1. Open one screen. Who is on today, which post, and each guard's hours this week. No scrolling a WhatsApp thread to rebuild it.

2. Call the named relief holder first. Tom is the week one relief guard on 32 hours. He moves from the warehouse Friday evening to the condo day shift, landing at 44 hours, right at the Ontario overtime threshold.

3. Take the relief slot yourself. The warehouse Friday evening is 8 hours, not 12, and you were not planning to work it. You absorb 8 hours instead of a 12-hour day shift 40 minutes away.

4. Follow your written escalation order. Named relief holder, then your part-timer list, then overtime offered to the guard closest to the site, then you. Write it down once, the way you would build a guard schedule that survives last-minute call-outs.

5. Publish the change in the app. Every guard sees the updated roster, and the client contact gets a notification, so the site supervisor does not tell you the post was uncovered.

6. Log the call-off. Time received, who was contacted, who accepted, how long the fill took. That log answers a client asking why the invoice changed, and a guard who calls off three Thursdays running.

A sick call inside 24 hours is not something a template prevents. That is why the relief slot exists. The template does not stop the gap. It stops the gap from landing on you by default.

What the owner sees on their phone

Once the call-off is filled, the phone is where the week stays visible. The today view puts every post on one screen: guard assigned, shift window, clock-in status. Nineteen shifts, one glance, from a parking lot.

Geofenced clock-in turns green when the guard is inside the site boundary. If nobody has clocked in at the condo day post by 07:10, you get a flag. You hear it from the software, not from the client.

Drag a shift onto someone who is short on rest, already booked, or at their weekly cap, and a conflict warning explains why. Not just a red box.

Swapping two guards takes a few taps. Both get a notification, so nobody shows up to the wrong site.

The repeating two-week template lives on your phone too. Publishing next week's schedule is a five-minute job on a Tuesday night instead of a two-hour spreadsheet session. Timesheets come from verified clock-ins, so Sunday payroll is a review, not an afternoon of reconciling texts.

Opspot is built for this: 1 to 50 guards, free to start, $8 per guard per month on Pro, no sales call, and a small firm can be running the same day. Worth checking what Opspot's free Starter plan actually covers before you pay for anything.

Choosing an employee scheduling app for a 6-guard company

If you are typing “employee scheduling app” into your phone after another 5 a.m. call-off, your actual feature list is shorter than the comparison pages suggest.

Start with repeating shift templates and a two-week pattern. Most employee scheduling apps give you a one-week view. Fewer carry a named relief slot across both weeks, and that slot is what keeps your own name off the roster by default.

Then check conflict detection, rest rules, and hour caps. If the app cannot warn you that a shift breaks 8 hours of rest or pushes a guard past 44 hours, it is a calendar, not a scheduling tool.

Mobile-first matters for your guards, not just for you. The test is simple: can someone you hire on Friday use the employee work scheduling app on Saturday with no training and no support call?

Compare pricing honestly. Per-guard-per-month pricing with a free tier for a 3-guard shop beats enterprise workforce management software built for hundreds of guards and a dedicated IT team.

Finally, ask what else the app does with the data. Geofenced clock-ins can feed payroll-ready timesheets and client-ready proof-of-service reports, so you are not paying for three separate tools. To see how that switch plays out over time, read shift scheduling software for Canadian security companies: what to expect in year one.

Opspot is one option on that shortlist: free to start, no long-term contract, built for small guard firms rather than enterprise operations.

What to do this week

You have the shortlist. Now run one cycle on your own roster.

1. Write your slots as slots, not people. Nineteen shifts a week: 7 plaza nights (1900 to 0700), 7 condo days (0700 to 1900), 5 warehouse evenings (1500 to 2300). Named posts, real times.

2. Publish both weeks every Thursday at 6 p.m. The first shift of week two is more than 96 hours out, so nobody can say the schedule landed on them.

3. Name two relief holders, one per week, and pick your lowest-hours guards. Write the escalation order under the template: relief holder, part-timer list, nearest guard on overtime, then you.

4. Cap consecutive nights at three. Keep everyone between 32 and 40 hours. Leave at least 8 hours of rest between shifts, ideally 12.

5. Put your own two shifts on the roster where everyone can see them. You are option four, not option one.

Opspot is free to start for up to 3 guards and $8 per guard per month after that, no sales call and no contract, so you can run one full two-week cycle and see whether the template holds.

Conclusion

Scheduling a six-guard company works when the roster stops depending on you. Write posts as slots with fixed times, publish both weeks every Thursday, and name relief holders so call-offs have a clear path. Cap consecutive nights, keep hours between 32 and 40, and protect rest. Put your own shifts on the board as option four, not option one. The result is a fairer, more predictable operation that can cover gaps without automatically pulling you back onto a post. This week, run one full two-week cycle using the steps above. Start free with Opspot if you want a small-firm scheduling tool, then adjust the template based on what actually happens. You built the company; let the system carry the schedule.