Evaluation and Documentation
What to know
Evaluation and documentation close the TR process. Evaluation determines whether goals were met and whether services should continue, change, or end. Candidates should know formative evaluation (ongoing monitoring) versus summative evaluation (end-of-service or program outcomes), how to select outcome measures, and how to collect reliable data. Documentation must be timely, objective, confidential, and linked to goals. Common formats include SOAP and DAP notes, progress notes, discharge summaries, and program evaluation reports. Good documentation distinguishes observations from opinions, records client responses and progress, and supports continuity, reimbursement, and quality improvement.
Traps
A common trap is confusing evaluation with assessment; assessment establishes baseline, while evaluation judges progress toward goals. Another is documenting “client enjoyed group” as an outcome without measurable evidence of change. Watch for late entries, subjective judgments presented as fact, missing incident reports, and notes that list activities rather than outcomes. Questions may ask what to document after a session; include attendance or participation only as context, then record response, progress toward objectives, barriers, and plan changes.
Worked rule
Use the “so what changed?” test. If a note says the client attended a cooking group, add what the client did, what skill was targeted, and whether the objective was met. For example: “Client completed two-step recipe with visual cues, initiated sharing ingredients twice, and met the social-interaction objective at 2 of 3 opportunities.” This links documentation to evaluation and avoids activity-only notes.