DELIVERY OBJECTIVE Create a responsive five-page studio website that helps visitors find classes and submit a trial booking request. Increased bookings are the desired business outcome, not a guaranteed delivery result. FACTS AND ASSUMPTIONS Confirmed: five pages, responsive build, class schedule, trial form, analytics, six-week target, Friday reviews, $8,000 budget, two revision rounds. Assumptions: the existing booking system can expose the required schedule and form flow; the client can provide complete pricing and policy information before content production. CLARIFICATION QUESTIONS Which pages are included beyond the homepage and class descriptions? Is the trial form a lead form or a direct booking flow? Which analytics events matter? Who approves final copy and accessibility decisions? DELIVERABLE REGISTER Website shell — acceptance: pages work on agreed browsers and breakpoints — owner: delivery team. Class schedule — acceptance: current schedule is visible and update path is defined — owner: client provides data. Trial form — acceptance: test submission reaches the agreed destination — owner: client provides access. Analytics — acceptance: agreed events fire in a test session — owner: delivery team with client account access. MILESTONE PLAN Week 1: requirements, sitemap, content inventory. Week 2: wireframes and approval. Weeks 3–4: design and copy for agreed pages. Week 5: development, form integration, analytics. Week 6: QA, client review, fixes, launch readiness. The six-week plan depends on timely assets and Friday approvals. RISK REGISTER High: booking-system access delayed; mitigation: validate integration in week 1. High: incomplete pricing or policy information; mitigation: content checklist with a deadline. Medium: two revision rounds exceeded; mitigation: written approval checkpoints. Medium: analytics account permissions; mitigation: confirm access before development. CHANGE CONTROL Requests outside the listed pages, integrations, copy scope, or two revision rounds are recorded separately, estimated, and approved before work starts. A new request can change the launch date or budget. CLIENT-FACING SCOPE SUMMARY We will create a responsive five-page website with class discovery, a trial booking form, and basic analytics within a six-week target, assuming the studio supplies required assets and access on schedule. The project includes two review rounds and excludes custom booking software. OPEN DECISIONS Final sitemap; booking versus lead-form behavior; analytics events; accessibility review owner; launch approval owner.