Most organizations say they coordinate care; fewer can prove it under scrutiny. When utilization is high or a serious incident occurs, commissioners and system partners ask concrete questions: Did you request the discharge information? When did you receive it? Who did you share it with? Did partners acknowledge it? Was the medication list reconciled and implemented? In complex care, the difference between confidence and concern is the evidence trail. This guide sits within Care Coordination, Data Sharing & Information Governance and relies on Complex Care Service Design because KPIs only matter when workflows and ownership exist. The focus here is a practical audit and measurement framework that demonstrates coordination performance without creating perverse incentives.
Why coordination measurement often misleads
Many providers measure the wrong thing: number of calls made, number of emails sent, or “documentation completed.” Those are activity metrics, not coordination reliability metrics. Others measure only outcomes (ED visits) without measuring the coordination mechanics that drive them (reconciliation timeliness, plan update propagation, partner acknowledgments). Measurement also fails when it punishes transparency. If staff believe metrics are used for blame, they will under-document problems and the organization loses its early warning system.
A credible framework pairs leading indicators (process reliability) with lagging indicators (harm, crisis use) and includes assurance checks (sampling audits) that validate that records reflect reality.
Two oversight expectations you must design to meet
Expectation 1: Funders and commissioners expect demonstrable coordination capability and improvement
In many publicly funded environments, oversight increasingly expects providers to show a quality improvement posture: defined measures, regular review cycles, targeted corrective actions, and re-measurement. For complex care, coordination is a cost and safety driver; payers want evidence that providers can manage transitions, reduce avoidable escalation, and coordinate with system partners reliably.
A provider that can show coordination KPIs and audit trails is more defensible than one relying on narrative claims.
Expectation 2: Governance expects secure, minimum-necessary disclosures with auditability
Information governance is scrutinized through evidence: disclosure logs, access controls, and documentation that shows why information was shared and what the purpose was. In incident reviews, oversight expects the provider to reconstruct timelines: who knew what, when, and what actions followed. If communications occur through informal channels with no record capture, the provider cannot answer these questions credibly.
Therefore, measurement must include auditability indicators, not just coordination “effort.”
The KPI set: what to measure so it reflects real coordination quality
A practical KPI set typically spans five domains: (1) closed-loop coordination performance, (2) disclosure governance and channel compliance, (3) version control and “single source of truth” reliability, (4) transition and follow-up timeliness, and (5) learning from coordination failures. Keep the set tight enough to review monthly and specific enough to trigger action.
Examples include: percentage of referrals acknowledged within target time; percentage of coordination loops closed within target time; percentage of discharges with documents received within X hours; time to medication reconciliation completion; percentage of plan updates with partner acknowledgment; disclosure logs completed for external sharing; proportion of communications through approved channels; two-shift verification completion after critical changes; and the rate of incidents where “information mismatch” was a contributing factor.
Operational example 1: Monthly loop-closure audit for referrals and follow-ups
What happens in day-to-day delivery. The provider maintains a coordination tracker where every time-critical request becomes a “loop” (discharge documents, DME, specialty referrals, crisis plan distribution). Each loop has a target timeframe and required states: initiated, acknowledged, actioned, confirmed complete. Monthly, the quality lead samples a defined number of loops across programs and checks the evidence: initiation timestamp, acknowledgement record, completion confirmation, and whether escalation occurred when timeframes were missed. Findings are shared with managers, who implement fixes (partner escalation pathways, improved templates, staffing coverage for weekends).
Why the practice exists (failure mode it addresses). The failure mode is open-loop coordination: referrals sent and assumed complete. In complex care, “assumed complete” produces lost follow-ups and crisis bounce-backs. The audit exists to detect loop failures early and force managerial action, not just frontline effort.
What goes wrong if it is absent. Delays become normal, needs remain unmet, and deterioration triggers ED use. When questioned, teams can describe what they tried but cannot evidence closure. Oversight partners interpret this as weak operational control and poor accountability.
What observable outcome it produces. Loop-closure auditing produces higher acknowledgement and completion rates, fewer lost referrals, and reduced avoidable escalation attributable to “no follow-up.” Over time, leaders can evidence improvement cycles: barriers identified, fixes applied, and closure rates rising.
Operational example 2: Secure disclosure and channel compliance sampling to prevent “phantom coordination”
What happens in day-to-day delivery. The provider defines approved channels and a disclosure logging rule: any external sharing that affects care must have a documented disclosure entry (what, to whom, purpose, timestamp). Each month, auditors sample communications linked to high-risk events (discharge, crisis episodes, med changes) and verify that (1) the right minimum-necessary packet was used, (2) the channel was approved, and (3) a disclosure log exists. Where staff used informal routes, leadership investigates why (tool usability, access barriers, unclear rules) and fixes the system, not just the individual.
Why the practice exists (failure mode it addresses). The failure mode is “phantom coordination”—people believe coordination happened because a message was sent somewhere, but it is not captured, traceable, or accessible to future shifts. Channel compliance sampling exists to ensure coordination is durable and auditable, and to prevent drift into personal texting and screenshots.
What goes wrong if it is absent. Informal communication grows, disclosure decisions become untraceable, and the organization cannot reconstruct timelines during incidents. Compliance exposure increases and safety suffers because next shifts cannot access the critical information chain.
What observable outcome it produces. Sampling produces higher record-capture compliance, fewer privacy incidents, and clearer coordination chains in incident reviews. Leaders can demonstrate reduction in “communication gaps” as a contributing factor to avoidable escalations.
Operational example 3: Version-control verification after plan changes and transitions
What happens in day-to-day delivery. The provider treats critical objects (med list/MAR, crisis plan, contact tree) as versioned documents with named owners. After any significant change (discharge, med change, crisis event), the supervisor completes a verification step: confirm the current version is stored in the designated source location, confirm distribution to defined partners (case manager, school/day program where applicable), and record acknowledgments. The quality team samples these events monthly, checking whether older versions remain in circulation and whether staff can access the current version quickly during simulated scenarios.
Why the practice exists (failure mode it addresses). The failure mode is version drift: different settings operate from different plans, leading to inconsistent responses and avoidable escalation. Verification exists to ensure updates propagate and are usable, not just “sent.”
What goes wrong if it is absent. Plans fragment across email attachments and binders, partners act on outdated contact routes, and medication lists diverge. In crises, staff cannot find the current plan quickly and default to EMS. Oversight then identifies continuity failures without evidence of change governance.
What observable outcome it produces. Verification produces higher partner acknowledgment rates, fewer “wrong version” incidents, and improved escalation timeliness because contact routes are current. Providers can evidence improved stability indicators (fewer repeat crises) linked to consistent plan execution.
Assurance: making the framework trustworthy and non-punitive
To keep measurement honest, leaders should pair metrics with learning actions: track not only rates, but also corrective actions and re-measurement outcomes. Use stratification: identify whether failures cluster by shift, partner type, or transition pathway. Publish clear definitions so staff know what is being measured and why. Where KPIs worsen, treat that as a signal to improve systems (tools, coverage, templates), not an excuse to suppress documentation.
When audit and KPI frameworks are well-designed, they become a commissioner-facing asset and an internal safety tool: coordination is no longer “claimed”—it is evidenced, improved, and resilient under scrutiny.