Darby Dental — DSO Implementation Playbook

Executive Summary

Darby Dental operates a multi-location dental services organization (DSO) managing operatory scheduling, staff coordination, and patient flow across independent practices. The DSO model creates unique scheduling complexity: practices maintain autonomy while needing centralized visibility, multiple pay structures exist simultaneously, and patient continuity depends on reliable provider-operatory matching. Implementing a robust scheduling-operations system directly addresses these friction points while enabling the rapid scaling that defines successful DSOs.

DSO practices benefit disproportionately from systemized scheduling because they face the "worst of both worlds"—distributed decision-making with consolidated accountability. A unified approach reduces per-location overhead, enables cross-location coverage, and creates data-driven staffing strategies that independent practices cannot execute. Expected full deployment: 14-16 weeks from kickoff to stabilized multi-location operations.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• Integration audit: Map existing systems (practice management software, payroll, EHR, staffing platforms). Identify required APIs and data synchronization points. Document current data quality issues (duplicate providers, incorrect credentials, mismatched fee schedules).
• Network infrastructure: Confirm bandwidth adequacy at each location (minimum 10 Mbps dedicated for scheduling operations). Test VPN/cloud access protocols.
• Device inventory: Audit front desk computers, tablets, and mobile devices. Establish minimum OS requirements. Plan for 2-3 devices per location for redundancy.
• Data migration readiness: Export historical scheduling data from each location (minimum 12 months). Verify provider license data, credential status, and operatory configurations. Flag missing or conflicting information for manual reconciliation.

Stakeholder Alignment

• Executive buy-in workshop (4 hours): Present DSO-specific ROI (see metrics below). Address ownership concerns about "losing control" by framing centralized operations as autonomy-enhancing (better coverage, reduced admin burden). Secure commitment to executive sponsorship.
• Location manager interviews (1-on-1, 30 min each): Understand current scheduling workflows, pain points, and informal processes. Identify power users and change resisters. Document practice-specific rules (preferred provider assignments, operatory specialization, blocked times).
• Provider survey: Gauge comfort with centralized scheduling, cross-location coverage expectations, and mobile access adoption. This data shapes rollout messaging.
• Establish steering committee: Executive sponsor, DSO operations director, 2-3 location managers, IT representative. Weekly 30-minute check-ins during implementation.

Baseline Metrics to Capture

Establish measurements before any changes:

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose one location exhibiting:

• Moderate complexity: 4-6 operatories, 8-12 providers (enough to stress-test logic, simple enough to recover quickly).
• Leadership openness: Practice manager and 3+ staff actively participate in design. Avoid change-resistant locations.
• Data maturity: Current scheduling system has reasonably clean data. Avoid locations with significant technical debt.
• Visibility: Accessible to project team for on-site support (ideally within 30 miles or enable frequent travel).

Configuration and Setup (Weeks 3-4)

1. Map current state: Spend 3 days on-site documenting:

   • Provider credentials, specialties, pay structures, scheduling preferences
   • Operatory attributes (hygiene/clinical, equipment, treatment type)
   • Recurring patterns (hygiene blocks, reserved slots, implicit rules)
   • Patient scheduling rules (appointment types, default durations)

2. Configure system core:

   • Input all providers with license verification, pay codes, availability windows
   • Define operatory types and time-blocking rules
   • Build appointment type templates (hygiene cleaning = 45 min, exam = 15 min, etc.)
   • Set up multi-level approval rules (front desk books, manager reviews cross-location requests)

3. Run data migration: Load 3 months of historical appointment data. Run reconciliation reports. Validate that recreated schedules match actual booking patterns.

4. Set escalation protocols: Define when scheduling system routes decisions to humans (overbooking, coverage gaps, provider conflicts).

Training Approach (Weeks 4-6)

• Train-the-trainer model: Identify 2-3 front desk power users + practice manager. Run 3-hour intensive workshop (hands-on platform walkthrough, scenario-based exercises, Q&A).

• Role-based modules:

  • Front desk staff (2 hours): Booking, provider availability, operatory selection, patient communication
  • Practice managers (1.5 hours): Override capabilities, scheduling rules, staff assignment, reporting
  • Providers (45 min): Mobile app access, schedule visibility, availability updates, time-off requests
  • DSO operations (2 hours): Cross-location logic, analytics, escalation management

• Shadow period (1-2 weeks): System runs in view-only mode while staff use legacy processes. Operators record feedback. System learns actual booking patterns.

• Go-live: Soft launch on a Monday. DSO operations team on-site or available via video for first 3 days.

• Documentation: Create laminated quick-reference guides at each workstation (booking workflow, common errors, escalation phone numbers).

Scaled Rollout (Weeks 7-16)

Wave Planning

Divide remaining locations into 3-4 waves (4-5 locations per wave):

• Wave 2 (Weeks 7-9): Similar-complexity locations to pilot; repeat proven training/config model
• Wave 3 (Weeks 10-12): Larger or more complex locations; allocate 1.5x configuration time
• Wave 4 (Weeks 13-16): Highest-complexity locations (multiple specialties, dense provider networks); run parallel pilots with Wave 3 lessons applied

Between waves: Conduct retrospectives. Document what worked, refine training, update playbooks.

Change Management

• Weekly all-staff video updates (10 min): Celebrate Wave 1 wins, preview upcoming Wave. Address fears directly.
• Location ambassadors: Designate one staff member per location as "go-to expert." Provide additional training and escalation authority.
• FAQ document (living): Capture real questions during each wave. Share across all locations before next rollout.
• Resistance management: 1-on-1 conversations with slow adopters. Shift framing from "system controls you" to "system removes tedious work, lets you focus on patients."

Support Infrastructure

• Dedicated phone line: Staffed 7 AM–6 PM weekdays during rollout. Route to most knowledgeable person available.
• Weekly office hours: Live video troubleshooting sessions. Recorded and archived for asynchronous access.
• Escalation SLA: Tier 1 (data entry errors): 4 hours. Tier 2 (workflow blocking): 2 hours. Tier 3 (system outage): 30 minutes.
• Peer support network: Create Slack/Teams channel where locations share tips and workarounds.

ROI Tracking

Key Metrics to Measure