How much booking notice should you require?

A customer books for 10am. It's 9:47. You're in another suburb, the equipment is at home and apparently the business now owns a helicopter.

Minimum booking notice is how far ahead a customer must book. Booking systems often call this a lead-time setting. Here, we're talking about that cutoff, rather than measuring how far ahead your customers usually book.

There isn't one correct number for every business. A vacant squash court and a catered event have different opinions about preparation.

Work backwards from arrival

List what has to happen after someone books and before the service starts.

A mobile repair might require reviewing the fault, locating parts, loading the van and travelling. A class might already have its instructor and room ready. A private event could require staff, supplies and venue approval.

Your lead time needs to cover the steps that cannot be completed in advance.

Don't confuse this with service duration. Duration reserves time for the work. Lead time stops the booking arriving too close to its start.

Use different rules where the work differs

A fixed, staffed venue may be able to accept short-notice bookings during opening hours. A mobile business may need longer notice for distant areas.

Use these questions to decide where your cutoff belongs:

The answers are more useful than borrowing another business's "24-hour policy" because it sounded official.

Suppose a mobile service needs 20 minutes to review and prepare a job, then 40 minutes to load and reach the customer. That's an hour before allowing for delays. You might test a 90-minute minimum notice for that service when staff are already working. If preparation can only happen the previous afternoon, a next-day cutoff makes more sense. These are worked examples, not recommended settings for every business.

Decide what happens outside normal hours

If someone books at 11pm for the following morning, will anyone review the details before they arrive?

For straightforward self-service work, that may be fine. For work requiring preparation, your notice rule needs to reflect the time the business can actually act.

Test evening, weekend and public-holiday scenarios. Twelve elapsed hours doesn't necessarily contain twelve working hours. A setting may count one while you are thinking of the other.

Write the promise from the customer's perspective: "Book by 3pm for next-day collection" is clearer than an unexplained technical setting.

Keep an exception route

A notice rule can stop an unsuitable automatic booking without stopping every conversation.

You might allow customers to request a short-notice appointment, then accept it if the equipment, staff and travel all work. State that requests need confirmation.

Don't advertise emergency availability unless you can support it. Customers with urgent problems need a dependable answer, not a form that someone checks after lunch.

Review the cost of your rule

Too little notice creates rushed preparation, missing materials and late arrivals. Too much notice can lose work you could comfortably accept.

For a few weeks, record short-notice requests, how many you accepted and what made the rejected ones impossible. Then adjust the rule for the service or area causing the problem.

For mobile businesses, Bookables supports lead-time rules on territories alongside area-specific hours and travel surcharges. See how territories work. Set up each area, then check the earliest time offered to a customer in that area.

Create your account and test the earliest time a customer can book. It should be a time you can reach using the vehicles you currently own.