A booking process should carry the customer’s request from first enquiry to a clear, confirmed appointment. Small service businesses often manage this across calls, messages and a calendar, making it easy to miss a changed address or an unconfirmed time. Document the information that must move between those channels.
Define when a request becomes a booking
Choose a small set of statuses that reflect the actual workflow: enquiry received, information required, quote sent, awaiting approval, confirmed, reschedule requested and cancelled. Make the trigger for “confirmed” explicit. A slot pencilled into a calendar is not necessarily a customer-approved appointment.
Capture only information needed for the service: customer contact, service location, requested work, access arrangements, preferred date, quoted scope and approval reference. Keep unusual personal or sensitive information out of a shared calendar title.
Write the confirmation step
Specify who sends the confirmation, which channel is used and what the message includes. A useful confirmation states the agreed date or arrival window, location, contact route, scope reference and what the customer needs to do before the visit. Avoid promising an exact arrival time if the business operates in service windows.
In a hypothetical mobile-maintenance business, a customer accepts a quote by email but asks by text to move the appointment. The office records “reschedule requested”, checks capacity, sends the revised confirmation and updates the field job. The old time remains visible in the change history instead of existing as a second active booking.
Give exceptions a route
Document how to handle unavailable stock, no access, weather disruption, an uncontactable customer or a request outside the quoted scope. Name a decision owner rather than writing “ask management”. Include how the customer is notified and where the outcome is recorded.
At the end of each day, review unconfirmed appointments and bookings with missing access information. This short check targets specific loose ends; it should not require rewriting every job record.
Test the procedure with three recent examples: a straightforward booking, a reschedule and a cancellation. Ask office and field staff whether they can identify the current appointment and the latest agreed scope from one record.
Australian Government process guidance provides a foundation for documenting repeatable work. The suggested booking statuses here are an operational design example. Tailor them to the business’s actual terms, privacy needs and customer-service commitments, and have the process owner approve the final procedure.



