The Scheduling Engine Walkthrough

Let's tackle a major issue for growing service businesses: the chaos of manual scheduling. Your office team is likely overwhelmed with managing engineer availability, checking qualifications, and calculating travel time, all while the customer waits. This manual method is inefficient and blocks scaling your operations.

Your solution is the Scheduling Engine. Think of it as the central brain of your operation. Remember, the engine handles the hard work, but you control its operation. It follows the rules you set: Skills determine who can do the job. Public Holidays limit available days. Shifts dictate the technician' working hours. Service Windows set arrival times. Scheduling Rules decide travel limits for engineers.

In the past, your entire scheduling process was a manual bottleneck. Your office team had to check skills, scan diaries, and calculate travel. And your customer was forced to call you during office hours. The Scheduling Engine provides two distinct payoffs. The first is for your internal office team with efficiency, and the second is for your external customers with convenience lets take a look at them.

Skills are key. In essence, they are the qualifications or abilities, such as being Gas Safe registered or EPA certified, required for a job.

Assigning these to your engineers ensures they are booked only for tasks they are qualified to handle.

Your skills logic is now set up. By aligning these qualifications with your Users and Job descriptions, your system becomes an automated gatekeeper. From now on, the scheduling engine will only suggest qualified candidates, ensuring compliance and reducing the risk of human error.

Your office staff are constantly asking "Who is actually working on Tuesday?" or "Is our lead heat pump technician on the early or late shift?" This guesswork leads to constant booking errors and an inability to confidently promise an appointment slot to a customer. Shift Patterns solve the problem. They are like the digital blueprint of your team's availability. The scheduling engine can't suggest an appointment unless it knows an technician is available. It's about a flexible system. Set the right shift times for tasks. For example, nine-to-five for installation, seven-day-rota for service.

You've mapped your team's Shifts, noting start, finish, overtime, and non-working hours. This logic powers the scheduling engine.

Your Scheduling Engine assumes your team is working unless told otherwise. It does not know if December 25th is a holiday for your business. If you don't explicitly block that time, the engine will offer that slot to customers just as any regular working day. You could manually add a normal "Holiday" event to every technician's schedule one by one, but that is high-risk. If you miss just one user, the engine will flood their open day with bookings that you will have to cancel. This is why we use Public Holiday Templates. They act as a centralized automation tool. When you create a list of dates, like your National Holidays, and link it to a user, the system generates a Normal Event on their diary for every single date on that list.

Because a "Normal Event" now sits on that day, the Scheduling Engine sees the time as "Busy" and strictly prevents any bookings. It's a clean, fail-safe way to manage company-wide availability. Use templates for dates that apply to everyone. For individual exceptions— like a specific technician calling in sick, or a few days of annual leave, you should continue to manually add those normal events to their specific diary.

From setting up Skills and Shift, we now have a system that knows who is qualified and when they are working. But you cannot show a customer a raw, unfiltered view of your diary. A customer doesn't care that your engineer has a 30-minute gap at 2:15 PM.

Service Windows simplify scheduling for customers. They offer convenient time slots, like a menu with Morning Slot or Afternoon Slot, while the system coordinates jobs efficiently.

Service Windows hide the complicated details, making bookings clear and consistent for every customer.

Now that you have your "who," "when," and "what" configured, it's time to fine-tune the engine's logic. These settings act as the final "rules" the system follows when calculating availability and offering appointments. Both of these critical configuration pages are located in the same category: Settings → Schedule and dispatch.

This page controls the fundamental behaviour of your diary. For the scheduling engine to function reliably, one setting here is non-negotiable.

The Setting: Allow overlap events

The Business Outcome (Why this matters): This is essential for automation. Setting this to 'No' is what prevents accidental double-bookings. It ensures that when the engine (or a user) looks for an available slot, it only sees genuinely available time. If you leave this as 'Yes', the engine may book a job on top of an existing appointment, causing administrative chaos.

Click here to see the related help centre article: Diary settings

This page is the "brain" of your routing logic. It tells the engine how to calculate travel and which engineers or technicians schedules to consider for a job.

The Setting: Allow overtime bookings

The Business Outcome (Why this matters): You defined overtime in your shift patterns to track your costs, not as standard availability. By setting this to 'No', you reserve those expensive overtime slots for your office staff to use manually for high-priority, emergency jobs. This prevents the automated portal from letting a customer book routine maintenance during your most expensive hours.

The Setting: Distance Consideration

The Business Outcome (Why this matters): This is a critical tool for protecting your profit margins. By setting a maximum distance from the engineer's start address, you act as a "geographical gatekeeper."

This prevents the portal from scheduling your best technician for a low-value job that is three hours away. It ensures your team is only scheduled for jobs within a reasonable, profitable radius. Any customer outside this range will be unable to book online and will be prompted to call your office, giving you manual control over the decision.

Click here to see the related help centre article: Route optimisation

We are almost there. We have built all the logic for your engine. Now we must make the final connection and tell our Job Descriptions which technicians to use for portal bookings. This is a critical step for controlling who is offered for online, automated scheduling.

And that's it. We have now fully covered the logic for your automated scheduling. In the final step we will see how this all comes together to power the Suggested Appointments feature for your office team.

You have now built a powerful, automated framework. By defining who can do the work with Skills, when they work with Shift Patterns, and how slots are offered with Service Windows, you have created a scalable foundation for your company's growth. Thank you for taking the time to learn with us, and good luck with your implementation.