What should a DSP handoff include?
The care recipient and date or shift being handed over, according to organizational policy.
Meaningful changes in routines, behavior, communication, participation or support levels.
What support was provided and how the person responded, avoiding interpretations presented as fact.
Upcoming events, appointments or time-sensitive needs that require follow-up.
Outstanding documentation, relevant safety concerns and the person responsible for the next step.
Separate completed care from future tasks
Document what actually happened, with occurrence time and author when required. Keep scheduled activities, medication reminders and pending tasks distinct from completed services.
An overdue reminder does not prove a medication was missed. A scheduled service does not prove that it was delivered. Staff should use the organization's approved primary record for confirmation.
Use a consistent handoff structure
What happened: “At 2:15 PM, Jordan requested a quiet space during the afternoon group activity.”
What support was offered: “Staff assisted Jordan to the designated quiet room.”
What happened next: “Jordan returned to the group after approximately 20 minutes.”
What to follow up: “Offer the quieter activity option at the next group transition and document the outcome.”
Where care software can help
KinNotice's planned handoff model connects relevant daily observations, upcoming events, unresolved items and recipient history. It is intended to reduce searching across notebooks, texts and systems.
Organizations should continue using approved shift communication and safety procedures when documenting handoffs.
Frequently asked questions
Is this a standardized regulatory handoff checklist?
No. It is a practical framework; organizations must apply their own rules, support plans and jurisdiction-specific requirements.
Does KinNotice replace verbal handoff?
No. The goal is to supplement required communication with accessible, accurate records.