|
Description: |
**Goal**
A fast, clean site that drives bookings and driver sign-ups, is easy to edit via CMS, and **meets TfL operator record-keeping requirements** for online bookings.
**Scope**
1. **IA & Design**
* Nav: Home · Book a Ride · Services · Corporate · Drivers · About · Contact · **Legal**
* Sticky header + floating “Book Now” (desktop/mobile)
* Brand: Yellow #F9D400 / Black #111111 / White; accessible contrast; modern system fonts.
2. **CMS + Dynamic Pages**
* Collections: **Pages**, **Services** (plus **Legal**, **Locations**, **Settings** if helpful).
* One dynamic template for Pages (fields: slug, H1, sub, buttons JSON, rich text, metaTitle/metaDescription).
* Dynamic Services template + static Services index (repeater).
3. **Pages to Build**
* **Home** (hero, USPs, services, fleet, trust, CTA)
* **Book a Ride** (Wix Form: journey type, pickup, drop-off, date/time, passengers, luggage, vehicle, flight no., notes, name, phone, email; notifications + success message)
* **Drivers** (benefits, requirements, multi-file upload application; auto-reply)
* **Corporate** (benefits, SLAs, enquiry form)
* **About** (compliance, coverage)
* **Contact** (tap-to-call, WhatsApp, map)
* **Legal** (**Passenger Terms & Conditions**, **Privacy Notice**, **Cookies**, **Complaints**) – editable via CMS.
4. **TfL Booking-Record Compliance (must-have)**
Create a bookings data model and admin UI that stores and exposes at least:
* **Responder name** (who accepted the booking request)
* **Dispatcher name** (who dispatched the vehicle)
* **Driver PHV licence number** (for the job fulfilled)
* **Vehicle VRM** used
* Timestamps (created/accepted/dispatched/completed), passenger details, pickup/drop-off, notes/flight, vehicle requested, status, quoted fare (if applicable).
* **Retention ≥ 12 months** for bookings, plus collections for **Complaints** and **Lost Property**.
* **Staff Register** for anyone who takes bookings/dispatches (name, role, DBS date/result, active).
* **Admin dashboard** (members-only): search/filter/export (CSV/XLSX), edit tracking/audit trail, role-based permissions so logged-in staff are recorded as responder/dispatcher automatically.
5. **Light Velo (preferred)**
* Render hero buttons from CMS “buttons JSON”.
* Simple form logic (e.g., hide drop-off when “Hourly” selected).
6. **SEO & Tracking**
* Meta title/description from CMS; `TaxiService` schema.
* GA4: events for `form_submit`, `phone_click`, `whatsapp_click`, `book_click`, `driver_apply`, `corporate_submit`.
* (Optional) Meta Pixel/Google Ads conversions.
* Image optimisation and no CLS on hero.
**What I’ll Provide**
* Final copy and page structure
* **CSV files** for CMS import (Pages, Services; Legal/Locations on request)
* Logo/assets and contacts ([info@cltaxis.co.uk](mailto:info@cltaxis.co.uk), +44 20 453 6611 / +44 7876 855167)
**Deliverables / Acceptance**
* Live site with CMS-driven pages; **Book a Ride** + **Drivers** forms working
* **Admin bookings dashboard** with search/filter/export + audit trail + role permissions
* Booking records include responder, dispatcher, **driver PHV licence**, **vehicle VRM**, timestamps; retention ≥ 12 months
* Legal pages (T&Cs, Privacy, Cookies, Complaints) published and linked from footer/forms
* GA4 events firing; schema present; images compressed; mobile performance verified
**Your Proposal (please include)**
1. Your plan to implement **CMS + dynamic pages + TfL-compliant bookings + admin export**
2. How you’ll set up the **Staff Register**, permissions, audit trail, and retention
3. 3–5 relevant Wix/Wix Studio portfolio links
4. Fixed price with milestones (CMS/Structure → Pages/Forms → Legal/SEO/Tracking → Admin/QA/Handover)
5. Timeline and two rounds of revisions
6. Any sensible improvements (e.g., corporate onboarding calendar, driver portal)
**Notes**
* Keep legal copy readable; link to T&Cs/Privacy at booking submit (checkbox).
* Use light code only; prefer native Wix features where possible.
* Prior experience with regulated service businesses is a plus. |
