Curve Dental — Implementation Playbook (DSO)

Curve Dental Implementation Playbook for DSOs

A Strategic Deployment Guide for Multi-Location Dental Organizations

---

1. Executive Summary

What Curve Dental Does

Curve Dental is a cloud-native practice management system that centralizes scheduling, charting, imaging, billing, and reporting across unlimited locations through a single, unified platform. Unlike legacy server-based PMS solutions, Curve operates entirely in the cloud, eliminating per-location infrastructure while providing real-time data aggregation and standardized workflows across your entire portfolio.

Why DSOs Benefit from Cloud-Based Practice Management at Scale

DSOs face a fundamental challenge: achieving operational consistency across dozens of locations while legacy PMS systems create data silos, version fragmentation, and IT maintenance burdens at every site. Curve Dental addresses these pain points directly:

• Centralized Data Aggregation: Every location feeds into a single database, enabling true enterprise-level reporting without manual data consolidation
• Standardization at Scale: Configure workflows, templates, and protocols once and deploy across all locations instantly
• Reduced IT Overhead: Zero server maintenance per location eliminates the need for on-site IT support and reduces hardware refresh cycles
• Real-Time Visibility: Leadership can access any location's performance data, patient records, or operational metrics instantly from anywhere
• Simplified M&A Integration: New acquisitions can be onboarded to your standard platform rapidly versus maintaining multiple legacy systems

Expected Timeline: Decision to Full Deployment

DSO Size	Pilot Wave	Full Deployment	Total Timeline
15–25 Locations	4–6 weeks	16–20 weeks	5–6 months
26–40 Locations	4–6 weeks	20–28 weeks	6–8 months
41–50 Locations	6–8 weeks	28–36 weeks	8–10 months

Note: Timeline assumes dedicated project management resources and typical integration complexity. Aggressive timelines are possible with additional resources.

---

2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Network Infrastructure (Per Location)

☐ Minimum 50 Mbps download / 10 Mbps upload dedicated internet connection
☐ Business-class ISP with SLA guaranteeing 99.9% uptime
☐ Secondary/failover internet connection recommended for high-volume locations
☐ Network latency under 100ms to Curve data centers
☐ Firewall configured to allow HTTPS traffic (port 443) to Curve domains
☐ Wi-Fi coverage in all operatories if using tablets/mobile devices

Hardware Requirements

☐ Workstations: Windows 10/11 or macOS 12+ with minimum 8GB RAM, modern browser (Chrome/Edge recommended)
☐ Monitors: Minimum 1920x1080 resolution; dual monitors recommended for clinical workstations
☐ Peripherals: USB or Bluetooth barcode scanners for patient check-in (optional)
☐ Tablets: iPad (9th gen or newer) or Android tablets with 10"+ screens for chairside use

Imaging System Compatibility

☐ Verify sensor/phosphor plate compatibility with Curve Imaging module
☐ Panoramic unit integration requirements (TWAIN driver or direct integration)
☐ CBCT integration via third-party viewers or DICOM compatibility
☐ Intraoral camera compatibility checklist

⚠️ Common Failure Point: Older imaging sensors may require driver updates or may not be compatible with Curve's cloud imaging. Audit all imaging hardware at every location before proceeding.

Vendor Onboarding Steps

🔵 Week 1: Kick-Off Activities

Day	Activity	Duration	Curve Contact
Day 1	Enterprise sales-to-implementation handoff call	1 hour	Implementation Manager
Day 2	Sign BAA and Master Services Agreement	N/A	Contracts team
Day 3	Receive enterprise admin portal credentials	N/A	Technical Account Manager
Day 4	Technical discovery call — review all locations' current tech stack	2 hours	Solutions Engineer
Day 5	Integration requirements meeting — PMS migration, imaging, clearinghouse	2 hours	Integration Specialist

🔵 Key Contacts to Establish ☐ Dedicated Technical Account Manager (TAM) — your primary escalation point
☐ Implementation Project Manager — owns timeline and milestones
☐ Integration Specialist — handles data migration and third-party connections
☐ Enterprise Support Line — dedicated phone/email for DSO-level issues
☐ Executive Sponsor (Curve side) — for escalations requiring commercial decisions

Data/Access Prerequisites

Per Location

☐ Export full patient database from current PMS in compatible format (consult Curve migration guide)
☐ Export all clinical notes, treatment history, and ledger data
☐ Export all X-ray images in standard formats (JPEG, PNG, DICOM)
☐ Document all procedure codes, fee schedules, and custom codes currently in use
☐ List all active insurance contracts and payer IDs
☐ Export provider NPIs, licenses, and credentialing documentation

Enterprise Level

☐ Inventory all current PMS systems and versions across portfolio
☐ Compile all clearinghouse relationships and submitter IDs
☐ Document all current IT vendors with contact information
☐ Identify any locations with unique compliance requirements (state-specific regulations)

⚠️ Common Failure Point: Data exports from legacy systems often have formatting issues or missing fields. Run a test export from one location early and submit to Curve for validation before mass extraction.

Enterprise-Level Requirements

Network Standards Across Locations

🟣 Executive Decision Required: Standardize network specifications across all locations

Specification	Minimum Standard	Recommended Standard
Primary Internet	50 Mbps down / 10 Mbps up	100 Mbps down / 25 Mbps up
Failover Internet	None	25 Mbps cellular/secondary ISP
Router/Firewall	Business-grade (Cisco Meraki, Ubiquiti, etc.)	Managed SD-WAN solution
Wi-Fi Standard	Wi-Fi 5 (802.11ac)	Wi-Fi 6 (802.11ax)

Hosting Model

Curve Dental is fully cloud-hosted — no decision required on centralized vs. location-level hosting. All data resides in Curve's SOC 2 Type II certified data centers.

SSO and Identity Management

🔵 ☐ Confirm Curve supports your identity provider (Okta, Azure AD, Google Workspace)
🔵 ☐ Provide SAML metadata to Curve integration team
☐ Define user provisioning workflow — manual vs. automated via SCIM
☐ Establish role hierarchy and permission templates

Centralized Credentialing

☐ Create master provider database with all NPIs, license numbers, and state credentials
☐ Define process for ongoing credential updates to flow to Curve
☐ Assign ownership of provider records (central credentialing team vs. local office managers)

Internal Stakeholder Alignment

Stakeholder Alignment Map

Stakeholder Level	Role	Communication Need	Approval Required For
Board/Investors	Oversight	Quarterly progress updates, ROI projections	Capital expenditure approval, timeline extensions
C-Suite (CEO, CFO, COO)	Sponsors	Weekly status, risk escalations, milestone sign-offs	Vendor contract, wave progression, budget allocation
Chief Dental Officer	Clinical Champion	Workflow design input, clinical protocol approval	Clinical template standardization, provider training approach
VP of Operations	Program Owner	Daily/weekly program management	Go/no-go decisions, resource allocation
IT Director/CISO	Technical Lead	Integration details, security review	Technical architecture, security compliance
Regional Managers	Regional Owners	Wave planning, location readiness, staff communication	Location pilot selection, escalation decisions
Office Managers	Local Leads	Training schedules, workflow changes, go-live prep	Staff training completion, local process adjustments
Providers	End Users	Clinical workflow changes, training	N/A (consultation, not approval)

Communication Cadence During Pre-Implementation

Audience	Frequency	Format	Owner
C-Suite	Weekly	15-min standup or email summary	VP of Operations
Regional Managers	Weekly	30-min video call	Program Manager
Office Managers (pilot locations)	Twice weekly	Email + office hours call	Implementation Lead
All Staff	Once (kick-off)	Town hall / video announcement	CEO or CDO

Baseline Metrics Capture

⚠️ Critical: Establish standardized measurement methodology BEFORE any implementation activities begin. Inconsistent measurement across locations will invalidate ROI calculations.

Required Baseline Metrics (Capture Across All Locations)

Metric Category	Specific Metric	Measurement Method	Capture Period
Scheduling Efficiency	Chair utilization rate	(Scheduled appointment hours) / (Available chair hours)	30-day average
Scheduling Efficiency	No-show rate	(No-shows) / (Total scheduled appointments)	30-day average
Scheduling Efficiency	Average days to next available hygiene appointment	Manual sampling	Point-in-time
Revenue Cycle	Days in A/R	Total A/R / Average daily production	Point-in-time
Revenue Cycle	Claim denial rate	(Denied claims) / (Total claims submitted)	30-day average
Revenue Cycle	Time from service to claim submission	Average days	30-day average
Clinical Efficiency	Average appointment duration by procedure type	Actual vs. scheduled time	30-day sample
Clinical Efficiency	Treatment acceptance rate	(Accepted treatment $) / (Presented treatment $)	30-day average
Staff Productivity	Collections per FTE	Total collections / Total FTEs	Monthly
Patient Experience	NPS or satisfaction score (if tracked)	Existing survey data	Most recent quarter
IT Operations	System downtime hours	Logged outages	Prior 90 days
IT Operations	Help desk tickets related to PMS	Ticket system data	Prior 90 days

Standardization Protocol

🟣 Executive Decision Required: Approve standardized metric definitions

☐ Create written definitions document for each metric with exact calculation methodology
☐ Identify single data source for each metric (avoid letting locations use different methods)
☐ Assign central analytics team member to collect/validate all baseline data
☐ Store baseline data in centralized repository accessible to leadership
☐ Deadline: Complete all baseline captures before Wave 1 pilot begins

---

3. Location Readiness Assessment

Scoring Framework

Rate each location on a 1–5 scale for each factor. Sum scores for composite readiness score (maximum 25 points).

Factor 1: IT Infrastructure Maturity

Score	Criteria
1	Unreliable internet (frequent outages), outdated computers (5+ years), running deprecated PMS version
2	Internet occasionally unstable, mixed-age hardware, PMS version 1-2 years behind current
3	Stable internet meeting minimum specs, hardware 3-4 years old, current PMS version
4	Business-class internet with failover, hardware 2-3 years old, all imaging equipment compatible
5	Enterprise-grade network with SD-WAN, hardware <2 years old, full imaging integration confirmed

Factor 2: Staff Tenure and Adaptability

Score	Criteria
1	Turnover >50% annually, staff openly resistant to technology, no prior system changes
2	Turnover 30–50%, mixed comfort with technology, difficult past software transitions
3	Turnover 15–30%, average tech adoption, previous transitions went adequately
4	Turnover <15%, majority comfortable with technology, smooth past transitions
5	Stable team, enthusiastic about technology, have successfully adopted new tools recently

Factor 3: Patient Volume

Score	Criteria	Guidance
1	<800 patients/month	Low impact, but also low learning opportunity
2	800–1,200 patients/month	Moderate volume
3	1,200–1,600 patients/month	Balanced risk/impact — ideal for pilots
4	1,600–2,000 patients/month	High impact but manageable
5	>2,000 patients/month	Highest impact but highest risk for pilots

Note: For pilot wave selection, score 3 is optimal. For later waves, higher scores indicate priority.

Factor 4: Existing Tech Stack Compatibility

Score	Criteria
1	Custom/niche PMS with no migration path, incompatible imaging, unique integrations
2	Uncommon PMS requiring significant manual migration, some imaging compatibility issues
3	Common PMS (Dentrix, Eaglesoft, Open Dental) with standard migration path, most imaging works
4	Common PMS with proven migration history, all imaging compatible, standard clearinghouse
5	Already on another cloud PMS, all equipment modern and compatible, clean data

Factor 5: Local Champion Availability

Score	Criteria
1	No one willing to lead adoption, active resistance from key staff
2	No strong champion, but no active resistance
3	Office manager willing but not tech-savvy, or tech-savvy person without influence
4	Engaged office manager with good technology comfort and team influence
5	Strong, respected champion (provider or manager) who actively wants to lead adoption

Readiness Scoring Template

Location	IT Infrastructure (1-5)	Staff Adaptability (1-5)	Patient Volume (1-5)*	Tech Stack (1-5)	Local Champion (1-5)	Composite Score
Location A						/25
Location B						/25
Location C						/25
Continue for all locations

For patient volume, adjust scoring based on wave: Pilots prefer score of 3; later waves prioritize 4-5.

Recommended Rollout Sequence Based on Scores

Composite Score	Rollout Wave	Rationale
20–25	Wave 1 (Pilot)	High readiness reduces pilot risk; success here builds organizational confidence
15–19	Wave 2	Solid readiness; benefit from pilot learnings
10–14	Wave 3	Requires additional preparation; use time during earlier waves to remediate gaps
Below 10	Wave 4 / Remediation Required	Do not deploy until specific readiness gaps are addressed

Readiness Remediation Actions

Gap Identified	Remediation Action	Typical Timeline
Internet reliability	Upgrade ISP, install failover	2–4 weeks
Outdated hardware	Hardware refresh	2–6 weeks
Staff resistance	Change management intervention, leadership visit	2–3 weeks
No local champion	Assign regional manager as interim champion, or delay until staffing change	1–4 weeks
Incompatible equipment	Replace or find workaround, engage Curve integration team	Variable

---

4. Rollout Strategy

Wave Structure Recommendation

For a DSO with 15–50 locations, implement in 3–4 waves:

Wave	Locations	Duration	Cumulative Timeline
Wave 1: Pilot	2–3 locations	4–6 weeks	Weeks 1–6
Buffer period	—	2 weeks (learning capture)	Weeks 7–8
Wave 2: Early Majority	5–8 locations	4–6 weeks	Weeks 9–14
Buffer period	—	1–2 weeks	Weeks 15–16
Wave 3: Scale	8–12 locations	4–6 weeks	Weeks 17–22
Wave 4: Remainder	Remaining locations	4–6 weeks	Weeks 23–28+

Adjust wave sizes based on internal project management capacity. Each active location requires approximately 4–8 hours of central team support during go-live week.

Wave 1 Pilot Location Selection Criteria

🟣 Executive Decision Required: Final pilot location approval

Select 2–3 locations that meet ALL of the following criteria:

Criterion	Rationale
Composite readiness score 20+	Minimize pilot risk
Patient volume in 1,200–1,600 range	Enough activity to stress-test system without excessive risk
Geographic proximity to central team OR strong local champion	Enables high-touch support during pilot
Representative of portfolio mix	Include at least one GP location and one specialty (if applicable)
Regional manager actively engaged	Regional leadership buy-in is critical for pilot success
No major staffing changes planned	Avoid locations with pending office manager departures, etc.

Recommended Pilot Configuration:

• 2 general practice locations in different regions (tests regional variation)
• 1 higher-complexity location (specialty mix, larger team, or higher volume) if readiness supports it

Timeline Per Wave

Week	Activities
Week 1	Technical setup, integrations, test environment, staff notification
Week 2	Staff training, parallel run begins, data migration finalization
Week 3	Go-live, intensive support, daily check-ins
Week 4	Stabilization, issue resolution, workflow refinement
Weeks 5–6	Optimization, feedback collection, documentation of learnings

Go/No-Go Criteria for Wave Progression

Criteria to Advance to Next Wave

🟣 Executive Decision Required: Wave progression approval

Category	Criteria	Threshold
System Stability	No critical system outages in past 2 weeks	100%
Data Integrity	All migrated patient records verified accessible and accurate	99%+
Staff Proficiency	All staff completed training and passed competency check	100%
Workflow Completion	Core workflows (scheduling, charting, billing) functioning without workarounds	100%
Revenue Cycle	Claims submitting successfully	95%+ clean claim rate
Patient Impact	No patient safety incidents related to system	0 incidents
Staff Sentiment	Champion confirms team is ready for central support to decrease	Yes
Learnings Documented	Pilot learnings captured and incorporated into Wave 2 materials	Completed

Red Flags That Delay Wave Progression

⚠️ Any of the following triggers an automatic hold:

• Critical functionality not working (e.g., cannot submit claims, cannot access images)
• Data migration errors affecting >1% of patient records
• Staff attrition >10% at pilot locations during implementation
• Provider refusing to use system
• Patient complaints related to system disruption

Rollback Plan

Triggers for Rollback Decision

🟣 Executive Decision Required: Rollback authorization

Trigger	Response
System unavailable >4 hours during business hours	Escalate to Curve executive sponsor, evaluate rollback
Critical data loss or corruption	Immediate rollback, engage Curve incident response
Regulatory/compliance concern identified	Pause deployment, legal review
Wave-wide staff rejection (>50% refusing to use)	Pause, conduct change management intervention before deciding

Rollback Procedure

1. Announce pause to all affected locations (same-day communication)
2. Revert to legacy PMS — requires legacy system still accessible
   • ☐ Verify legacy system backups current before each wave go-live
   • ☐ Maintain legacy system access for minimum 30 days post go-live
3. Isolate failing wave — continue operations at already-successful locations
4. Root cause analysis within 48 hours
5. Remediation plan before re-attempting failed wave
6. Executive communication within 24 hours of rollback decision

⚠️ Common Failure Point: Organizations often decommission legacy systems too quickly. Maintain parallel access for 30 days minimum.

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration & Data Migration

Migration from Dentrix

🔵 Curve involvement required

Step	Action	Duration	Owner
1	🔵 Request Dentrix Data Extraction Guide from Curve	Day 1	Implementation Lead
2	Install Curve Data Extraction utility on Dentrix server	1–2 hours per location	Local IT / Office Manager
3	Run full database extraction	2–8 hours depending on database size	After hours recommended
4	🔵 Upload extraction to Curve secure transfer portal	1–2 hours	Implementation Lead
5	🔵 Curve performs data mapping and transformation	5–7 business days	Curve Migration Team
6	Receive migration preview report — review for accuracy	1–2 days	Office Manager + Billing Lead
7	⚠️ Validate sample patient records (minimum 25 per location)	2–4 hours	Clinical staff
8	🔵 Approve migration and schedule final import	Same day	Implementation Lead
9	🔵 Final data import (performed after hours)	4–12 hours	Curve
10	Post-migration validation	2–4 hours	Office Manager

Migration from Eaglesoft

🔵 Curve involvement required

Step	Action	Duration	Owner
1	🔵 Obtain Eaglesoft Export Template from Curve	Day 1	Implementation Lead
2	Verify Eaglesoft version compatibility	30 min	Local IT
3	Run Eaglesoft backup and export utility	2–6 hours	After hours
4	🔵 Submit export files via secure transfer	1 hour	Implementation Lead
5	🔵 Curve data mapping	5–7 business days	Curve
6	⚠️ Validate financial ledger accuracy (critical for A/R)	2–4 hours	Billing Lead
7	🔵 Final import	4–12 hours	Curve

Migration from Open Dental

🔵 Curve involvement required

Step	Action	Duration	Owner
1	Generate Open Dental database export (MySQL)	1–2 hours	Local IT or managed IT vendor
2	🔵 Submit to Curve via secure portal	1 hour	Implementation Lead
3	🔵 Curve performs direct database migration	3–5 business days (faster than other PMS)	Curve
4	Validation	2 hours	Office Manager

⚠️ Common Failure Point: Appointment history and clinical notes are the most common migration issues. Always validate a sample of historical appointments and past treatment notes.

Imaging System Integration

Curve Imaging Module Setup

Step	Action	Duration	Owner
1	Inventory all imaging hardware per location	1 hour per location	Office Manager
2	🔵 Submit hardware inventory to Curve for compatibility check	2 days	Implementation Lead
3	🔵 Receive compatibility report with any required driver updates	Curve
4	Install/update TWAIN drivers on all imaging workstations	1–2 hours per workstation	Local IT
5	Configure Curve Imaging bridge settings	30 min per workstation	Local IT
6	⚠️ Test image capture from every sensor/camera at every workstation	1 hour per location	Clinical staff
7	Configure image acquisition defaults (exposure settings, auto-enhance)	30 min	Provider

Historical Image Migration

Step	Action	Duration	Owner
1	Locate all image storage directories from legacy system	1–2 hours per location	Local IT
2	🔵 Request Curve Image Migration Tool	Day 1	Implementation Lead
3	Run image export/tagging utility	4–12 hours (run overnight)	Local IT
4	🔵 Upload to Curve for ingestion	Variable	Curve
5	⚠️ Validate image linking — confirm images appear in correct patient charts	2–4 hours	Clinical staff

⚠️ Common Failure Point: Images often export without proper patient linking. Curve's migration tool handles most cases, but orphaned images require manual review.

Test Environment Setup

🔵 Curve involvement required

Central Test Environment (Recommended for DSOs)

☐ 🔵 Request dedicated DSO sandbox environment from Curve
☐ Populate sandbox with migrated data from 1–2 pilot locations
☐ Create test user accounts for central team and pilot champions
☐ Configure all enterprise settings (SSO, roles, templates) in sandbox first
☐ Run full workflow test scenarios:

Test Scenario	Validating	Pass Criteria
New patient registration	Demographics flow, insurance verification	Patient record created correctly
Appointment scheduling	Schedule template, operatory assignment	Appointment appears on schedule
Clinical charting	Odontogram, perio charting, notes	All clinical data saves and displays
Image capture	Imaging bridge, sensor compatibility	Image captured and linked to patient
Treatment planning	Procedure codes, fee schedules	Treatment plan displays with accurate fees
Claim submission	Clearinghouse connection, claim format	Claim accepted by clearinghouse
Payment posting	Ledger accuracy, adjustment codes	Ledger balances correctly
Reporting	Standard reports, filters	Reports generate with expected data

☐ Document all issues discovered and resolution
☐ Sign off on test environment before production migration

Security and HIPAA Compliance

Enterprise-Level HIPAA Checklist

🟣 Executive Decision Required: Security architecture approval

Requirement	Action	Owner	Verification
Business Associate Agreement	🔵 ☐ Execute BAA with Curve	Legal	Signed document on file
SOC 2 Type II	🔵 ☐ Obtain current SOC 2 report from Curve	Compliance	Review for any exceptions
Data Encryption	☐ Confirm encryption at rest and in transit (AES-256, TLS 1.2+)	Security	Curve documentation
Access Controls	☐ Define role-based access matrix	Operations	Documented and approved
User Provisioning	☐ Establish onboarding/offboarding procedures	HR/IT	Written SOP
Audit Logging	☐ Confirm audit trail capabilities and retention	Compliance	Test and document
Breach Notification	🔵 ☐ Confirm Curve's breach notification procedures align with your requirements	Legal	Documented in BAA
Data Governance	🟣 ☐ Define data ownership and retention policies	C-Suite	Board-approved policy
Backup & Recovery	🔵 ☐ Confirm Curve backup frequency and RTO/RPO	IT	Document in system inventory

Standardized vs. Location-Specific Configuration

Standardized Configuration Template (Apply Across All Locations)

Configuration Area	Standard Setting	Rationale
Procedure codes	Use centralized code list; CDT codes only, no custom codes	Enables enterprise reporting consistency
Fee schedules	Master fee schedule with regional adjustments via percentage	Simplifies updates, enables benchmarking
Appointment types	Standardized list of appointment types and colors	Consistent scheduling experience
Clinical templates	Standard note templates by procedure category	Quality and compliance consistency
User roles	Defined role hierarchy with standard permission sets	Security and audit compliance
Report templates	Enterprise report package available to all locations	Consistent KPIs
Claim submission	Single clearinghouse relationship where possible	Simplified revenue cycle management
Treatment plan templates	Standard presentation format	Patient experience consistency

Location-Specific Configuration (Allow Local Discretion)

Configuration Area	Local Discretion Allowed	Guardrails
Provider schedules	Hours of operation, provider availability	Must map to standard appointment types
Operatory names	Local naming conventions	Must follow standard naming format
Fee schedule adjustments	+/- 15% adjustment to master fees	Must be approved by regional manager
Specialty procedures	Specialty-specific codes and templates	Must use standard CDT codes as base
Local insurance contracts	Location-specific payer fee schedules	Must integrate with centralized A/R reporting
Staff schedules	Individual staff working hours	N/A

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location requires one certified Local Champion. Selection criteria:

Criterion	Requirement
Role	Office Manager (preferred) or senior clinical staff member
Tenure	Minimum 1 year at location
Tech Comfort	Demonstrates proficiency with current systems
Influence	Respected by team, able to drive adoption
Availability	Can commit 4–6 hours during implementation, ongoing 1–2 hours/week
Communication	Strong verbal skills to deliver training

Champion Responsibilities

Phase	Responsibility	Time Commitment
Pre-Implementation	Complete champion certification training	4–6 hours
Pre-Implementation	Gather location-specific configuration needs	2 hours
Training Week	Deliver role-specific training to all staff	6–8 hours
Go-Live Week	Serve as first-line support for all staff questions	4–6 hours
Post Go-Live	Ongoing support, train new hires, report issues	1–2 hours/week

🔵 Champion Certification Training (Delivered by Curve)

• Format: Virtual live training, 2 sessions × 2 hours each
• Assessment: Must pass proficiency quiz (80%+ score)
• Materials: Champion toolkit including training slides, quick reference guides, FAQ document

Standardized Training Materials

Created Centrally (By Corporate/Curve)

☐ Role-specific training slide decks (branded with DSO identity)
☐ Quick reference guides (one-pagers per role)
☐ Video library of core workflows (5–10 minutes each)
☐ FAQ document updated after each wave
☐ Go-live day checklist for champions