Table of Contents

Setting Up Schedules General Overview

Mitchell Paul-Soumis Updated by Mitchell Paul-Soumis

Scheduling Addresses

Scheduling addresses allow you to define starting and ending locations for your technicians. Typically, this will be your office or their home, but you can use any address you like.

Creating a Scheduled Address

A Scheduled Address is created in a similar way to serviceable addresses, requiring the street address followed by validation to generate a precise pin.

The difference between Schedule Addresses is the inclusion of the "Type" and "Users" fields.

The "Type" Field contains 3 selections - "Both the start and end point", "The ending point for the day", and "The starting point for the day".

Meanwhile, the "User" field allows you to determine which users the Scheduling Availability will apply to.

Start and End Point Interactions

The Start and End point fields can be used in a variety of ways. In most cases, the start address will typically be your main office - however if your technicians have a work truck and depart from their home address then the starting address for that particular user can be updated to reflect that.

Similarly, the end point on Schedule Addresses is used to identify the travel time required by the technician to end their day. In most cases, the end point is the main office, however this can equally be set to the home address of an individual user.

The start and end point interact directly with the scheduling availabilities, being taken into account for travel time to their first job of the day - as well as from their last job of the day back to the end point.

Scheduling Availabilities

Configuring a well-defined Scheduling System allows you to define when your individual technicians are available, not only on a daily basis - but on a minute-by-minute basis.This allows you to build multi-layered schedules that support different types of jobs at different times, as well as scheduling vacation times, and other unavailable events on a per day, week, month, or year basis.

Creating an Availability

Creating a Scheduling Availability takes place in two parts:

  1. Creating the Schedule Container
  2. Adding Days of the week & Times of the day
Creating the Schedule Container

The purpose of this container is to group together users, job types and GeoFences with the purpose of applying availability or unavailability to these groups.

Below is a summary of each mandatory field and its purpose:

  1. Name - A descriptive name for the container. For example, Residential Installations or Bill's Schedule.
  2. Start Date - This field determines on which date should this container begin to be applied to the compound schedule.
  3. Infinite Repetitions | Repetitions - If infinite repetitions is enabled, this schedule repeats forever. If it is disabled, then this schedule will repeat the number of times defined in Repetitions. Repetitions determine how many occurrences of this Schedule Blocker occur before stopping; starting from the entered Start Date.
If the Infinite Repetitions check box is empty, then the Repetitions field becomes a mandatory field
  1. Weeks Between Repetitions - This value defines the frequency of repetition. For example:
    1. If weeks is set to 0, this schedule repeats every week.
    2. If weeks is set to 1, the schedule repeats every other week.
    3. If weeks is set to 3, then the schedule repeats one week out of every four.

Below is a summary of each optional field in the creation process

  1. Available - If this box is checked, it will add the listed users to the schedule during the days and times set. If the box remains unchecked, it will mark the selected users as unavailable during the set days and times
  2. GeoFence - The GeoFence field allows you to selectively apply the Schedule Availability to jobs which fall under a specific GeoFence area
  3. Users - Which users should have this schedule container applied to them.
  4. Job Types - Which job types are applied in this schedule container.
If a user has overlapping availability and unavailability on different schedules, it will be treated as unavailable time.
Filling the container with days and times

Populating the container is as simple as setting the Days of the week available on the schedule, with optional time specification.

An example of how you might take advantage of the flexibility offered by the optional time window is to set large time windows on weekdays, while setting much smaller one on weekends.

Schedule Blockers

Schedule Blockers are effectively the opposite side of Schedule Availability - determining days and times that individual users aren't available to be scheduled for a job.

A Scheduled Blocker is also created in a very similar way - providing nearly identical fields to the container seen in Schedule Availability. Similarities to the Schedule Availability section continue onto creating specific days of the week and times of the day for each blocker.

Creating the Schedule Blocker container

Creation of the container starts by clicking on the "Create Schedule Blocker" button in the page header, then filling out the pop-up window:

The required information to be filled out is below:

  1. Name - Some name for the blocker you'll be creating
  2. Start Date - The Start Date for the Schedule Blocker, and any days and times added will only apply after this date
  3. Infinite Repetitions | Repetitions - If infinite repetitions is enabled, this schedule repeats forever. If it is disabled, then this schedule will repeat the number of times defined in Repetitions. Repetitions determine how many occurrences of this Schedule Blocker occur before stopping; starting from the entered Start Date.
If the Infinite Repetitions check box is empty, then the Repetitions field becomes a mandatory field
  1. Weeks Between Repetitions - This value defines the frequency of repetition. For example, if weeks is set to 1, this schedule repeats every week. If weeks is set to 2, the schedule repeats every other week. If weeks is set to 4, then the schedule repeats one week out of every four.

The following field is not mandatory, but is highly recommended.

  1. Users - Selecting users on your instance will have this blocker apply to them on the selected Days and Times. Selecting no users will apply the blocker to no one.
Filling the container with Days and Times

Unlike Schedule Availability, there's no option to make the blocker last all day. For something that lasts multiple hours, or all day, it's recommended to use Schedule Time Off.

Common uses for Schedule Blockers

Schedule blockers are a way for you to define blocks of time on specific days, for specific users, that are blocked from having jobs scheduled in them. While you can define unavailable time in a schedule, this time is rigid and cannot be modified on the fly. Schedule blockers can be moved on a day by day basis.

Schedule Blockers are most commonly used for events that may interrupt the normal flow of the day on a predictable basis. The most common use for this section is to schedule out lunches for your technicians, as pictured below:

Schedule Time off

The Schedule Time off component complements both Schedule Blockers and Schedule Availability, designed to fill in the gap for unexpected interruptions. Activities such as vacation time-off, appointments, vehicle issues, or family emergencies would get entered as Schedule time-off to ensure no appointments are being assigned to this technician during a period of time where they're unavailable.

How did we do?

Job Types: Best Practices

Applying Task Templates to Jobs

Contact