Say you run a landscaping crew out of the northeast. In March, one of your foremen texts you that he wants the second week of July for a family trip. You say sure and mean to write it down. In May, your other foreman asks for the same week in person at the yard. You say yes again. Come July, you are short two leads in the busiest month of the year, and nobody did anything wrong except the system, which was your memory. A proper vacation request system for a small business does not need to be fancy. It just needs to make sure every request lands in one place, gets a clear answer, and shows up where everyone can see it.
The problem with texts and whiteboards
Most small businesses start with whatever is handy. That is fine at three people. It starts to crack somewhere around eight or ten, and the cracks look like this:
- Requests get lost. A text gets buried, a verbal yes is forgotten, a sticky note falls off the monitor.
- No one can see conflicts. The manager approving Tuesday's request does not know the owner approved the same dates last week.
- Balances are a guess. "How many days do I have left?" turns into ten minutes of digging through old pay stubs.
- It feels unfair. When there is no visible process, people assume approvals depend on who asked nicely or who the boss likes.
- There is no record. If a dispute comes up later, you have nothing but memory and a few texts.
What a good time off request system does
Whether it is a spreadsheet, an app or something custom, a working time off request system follows the same five steps:
- Request. The employee picks dates and a type (vacation, unpaid, sick, personal) in one place. No texts.
- Approval. The right person gets notified, approves or declines, and the employee gets the answer in writing.
- Calendar. Approved time off shows on a shared team calendar automatically, so everyone can see who is away.
- Balance. Days used and days remaining update on their own, so nobody has to count.
- Coverage warning. Before approving, the manager sees a flag if the request would leave a shift, crew or role uncovered.
That last step is the one most simple setups skip, and it is the one that prevents the July problem above.
Set clear approval rules
A system is only as fair as its rules. Write them down, share them with the team, and apply them the same way to everyone. A one-page policy covers most of it.
Blackout periods
Some weeks you simply cannot run short. For a Calgary restaurant or bar, that might be Stampede. For a tax preparer, it is March and April. For a snow removal company, it is any week with a big storm in the forecast, which is harder to plan for. Name the blackout periods up front, ideally at the start of the year, so nobody books a non-refundable trip and then gets turned down.
Busy seasons
Softer than a blackout: maybe vacation is allowed during the spring rush, but only one week at a time, or only with more notice.
Maximum people off
Set a limit per team or role. "No more than one foreman off at a time." "At least two licensed stylists on every Saturday." A three-chair salon in Kensington might allow only one stylist off on any given Saturday, while a ten-person office might allow two people from any department.
Notice and tie-breakers
Decide how much notice you want for different lengths of time off, and how you break ties. First-come, first-served is simple and easy to explain. Some businesses rotate priority for the most popular weeks, like Christmas, so the same person does not get it every year.
| Rule | Example | Why it helps |
|---|---|---|
| Blackout dates | No vacation during Stampede week for front-of-house staff | No surprises, no awkward refusals |
| Max off at once | One crew lead per week, two techs per week | Every shift stays covered |
| Notice period | Longer notice for a full week than for a single day | Time to adjust the schedule |
| Tie-breaker | First request in the system wins | Feels fair, easy to check |
| Approver | Direct manager, owner as backup | Requests do not sit waiting |
Alberta vacation basics your system should reflect
Your rules sit on top of Alberta's employment standards, not instead of them. The key minimums:
- Entitlement: after one year with you, employees are entitled to at least 2 weeks of vacation per year. After five years, at least 3 weeks. Employees under one year are not entitled to vacation time unless their contract says so, although vacation pay still accrues on their wages.
- Timing: vacation must be taken within 12 months after it is earned. Your system should flag balances that are getting close to that point, so time does not quietly pile up.
- Who picks the dates: you can decline specific dates for operational reasons. If you and the employee cannot agree, the employer can set the vacation dates by giving at least 2 weeks' written notice.
- Vacation pay timing: vacation pay must be paid no later than the next regular pay day after the vacation begins, or earlier if the employee asks at least a day before the vacation starts.
- Smaller chunks: vacation can be split into shorter periods if the employee requests it in writing, and half days can work if you both agree.
For how the 4% and 6% calculation works, see Alberta vacation pay explained for small employers. Construction employees have their own vacation pay rules, so check those separately if they apply to you.
This is general information, not legal advice. Rules change, so confirm the details on the official Alberta vacation and vacation pay page or call Alberta Employment Standards.
One more thing worth building in: stat holidays. A request that spans a general holiday, like the Labour Day long weekend, affects both the schedule and payroll. A good system shows those days on the calendar so they are not counted as vacation days by mistake. The Alberta stat holidays guide has the dates.
Your options, from simple to custom
A shared spreadsheet and calendar
A request form that feeds a spreadsheet, plus a shared calendar the manager updates by hand. Free or nearly free, and much better than texts. The weak points: someone has to remember to update the calendar and the balances, and there is no automatic coverage warning. Fine for under ten people with simple schedules.
A scheduling app with time off built in
Many shift scheduling apps include time-off requests, approvals and a calendar. If you already use one for shifts, turn this on first. Per-user monthly pricing is common. Check whether it tracks balances the way you need and whether it handles your blackout rules.
A payroll add-on
Some payroll platforms offer time-off tracking that ties balances directly to pay. That is convenient for vacation pay, but the request and approval side is sometimes basic, and staff may need yet another login.
A custom tool
Worth it when your rules do not fit the boxes: crews instead of shifts, ticketed roles that must be covered, multiple locations, or a mix of salaried and hourly staff. A custom tool can connect to the scheduling and payroll you already use instead of replacing them. For ballpark numbers, see custom software costs in Canada.
This week, make a single request form (even a free online form) and tell the team it is the only way to request time off from now on. Put every approved request on one shared calendar. You will see conflicts before they happen, and you will have a record.
Rolling out your vacation request system
- Write your one-page policy: blackout dates, max off, notice, tie-breaker, approver.
- Load everyone's current balance and any already-approved time off into the new system.
- Tell the team the start date, and stop accepting requests by text after that.
- Answer every request in the system within a set time, so people trust it.
- Review the rules after your first busy season and adjust.
Where Sidekick fits
We build vacation and holiday automation for Calgary small businesses: time-off requests, approvals and a team calendar in one place, balances that track themselves, stat holidays flagged ahead, and a warning before a shift or crew goes uncovered. It connects to the scheduling and payroll you already use. Book a free call and we can look at how your team handles it today.
Frequently asked questions
What is the simplest vacation request system for a small business?
A single online request form that feeds a spreadsheet, plus one shared calendar for approved time off. It is not automated, but it puts every request in one place and gives you a record.
Can an Alberta employer refuse a vacation request?
An employer can decline specific dates for operational reasons. If the employer and employee cannot agree on dates, the employer can set them with at least 2 weeks' written notice.
When do Alberta employees become entitled to vacation time?
After one year of employment, employees are entitled to at least 2 weeks per year, rising to at least 3 weeks after five years. Before one year, there is no vacation time entitlement unless the contract provides it.
How do I handle everyone wanting the same week off?
Set a maximum number of people off per team or role, name blackout periods in advance, and use a clear tie-breaker such as first request received. Apply the rules the same way to everyone.
Want time off that tracks itself?
Free 30-minute call. We'll map out what you need, how long it takes and what it costs. No pressure.
Book a free call →