Covered — Implementation Playbook (DSO)

Executive Summary

Covered is a membership-financing platform that enables dental practices to offer direct-pay memberships, recurring revenue contracts, and bundled treatment plans—replacing or supplementing insurance revenue. For Dental Service Organizations (DSOs), Covered solves the critical challenge of revenue predictability across multi-location networks while improving patient access and reducing administrative friction.

DSOs uniquely benefit from Covered because centralized financial systems, standardized workflows, and multi-location data visibility create immediate leverage: a single platform deployment scales across dozens of locations, shared finance and compliance resources accelerate implementation, and aggregated membership data drives network-wide clinical and financial decision-making.

Expected Timeline: 16 weeks from kickoff to full network deployment across initial wave locations; 6–9 months for 80%+ provider adoption across the DSO.

Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

• EHR/Practice Management Integration: Confirm API compatibility with your primary PM system (Dentrix, Eaglesoft, Open Dental, Curve, etc.). Covered requires read/write access to patient demographics, treatment plans, and account balances. Coordinate with your IT/PMO team to provision sandbox environments and confirm firewall/security protocols.

• Payment Processing: Verify merchant account configuration and PCI compliance. Covered supports Stripe, Square, and Authorize.net; confirm which processor is integrated with your PM system today and whether changes are needed.

• Network Infrastructure: Audit bandwidth and latency across all practice locations. Covered runs in the cloud but requires reliable internet; practices with <10 Mbps downloads should remediate before go-live.

• Device Ecosystem: Confirm iPad/tablet availability for checkout (Covered's point-of-sale interface) and staff workstations with modern browsers (Chrome, Safari, Firefox). Older Windows 7 deployments must be upgraded.

Stakeholder Alignment

• Finance & Revenue Cycle Lead: Owns go-live budget, payment reconciliation workflows, and revenue recognition policy. Must sign off on cash flow modeling and KPI targets.

• Clinical Operations Director: Responsible for membership treatment plan standardization and provider training. Secure commitment for 4–6 hours of clinical staff time per location during weeks 3–6.

• Compliance & Legal: Reviews membership agreement templates, state-specific regulations (e.g., insurance parity laws in CA, NY), and data privacy (HIPAA, GDPR if applicable). Allow 2 weeks for template review and sign-off.

• IT/Systems Admin: Manages integration, security configurations, and ongoing technical support. Assign a single point of contact with <2-day response SLA during pilot phase.

Baseline Metrics to Capture

Before any configuration, document:

• Current membership programs (if any): patient count, revenue, pricing, churn rate, NPS
• Insurance mix: % PPO vs. HMO vs. uninsured by location
• Treatment plan capture rate: % of patient visits with documented treatment plans
• Average patient LTV: 24-month revenue per active patient, by location cohort
• Operational overhead: admin hours spent on insurance claims, payment posting, patient financial counseling

These become your pre/post comparison baseline.

Pilot Wave (Weeks 3–6)

Location Selection Criteria

Choose 2–3 geographically diverse pilot locations that represent your network:

• Size: Mix of high-volume (>800 patient visits/month) and moderate (300–500) sites to test scalability and training approaches.
• Readiness: Select practices with engaged owners/managers, stable PM systems, and <3 staff turnover in past 12 months.
• Financial health: Avoid locations in crisis mode; Covered requires management bandwidth.
• Insurance dependency: Prioritize locations with 40%+ uninsured/self-pay patients (higher membership upside) OR practices saturated with PPO/HMO (opportunity to reduce claim friction).
• Patient demographics: Include at least one location with significant Spanish-speaking or international patient base to surface localization gaps early.

Configuration and Setup

Week 3:

1. Master membership plan design (Finance + Clinical leads):

   • Define 2–3 plan tiers: e.g., Essential ($15–25/mo.: exams, X-rays, cleanings), Plus ($35–50/mo.: +fillings/periodontal), Premium ($60–80/mo.: +implant/ortho discounts).
   • Document treatment inclusions, annual maximums, exclusions, and annual fee structure.
   • Confirm pricing strategy with leadership (competitive analysis, margin targets).

2. PM system integration setup (IT lead):

   • Deploy Covered connector in sandbox; test patient sync, transaction logging.
   • Map custom fields (referral source, practice ID, clinician IDs) to ensure accurate attribution.
   • Run 48-hour test sync; validate 100% data accuracy before production toggle.

3. Payment processor configuration (Finance + IT):

   • Enable ACH and card tokenization in your payment gateway.
   • Set up accounting mappings: membership revenue → Chart of Accounts line item; failed payment → AR aging bucket.

Week 4:

4. Staff training cohort 1 (Clinical ops lead):

   • Conduct 2-hour workshop with dentists, hygienists, front desk at pilot locations.
   • Live demo: patient checkout flow, membership enrollment in PM, payment retry logic.
   • Hands-on: staff enroll 5 test patients, process simulated failed payments.
   • Distribute quick-reference cards (laminated): "How to Offer Membership to a Hesitant Patient."

5. Patient communication materials (Marketing):

   • Customize Covered's email/SMS templates with your DSO branding, logo, practice-specific URLs.
   • Design in-office signage (3–4 poster templates for waiting room, treatment area, checkout).
   • Create FAQ one-pager for staff (address top 10 questions: "Can I cancel anytime?" "Is this insurance?" "What if I move?").

Week 5–6:

6. Soft launch (Pilot locations only):

   • Go-live restricted to staff testing and opt-in patients (existing high-value patients, referral sources).
   • Target: 30–50 active memberships per location by end of week 6.
   • Daily standups (15 min): IT, pilot location managers, Covered support. Track: enrollment velocity, payment success rate (target: 95%+), system uptime.

7. Feedback loops:

   • Weekly pulse survey (2 questions): staff ease-of-use, patient reaction to enrollment experience.
   • Shadow a front-desk team member for 2 hours; observe real checkout interactions; note friction points.
   • Finance reconciliation check: manually validate 10 membership payments posted to your accounting system.

Scaled Rollout (Weeks 7–16)

Wave Planning

Wave 2 (Weeks 7–10): Expand to 5–8 locations (mix of demographics/size similar to pilot).

• Apply pilot learnings: streamlined training, pre-configured plans, refined talking points.
• Target: 200–300 total active memberships across wave 2.

Wave 3 (Weeks 11–14): Roll out to remaining core locations (prioritize >$500K annual revenue sites).

• Reduce on-site training to 1.5 hours per location (staff confidence higher); shift to self-guided modules.
• Target: 500–800 active memberships.

Wave 4 (Weeks 15–16): Satellite/smaller locations; optional for low-revenue sites (<$200K/year).

• Fully remote training; leverage wave 3 peer champions.

Change Management

• Designate 1–2 "Membership Champions" per location: staff who complete advanced certification, mentor peers, escalate issues.
• Bi-weekly town halls (30 min, optional): highlight success stories, answer Q&A, preview upcoming features.
• Performance transparency: share practice-level membership KPIs in staff huddles; tie to clinic bonuses (e.g., "$X in membership revenue unlocks team lunch").
• Objection handling playbook: provide scripts for common staff resistance ("This replaces insurance," "Patients will think we're greedy"). Emphasize: "This supplements insurance and helps uninsured patients access care."

Support Infrastructure