How to Collect Employee Availability and Time-Off Requests

Why availability gets lost in text messages

In many teams, availability lives in text messages, a paper sheet on the wall or a manager's memory. A student says they cannot work Tuesdays, someone asks for next Friday off in a group chat, and by the time the schedule is built the information is gone or out of date.

The result is a roster that looks fine on screen and falls apart on the day. Staff are scheduled in windows they said they could not work, approved time off is forgotten, and the manager spends the week finding cover and apologising.

The fix is to keep availability and time-off requests next to the schedule, entered by the employee, approved by a manager, and checked automatically while the roster is built.

Why this happens

• Availability is collected once, on paper or in chat, and never updated.
• Time-off requests are agreed verbally and not recorded anywhere the scheduler looks.
• The scheduler has no warning when a shift lands on a day the person said they cannot work.
• Approved leave sits in a different system from the roster.
• Nobody can tell which requests are still waiting for an answer.

Biznsbook addresses this through employee availability windows, time-off requests with manager approval, availability and leave warnings in the builder in Labour Scheduling, on the same roster, clock and swaps as the rest of the module.

Small gaps in scheduling rarely fail loudly. They show up later as numbers nobody can explain. Recording each step where it happens removes the guesswork.

Step-by-step: Collect Employee Availability and Time-Off Requests

Written for owners, managers and shift supervisors who roster staff in Biznsbook Labour Scheduling, with or without HRMS.

1. Open Availability & Time Off. Staff open My Work → Availability & Time Off. They must be recognized as labour employees, either added under Labour Setup or linked from HRMS.
2. Add when I can work. Add a day with a type: Can't work, Prefer to work or Available. Tick All day or give a time range. A day with no entry means the person is free all day.
3. Request time off. Choose the dates, a type (vacation, sick, personal or other) and whether it is paid, then send the request. A pending or approved request can be cancelled.
4. Review the queue. Managers open Labour Schedules → Time-Off Requests, which lists pending requests and can be filtered by status.
5. Approve or deny. Approve or deny with an optional note. To record leave you already agreed, use Record time off for an employee; it is saved as approved straight away.
6. Build with the warnings on. In the schedule builder, a shift inside a Can't work window, or on approved time off, shows a warning before you publish.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Availability is collected once, on paper or in chat, and never updated. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 2: Time-off requests are agreed verbally and not recorded anywhere the scheduler looks. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 3: The scheduler has no warning when a shift lands on a day the person said they cannot work. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 4: Approved leave sits in a different system from the roster. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 5: Nobody can tell which requests are still waiting for an answer. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.

Each of these turns into a question the manager cannot answer quickly. Fix the process on the record rather than in email threads or spreadsheets.

Best practices that hold up as you scale

• Open Availability & Time Off — Staff open My Work → Availability & Time Off.
• Add when I can work — Add a day with a type: Can't work, Prefer to work or Available.
• Request time off — Choose the dates, a type (vacation, sick, personal or other) and whether it is paid, then send the request.
• Review the queue — Managers open Labour Schedules → Time-Off Requests, which lists pending requests and can be filtered by status.
• Approve or deny — Approve or deny with an optional note.

Set the rule once in settings, let staff enter their own information, and review the results weekly before you publish the next roster.

How Biznsbook supports this workflow

employee availability windows is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

time-off requests with manager approval is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

availability and leave warnings in the builder is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Labour Scheduling works on its own. Managers need the Labour Scheduling Manager role (or Shift Supervisor for schedules and attendance); invited staff get the Shift Worker role. HRMS, Payroll, Inventory and Accounting are optional.

Suggested implementation timeline

1. Week 1: Set up employee availability windows and the permissions the people involved need.
2. Week 2: Run the real process in Biznsbook only, with no side spreadsheet, for one team or site.
3. Week 3: Review what was recorded with the people involved and tighten the rules where they disagreed.
4. Month 2: Roll out to every team or site.
5. Ongoing: Reviewing availability and requests each week.

Related guides

Cluster hub: Scheduling guides. Module: scheduling software. Also see build employee schedules and publish employee schedules.

Three kinds of availability, one simple rule

Each entry is one of three types. Can't work is a hard statement from the employee: do not schedule me here. Prefer to work is a soft signal that helps when you are filling open shifts. Available is the neutral default for a day you want to spell out. Because a day with no entry means free all day, staff only need to describe their exceptions, which keeps the page short and the data current.

An entry can cover the whole day or a time range, so a student who is free after 4 pm can say so once instead of declining every morning shift. If circumstances change, the employee edits the entry themselves; nobody has to retype it for them.

Keeping approvals quick and visible

The Time-Off Requests list is the manager's single queue. Filter to pending, work through them, and add a short note when you deny one so the employee knows why. Approved time off then appears as a leave warning in the builder, so the roster respects it without anyone remembering it.

When a request comes in verbally, record it with Record time off for an employee. It is saved as approved, so the schedule still knows about it and there is one record of who was away and when.

Metrics to track monthly

• Pending time-off requests
• Labour % against target by day
• Open shifts left after auto-fill
• Short-notice changes and premium hours
• Missed-break exceptions

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual workarounds vs Biznsbook

Compare common manual workarounds with Biznsbook employee availability windows and the related capabilities.

Reviewing availability and requests each week

Before building the next roster, clear the pending time-off queue, ask staff to update any availability that has changed, and then build. Doing the queue first means the builder warnings reflect decisions already made, and staff see that a request gets an answer.

Write the rule down in your staff handbook so the settings and the policy say the same thing.

Frequently asked questions

How this differs by industry