Service concerns resolved within ten business days rose from 48% to 83%
At one community-based human-services organization, CARES and organization staff replaced fragmented concern handling with a shared register, named accountability, escalation deadlines, and evidence-based closure.
Routine service concerns reaching documented resolution within ten business days
21 of 44 concerns compared with 43 of 52
The result, with the closure rule attached.
Comparing concerns received in January–March 2025 with those received in July–September 2025, the share reaching documented resolution within ten business days rose from 21 of 44 to 43 of 52.
- What changed
- A concern register, response and escalation matrix, closure-verification checklist, and monthly feedback-to-action review replaced unowned forwarding and inconsistent closure practices.
- What was measured
- The proportion of received routine service concerns reaching documented resolution within ten business days of receipt.
A response could be sent while the concern remained unresolved.
Concerns arrived by telephone, email, and conversations with program staff. Some were forwarded among managers without one accountable person for the final response. Cross-program issues could produce conflicting instructions without anyone correcting the source or confirming the next step with the client.
Satisfaction summaries did not show whether individual concerns had been addressed. Prior training emphasized respectful communication but did not define deadlines, escalation authority, or evidence required before closure. Repeated status inquiries and inconsistent management reports exposed unresolved work.
The team separated reply, corrective action, acknowledgment, and satisfaction.
CARES and the organization’s client-services manager reconstructed 44 baseline concerns from shared-mailbox records, call logs, and supervisor notes. The comparison cohort contained 52 concerns. Each concern involved a different client, and the following rules applied to both cohorts.
- One concern meant dissatisfaction requiring a response or corrective decision. Multiple contacts about the same issue counted once; general questions were excluded.
- Separate pathways handled urgent safety matters and matters requiring formal review rather than counting them as routine concerns.
- Receipt day was day zero. Business days excluded weekends and organizational holidays, and reassignment did not pause the clock.
- Documented resolution required completed corrective action or an explained disposition, delivery of the response, client acknowledgment, and no outstanding review or appeal.
- Acknowledgment did not mean agreement or satisfaction. A concern awaiting client contact remained open even if internal action was complete.
- Follow-up continued for 30 calendar days. Every client received the same five-point survey invitation at day 30 asking, “How satisfied are you with the handling of your concern?” The wording, channels, and seven-day response window were identical in both cohorts.
The organization had intake channels but no shared definition of completed work.
The terms replied, referred to a manager, and resolved were used interchangeably. Authority to make routine corrections was unclear, and managers lacked common issue categories for identifying repeated causes.
CARES separated three questions: Was the response timely? Was the required action complete? Was the client satisfied? Management kept these measures separate rather than combining them into a composite score that would conceal different operating conditions.
Four controls connected receipt, action, response, and verified closure.
- 01
Concern register and classification guide
The register exposed receipt date, accountable manager, next action, deadline, and closure evidence. Sensitive narratives remained in restricted records.
- 02
Response and escalation matrix
Routine concerns required acknowledgment within two business days and resolution within ten. Overdue work escalated without resetting the clock, and authority for routine corrections became explicit.
- 03
Closure-verification checklist
Closure required evidence of action, response delivery, acknowledgment, and no outstanding review. A manager sampled five closures each month.
- 04
Feedback-to-action review
A monthly review connected recurring concern categories to corrective work owned by program teams. CARES facilitated the initial reviews before staff assumed the routine.
Eight staff members completed role-play exercises. A two-week pilot covering nine concerns revealed that a concern could be closed without an acknowledgment date. The team corrected the control before wider use.
Faster closure coincided with fewer repeat status inquiries.
Scroll horizontally or use the arrow keys to compare all measures.
| Measure | Jan–Mar 2025 | Jul–Sep 2025 | Evidence basis |
|---|---|---|---|
| Resolved within 10 business days | 21 of 44 · 48% | 43 of 52 · 83% | Receipt dates, corrective-action records, and acknowledgment logs |
| Resolved within 30 calendar days | 36 of 44 · 82% | 48 of 52 · 92% | Fixed day-30 disposition review |
| Another status inquiry before resolution within 30 days | 19 of 44 · 43% | 10 of 52 · 19% | Contact logs, counted once per concern; improvement is a decrease |
| Satisfied or very satisfied among survey respondents | 13 of 22 · 59% | 26 of 34 · 76% | Five-point post-concern survey |
| Survey response rate | 22 of 44 · 50% | 34 of 52 · 65% | Invitation and response records |
Four comparison-period concerns remained unresolved at day 30. Two were awaiting acknowledgment and were not counted as resolved merely because internal action was complete. Percentages are rounded; comparison-period survey collection ended November 6, 2025.
The satisfaction result cannot represent all clients or the organization as a whole. The samples were small, response rates changed, nonrespondents may have differed, and issue severity was not statistically adjusted. Concern volume rose from 44 to 52; improved capture may have contributed, but the reason for the increase was not established. Baseline reconstruction also could not recover concerns that had never been documented.
Staff described the operating shift as moving from clearing an item after a reply to documenting what changed and whether the client received the response. Higher trust, reduced disengagement, and causal attribution were not demonstrated, and the result was not independently audited.
The test was whether staff could verify closure without CARES managing the queue.
At handoff, the client-services manager became system owner, program managers retained responsibility for resolutions, and the operations director owned escalations and overdue corrective actions. The package included the register specification, classification guide, response matrix, closure checklist, survey instructions, training scenarios, and monthly-review agenda.
Two backup employees demonstrated intake, assignment, escalation, and closure review without CARES operating the process.
Post-handoff record check
9 of 10In November, the manager and a backup checked ten October concerns marked resolved outside the comparison cohort. Nine met every closure requirement. One lacked acknowledgment evidence and was reopened. CARES reviewed the findings but did not conduct client follow-up or manage the queue.
The check supports transfer of the operating controls; it is not a new outcome cohort. Consistent survey participation across language groups remained unfinished, so the organization retained an assisted-response option while it continued that work.
Closure became an evidence gate, not a status label.
This representative structure shows the operating logic without reproducing a client record, internal identifier, or identifying information.
The concern remained open if the instructions had been corrected but the client had not acknowledged the response. Administrative completion and satisfaction remained separate fields so neither could substitute for the other.