TL;DR
Compare urgent-care locations by the service offer, channel evidence, access conditions and encounter states each report actually covers. Keep new-site launch periods, employer activity, repeat encounters and missing source links visible. A group average cannot explain which office needs a message repair, a receiving fix or a different acquisition test.
Choose the comparison before ranking offices
Ask what decision the owner needs to make: move a consumer campaign budget, repair a service destination, assess employer development or investigate low completed encounters. Give that question a defined unit. An office's total encounters may include returning people and employer-directed work that a consumer acquisition campaign was never designed to produce.
Use the same state definitions where the processes truly match. Preserve local differences when they change the meaning of the event. A registration at an office using requests cannot be silently compared with a confirmed appointment at another office.
Do not use opening date, office size or a broad geographic label as a substitute for actual service and access evidence. If a site is still launching a service, show that context instead of treating every difference as an established performance gap.
Build a location-by-channel encounter comparison
Create a row for each actual location, service and channel combination needed for the decision. Leave missing data unavailable. The table is an original report specification, not a claim that any particular system supplies every field.
| Comparison field | Record from actual evidence | Reason it stays visible |
|---|---|---|
| Location and operating stage | Named office; launch, stable offer or material change under your definitions | Separates untested launch conditions from an established offer |
| Service and access state | Verified capability, request route and relevant changes | Shows whether the promoted promise was supportable |
| Channel and buyer type | Paid, organic, documented outreach or unknown; consumer or employer branch | Keeps different buying paths distinct |
| Upstream event | Platform measure with original label and period | Avoids treating discovery as an encounter |
| Received administrative state | Inquiry, registration, confirmed appointment where applicable or unresolved | Locates the handoff actually observed |
| Arrival and encounter state | Clinic-verified arrival and completed event under declared definitions | Prevents requests becoming completed activity |
| Relationship | Group relationship and location-entry status in separate fields under approved rules | A person can be new to this location while already known to the group |
| Financial basis, if used | Matching cohort, actual collections cutoff and agreed cost scope | Keeps financial comparisons interpretable |
| Missing evidence and owner | Unresolved linkage or definition and next permitted action | Prevents unknowns becoming poor performance scores |
Attach report period ___; cohort anchor ___; observation cutoff ___; definition version ___; material service or tracking change ___. Keep each source's period clear rather than implying all rows describe the same population.
Compare discovery with its original platform meaning
Google lets managers download Business Profile performance for multiple locations. Its guidance also says available metrics depend on the business, and the report includes activity from organic results and Google Ads. Google's performance documentation. Keep those boundaries when preparing a location comparison.
Do not label a profile interaction total as organic patient acquisition. Do not turn a missing metric into a confirmed absence of demand. If a location lacks supported reporting, retain the missing-data state and investigate the coverage before ranking it against other offices.
Use the reporting guide to preserve method, dates and limitations. This comparison adds location-specific service support and encounter states so the group does not reallocate spend from a misleading summary.
Diagnose the difference before changing allocation
If an office receives relevant requests but the registration route fails, assign the handoff repair. If it advertises an unsupported service, resolve the offer and promotion. If its employer pipeline contains unresolved commercial discussions, assess that buying process rather than judging consumer conversion from it.
If completed encounters include mostly established relationships under the declared rule, keep that workload visible and review new-relationship acquisition separately. A location receiving a person already known elsewhere in the group should not inflate the group's acquired-person total.
When the available evidence cannot distinguish the cause, make the next task the missing definition or observation. Do not allocate a budget as though an unexplained average proves the problem is demand. Require the agency to identify the supported branch of the decision and its confidence.
Roll up only compatible measures
If you calculate a group proportion, combine the qualifying numerator and denominator from compatible, nonoverlapping rows under the same definition. Resolve duplicated encounters or people across channels and locations inside approved practice systems before adding counts. Mixed-source labels are alternate views of the same event, not extra encounters. If deduplication is unsupported, retain separate series and disclose the limit.
Divide the combined qualifying count by its matching combined denominator. Do not take an unweighted average of location percentages and call it the group's encounter rate. If a qualifying denominator is empty or incompatible, show the limitation rather than constructing a rate. Use the group-level relationship rule for an acquired-person total; summing new-to-location labels does not establish new-to-group acquisition.
Keep service, buyer and operating-stage views available even when a compatible total can be calculated. A valid combined measure can still hide a specific broken destination. The service-by-location guide helps organize the underlying coverage facts.
End the meeting with location and service ___; observed constraint ___; evidence ___; proposed allocation or repair ___; owner ___; acceptance condition ___; next review ___. Use actual costs and authorized amounts if money moves. The table informs a decision; it does not predict another office's future demand.
GetPatients has a commercial interest in healthcare visibility services. Apply the same comparison requirements to its reports and other providers. Keep this operating-location review separate from a prospective new-site launch brief.
Frequently asked questions
Can we still show a group total?
Yes, when the units, periods and definitions are compatible. Preserve the local rows and limitations so the total does not erase the decision the owner needs to make.
Should the location with the lowest encounter count lose budget?
Investigate its supported offer, channel coverage, receiving process and operating context first. The total alone does not identify the useful spending change.
What if locations use different registration systems?
Map each system to supported common states where possible. Keep unmatched states separate and disclose the gap rather than forcing a complete funnel.