Non-Job Events Redesign

RoleLead Designer
Timeline3 months

Making non-job events (meetings, training, breaks) a first-class scheduling tool, so dispatchers can block off technician time quickly and confidently.

Non-Job Events on the ServiceTitan Dispatch Board: a weekly “Lunch for an hour” event blocked on technicians' rows, with its event details flyout listing technicians, date, time, and repeat schedule

Overview

Non-job events (NJEs) are how dispatchers and back-office admins block off technician time for activities like meetings, training, or breaks. They’re essential for workforce planning, accurate payroll, and protecting technician time.

The legacy NJE experience had fallen behind job scheduling. This redesign brought NJE creation and management in line with the job scheduling experience on the Dispatch Board, with recurrence, multi-technician scheduling, verified locations, integration controls, and a full audit trail.

The Problem

Dispatchers trying to block off technician time found creating and managing non-job events error-prone, inflexible, and frustrating. The experience lacked intuitive editing workflows, didn’t account for complex recurrence patterns, and integrated poorly with Dispatch Pro, Capacity Planning, and Timekeeping.

Before: the old experience

This is what dispatchers were working with before the redesign.

Legacy Dispatch Board with an event popover for an event named test, showing only the technician, date and time, and who created it, with Delete and Edit Event links
Before: clicking an event opened a small popover with just a name, a time and its creator. To change anything, you had to find the small “Edit Event >>” link, which opened a separate page.
Legacy Edit Recurring Event dialog asking whether to change only this event, following events, or all events, with a Cancel this change button
Before: editing a recurring event meant choosing between only this event, following events or all events. There was no way to say which technicians the change was for.
Legacy full-page Edit Event form with title, date and time fields, All Day and Repeat checkboxes, three clear and capacity checkboxes, a description box, and a members list
Before: the full-page Edit Event form took dispatchers off the board entirely. Recurrence was hidden behind a small “Edit” link, and three checkboxes were the only controls over where an event showed up.

Goals

Target metrics set for after general availability (goals, not results):

Key Design Challenge

NJEs had to work like jobs without being jobs. The redesign needed to mirror the job scheduling experience dispatchers already knew, while giving them explicit control over how each event affects payroll, capacity, Dispatch Pro, and what technicians see on mobile. It also had to work across the Weekly, new Daily, and Classic Dispatch Boards without redesigning the technician mobile apps.

Design Approach

The Solution

Creating an Event

Dispatchers create an NJE from a side panel that resizes the Dispatch Board instead of covering it, so the schedule they’re planning around stays visible. It works the same way on the Weekly, new Daily, and Classic boards. One event can cover several technicians at once, and the Technicians picker is grouped by team, so blocking off a whole crew for a meeting or training takes a few clicks instead of one event per person.

Non-Job Event side panel open next to the Dispatch Board, with the Technicians dropdown listing technicians grouped under Water Boiler Install Team and Water Boiler Maintenance Team

The Technicians picker groups people by team, so one event can cover a whole crew.

The rest of the form mirrors job scheduling: date, start and end time with an all-day option, standard and custom recurrence with human-readable summaries, and an address field with verification and a dropdown of previously used addresses. Timesheet activity selection is built into the same flow, so payroll is handled at the moment the event is created rather than fixed afterward.

The full Non-Job Event create form: event name, technicians, date, start and end time, all day, repeat, address, timesheet activity, four visibility and capacity checkboxes, and a description field with a 0 of 100 character counter

The full create form, from scheduling details to timesheet activity and visibility settings.

Visibility and Capacity Controls

Four plain checkboxes replace behavior that used to be hidden and inconsistent across connected systems. Dispatchers decide whether an event counts toward scheduling and dispatching capacity, whether technicians see it in the mobile app, and whether it clears from the technician’s calendar and the Dispatch Board once it’s over. NJEs show up only where they should, and Dispatch Pro and Capacity Planning treat that time the way the dispatcher intended.

Event Details and Audit Trail

Opening an event shows everything at a glance: every technician on it, the date and time, a readable repeat rule, the address, and whether it’s included in Dispatch Pro, Capacity Planning, and the mobile app. Next to the event information, a new Audit Trail tab records a granular edit history, including field-level before-and-after changes, who made each change, and where it came from. It supports troubleshooting and the record-keeping needs of larger customers.

Event details for a weekly recurring event called Lunch for an hour, listing seven technicians, date and time, repeat days, address, Dispatch Pro, Capacity Planning and mobile app settings, with Non Job Event Information and Audit Trail tabs

Event details show who’s on the event, when it repeats, and where it counts, with the Audit Trail one tab away.

Editing Recurring Events

Multi-technician recurring events raised a question the old experience never answered: whose schedule is this change for? When a dispatcher edits a recurring event, a dialog lists every technician on it and asks which ones the edit applies to, then whether it covers this event, this and following events, or the whole series. One technician can leave a weekly lunch block without changing it for everyone else.

Edit recurring event dialog listing the technicians associated with the event, a Technicians to edit selector, and options for This event, This and following events, or All events

Recurring edits are scoped by technician and by occurrence.

Completing Events

Completing events was added during the project to match job scheduling. Because an event can belong to several technicians, the Complete event dialog shows everyone associated with it and asks which technicians to mark complete, so one person finishing early doesn’t close the event for the whole group.

Complete event dialog listing the technicians associated with the non-job event and a Technicians to mark as complete selector

Dispatchers choose exactly which technicians to mark complete.

Notable Details

Research & Validation

The need was clear before design started: NJEs were among the top sources of dispatch support tickets, and teams behind Capacity Planning, Dispatch Pro, and Payroll pointed to incomplete NJE integrations as a blocker to adoption.

Outcomes

The redesign moved NJEs from a workaround toward a first-class scheduling tool.

Reflections

The biggest lesson was that “small” features like non-job events carry a lot of hidden weight. They touch payroll, capacity, automation, and technician schedules, so unclear behavior quickly turns into support cases and workarounds.

Mirroring the job scheduling patterns dispatchers already knew made the redesign feel familiar, but the real value came from making behavior explicit: clear controls instead of hidden rules, and an audit trail instead of guesswork. Keeping a tight scope (no auto-scheduling, reporting, or mobile redesign) let us fix the foundations first. Next, I’d use the planned tracking to see how recurrence and multi-tech scheduling are actually used, and decide which of the deferred capabilities matter most.