Excel to Booking System · Your App Cloud
Build a booking app from your Excel spreadsheet
In a booking sheet, a booking is a filled cell and the rules live in someone's head. Upload the workbook, turn slots, rooms and colors into records, then write down the rules the sheet never enforced.
From booking grid to bookings with rules.
Three passes: read the grid, write down what people remembered, then try to book the same slot twice.
01
Unpick the grid
Upload the workbook and say what its rows, columns and filled cells mean. A name under Room B at 10:30 on Tuesday is one booking with a room, a date, a start, an end and a customer.
02
Write the rules the sheet never enforced
Most booking sheets rely on people, not rules, to keep entries right. List what those people remember: opening hours, slot length, the gap between bookings, spots per session, how much notice you need, and who may book what.
03
Book the same slot twice on purpose
Before you share the address, request one slot from two test accounts. Then cancel a booking and see whether its slot opens again, and make one booking from a phone set to another time zone.
What each part of the booking sheet becomes.
The layouts below are illustrative, not taken from a real business. Find the row closest to your workbook and read across to the check.
| In your booking sheet | In your booking app | What to check |
|---|---|---|
| Time slots down the side (9:00, 9:30, 10:00) and days or dates across the top | Opening hours and a slot length, written as rules instead of rows of empty cells | An empty cell doesn't say whether a slot is free or closed. Mark lunch breaks, holidays and closed days yourself, then compare one week of open slots with the sheet. |
| A filled cell such as 'Emma Clarke 555-0142' | A booking with a resource, date, start and end, and the customer's name and phone in fields of their own | Open five bookings beside their cells. The name and number should sit in separate fields. List the cells that hold only initials, so you can finish them. |
| A cell merged across three slots for a 90-minute appointment | One booking with a start time and an end time | Excel keeps a merged cell's text in its upper-left cell only, and the other slots it covers are empty. Confirm the booking runs to its real end, not just to the end of the first slot. |
| One tab per room, per therapist or per week | Resources the person booking chooses from, and a single list of bookings with a date on each | A new week's tab that started as a copy of the last one can still hold one-off bookings nobody cleared. Count one room's bookings for one week and compare the number with that tab. |
| Fill colors, such as green for confirmed, yellow for pending and gray for blocked, or a question mark after a name | A status on every booking (requested, confirmed, canceled) and blocked time on the resource | Write the color key into the prompt. Then find two bookings whose only sign of being provisional was a color or a question mark, and check which status each one got. |
| A class sheet with Seat 1 to Seat 12 across each session's row, or a 'spots left' formula | A session with a capacity, and one booking per attendee | Compare spots left for three sessions, including one that is full. Decide what a 13th request gets: a refusal or a spot on a waitlist. |
| A clash check you built with COUNTIFS, or a highlight when two names share a slot | A rule you describe: how many bookings each room, person or item can take at the same time | The sheet could only flag a clash after someone typed it. In the app, try to save a second booking for a full slot from another test account and read what that person is told. |
| The same class typed into every Tuesday row until December | A repeating booking, with the dates it skips | Look for the weeks someone cleared by hand, such as Thanksgiving week. Name those dates in the prompt, then check that the repeating booking skips each one. |
| Paid, Deposit and Notes columns beside each booking | A payment status on the booking, and staff notes kept apart from what customers see | Mark the deposit paid when it arrives through the payment link you already use. Then sign in as a test customer and confirm the staff notes don't show. |
What a booking sheet leaves to memory.
The workbook shows who is booked where. It rarely says why a slot is closed, how long a room needs between clients, or who is allowed to squeeze someone in. Put those unwritten rules in the prompt next to the file.
Grid or list
Booking sheets come in two shapes. A list keeps one row per booking, with date, start, end and room columns. A grid puts slots down the side and days or rooms across the top. Say which you have, and for a grid, what an empty cell means.
Past bookings: bring them or start fresh
Last year's bookings are history, not availability. Decide whether the app needs them to show a customer's earlier visits, or whether it starts on a set date with future bookings only.
Names and phone numbers are personal data
In a shared booking sheet, anyone who opens the file can see every customer's details. In the app, decide who sees them: staff who sign in, not other customers. Set this through the access you describe for each collection, then check it from a customer's test account.
Pick a cut-over date
An upload is a snapshot, not a sync. Choose the day bookings stop going into the sheet. Import the future bookings the evening before, then treat the workbook as a read-only record so nobody books a slot the app can't see.
An illustrative starting point
A booking app that runs on your rules.
Rooms, people or equipment to choose from, open slots worked out from your hours, and bookings with a status staff can confirm.
A calendar built from rules
Ask for open slots to come from the hours, slot length and gaps you describe, not from copied blank cells. When your hours change, you edit one rule instead of redrawing next month's grid, then check next month's slots.
Bookings with a status
Each booking records who, what, when and where, plus requested, confirmed or canceled. Ask for a canceled booking to keep its record and free its slot, then test that both happen.
Resources people can choose
Rooms, staff or equipment become a list the person booking picks from. Each one can have its own hours and capacity, so a room that closes on Fridays needs no grayed-out cells.
Confirmations you control
The app can email a confirmation once a booking is saved, and send tomorrow's reminders on a schedule you set. Send each message to your own address first. Delivery times aren't guaranteed.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Database
Keep data and context for apps and agents
Authentication
Give the right people access
Email
Keep conversations moving
A little more context
Good questions.
Can I keep taking bookings in Excel while I test the app?
Yes, while you test, but nothing typed into the sheet after the upload reaches the app. Try the app with a copy of last month's workbook. On the day you switch, bring the upcoming bookings across in one deliberate re-import, then stop booking in Excel.
Will the app prevent double bookings?
Not by itself. It needs a rule you describe, and a test that shows the rule holding. Say how many bookings each room, person or item can take at the same time. Then request one slot from two test accounts at nearly the same moment, and check that the second is refused or waits as a request. Repeat the test whenever you change the rules, and don't promise customers clash-free booking until it passes.
Can customers book for themselves?
You can design it that way. Decide whether a customer's booking is confirmed straight away or waits for staff to approve it, and whether customers sign in or only leave a name and email. Saved bookings and sign-in need a backend.
How are time zones handled?
A cell that says 9:00 doesn't say which time zone it means; the people using the sheet just know. Say it in the prompt, for example Pacific time for a studio in San Diego. Then book from a device set to Eastern time and check the time on the booking. Repeat for a date on the weekend daylight saving time starts.
What about cancellations and no-shows?
Write your rule in the prompt, such as no changes within 24 hours of the start, and say who may override it. Ask for canceled and no-show to be statuses rather than deleted bookings, so a customer's history stays together. Then cancel a test booking and check that its slot can be booked again.
How do I handle deposits?
Keep taking deposits through the payment link or page you already use, and link to it from the booking confirmation. Give each booking a deposit status that staff update when the money arrives. Decide which services need a deposit and what happens to it when someone cancels inside your notice period, and say so on the booking page.
Will the booking page work on phones?
The booking page is published at a web address and opens in a browser, including on phones. A week grid with three rooms across won't fit a small screen, so ask for a day view that lists the open times. Then make a test booking on your own phone before you share the address.
Which plan does a booking app need?
Taking bookings means saving them and knowing who made each one, which needs a backend, as do email confirmations, so a booking app is an app with data, and putting it live needs a paid plan. A page with your hours and phone number would be a one-page site, which Free publishes. Model and service usage is metered separately.
Explore Pricing for plans, included capabilities, and usage details.
Keep exploring.
Build an online booking app ↗
See the outcome and the capabilities behind it.
Why double bookings happen ↗
Where clashing bookings come from when availability lives in a sheet or a shared calendar, and what closes the gap.
Create an appointment scheduling app ↗
For time with a person rather than a room or an item: appointment types, durations and what a customer prepares beforehand.
Understand data and context ↗
Give information the right place in your app.
Prepare to publish ↗
Check the experience you will share.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building