If you ask clinical supervisors at most behavioral health agencies whether their staff are on top of unsigned documentation, most will tell you yes. The alerts are there, staff can see them, and everyone knows they are supposed to act on them.
What they may not realize is that the alert system has quietly stopped being functional.
How It Happens
CareLogic generates unsigned document alerts automatically, which is genuinely useful. The gap is on the administrator side: there is no standard report that gives an administrator a clean, filterable view of every unsigned document across the organization. System administrators do have a tool in the CS Tools menu that shows the full volume of unsigned documents system-wide, but it shows limited identifying information. It is useful for gauging how big the problem is, and much less useful for actually working through the list.
Because of that visibility gap, backlogs grow quietly:
A clinician leaves, and their unsigned documents stay in the system.
A form gets retired, but the existing unsigned instances remain active.
Documents created in error, duplicated by mistake, or never completed keep generating alerts indefinitely.
The specifics here are CareLogic, but the pattern shows up in nearly every EHR: alerts that never get retired, backlogs nobody can easily see, and staff who learn to tune them out.
The Alert Noise Problem
Over time, staff inboxes fill up. A clinician with 200 unsigned document alerts has no practical way to tell the ones that matter from the ones that have been sitting there since 2021. So they do what anyone would do: they stop treating the alerts as actionable.
The alert system that was designed to protect documentation integrity becomes invisible wallpaper. That is not a staff discipline problem. It is a predictable response to a system that stopped giving people a usable signal.
The downstream effects are real. Valid unsigned documentation goes unaddressed. Compliance risk accumulates. And when a supervisor asks whether documentation is current, the honest answer, that nobody actually knows, is not one most agencies are prepared to give.
How to Dig Out
Getting out of this situation takes two things working together.
First, a report that lets you work the list. You need unsigned documents surfaced with enough identifying detail to act on: document type, author, client, date, and program. Without that, the cleanup can't get past estimating the size of the problem.
Second, a systematic cleanup that sorts every document into the right bucket:
Documents that need to be signed. These are legitimate, and someone with the right access needs to complete them.
Documents that need to be voided. These were created in error, duplicated, or belong to forms and situations that no longer apply.
Documents that point to a configuration problem. These are generating alerts that should never have existed, and fixing them at the source stops the problem from refilling.
The cleanup is real work. But once it is done, the alert system works again, and staff start trusting it.
Where This Fits
This is the quiet kind of drift we described in Decisions That Made Sense Three Years Ago: nothing was ever broken, the system just kept running while the organization around it changed. It also has the same shape as The Report Everyone Runs and No One Trusts. In both cases, a signal people once relied on slowly loses their trust.
If you're not sure how many unsigned documents are sitting in your system, or whether anyone could tell you, that is worth finding out before an audit finds out for you. We offer a complimentary EHR strategy call as a starting point. No obligation, just a conversation about where things stand.