Visit Website →
← Back to blog

Set Service Durations: 6 Steps to Protect Aussie Trade Calendars

October 10, 2026
Set Service Durations: 6 Steps to Protect Aussie Trade Calendars

Edit the service's duration field and confirm its before and after buffers, then immediately test two neighbouring slots. The duration field controls what customers see when booking, while the buffer settings determine how much extra time the calendar blocks around that slot for preparation, cleanup and travel. Checking both, then testing, catches overlaps before they turn into double bookings.

TL;DR:

  • Choose a fixed length for repeatable jobs, published options for distinct service tiers, or a customer chosen length only when staff approval prevents conflicts.
  • Set buffers by job type, and schedule travel separately because route time varies between jobs while preparation and cleanup usually remain constant.
  • For assets without service history, enter a start date or starting meter reading first, or the system may mark them overdue or available incorrectly.
  • Check the minute before, the permitted start time, and the minute after; confirm the slot list and completed booking show the same availability.
  • Check operating hours, time zones, and holiday schedules before changing durations, because these service level settings also determine valid start and end times.
MyAirCare
Keep Air-Con Bookings on Track
MyAirCare brings customer bookings, payments, reminders and mobile job management together for Australian air-conditioning cleaners.
Explore MyAirCare

Table of Contents

Step-by-step: how to set or change a service duration

Most booking and field-service systems organise this information the same way, even if the field names differ slightly.

  1. Find the service or asset record, usually under a menu called Services, Booking Types or Assets.
  2. Open the record and look for a field labelled "service duration," "service time" or sometimes "appointment length."
  3. If the asset has no service history, set a baseline: a service start date, or a starting kilometre or hour reading, so the system does not treat it as overdue from day one.
  4. If the service repeats on a schedule, set the repeat interval or recurrence cadence alongside the duration.
  5. Save the change, then confirm it has pushed through to staff calendars and any public-facing booking page.
  6. Work through a short checklist: the customer booking page, automated reminder templates, pricing displays and staff calendars should all reflect the new duration.

Some platforms separate the visible duration from the internal buffer settings, which sit in a different tab or dropdown. According to Microsoft Learn's guide to configuring service availability, buffer defaults are set on the service details page, and before and after dropdowns control hidden time that blocks staff availability even though customers never see it. That distinction matters because a technician's real workload includes more than the time a customer is charged for.

When a service has no prior bookings to reference, the gap shows up fast: new assets with no history can appear falsely overdue or available, so setting a baseline start date or meter reading first avoids an awkward first booking.

Pro Tip: Update the booking page, reminder templates and staff calendar in the same session as the duration change, so nothing falls out of sync for a week while you remember to circle back.

Which duration model fits: fixed, published choices or customer-selected

Three common models cover most scheduling needs, and the right one depends on how much the job varies.

  • Fixed duration works for routine, repeatable jobs like a standard clean or inspection where the time rarely changes.
  • Published choices suit services with distinct tiers, such as a basic service versus a deep service, each carrying its own price and resource needs.
  • Customer-selected duration allows a client to pick a longer or shorter slot, but this usually needs staff approval before it is confirmed, since an unchecked custom length can quietly eat into the next booking.

Each model has flow-on effects. A fixed duration keeps pricing and reminders simple. Published choices need separate pricing and reminder text per option. Customer-selected durations need a review step, otherwise resource allocation becomes unpredictable and staff calendars start absorbing the difference.

Buffers, preparation, cleanup and travel: protecting hidden time

The duration a customer sees is rarely the whole story. Preparation before the job, cleanup after it, and travel to the next site all need to be accounted for somewhere, or the calendar will double-book a technician who looks "free" on paper.

A single global buffer applied to every service tends to either waste time on simple jobs or shortchange complex ones. Job-type defaults work better: a routine task might need a short buffer, while a complex install needs considerably more. Travel can be handled as a separate scheduled block or folded into an integrated drive-time calculation between stops, but either way it needs to be visible to the system making the booking decision.

Booking Handbook's guide to buffers, duration and travel frames this as "time to protect," calculated as preparation plus service plus cleanup plus travel. A worked example shows how quickly these add up:

Four time components set the next safe booking

If that job starts at 9:00 AM, the earliest safe start for the next booking is 10:50 AM, not 10:00 AM. Booking the next job any earlier risks a technician arriving late or skipping cleanup.

Pro Tip: Treat travel as its own line item rather than folding it silently into "buffer," since travel time varies by job pair while prep and cleanup usually stay constant.

Test and verify: safety checks after changing durations

A duration change is not finished until it has been tested against real neighbouring slots.

  1. Create two test bookings back to back, including the full preparation, cleanup and travel time, and confirm what start time the system offers for the second one.
  2. Check the availability list or slot picker directly to see whether it correctly blocks the minute before the safe start time.
  3. Review reminder templates, staff calendars and pricing displays for edge cases, such as a published-choice service that recalculates price but not duration.
  4. If a conflict appears, roll back the change or widen the buffer rather than leaving it live for customers to book into.

Booking Handbook recommends testing the exact boundary: the minute before, the exact allowed time and the minute after, to confirm the slot list and the final booking agree.

Practical scheduling habits that protect capacity

A handful of habits separate calendars that run smoothly from ones that generate constant rework.

  • Set buffers by job type rather than one flat number across every service, since a routine task and a complex install carry different hidden workloads.
  • Cluster jobs geographically when bookings come in, rather than relying only on route optimisation after the fact, to cut travel overhead between stops.
  • Measure a handful of representative real-world jobs, from arrival to departure, before rolling a duration change out across the whole service catalogue.

Service level settings also matter here. Oracle's documentation on defining service levels notes that authorised hours of operation, time zones and holiday schedules all feed into how a system calculates valid start and end times, which is worth checking before assuming a duration problem is the only cause of a scheduling conflict.

Common mistakes and quick operational wins

The most common error we see is a single global buffer applied across every service type, which either wastes staff time on simple jobs or leaves no room on complex ones. Per-job defaults, even a rough first pass, fix most of this immediately.

Common mistakes and quick operational wins — overview diagram

The second lever worth pulling early is pairing clear, published durations with automated reminder timing that matches the job length, since a customer who knows exactly how long a visit will take is less likely to reschedule at the last minute.

Neither change requires new software. They require someone to sit down, measure a few real jobs, and set the numbers once properly.

— Lewis

Configuring durations and buffers inside MyAirCare

This scheduling system is built with a service duration field, separate before and after buffer settings, and team calendars that update immediately after changes. Automated reminders and secure payments through Stripe use the same duration data, so changes to service length update customer messaging and invoicing automatically.

MyAirCare

  • Set a fixed, published-choice or customer-approved duration per service, with buffers that reflect real prep and cleanup time.
  • Push changes instantly to staff calendars and your branded booking page, then run the two-booking test described above on a live service.
  • Check the pricing page to compare the Free plan against MyAirCare Pro, or start configuring a service today on the MyAirCare platform.

For teams juggling calendar sync across multiple tools, Wattle AI's guide to appointment calendar sync covers practical steps for avoiding double bookings once several systems are involved.

FAQ

What does "service duration" mean?

Service duration is the length of time a booking system allocates to a job, from the customer-visible appointment length through to any hidden buffer time for preparation, cleanup or travel. The visible duration and the total blocked time are not always the same number.

Recommended intervals vary by industry and by the specific equipment or vehicle involved, so there is no single figure that applies everywhere. Checking the manufacturer's schedule or an asset's service history, and setting a baseline service start date when no history exists, gives a more reliable starting point than a generic rule.

Should scheduling be based on time or usage?

Both measures are used depending on the asset: some services are scheduled by elapsed time, others by a usage figure such as kilometres or hours run. Setting a baseline value, whether a start date or a starting meter reading, lets the system track whichever measure applies to that asset.

What is a schedule of service?

A schedule of service is the set of rules, including authorised operating hours, time zones and any holiday schedule, that a system uses to calculate valid start and end times for a job. Oracle's service level documentation outlines how these settings feed into scheduling calculations.

Sources