--- title: "Scoping a booking system around real availability — Orvun Labs" description: "A booking system promises more than a time on a calendar." canonical: "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability" language: "en" last_modified: "2026-09-13" --- # Scoping a booking system around real availability A booking system promises more than a time on a calendar. ![Editorial diagram of connected steps and decision points](https://orvunlabs.com/images/blog/automation.svg) - Published: 2026-09-13T09:00:00.000Z - [Workflow automation](https://orvunlabs.com/en/journal/topic/automation.md) ## What the system promises A booking system promises more than a time on a calendar. It commits a resource, a duration and a set of conditions. Write those commitments before choosing screens. The difficult parts often concern preparation, cleanup, staff qualifications and changes after confirmation, rather than the calendar view itself. ## Compare the practical options Use an existing scheduling product when its availability rules and cancellation process fit. Consider custom work when several resources must be reserved together or exceptions are central to operations. List customer booking, staff administration and external calendar synchronization separately. Decide which source controls availability; copying events between calendars does not by itself prevent competing reservations. ## Test the whole journey Take an illustrative workshop that needs a technician and a service bay. A ninety-minute appointment also requires setup time. The system should check both resources together, hold them during confirmation and release the hold if the request expires. A reschedule must secure the new slot before relinquishing the old one, or clearly explain that the original booking has been lost. ## Make recovery visible Do not treat displayed availability as a guaranteed reservation. Test two customers choosing the same slot, a staff absence, a repeated payment notification and a change of timezone. Specify cancellation consequences independently from reminder delivery. If a confirmation message fails, the reservation must remain visible to staff with a way to resend the message. ## Model time, holds and changes separately For the workshop, write a resource rule before drawing the diary. The technician's working hours, service-bay occupancy and preparation buffer all restrict the appointment. State whether preparation blocks the same technician and bay or a different resource. Treat opening hours and actual bookable capacity separately: an open business can still have no available technician. Include the timezone of the location in the booking record and make the customer's displayed time unambiguous. Then distinguish a provisional hold from a confirmed booking. Choose an expiry rule and explain it to the customer while they complete any required details. Availability must be checked again when confirmation is attempted; yesterday's page or another customer's cancellation may have changed it. If payment is part of confirmation, define what happens when payment succeeds after the hold expires. That case needs a deliberate reconciliation path, not an automatic promise that capacity still exists. Practice a reschedule that crosses a staff absence. The operator should see eligible alternatives, any changed conditions and whether customer approval is needed. Keep the previous booking history, and attach reminders to the current confirmed version so an old reminder does not send the customer to the wrong time. Give staff a visible list of holds needing attention, failed confirmations and unresolved payment states. A small queue for these exceptions is usually clearer than burying them among ordinary appointments, provided each item has an owner and a safe next action. ## Booking acceptance cases | Case | Required outcome | | --- | --- | | Two people confirm the final slot | At most one confirmation owns the required resources; the other receives a usable alternative or a clear unavailable result. | | Payment arrives after a hold expires | The payment and booking states are reconciled under the agreed policy, with no unsupported capacity promise. | | Customer changes the appointment location | The location, displayed time and required resources are recalculated and presented before the change becomes final. | | Reminder delivery is retried | It uses the current confirmed booking and does not reinstate cancelled or replaced appointments. | ## Take these examples to review What exactly becomes unavailable when a booking is confirmed? Who may override capacity, and is that recorded? Which changes require customer agreement? Sketch one ordinary booking, one cancellation and one reschedule with the operations owner before estimating the system. ## Workflow automation Less copying. More control over the work. - [Discuss this service](https://orvunlabs.com/en/services/workflow-automation.md) ## Related reading - [When a spreadsheet needs to become a business application](https://orvunlabs.com/en/journal/when-a-spreadsheet-needs-to-become-a-business-application.md) - [Automating approvals without losing accountability](https://orvunlabs.com/en/journal/automating-approvals-without-losing-accountability.md) - [Turning manual reporting into a dependable reporting process](https://orvunlabs.com/en/journal/turning-manual-reporting-into-a-dependable-reporting-process.md) ## Let's make something useful. A first product, a difficult workflow or software that needs a fresh start. Tell us where you are. - [Tell us about your project](https://orvunlabs.com/en/contact) ## Structured data ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://orvunlabs.com/#organization", "name": "Orvun Labs", "url": "https://orvunlabs.com", "logo": "https://orvunlabs.com/orvunlabs-icon-512.png", "description": "Custom software, SaaS products and AI-powered tools — designed around your business.", "knowsAbout": [ "Custom software", "SaaS product development", "AI integration" ] }, { "@type": "WebSite", "@id": "https://orvunlabs.com/#website", "name": "Orvun Labs", "url": "https://orvunlabs.com", "inLanguage": [ "en", "es", "de", "fr", "pt", "ja", "hi", "ar", "id", "tr", "pl" ], "publisher": { "@id": "https://orvunlabs.com/#organization" } }, { "@type": "WebPage", "@id": "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability#webpage", "url": "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability", "name": "Scoping a booking system around real availability", "description": "A booking system promises more than a time on a calendar.", "inLanguage": "en", "isPartOf": { "@id": "https://orvunlabs.com/#website" }, "about": { "@id": "https://orvunlabs.com/#organization" }, "breadcrumb": { "@id": "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability#breadcrumb" } }, { "@type": "BreadcrumbList", "@id": "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Orvun Labs", "item": "https://orvunlabs.com/en" }, { "@type": "ListItem", "position": 2, "name": "Scoping a booking system around real availability", "item": "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability" } ] }, { "@type": "BlogPosting", "headline": "Scoping a booking system around real availability", "description": "A booking system promises more than a time on a calendar.", "datePublished": "2026-09-13T09:00:00.000Z", "dateModified": "2026-09-13T09:00:00.000Z", "inLanguage": "en", "author": { "@id": "https://orvunlabs.com/#organization" }, "publisher": { "@id": "https://orvunlabs.com/#organization" }, "image": [ "https://orvunlabs.com/images/blog/automation.svg" ], "mainEntityOfPage": { "@id": "https://orvunlabs.com/en/journal/scoping-a-booking-system-around-real-availability#webpage" } } ] } ```