This improvement to the Dispatch Board lets dispatchers schedule recurring non-job events on a specific weekday each month and set an end date for any recurring series, replacing manual workarounds with a built-in scheduling option.
What's changing?
Before this improvement, dispatchers could only create recurring non-job events using daily and weekly patterns. There was no way to schedule events on patterns like the first Monday or last Friday of each month, which forced dispatchers to create events manually or edit them one by one. Recurring series also ran indefinitely with no option to set a stop date. Now, when creating or editing a non-job event on the Dispatch Board, dispatchers can select a monthly recurrence pattern, choose an ordinal position (1st, 2nd, 3rd, 4th, or Last) and a day of the week, and optionally set an end date. The end date option is available across all recurrence types, including daily, weekly, and monthly. Existing recurring series remain unchanged and continue to work as before.
Resources
Before and after
Before (current)
Go to the navigation bar and click Dispatch.
Select the Dispatch Board or Classic Dispatch Board.
On the Dispatch Board you selected, click a technician's timeline within the time slot when you want to schedule the event and click Book a non-job event.
Check the Repeat option.
See only Daily and Weekly recurrence patterns available. No monthly weekday option exists.
To schedule a monthly weekday event (for example, a team meeting on the first Monday of every month), create each event manually month by month.
Note: There is no option to set an end date. The recurring series continues indefinitely.
Impact: Dispatchers spend extra time manually creating and managing monthly events, increasing the risk of missed or incorrectly scheduled events.
After
Go to the navigation bar and click Dispatch.
Select the Dispatch Board or Classic Dispatch Board.
On the Dispatch Board you selected, click a technician's timeline within the time slot when you want to schedule the event and click Book a non-job event.
In the Non-Job event side panel that opens, enter non-job event details.
From the Repeat dropdown, choose how often the event should repeat.
Click Custom and, on the Custom recurrence pop-up, use the fields to set your preferred recurrence schedule.
In the recurrence options, choose the specific weekday option. Select the ordinal position (1st, 2nd, 3rd, 4th, or Last) and the day of the week (for example, 1st Monday or Last Friday).
Optionally, set an end date for the recurring series to stop the series automatically on a specific date.
Save the event. ServiceTitan generates the series on the correct monthly dates.
Impact: Dispatchers can schedule monthly weekday events in seconds and control when a recurring series stops, reducing manual work and preventing indefinite event series.
Who uses this feature
All business types
Dispatchers
Region availability: All regions
How it works for your industry
Residential service and replacement
A dispatcher schedules a recurring team meeting every first Monday of the month for the HVAC crew to review performance metrics. The series automatically ends after six months when the review cycle is complete.
A plumbing dispatcher blocks the third Wednesday of each month for a technician's recurring training session. With the end date set, the series stops at the end of the training program.
An electrical company dispatcher sets a monthly safety briefing for the last Friday of every month and no longer needs to create each event individually.
Commercial service and replacement
A facilities maintenance dispatcher schedules a monthly check-in with the property management team on the second Tuesday of each month, with the series ending at the contract renewal date.
A commercial HVAC dispatcher blocks the first Thursday of every month for a fleet vehicle inspection across the technician team. Setting an end date aligns the series with the fleet maintenance contract.
A dispatcher managing multi-site commercial accounts sets a recurring coordination meeting on the last Monday of each month that automatically stops when the project wraps up.
Residential construction
A general contractor's dispatcher schedules a monthly subcontractor coordination meeting on the first Wednesday of each month for an active build. Setting the end date to the projected completion date keeps the Dispatch Board clean after the project wraps up.
A dispatcher blocks the second Monday of every month for a recurring materials review with the purchasing team. The series runs only through the duration of the construction phase rather than indefinitely.
A home builder's dispatcher creates a recurring safety walk on the last Friday of each month across all active job sites. Each event stops automatically when the build season ends in the fall.
Commercial construction
A dispatcher managing a multi-phase commercial build schedules a monthly progress review on the third Thursday of each month, with the series ending at the substantial completion milestone.
A project coordinator blocks the first Tuesday of every month for a recurring owner-contractor meeting and sets the end date to align with the contract closeout date.
A commercial dispatcher sets a recurring equipment inspection for the last Wednesday of each month across the heavy equipment crew. The end date prevents the series from continuing after the equipment lease expires.
How to prepare
If you're not already part of the Daily Dispatch Board Early Access, go to Settings > Dispatch Board > New & Upcoming Features and enable the Redesigned Dispatch Board toggle.
Identify recurring events that dispatchers currently create manually on a monthly basis and plan to convert them to the new monthly weekday recurrence pattern.
Train dispatchers on the new monthly recurrence option, including how to select the ordinal position and weekday, and how to set an end date for any recurring series.
Review existing indefinite recurring series and determine whether an end date should be applied.
Bookmark any knowledge base articles or Academy videos for team training.