Documentation and Reporting

Documentation supports continuity of care, clinical decisions, supervision, legal and payer requirements, and accountability. Records must truthfully represent what occurred. A polished note is not useful if it omits significant events or contains invented values. Complete documentation within the required time frame. Delayed notes rely on memory and increase the risk of error. Keep raw data available so summaries and graphs can be checked.

Describe what a person did, said, or produced. Include measurable details such as count, duration, percentage, prompts, or task steps when relevant. Avoid labels such as lazy, manipulative, noncompliant, or had a bad attitude unless a term is operationally defined in the plan. Separate direct observation from reports. Write “caregiver reported two hours of sleep” rather than presenting the information as something you observed.

A routine note commonly includes relevant context, goals or procedures implemented, measurable performance, prompt levels, reinforcement, significant behavior, health or safety events, environmental changes, and communications. Follow the employer’s format and include only information relevant to services. Do not diagnose, recommend treatment changes outside scope, or fill notes with personal opinion. Avoid copy-and-paste language that inaccurately repeats events from another day.

Report significant new behavior, sudden increases or decreases, injury, illness, medication changes, sleep concerns, environmental disruptions, suspected abuse or neglect, and procedural barriers according to policy. Some matters require immediate contact rather than waiting for the next supervision meeting. When a family requests a clinical change, listen and relay the concern accurately. Do not promise a new intervention or give advice outside the current plan.

Incident reports should identify observable events, timing, location, people notified, procedures used, injury or property impact, first aid or medical care, and follow-up required. Use neutral language and avoid assigning blame. Routine notes and incident forms may both be required. Confidentiality does not mean omitting an event; it means documenting it through secure, authorized systems.

Store paper and electronic records only in approved locations. Use individual credentials, lock screens, protect devices, and transmit information through authorized secure channels. Share only with people who are permitted and need the information. Do not place identifiable client information into unapproved AI tools, personal email, social media, consumer messaging apps, or public cloud storage. A missing name does not guarantee that a person cannot be identified from context.

Correct errors through the approved amendment process. Do not erase an audit trail, use another person’s login, or alter raw data to make it match a graph. If the graph and source sheet differ, preserve both, report the discrepancy, and reconcile them transparently. Missing data should be marked as missing, not zero. Zero communicates that observation occurred and the behavior did not.

A useful handoff is concise, factual, and limited to what the next authorized team member needs for continuity and safety. Report pending follow-up, current risks, changes in reinforcer value, and important contextual variables. When instructions are unclear, request clarification before implementation. Document meaningful procedural deviations and supervision contacts as required.