SourceClub
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
SourceClub — Implementation Playbook (DSO)
Executive Summary
SourceClub is a cloud-native scheduling and operations platform purpose-built for multi-location dental service organizations (DSOs), dental groups, and regional practice networks. It consolidates appointment scheduling, hygiene coordination, operatory utilization, and staff assignment across unlimited locations into a single, intelligent system—eliminating the calendar chaos of fragmented Excel sheets, multiple booking platforms, and phone-based coordination.
Why DSOs specifically benefit: DSOs operate under fundamentally different constraints than solo practices. You manage shared resources across locations, align hygiene schedules with doctor availability, balance patient flow across multiple operatories, and coordinate staff shifts that span multiple sites. SourceClub's group-native architecture eliminates the workarounds required to force single-practice software to work at scale.
Expected timeline to full deployment: 12-14 weeks from kickoff to all locations live and stable, with 8-12 weeks to ROI-positive metrics (reduced scheduling gaps, improved chair utilization).
Pre-Implementation Checklist (Weeks 1-2)
Technical Requirements
- Network & Hardware: Verify all practice locations have stable broadband (minimum 10 Mbps). SourceClub runs entirely cloud-based (no servers to install), but staff need reliable access. Identify 1-2 devices per location for primary access (iPad recommended for front desk, desktop for back office).
- Data Export Capability: Work with your current scheduling system vendor (Dentrix, Eaglesoft, Open Dental, etc.) to export clean appointment history for the past 12 months. Include patient contact info, appointment type, duration, provider, and location tags. This becomes your historical baseline.
- User Directory: Compile a complete staff roster with roles (dentist, hygienist, front desk, office manager). Include emails and phone numbers. SourceClub's permission model relies on accurate role assignment.
- Integration Prerequisites: If you use a practice management system (PMS), confirm API access is enabled. SourceClub integrates with major PMS platforms; pre-flight these connections.
Stakeholder Alignment
- Executive Sponsor: Designate a C-level champion (typically COO or DSO President) who owns the outcome and removes blockers.
- Location Leaders: Meet individually with each practice manager/owner. Address concerns head-on: "Will this replace my office manager?" (No—it automates chaos, not jobs). Get written commitment to 90-minute weekly training participation.
- Clinician Buy-In: Schedule 15-minute calls with 3-4 dentists and hygienists. Show how SourceClub eliminates last-minute schedule changes and double-bookings. Clinicians drive adoption; skepticism here kills momentum.
- Governance Committee: Establish a weekly steering committee (8 people max: exec sponsor, implementation lead, IT, 1-2 location managers, 1 clinician, CFO). This group makes policy calls and unblocks issues.
Baseline Metrics to Capture
Document these before SourceClub goes live:
- Scheduling Efficiency: Average time to book an appointment (measure front-desk time-to-slot). Typical DSO baseline: 3-4 minutes per call.
- Chair Utilization: Calculate current operatory utilization by location (total booked minutes ÷ available chair minutes). Typical: 60-70% for established DSOs.
- No-Show Rate: Percentage of scheduled appointments not kept.
- Hygiene-to-Doctor Ratio: Average # of hygiene hours per doctor-hour (target: 1.5:1 for health).
- Staff Overtime: Monthly overtime hours per location.
- Patient Satisfaction: Current NPS or satisfaction score (if available).
Measurement approach: Use SourceClub's built-in reporting to re-measure these at day 30, 60, and 90. Typical DSO results: booking time drops 40-50%, utilization rises 8-12%, no-shows drop 15-25%.
Pilot Wave (Weeks 3-6)
Location Selection Criteria
Choose 2-3 pilot sites (not 1; you need validation across different operational styles):
- Readiness Level: Pick one high-performing location and one struggling with scheduling chaos. Avoid the office in crisis mode.
- Staff Stability: Ensure front-desk team will be present for 4+ weeks during ramp-up. Turnover kills pilots.
- Stakeholder Attitude: Include at least one location manager who is openly enthusiastic and one who is skeptical but open. This balances feedback.
- Size: Mix a 3-4 chair location with a 6+ chair location to test system behavior at different scales.
Configuration and Setup (Week 3)
- Data Migration: SourceClub's onboarding team imports your cleaned PMS export. You'll review for data quality, flag duplicates, and confirm appointment type taxonomy.
- Operatory Mapping: Define each chair's attributes in the pilot locations: chair ID, type (hygiene-capable, surgical), location assignment. This is tedious but critical—garbage in = garbage out in utilization reports.
- Staff Scheduling Rules: Encode scheduling policies: Which hygienists work which days? Which doctors cover which locations? What's the maximum appointment length? SourceClub's rules engine captures this logic so the system respects your operations.
- Patient Communication Template: Configure automated SMS/email confirmations and reminders. This is a quick win—reduces no-shows immediately (10-15% improvement common).
Training Approach (Weeks 4-6)
Role-Based Curriculum: Don't give everyone the same training.
- Front Desk: 90-minute focused session on appointment creation, conflict detection, waitlisting. Practice 10 real booking scenarios.
- Office Managers: 120-minute deep dive on utilization reports, staff scheduling, location analytics.
- Clinicians: 30-minute overview. Show the provider dashboard. Emphasize that it prevents their schedule from getting broken.
Peer Champions: Identify 1-2 staff members per location who are tech-comfortable. Invest an extra 2 hours with them. They become your internal support team.
Live Coaching: During week 5-6, have a SourceClub coach embedded at each pilot location for 2 hours daily. Real-time troubleshooting, process refinement. This is when the system actually improves your workflows.
Weekly Steering Calls: Harvest feedback from pilots. Document blockers and wins. Adjust configuration before scaled rollout.
Scaled Rollout (Weeks 7-16)
Wave Planning
- Wave 1 (Weeks 7-9): 4-6 locations. You've solved configuration issues and have trained peer champions. Leverage pilot learnings.
- Wave 2 (Weeks 10-12): 5-8 locations. Reduced hands-on coaching—rely on peer champions and documentation. SourceClub remains available for critical issues.
- Wave 3 (Weeks 13-16): Remaining locations. Largely self-directed with minimal support.
Principle: Each wave should be 60-70% larger than the previous (not all-at-once). Compressed timeline creates support debt.
Change Management
- Communication Cadence: Weekly 15-minute town halls (or recorded videos). Show wins from earlier waves. Address fear directly: "Yes, your schedule will change—that's the point. You'll have fewer double-bookings."
- Quick Wins Strategy: In first 30 days, prioritize features that solve the most painful problem at each location. If location X hates hygiene coordination chaos, enable hygiene-specific scheduling views first. Don't try to optimize everything simultaneously.
- Resistance Mapping: Identify the 2-3 staff members most likely to resist change. Schedule 1-on-1 conversations before their location goes live. Listen. Often resistance is about fear of job loss or loss of control—address those directly.
Support Infrastructure
- Dedicated Slack Channel: Centralized troubleshooting. SourceClub + your internal IT in one channel. Prevents email silos.
- Weekly Office Hours: 30-minute video call where location teams ask questions. Recorded for async access.
- Knowledge Base: Curate a 15-page runbook of your actual workflows. Screenshot-heavy. Beats generic documentation.
- Escalation SLA: Critical issues (system down, data loss) → 2-hour response. Standard issues
AI-generated implementation guide based on public vendor information. Verify specifics directly with SourceClub.