One Practice, Several Sites: Reports That Drive Better Decisions

A second physical therapy location adds more than treatment rooms. It adds another schedule, staffing pattern, referral network, and set of operational decisions. By the third or fourth site, an owner can have plenty of reports but still struggle to answer a simple question: Which location needs help, and what should we change? The problem is often inconsistent definitions rather than missing data. One clinic counts evaluations as new patients; another counts scheduled evaluations, including cancellations. A floating therapist’s visits appear under their home clinic instead of the treatment location. Collections arrive this month for care delivered months earlier. Useful multi-location management starts by making those differences visible. Here is a practical framework for turning site-level data into decisions without flattening the clinical realities of each location. ## 1. Establish the Rules Before Building the Dashboard Create a short reporting dictionary that applies across the practice. Each measure should have a definition, source, owner, reporting period, and location-assignment rule. Start with these foundational fields: - **Service location:** Where the encounter actually occurred. - **Provider home location:** The therapist’s primary assignment, kept separate from service location. - **Episode of care:** A defined treatment course, with consistent opening and closing rules. - **Appointment status:** Standard meanings for completed, canceled, late-canceled, and no-show. - **Reporting date:** Whether a report uses service date, posting date, or payment date. ### Decide how shared activity gets credited Assign completed visits to the service location, even when a therapist floats between clinics. Record staffing hours at the site where the therapist worked. Otherwise, one clinic may appear unusually productive while another absorbs its labor cost. For financial reporting, document how payments, refunds, adjustments, and shared expenses are attributed. Keep centralized billing costs separate from direct clinic expenses unless you have an explicit allocation method. **Launch checklist:** - [ ] Every active location has a unique, consistent identifier. - [ ] Appointment statuses mean the same thing everywhere. - [ ] Staff know how to record cross-site coverage. - [ ] Reports state their date basis and refresh timing. - [ ] Someone owns corrections to misassigned records. ## 2. Build Three Views Instead of One Giant Report Different decisions need different levels of detail. A front-desk supervisor should not have to search an executive financial report to find tomorrow’s scheduling problems. | Reporting view | Primary question | Useful contents | |---|---|---| | Daily operations | What needs attention today? | Open evaluation slots, coverage gaps, unsigned notes, authorization exceptions | | Weekly site review | Where is a workflow breaking down? | Evaluation access, attendance, follow-up scheduling, documentation delays | | Monthly leadership review | Where should resources change? | Capacity trends, episode outcomes, financial performance, staffing costs | Each view should allow a manager to move from an aggregate result to the underlying records, subject to appropriate access permissions. A percentage alone rarely explains a problem. If a clinic’s attendance falls, managers need to see whether the change is concentrated in an appointment type, time block, or scheduling workflow. ## 3. Compare Locations Fairly Raw visit counts are useful for workload planning, but weak as a stand-alone ranking. A clinic with more treatment hours should usually complete more visits. A location treating complex neurological conditions may have different scheduling requirements from a predominantly orthopedic site. Use a small scorecard with explicit denominators: - **Attendance rate:** Completed appointments divided by appointments expected to occur, using a documented cancellation cutoff and excluding clinic-canceled appointments consistently. - **Evaluation access:** Median days from a defined starting event, such as a complete referral, to the first offered evaluation. Track patient-selected delays separately when possible. - **Visits per staffed clinical hour:** Completed visits divided by staffed clinical hours, with consistent rules for meetings, leave, and administrative time. - **Documentation timeliness:** Encounters signed within the practice’s defined timeframe divided by encounters requiring documentation. - **Outcome change:** Change on the same validated measure for comparable patient groups, with the measurement interval and completion rate shown. ### Show context beside performance Include staffing levels, visit mix, payer mix, clinic maturity, and relevant specialty services. Display counts alongside percentages; small samples can swing sharply. **Hypothetical example:** Clinic A completes more visits than Clinic B, but also has substantially more staffed treatment hours. After reviewing visits per staffed hour, leadership finds similar utilization. Clinic B’s actual bottleneck is evaluation availability, so the response is additional evaluation coverage—not pressure to shorten follow-up visits. Avoid turning productivity measures into clinical quotas. Reports should identify questions for review, not dictate visit frequency or discharge decisions. ## 4. Treat Cross-Site Transfers as a Defined Workflow Patients may attend a different location because of work, transportation, or specialty needs. Without a transfer process, the receiving clinic may lack current goals, repeat intake work, or assume authorization information is valid for the new setting. Create a transfer checklist that covers: - [ ] Confirm patient identity and use the existing record rather than creating a duplicate. - [ ] Identify the episode, treating clinician, current goals, and latest signed documentation. - [ ] Verify whether payer requirements permit care at the receiving site and by the receiving provider. - [ ] Confirm authorization dates, remaining visits or units, and any location-specific restrictions. - [ ] Assign responsibility for follow-up scheduling and patient communication. - [ ] Record whether the move is temporary, shared-site care, or a permanent transfer. Do not assume authorization balances reset when a patient changes locations. Where limits apply across an episode or payer authorization, review activity across all relevant sites. Report transfers separately from new patient acquisition. Otherwise, a receiving location can look as though it generated new demand when it actually served an existing patient. ## 5. Make Financial Reports Match the Question A monthly collections total does not describe the financial value of that month’s treatment activity. Payments often relate to earlier service dates, and posting delays can make site comparisons misleading. Use distinct views for distinct purposes: - **Cash view:** Payments and refunds posted during the reporting period. - **Service-period view:** Charges, adjustments, and payments associated with a defined period of care, allowing time for claims to mature. - **Exception view:** Unbilled encounters, unresolved denials, and aging balances assigned to an owner. Reconcile site totals to the practice total before reviewing trends. Investigate unassigned locations, duplicate transactions, and inconsistent adjustments. For shared costs, show both direct site results and results after allocation. A location should not appear to deteriorate simply because leadership changed the formula for distributing central expenses. ## 6. Evaluate Software Through Real Multi-Site Scenarios When evaluating IKON EMR, connect its AI scribe, telemedicine, billing, and patient portal features to specific operational needs rather than treating them as a feature checklist. Ask how AI-assisted drafts move through clinician review and signature. Test how telemedicine encounters are classified in site reports, how billing records retain location attribution, and how portal communication supports patients attending more than one clinic. Confirm which reports are built in and which require configuration or exports. Include HIPAA compliance in the workflow review: examine role-based access, audit logging, access termination, and safeguards for exported reports. Software alone does not make a practice compliant; policies, configuration, workforce training, and appropriate agreements also matter. Use a test scenario involving a floating therapist, a cross-site transfer, and a corrected payment. Follow each record through the reports before relying on the totals. ## 7. Turn Reviews Into Assigned Actions Keep the weekly review focused: identify one meaningful exception, examine the underlying records, choose an action, and assign an owner and review date. **Hypothetical example:** A site has unused follow-up capacity but long waits for evaluations. The manager pilots revised appointment templates, then checks evaluation access, follow-up availability, and staff workload together. Improving one measure should not quietly damage another. Maintain a simple action log: issue, suspected cause, intervention, owner, review date, and result. This prevents the same dashboard discussion from repeating without a decision. ## FAQ ### How many metrics should a multi-location practice track? Start with a small set covering access, attendance, capacity, documentation, outcomes, and finances. Add a metric only when it supports a recurring decision and has a clear owner. ### Should every clinic have identical targets? Use shared definitions, but account for staffing, specialty mix, and clinic maturity when setting targets. Compare each site with its own trend as well as comparable locations. ### How often should leadership review reports? Review immediate exceptions daily, operational trends weekly, and financial and resource decisions monthly. Label incomplete periods and delayed data so managers do not mistake reporting lag for performance changes. The goal is not identical clinics. It is a shared operating language that makes local differences understandable—and gives every location a clear path from reporting to improvement.