Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how old open family requests are at week end. The result would describe the request queue. Review the first few notes together before the process expands. The family should know when to expect an answer. The record should show the time and the person who made the decision.
The protocol does not measure whether the request was reasonable. It measures whether it was owned. Ask whether a new reviewer could act on the record without a conversation. Keep the evidence with the record rather than in a separate log. The coordinator should record the client and the visit before the next call.
Population and unit of analysis
Define the population as family requests open on a stated date. The unit is one request, with the family, the issue, the owner, and the promised date recorded. Update the template when the same question appears twice. Keep the boundary visible in the place where the work is assigned. The review should leave one owner and one date. The record should show the time and the person who made the decision.
Link the request to the client so the same request is not counted twice. Name the owner in the same line as the action. Test the rule on one real visit before applying it to the schedule. Review the first few notes together before the process expands. A note that cannot be reproduced is not a control. The coordinator should record the client and the visit before the next call.
Definitions and measures
Define age as the time between the request and the review date. Define ownership as a named owner and a promised response date. Test the rule on one real visit before applying it to the schedule. Ask whether a new reviewer could act on the record without a conversation. The team should test the rule on one real visit before the next shift. The record should show the time and the person who made the decision.
Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it. The team should test the rule on one real visit before the next shift. A note that cannot be reproduced is not a control.
Evidence standard
Use the request record and the message log. A note that says pending without a date is weak evidence. Keep the original note beside the corrected version. Keep the evidence with the record rather than in a separate log. The coordinator should record the client and the visit before the next call. The evidence should stay with the visit record.
Record the date and the channel. Ask whether a new reviewer could act on the record without a conversation. Keep the evidence with the record rather than in a separate log. A short note with four fields is easier to use than a long narrative. The record should show the time and the person who made the decision. The team should test the rule on one real visit before the next shift.
Sampling and collection
Use a census of the open requests. If sampling is necessary, stratify by client and issue. Record the exception and the person who approved it. Ask whether a new reviewer could act on the record without a conversation. The record should show the time and the person who made the decision. The review should leave one owner and one date.
Pilot the review on a few requests and compare the reviewers. Clarify how a request with multiple issues is treated. Test the rule on one real visit before applying it to the schedule. Ask whether a new reviewer could act on the record without a conversation. The review should leave one owner and one date. The evidence should stay with the visit record.
Analysis and reporting
Report the age distribution and the ownership rate. Show the requests without a promised date. Record the exception and the person who approved it. Use the same format for every handover so the next reader can scan it. The evidence should stay with the visit record. The team should test the rule on one real visit before the next shift.
Present the results as a description of the queue, not a judgment about the family. Test the rule on one real visit before applying it to the schedule. Update the template when the same question appears twice. Record the exception and the person who approved it. The evidence should stay with the visit record. The coordinator should record the client and the visit before the next call.
Limits and sources of error
The request may be recorded in a different system. State the systems included. A control that depends on memory is not yet a control. Review the first few notes together before the process expands. The evidence should stay with the visit record. The record should show the time and the person who made the decision.
The family may have called back. Record the contact. Name the owner in the same line as the action. Use the same format for every handover so the next reader can scan it. The coordinator should record the client and the visit before the next call. The team should test the rule on one real visit before the next shift.
Review cadence
Repeat the review after a process change or at the same interval each month. Compare the same issue types. Ask whether a new reviewer could act on the record without a conversation. Name the owner in the same line as the action. The review should leave one owner and one date. The caregiver should see the confirmed schedule before the visit.
Assign the follow-up to the operations lead and set a date. The protocol should produce a specific decision about the family request process. Use the same format for every handover so the next reader can scan it. Record the date and the source so the next reviewer can repeat the check. The evidence should stay with the visit record. The family should know when to expect an answer.
