research

How long do family requests wait for an answer for the quarter-start review

A practical protocol for measuring family request response time at quarter start, including the exceptions that should pause the clock.

Staffing Care Home Editorial TeamPublished 11 min read
How long do family requests wait for an answer for the quarter-start review
On this page8 sections

How long do family requests wait for an answer for the quarter-start review: research question and scope

This review asks how long a family request waits between the first documented contact and the first documented answer. The scope covers requests received during the first two weeks of the quarter, when new care plans and schedules create a burst of questions. It includes scheduling questions, care plan questions, and requests for information about a visit. It excludes complaints that are handled through a formal grievance process, unless the same request also appears in the family log.

The start event is the first recorded contact from the family, not the date the coordinator opened the file. The stop event is the first documented answer to the specific question, not a general callback. If the family asks a follow-up question, that is a new request with its own start event. Fixing those boundaries before collection prevents the average from drifting toward the easiest cases.

Population and unit of analysis

The population is every family request logged for an active resident during the window. The unit is one request, even when the same family contacts the agency several times about the same topic. If a request is reopened because the first answer did not resolve it, count the reopening as a separate unit and link it to the original. That link lets the review show both the first response time and the time to a final answer.

Stratify by channel, request type, and whether the request needed a care manager. A phone request may be logged later than an email, and a clinical question may wait for a different reviewer. The family request routine describes the fields that should be present. Use those fields to decide whether a request is in scope before measuring the time.

Definitions and measures

The primary measure is the elapsed time from the start event to the stop event, reported in hours for requests answered within a day and in days for longer requests. A request answered within the promised window is on time; a request answered after the window is late. If no response date was promised, use the agency's written standard. Do not invent a standard after seeing the data, because that makes the result impossible to compare.

Secondary measures include the share of requests with no named responder, the share that required escalation, and the share that were reopened. Report the number of requests that were closed without a documented answer, because a closed item is not necessarily an answered item. Each measure needs a denominator and the review window. A count without a denominator can make a small team look better or worse than it is.

Evidence standard

The evidence is the request entry plus the response entry. The request entry should show the date, channel, family contact, and the question. The response entry should show the date, the responder, the channel, and a short note of what was said. A status change from "open" to "closed" is not evidence of an answer. If the response was given by phone, the note should record the call and the person who made it.

The reviewer should distinguish an answer from an acknowledgment. "We received your request" is not the stop event. A request that was acknowledged and then forgotten should remain open for measurement. The family request response study shows why this distinction changes the result. Use the same rule for every request in the sample.

Sampling and collection

Sample from the family request log, not from the coordinator's inbox. Export the log at a fixed time each day so the open and closed states are comparable. Capture the request text, the promised date, the responder, the response date, and any linked care record. If the log does not store history, take a daily snapshot and note the limitation. A single end-of-quarter export may lose the intermediate states that explain a delay.

Include a mix of routine questions, care plan questions, and requests that required escalation. Add a small comparison group of requests that were answered on the same day. The comparison shows what a healthy response looks like in the same period. Record the collection date and the person who pulled the data, so a later reviewer can reproduce the sample.

Analysis and reporting

Report the median and the range, not just the average. A few very old requests can pull the average up and make the routine look worse than it is. The median shows the typical wait, while the range shows the outliers that need attention. Report the share answered within the promised window and the share still open at the end of the review.

Break the results down by request type and by responder role. If clinical questions wait longer than scheduling questions, that may be appropriate because they need a different reviewer. The report should say whether the delay is a queue problem or a decision problem. The incident log review is relevant when a family request is tied to a safety event. Do not combine the two measures without explaining the difference.

Limits and sources of error

The review measures documented response time, not family satisfaction. A fast answer can be wrong, and a slower answer can be thorough. The log may also miss requests that were handled in person or through a channel that was never recorded. If those channels are common, the measured time will overstate the formal process and understate the real workload.

Other limits include requests that were logged after the fact, responses that were given but not recorded, and family members who contacted more than one person. Use a consistent rule for duplicate contacts and state it in the report. If the sample is drawn from one agency or one service line, do not present it as an industry benchmark. The result describes the evidence in that setting.

Review cadence

Review response time monthly during the quarter and repeat the full method at the next quarter start. The monthly check can use a smaller sample and focus on the requests that missed the promised date. The quarter-start review should keep the same definitions so the comparison is meaningful. If the definition changes, preserve the old result and label the new rule.

Assign the review to a named role and set a follow-up date for any recommended change. The follow-up should confirm whether the log fields, the responder list, or the escalation path actually changed. A report that is filed without a follow-up is only a description of the past. The goal is a family request process that answers the question once, clearly, and within the window the agency promised.

Sources

<- Back to research