Document text
PROJECT CHARTER
Website launch · approved working draft
Sponsor Jordan Lee Project lead Maya Chen
Start 28 October 2026 Target launch 18 December 2026
Status Charter for approval Decision date 30 October 2026
SITUATION AND PURPOSE
Customers cannot compare the current offer on mobile without contacting sales. The project will publish a clear, accessible product site and a measured enquiry path.
OBJECTIVE
Launch the approved site with product pages, pricing explanation, analytics, accessibility checks, and an owned handover. Success is assessed against the measures below, not by launch date alone.
IN SCOPE OUT OF SCOPE
Product, pricing and contact pages CRM replacement
Mobile and accessibility acceptance New brand identity
Analytics and content handover Paid-media campaign
SUCCESS MEASURES
• Product owner approves every page before release.
• Mobile acceptance passes at 360 px.
• The analytics funnel records consented page views and enquiries.
• Operations receives the runbook and rollback procedure.
MILESTONES AND OWNERS
Milestone Owner Due Exit decision
Scope and content approved Maya 06 Nov Sponsor sign-off
Build accepted Noah 04 Dec Acceptance checklist
Launch readiness Priya 16 Dec Go / no-go
Launch and handover Maya 18 Dec Operations owns runbook
RISKS, ASSUMPTIONS AND CONSTRAINTS
Risk: late content approval compresses acceptance; response: freeze the first release at the approved scope. Assumption: product owners remain available for twice-weekly decisions. Constraint: customer data must not be copied into test environments.
GOVERNANCE
The sponsor approves scope or budget changes. The project lead owns the plan and decision log. Work starts only after charter approval. Next step: assign exactly one Accountable role to each deliverable in the RACI matrix.
Approver Decision Date
Jordan Lee Approved / changes requested
Project charter · working document · Layers