Create Time-Off Blocks
Block time on the schedule for vacations, personal time, or company holidays so your team's availability stays accurate.
What this guide covers
This guide explains how to create time-off blocks on the JobsiteOn schedule. Time-off blocks reserve time on the calendar for vacations, sick days, personal appointments, company holidays, or any period when a team member is unavailable for work.
By the end you will know how to:
- Create a time-off block for a team member
- Set full-day or partial-day time off
- Create recurring time-off blocks
- Delete or modify existing time-off blocks
Before you begin
- You need access to the Schedule module in your JobsiteOn workspace
- Administrators can create time-off blocks for any team member
- Individual team members may be able to request or create their own time off depending on workspace permissions
What time-off blocks do
A time-off block marks a period on the calendar as unavailable. When a time-off block exists:
- The blocked time appears visually distinct on the calendar (typically grayed out or crossed)
- The dispatch board shows the team member as unavailable during that period
- Conflict warnings appear if someone tries to schedule an event during blocked time
Tip: Use time-off blocks for planned absences. For permanent schedule changes (like a team member who never works Fridays), configure their weekly availability in team settings instead.
Step 1 -- Open the schedule and select a date
Navigate to the Schedule from the left sidebar. Switch to day or week view and find the date where you want to create the time-off block.
Step 2 -- Create the time-off block
Click on the time slot where the absence starts, or click the New Event button and select Time Off as the event type.
Fill in the following fields:
- Team member -- Select who the time off is for
- Date -- The date or date range
- All day -- Toggle on for full-day time off, or set specific start and end times for partial-day blocks
- Reason (optional) -- Add a note like "Vacation" or "Doctor appointment"
Screenshot: The time-off creation form showing fields for team member, date range, all-day toggle, and an optional reason field
Step 3 -- Set a date range for multi-day time off
For vacations or extended absences, set a start date and end date to create a block that spans multiple days. The block appears across all days in the range on the calendar.
For example, to block a full week of vacation:
- Start date: Monday, April 6
- End date: Friday, April 10
- All day: On
- Reason: Vacation
Step 4 -- Save the time-off block
Click Save to create the block. It immediately appears on the calendar for the selected team member.
Animation: A walkthrough showing a user creating a three-day time-off block for a team member, with the block appearing across three days on the week view calendar
Creating recurring time-off blocks
For regular absences (like a team member who has every other Friday off), you can set the time-off block to repeat. When creating the block, look for a Repeat option and configure the recurrence pattern.
Editing or deleting a time-off block
Click on an existing time-off block on the calendar to open its details. From there:
- Edit -- Change the dates, times, or reason
- Delete -- Remove the block entirely, making the team member available again for that period
If you delete a block from a recurring series, you may be asked whether to delete just this occurrence or all future occurrences.
Note: Deleting a time-off block does not automatically reassign events that were rescheduled because of the block. Review the affected dates to make sure the schedule still makes sense.
How time-off blocks appear on the dispatch board
In dispatch view, a team member with a time-off block shows a visual overlay on their column indicating they are unavailable. This makes it easy for dispatchers to see at a glance who is available and who is out.
Screenshot: The dispatch board showing one team member's column with a time-off overlay labeled "Vacation" while other team members show normal availability
Related articles
Did this answer your question?