Real Examples, Real Data

8 Project Charter Examples With Real Budgets, Risk Registers, and SMART Criteria

No competitor has more than 2 filled-in examples. Each example below includes a problem statement with metrics, SMART success criteria, scope boundary tables, risk registers with P x I scoring, and key milestones.

Updated 11 April 2026

Quick Comparison

#ProjectIndustryBudgetDurationFormat
1Customer Support AI Triage SystemSoftware / IT$140K to $180K16 weeksLean
2Website Conversion Rate OptimisationMarketing$55K to $75K12 weeksLean
3Corporate Office RelocationOperations$320K to $400K20 weeksFull PMO
4Invoice Processing AutomationProcess Improvement$28K to $35K10 weeksLean
5Employee Engagement Survey PlatformHR / Research$42K to $55K14 weeksLean
6SAP to Oracle ERP MigrationIT / ERP$1.1M to $1.4M18 monthsFull PMO
7Medication Administration Error ReductionHealthcare$65K to $85K12 weeksLean-to-Mid
8Commercial Building HVAC and Electrical RenovationConstruction$2.2M to $2.8M14 monthsFull PMO
Example 1

Customer Support AI Triage System

Software / IT$140K to $180K16 weeks

Problem Statement

Customer support response time averages 48 hours for enterprise clients, resulting in a 23% churn rate among accounts worth $85K+ annually. The current manual triage process routes 60% of tickets to the wrong team on the first attempt. Over the past 12 months, delayed responses have contributed to the loss of 12 enterprise accounts ($1.02M in annual recurring revenue).

Success Criteria

  • 1.Reduce average first-response time from 48 hours to under 4 hours within 90 days of launch
  • 2.Increase first-contact resolution rate from 38% to 65% by end of quarter 2
  • 3.Reduce enterprise client churn from 23% to under 12% within 6 months of deployment
  • 4.Achieve 85% ticket routing accuracy (up from 40%) within 60 days of launch

Scope Boundaries

In Scope

  • +Build AI-assisted ticket classification and routing for email and portal channels
  • +Integrate with Zendesk API for ticket ingestion and response delivery
  • +Train classification model on 24 months of historical ticket data (42,000 tickets)
  • +Deploy to production with staged rollout (10% > 50% > 100% over 3 weeks)

Out of Scope

  • -Do not build phone or live chat integration (Phase 2, pending Phase 1 results)
  • -Do not replace existing Zendesk platform (integration only, no migration)
  • -Do not automate response generation (classification and routing only)
  • -Do not process tickets from the free-tier customer segment

Risk Register

RiskProbImpactSeverity
Historical ticket data quality insufficient for model trainingMediumHighHigh
Zendesk API rate limits restrict real-time routing during peak hoursLowMediumLow
Enterprise clients reject AI-routed tickets as impersonalMediumMediumModerate

Key Milestones

Week 2

Data audit and model requirements

Week 8

Model training and validation

Week 12

Staged production rollout

Week 16

Full deployment and monitoring

Example 2

Website Conversion Rate Optimisation

Marketing$55K to $75K12 weeks

Problem Statement

The company website converts at 1.2%, half the B2B SaaS industry average of 2.4%. The homepage bounce rate is 72% and the pricing page has a 6-second average time on page (benchmark: 45 seconds). With 85,000 monthly visitors, each 0.1% conversion improvement equals $127K in annual pipeline value at our current deal size ($15K ACV).

Success Criteria

  • 1.Increase homepage-to-signup conversion rate from 1.2% to 3.5% within 6 months
  • 2.Reduce homepage bounce rate from 72% to under 45% within 90 days of launch
  • 3.Increase pricing page average time on page from 6 seconds to 45+ seconds
  • 4.Generate 340 additional qualified leads per month (based on 0.4% conversion lift at current traffic)

Scope Boundaries

In Scope

  • +Redesign homepage with value proposition testing (3 variants)
  • +Redesign pricing page with interactive cost calculator
  • +Redesign signup flow (reduce from 7 fields to 3 fields)
  • +Implement A/B testing framework for ongoing optimisation

Out of Scope

  • -Do not redesign blog, documentation, or help centre pages
  • -Do not modify backend infrastructure or API layer
  • -Do not change pricing model or tier structure (design only)
  • -Do not include paid advertising campaign setup or management

Risk Register

RiskProbImpactSeverity
A/B test sample size insufficient for statistical significance within timelineMediumMediumModerate
Stakeholder disagreement on creative direction delays design approvalHighLowModerate
Signup form reduction causes data quality issues for sales teamLowHighModerate

Key Milestones

Week 3

User research and wireframes

Week 5

Design approval

Week 9

Development and QA

Week 12

Launch and A/B testing

Example 3

Corporate Office Relocation

Operations$320K to $400K20 weeks

Problem Statement

The current office lease expires on 31 March 2027 with no renewal option. The building does not meet updated fire safety codes, requiring $180K in upgrades that the landlord will not fund. Additionally, the office is at 110% capacity with 240 employees in a space designed for 220, resulting in 3 formal HR complaints about working conditions in the past quarter.

Success Criteria

  • 1.Complete move to new premises by 15 March 2027 (2 weeks before lease expiry)
  • 2.Zero business days lost during transition (weekend and evening moves only)
  • 3.New office passes fire safety and occupancy inspection on first attempt
  • 4.Employee satisfaction score for new office above 4.0/5.0 within 30 days of move

Scope Boundaries

In Scope

  • +Negotiate and sign lease for new premises (300+ person capacity)
  • +Plan and execute physical move of all furniture, equipment, and IT infrastructure
  • +Set up network, phone, and security systems at new location
  • +Coordinate with building management for access, loading dock, and elevator scheduling

Out of Scope

  • -Do not purchase new furniture (existing furniture moves unless damaged)
  • -Do not redesign organisational seating plan (HR owns seating assignments)
  • -Do not negotiate lease termination for current premises (Legal owns this)
  • -Do not handle employee commute concerns or remote work policy changes

Risk Register

RiskProbImpactSeverity
New premises construction/fit-out delayed beyond move deadlineMediumHighHigh
IT infrastructure incompatibility with new building wiringLowHighModerate
Key vendor (moving company) unavailable for weekend move windowMediumMediumModerate
Employee resistance to new location increases turnoverLowMediumLow

Key Milestones

Week 4

Lease signed for new premises

Week 8

Fit-out design approved

Week 16

IT infrastructure installed and tested

Week 19

Physical move complete

Week 20

Post-move punch list resolved

Example 4

Invoice Processing Automation

Process Improvement$28K to $35K10 weeks

Problem Statement

The accounts payable team manually processes 1,200 invoices per month, taking an average of 12 minutes per invoice. Error rate is 4.8% (58 invoices/month require rework). Each rework cycle takes 25 minutes and delays payment by 3 to 5 days. Late payment penalties averaged $8,200 per month over the past quarter. Two AP clerks spend 60% of their time on manual data entry.

Success Criteria

  • 1.Reduce average invoice processing time from 12 minutes to under 3 minutes within 60 days
  • 2.Reduce error rate from 4.8% to under 1% within 90 days of deployment
  • 3.Eliminate late payment penalties (target: $0/month, current: $8,200/month)
  • 4.Free 40% of AP clerk time for exception handling and vendor relationship management

Scope Boundaries

In Scope

  • +Deploy OCR-based invoice capture for PDF and email invoices
  • +Integrate with SAP AP module for automated posting
  • +Build exception handling workflow for invoices that fail validation
  • +Train AP team on new system and exception handling process

Out of Scope

  • -Do not automate purchase order matching (Phase 2)
  • -Do not change vendor payment terms or banking relationships
  • -Do not migrate historical invoice data (current system retained as archive)
  • -Do not automate expense reports or employee reimbursements

Risk Register

RiskProbImpactSeverity
OCR accuracy below 95% for handwritten or low-quality scanned invoicesMediumMediumModerate
SAP integration requires custom BAPI developmentLowHighModerate
AP team resistance to workflow changeLowLowLow

Key Milestones

Week 2

Vendor selection and contract

Week 6

OCR configuration and SAP integration

Week 8

User acceptance testing

Week 10

Go-live and monitoring

Example 5

Employee Engagement Survey Platform

HR / Research$42K to $55K14 weeks

Problem Statement

The annual employee engagement survey has a 34% response rate (industry benchmark: 70%). The current process uses a generic SurveyMonkey link sent via mass email, with no department-level reporting. HR cannot identify which teams have low engagement because results are only available in aggregate. Exit interview data shows that 28% of departing employees cite 'feeling unheard' as a top-3 reason for leaving.

Success Criteria

  • 1.Increase survey response rate from 34% to 70%+ for the next annual survey
  • 2.Deliver department-level engagement scores within 48 hours of survey close
  • 3.Achieve 90% manager access rate for their team's results within one week of publication
  • 4.Reduce 'feeling unheard' exit interview citation from 28% to under 15% within 12 months

Scope Boundaries

In Scope

  • +Select and deploy survey platform with department-level analytics
  • +Design survey instrument with 25 validated engagement questions
  • +Build automated reporting dashboards for HR and department managers
  • +Create communication plan and manager training for survey rollout

Out of Scope

  • -Do not conduct pulse surveys (annual survey only for this project)
  • -Do not integrate with HRIS for automated distribution (manual upload acceptable)
  • -Do not redesign the exit interview process (separate HR initiative)
  • -Do not include contractor or vendor engagement in survey scope

Risk Register

RiskProbImpactSeverity
Survey fatigue if questions overlap with recent department surveysMediumMediumModerate
Manager resistance to transparent team-level scoresHighMediumHigh
Data privacy concerns limit question types (GDPR, local regulations)LowHighModerate

Key Milestones

Week 3

Platform selection

Week 7

Survey design and validation

Week 10

Dashboard development

Week 12

Communication plan and manager training

Week 14

Survey launch

Example 6

SAP to Oracle ERP Migration

IT / ERP$1.1M to $1.4M18 months

Problem Statement

The SAP ECC 6.0 system reaches end of mainstream support in December 2027. The company has two options: migrate to SAP S/4HANA ($2.1M estimated) or migrate to Oracle Cloud ERP ($1.2M estimated). The executive committee selected Oracle based on a total cost of ownership analysis. Currently, 340 users across 4 departments (Finance, Supply Chain, HR, Manufacturing) use SAP daily. System downtime averages 14 hours per quarter, costing $45K per incident in lost productivity.

Success Criteria

  • 1.Complete Oracle ERP go-live for all 4 departments by 30 September 2027
  • 2.Migrate 100% of active master data with less than 0.1% data integrity errors
  • 3.Achieve 95% system uptime in the first 90 days post-migration (vs current 98.4%)
  • 4.Train 340 users to proficiency (pass competency assessment) before go-live
  • 5.Maintain business operations with zero unplanned downtime exceeding 4 hours during cutover

Scope Boundaries

In Scope

  • +Migrate Finance, Supply Chain, HR, and Manufacturing modules to Oracle Cloud ERP
  • +Migrate 5 years of transactional data and all active master data records
  • +Configure 12 custom integrations with downstream systems (CRM, WMS, BI platform)
  • +Conduct 3 mock cutovers before production migration
  • +Deliver role-based training for all 340 users across 4 departments

Out of Scope

  • -Do not migrate the legacy Plant Maintenance module (decommission, replace with Oracle Asset Management in Phase 2)
  • -Do not customise Oracle ERP beyond configuration (no custom code; adapt business processes to Oracle standard)
  • -Do not migrate archived data older than 5 years (retain in SAP archive for compliance)
  • -Do not replace the existing CRM system (integration only)

Risk Register

RiskProbImpactSeverity
Data migration errors in financial master data cause reporting discrepanciesMediumHighHigh
Custom integration with WMS requires vendor cooperation that may be delayedHighHighCritical
User adoption below target delays go-live and extends parallel run costsMediumMediumModerate
Oracle licensing cost increase during project timelineLowHighModerate
Key SMEs unavailable for UAT due to business-as-usual prioritiesHighMediumHigh

Key Milestones

Month 3

Requirements and gap analysis

Month 8

System configuration complete

Month 11

Integration testing complete

Month 13

Mock cutover 1

Month 16

User training complete

Month 18

Production go-live

Example 7

Medication Administration Error Reduction

Healthcare$65K to $85K12 weeks

Problem Statement

Medication administration errors on the Medical-Surgical unit average 3.2 per 1,000 patient-days, exceeding the AHRQ benchmark of 1.5. In the past 6 months, 4 errors resulted in extended hospital stays (average 2.3 additional days per incident at $2,800/day). One near-miss involved a wrong-dose event caught by pharmacy review. The unit has 48 beds, 62 nursing staff, and administers approximately 1,400 medication doses per day.

Success Criteria

  • 1.Reduce medication administration errors from 3.2 to under 1.5 per 1,000 patient-days within 90 days
  • 2.Achieve 98% barcode scanning compliance for all medication administrations
  • 3.Reduce near-miss events from 8 per month to under 3 per month
  • 4.Zero wrong-patient medication events in the 6 months following implementation

Scope Boundaries

In Scope

  • +Implement bedside barcode medication verification system on Med-Surg unit
  • +Redesign medication administration workflow to include mandatory double-check for high-alert medications
  • +Train all 62 nursing staff on new workflow and barcode system
  • +Establish daily medication safety huddle and weekly error review process

Out of Scope

  • -Do not extend to ICU, ED, or outpatient units (Med-Surg pilot only)
  • -Do not change pharmacy dispensing processes (focus on administration only)
  • -Do not implement automated dispensing cabinets (separate capital project)
  • -Do not modify the electronic health record medication order entry module

Risk Register

RiskProbImpactSeverity
Nursing staff resistance to barcode scanning adds 2 to 3 minutes per medication passHighMediumHigh
Barcode system downtime forces manual workaround, increasing error riskLowHighModerate
Insufficient Wi-Fi coverage in patient rooms causes scanning failuresMediumMediumModerate

Key Milestones

Week 2

Baseline measurement and workflow analysis

Week 5

System installation and testing

Week 8

Staff training (all shifts)

Week 9

Go-live with daily monitoring

Week 12

90-day outcome measurement

Example 8

Commercial Building HVAC and Electrical Renovation

Construction$2.2M to $2.8M14 months

Problem Statement

Building C (42,000 sq ft, built 1998) failed its annual HVAC inspection for the third consecutive year. The existing system operates at 62% efficiency (industry standard: 85%+), resulting in $14,200/month in excess energy costs. The electrical panel does not meet current NEC code requirements, creating $18K/month in penalty exposure until remediation. The building has 180 occupants across 3 floors.

Success Criteria

  • 1.Pass HVAC and electrical inspections on first attempt post-renovation
  • 2.Achieve 85%+ HVAC efficiency rating (up from 62%) within 30 days of commissioning
  • 3.Complete renovation with zero OSHA recordable safety incidents
  • 4.Reduce building energy costs by 35% within the first full billing cycle post-completion
  • 5.Maintain building occupancy during renovation with no more than 2 floor closures simultaneously

Scope Boundaries

In Scope

  • +Replace HVAC system on all 3 floors including ductwork, handlers, and controls
  • +Upgrade electrical panels, wiring, and distribution to current NEC code
  • +Install building automation system (BAS) for HVAC and lighting control
  • +Fire safety system integration with new HVAC ductwork
  • +Obtain all required permits (mechanical, electrical, fire, occupancy)

Out of Scope

  • -Do not renovate plumbing, elevators, or structural elements
  • -Do not install solar panels or renewable energy systems (separate project)
  • -Do not renovate tenant fit-out spaces (base building systems only)
  • -Do not upgrade fire suppression system (sprinklers current and compliant)

Risk Register

RiskProbImpactSeverity
Permit approval delays push schedule beyond 14-month timelineMediumHighHigh
Concealed asbestos discovered during demolition requires abatementMediumHighHigh
HVAC equipment supply chain delays (lead time currently 12 to 16 weeks)HighMediumHigh
Occupied building renovation disrupts tenant operations beyond acceptable limitsMediumMediumModerate

Key Milestones

Month 2

Permits approved

Month 3

Equipment ordered and lead time confirmed

Month 6

Floor 1 renovation complete

Month 9

Floor 2 renovation complete

Month 12

Floor 3 renovation and BAS commissioning

Month 14

Final inspections and closeout

How to Write Each Section →Build Your Own Charter →Agile Charter Template →Six Sigma Charter →