Availability and capacity
Show the people, working hours, leave, resources and existing commitments that determine whether a slot is genuinely available.
CUSTOM BOOKING SYSTEM DEVELOPMENT · UK
A booking system that understands what happens after the appointment.
Generic calendars are useful until a booking also needs the right customer record, staff member, asset, job status, notes, price, history and follow-up. IT Hospital builds booking software around that complete operational workflow.
WHAT WE CAN HELP WITH
Connect the diary to the work it creates.
Customer and subject history
Connect each appointment to a customer and, where useful, a vehicle, pet, device, property or other subject with its own history.
Operational status
Move work through clear stages such as booked, checked in, active, awaiting approval, ready and completed—using terminology that fits the business.
Communication and oversight
Prepare customer updates and give authorised staff useful visibility of workload, outcomes, cancellations and data quality.
CONCEPT SYSTEMS
One proven foundation.
Different business workflows.
These interfaces show how the booking, customer, staff and status foundations used in real operational systems could be adapted for other appointment-led businesses.
Capability demonstration—not a client case study. Every name, appointment and price below is fictional. The concepts show a realistic delivery direction, not an existing vertical product.
HAIR & BEAUTY STUDIO
A staff diary and customer portal built around services, time and price.
A customer can see upcoming appointments and request a preferred slot. The studio reviews the request against stylist skills, service duration, working hours and existing bookings before confirming it.
- Appointment requestsCustomers request; staff retain control of confirmation.
- Service costingFixed prices or honest ranges for variable work such as colour.
- Client historyPrevious services, preferences, notes and future appointments together.
- Clear communicationRequested, confirmed, completed and cancelled states drive updates.
TODAY · TUESDAY 15 SEPTEMBER
Studio diary
MIA · STYLIST09:00 · 60 MINCut & finishEmily R. · £48 · Confirmed 10:30 · 150 MINColour refreshSophie L. · £85–£110
AVA · BEAUTY09:30 · 45 MINGel manicureHannah P. · £36 · Confirmed 11:00 · REQUESTBrow appointmentLucy M. · Review slot
CUSTOMER PORTALMy appointments
UPCOMINGCut & finishTue 22 Sep · 10:00 with Mia Confirmed · £48
Previous services and preferences stay available for a faster repeat booking.
CONCEPT · FICTIONAL DATA
PET GROOMING
Owner, pet and grooming history
Appointments connected to breed, coat, temperament, allergies, preferred cut, previous notes and collection status.
RequestedConfirmedGroomingReady
- Pet profile
- Grooming notes
- Ready for collection
CONCEPT · FICTIONAL DATA
TATTOO STUDIO
Consultation through to aftercare
Artist availability, design references, deposits, multi-session work, consent steps and aftercare kept with the client record.
EnquiryConsultationBookedAftercare
- Artist diary
- Deposits
- Session history
CONCEPT · FICTIONAL DATA
BIKE & EQUIPMENT REPAIR
Booking, asset, quote and collection
A customer request becomes an inspectable job with equipment history, diagnosis, quote approval, parts and progress updates.
BookedDiagnosingApprovedReady
- Asset history
- Quote approval
- Job status
Reusable foundations can shorten delivery.Authentication, customer records, staff availability, booking states, audit history and backup patterns do not need to be rediscovered for every project.
Each business still needs its own workflow mapped, terminology agreed, data protected and integrations scoped. Reuse accelerates the dependable parts without pretending every business is identical.
SELECTED WORK
Real systems.
Built around real work.
These are not template demonstrations. Each system began with an operational problem and was shaped around the people who use it.
01CLIENT SYSTEM
Car2Code Workshop System
A private operational platform that brings workshop bookings, customer and vehicle history, staff availability, holiday records and performance oversight into one focused workspace.
- Workshop diary
- Customer CRM
- Staff hours & leave
- Secure cloud data
WORKSHOP DIARY
Monday, 7 September
09:0010:0011:0012:00
Alex09:00–10:30Annual serviceAB12 CDE · Returning customer 11:00–12:00DiagnosticsXY67 ZZZ · New customer
Sam09:30–11:00Repair workCD34 EFG · Parts ready 11:30–12:15CollectionGH56 JKL · Customer notified
Jordan
Approved holiday7–11 September · balance updated
02INTERNAL PRODUCT
IT Hospital Workshop OS
IT Hospital’s own repair-management workspace, connecting intake, active repairs, compatible parts, customer updates, payments, reporting and recoverable operations.
- Repair workflow
- Parts & stock
- Customer updates
- Audited backups
WORKSHOP OVERVIEW
Good morning.
ACTIVE WORKTECHNICIANSTATUS
Laptop display replacementRepair #0421 · Demo customerAlex M.In repair
Phone battery serviceRepair #0420 · Demo customerSam R.Ready
Console HDMI diagnosisRepair #0419 · Demo customerUnassignedBooked in
Privacy built into the presentation. All interface examples use fictional demonstration data. Private customer and business information is never displayed.
A PRACTICAL APPROACH
Keep the familiar diary. Improve everything around it.
Clear decisions, direct communication and no unnecessary complexity.
- 01
Map how bookings work today
Understand the calendars, forms, messages, paper notes, customer records and hand-offs already in use.
- 02
Define the useful minimum
Choose the smallest connected workflow that removes a meaningful operational problem rather than recreating every possible feature.
- 03
Test real appointment scenarios
Use realistic examples across desktop and mobile, including rescheduling, cancellations, staff absence and returning customers.
- 04
Launch with safeguards
Treat permissions, validation, audit history, backups and recovery as part of the booking product—not optional extras.
GOOD TO KNOW
Custom booking software is justified by the workflow—not the word custom.
- If Calendly, Fresha or another established platform already handles the important process well, using it may be the better choice.
- A custom system becomes valuable when generic tools force repeated work, fragment customer history or cannot represent capacity correctly.
- The first version can focus on staff operations before adding customer self-service, payments or integrations.
- Car2Code shows this approach in practice: a familiar workshop diary connected to customers, vehicles, staff availability and repair history.
COMMON QUESTIONS
Useful answers before you enquire.
If your situation is unusual, tell us what you are trying to achieve and we will advise honestly.
Yes. The workflow, labels, permissions and information captured should reflect the real operation rather than forcing the team into generic appointment language.
Customer self-booking can be included when it suits the service. Some businesses benefit from staff-controlled bookings first because each job needs triage, a quote or a specific resource.
Yes. A booking can connect to a vehicle, device, pet, property, project or another subject with its own notes and history.
Email, SMS or WhatsApp-related workflows may be possible depending on the chosen provider, consent requirements and the exact communication process. Integrations are scoped explicitly.
No. A useful first version can improve the diary and internal records while preserving valuable existing tools. Later stages should be driven by actual use.
No. They are clearly labelled concept interfaces using fictional data. They demonstrate how proven booking, customer, staff and status foundations could be adapted quickly, while the final workflow, safeguards and integrations would still be designed for the individual business.
Start by measuring the repeated administration, errors, delays, lost history and limitations of the current tools. Discovery should compare that cost and risk with adapting an existing product.
DISCUSS A BOOKING WORKFLOW
Show us what the calendar cannot currently handle.
Describe how a booking begins, what staff need during the job and what should be recorded when it is complete. That is enough to start.
Read the Car2Code booking-system case study