WEBSITE BOOKING HANDOVER
UpOnUp | https://uponup.com/guides/add-booking-to-business-website/

Download and edit a copy in your own document or text editor.
Use this plan with any website provider. Nothing is submitted to UpOnUp.
Leave unanswered points marked "To confirm".
Record business arrangements and public links. Do not include passwords,
account recovery details, payment credentials or customer records.

Business:
To confirm
Plan date and version:
To confirm
Person or role approving the arrangements:
To confirm

1. WHAT CAN THE CUSTOMER ARRANGE?

Services, appointments, stays or other bookings the website should support:
To confirm

Which services can be booked immediately?
To confirm

Which need a consultation, assessment or team approval first?
To confirm

At what point is the time, place or resource actually reserved?
To confirm

Website button wording:
To confirm

Message after a request is received:
To confirm

Confirmation after a booking is completed:
To confirm

A preferred date is not a reserved appointment.
Use wording that matches the actual process.

2. CURRENT PROVIDER AND WEBSITE CONNECTION

Booking provider and public booking page:
To confirm

Proposed connection:
[ ] Link to the existing provider
[ ] Supported tool embedded in the website
[ ] New system or integration requiring separate assessment
[ ] To confirm

Which supported method does the provider document? Add the documentation link:
To confirm

Account, plan or permission requirements to check with the provider:
To confirm

Charges, limits or setup work to confirm before agreeing the connection:
To confirm

For an embed, who maintains the connection and checks changes?
To confirm

Alternative contact route if the booking tool cannot load or complete:
To confirm

3. SERVICE, STAFF, LOCATION AND CAPACITY

Services and any direct public booking links:
To confirm

Staff or teams available for each service:
To confirm

Locations, addresses and the correct destination for each booking route:
To confirm

Rooms, equipment, tables or other resources that limit capacity:
To confirm

Which system controls availability and checks for clashes?
To confirm

Who updates availability, opening hours, closed dates and service changes?
To confirm

Any timing rules to check: duration, preparation time, minimum notice,
time zone or other business requirements:
To confirm

Choices the customer will still need to make after leaving the website:
To confirm

4. PAYMENT, CHANGES AND RESPONSIBILITY

Is payment or a deposit required? Which provider handles it, and when?
To confirm

Where can the customer find the approved price and payment conditions?
To confirm

Who handles payment questions, cancellations, changes and refund queries?
To confirm

Public change/cancellation route and approved policy:
To confirm

Who checks requests and replies? Who covers their absence?
To confirm

Response commitment, only if the business can reliably keep it:
To confirm

Who keeps the website and provider information consistent?
To confirm

5. BEFORE LAUNCH

Agree testing with the receiving team and use the provider's supported
test method. If a test could reserve real capacity or take payment, agree
the arrangements first. Keep customer records out of this planning sheet.

For each check, record the test date, page address, result and any issue.

Correct service, person and location:
Date / page / result / issue:
To confirm

Available and unavailable times; closed days; required resources:
Date / page / result / issue:
To confirm

Time zone, where it matters:
Date / page / result / issue:
To confirm

Request message matches the actual request record and reply process:
Date / page / result / issue:
To confirm

Completed booking matches the provider record and customer confirmation:
Date / page / result / issue:
To confirm

Approved payment/deposit and cancellation information is easy to find:
Date / page / result / issue:
To confirm

Changing or cancelling follows the agreed process; original booking checked:
Date / page / result / issue:
To confirm

Phone and keyboard journey from service page through confirmation:
Date / page / result / issue:
To confirm

Failure or unavailable-tool route gives the customer a useful next step:
Date / page / result / issue:
To confirm

Outstanding fixes and responsible role:
To confirm

Business approval of the wording and arrangements:
To confirm

NEXT STEP

Use the plan to agree the website connection and responsibilities before
commissioning the work. An existing booking link, a supported embed and
new booking software are different scopes. Confirm the provider's current
features and terms rather than assuming a capability is included.

Wider website brief:
https://uponup.com/guides/website-design-brief/

Request form planning:
https://uponup.com/guides/quote-request-form/

Website launch checklist:
https://uponup.com/guides/website-launch-checklist/