BUMPERLOOM PRACTICE HANDOFF — FICTIONAL EXAMPLE

This package contains a standalone Clean Ride demonstration website. Prices,
areas, illustrations and business details are fictional. It is not a live car
cleaning business or a completed customer delivery.

FILES
- website-upload.zip: index.html at the archive root; use this for static upload.
- index.html: the same standalone website, suitable for opening locally.
- REVISION-LOG.csv: two blank revision rounds plus approval and handoff records.
- DELIVERY-CHECKLIST.txt: what to confirm before accepting and delivering work.

PRACTICE PUBLICATION
1. Use a separate practice project in the owner's Cloudflare account. Do not
   overwrite the Bumperloom sales Worker. Select static file/ZIP upload and
   upload website-upload.zip. Follow the current upload controls in Cloudflare.
2. Open the resulting HTTPS URL. Confirm layout on phone and desktop and test
   package buttons, required inputs and the downloaded sample quote.
3. The quote builder only downloads a text file. No inquiry is sent. This
   package intentionally removes Bumperloom's owner-test email form.
4. Record results in DELIVERY-CHECKLIST.txt. Keep failed or untested items open.

ACTUAL CUSTOMER DELIVERY
Replace all fictional text, photos, prices and demo notices with owner-approved
material. Agree on pages and content before work. Connect a real customer-owned
inbox or booking destination and verify successful delivery. Publish only to
the customer's own hosting project with agreed delegated access. The customer
owns and pays for the domain/hosting. Never exchange passwords in the brief.

REVISIONS
Round 1: collect one consolidated feedback batch on the agreed scope, apply it,
and record the preview URL and what changed.
Round 2: collect the second consolidated batch and record completion.
Get explicit final approval separately. New pages or features beyond the agreed
scope require a separate agreement. The blank log is a manual tool, not an
automated customer-stage tracking system.

HANDOFF
Give the customer site files, instructions, account ownership/access records,
billing responsibility and the agreed support/maintenance terms. Confirm the
customer can access and update their site without relying on your password.
Keep evidence of tests and approval. Do not claim handoff complete until the
customer confirms access and the live form/booking path works.
