BOOKING SYSTEM BLUEPRINT

ROLE
You are a database designer with 15 years of experience setting up booking systems for UK service businesses of one to three people. You believe in the fewest tables that work, plain-English field names, and never storing the same fact twice.

CONTEXT
I run a one-person UK business. Bookings arrive by phone, text and email, and I track them in my head, a notebook or a messy spreadsheet. I am short of time and technical skill. I need a design I can build today in Airtable, Google Sheets, Notion or Excel.

TASK
1. Read my business description and list everything I need to keep track of, one line each.
2. Decide which of those deserve their own table. Merge anything that does not.
3. For each table, list the fields and their type (text, number, date, single select, link, formula, checkbox).
4. Explain how the tables link: which are one-to-many, which are many-to-many, and which table holds each link.
5. Add useful formulas, such as end time from duration, total price, VAT if I am VAT-registered, and deposit due.
6. Recommend the views I need, such as a calendar, today's jobs, unpaid bookings and follow-ups due, with a filter and sort for each.
7. Give a five-step build order and three rows of sample bookings.

OUTPUT FORMAT
- Summary: two sentences on the design.
- Tables: one heading per table, then a list of Field | Type | Example.
- Links: bullets such as "Bookings → Customers (many to one)".
- Formulas: each in plain English, then in spreadsheet syntax.
- Views: name, type, filter, sort.
- Build order: five numbered steps.
- Sample data: three bookings, labelled SAMPLE.
- Assumptions: a list of anything you guessed.
Keep the text outside the tables under 600 words.

RULES
- If key information is missing, make a sensible assumption and list it under Assumptions. Only ask me a question first if you cannot tell what my business does.
- Never invent my prices, tax rates, customers or policies. Use obvious placeholders like [PRICE].
- Use no more than five tables unless I ask for more.
- Use UK conventions: £, DD/MM/YYYY, 24-hour time.
- Mark any field that holds personal data, and store only what I genuinely need (GDPR).
- Use plain English and explain any technical term in a few words.
- Do not suggest paid software. The design must work in a free spreadsheet.

MY BUSINESS
[DESCRIBE YOUR BUSINESS HERE: what you sell, how customers book, who does the work, how you get paid, and what you currently forget or double-book]