Most MDS coordinators can tell you which assessments are due this week. Fewer can tell you, at a glance, which ones are at risk of slipping, who is waiting on a missing piece of documentation, and how often the team lands inside the window versus scrambling on the last day. That gap between "I know what is due" and "I can see what is drifting" is where analytics earns its keep.
This post walks through a weekly MDS timing view that an administrator, DON and MDS coordinator can review together in fifteen minutes.
Why timing deserves its own view
Under PDPM, the assessment is the bridge between the care your team delivers and how the stay is classified for payment. Assessment windows are defined in the MDS 3.0 instructions, and the dates feed everything downstream: case-mix classification, billing, and several quality measures. When an assessment is late or out of sequence, the consequences are rarely dramatic on any single day. They show up later, as billing holds, rework, or a classification that does not reflect what was actually happening with the resident.
A calendar tells you what is due. A timing view tells you how the process is behaving.
What to put on the page
Upcoming assessments by days remaining
List every assessment due in the next 14 days, sorted by the days left in its window. Color the rows simply: comfortable, getting close, and at risk. The point is not to nag; it is to let the coordinator start the week knowing where to point attention.
Completion status, not just due dates
For each upcoming assessment, show which sections are complete and which are waiting on someone. If the therapy section is the usual holdup, the view should make that visible without a meeting to find out.
Trailing on-time rate
Track the share of assessments completed inside their window over the last four to eight weeks. Keep it as a simple trend line rather than a single number. A line that dips every time census spikes tells you something about workload, not about effort.
Days-to-complete distribution
Averages hide the stragglers. Show how many assessments finished early, on the final day, or past the window. If most land on the last day, the process has no buffer, and one sick call can tip it.
Questions the data lets you ask
- Do late assessments cluster around admissions on weekends or holidays?
- Is one discipline or one unit consistently the last section to close?
- Does completion pace change when the coordinator is out, and is there a backup?
- Are changes of therapy or interrupted-stay situations handled with the same discipline as the routine ones?
None of these questions are accusations. They are process questions, and a timing view lets you answer them with a pattern instead of an impression.
Turning the view into a weekly rhythm
A dashboard only changes outcomes when it is attached to a routine. A reasonable cadence looks like this:
- Monday: the MDS coordinator reviews the 14-day list and flags anything at risk.
- Midweek: a brief check-in with nursing and therapy leads on open sections.
- Friday: a look at what closed, what slipped, and why, with one process note recorded for next week.
Keeping a short written note each Friday matters more than it sounds. After two months you will have a record of recurring causes: a section that is chronically late, a unit that needs a reminder, a handoff that fails when a particular role is on leave.
A hypothetical example
Picture a hypothetical 100-bed building where the on-time rate looks fine overall, but the distribution shows that most assessments close on the final day. Nothing is wrong yet, but there is no margin. The team decides to move an internal target up by a day and to have therapy complete its section earlier in the window. Over the next several weeks the "final day" cluster shrinks, and the coordinator reports fewer evening scramble sessions. The change did not require new staff, only visibility and a shared target.
Common pitfalls
- Tracking only misses. If the view shows only late items, people stop looking at it. Show what is going well too.
- Using it to rank individuals. Timing data is about the process. Treat it as a tool for removing obstacles.
- Letting data go stale. A view refreshed monthly is a report. A view refreshed daily is a working tool.
- Ignoring the data source. The timing information already lives in your EHR. The work is in pulling it into one place, not in re-entering it.
Getting started
You do not need a long project. Begin with the 14-day list and the on-time trend, review them weekly, and add more only when the team asks. If you would like to see how assessment timing can be pulled from PointClickCare data into a single view, CarePulse can walk through it with your own numbers in a short demo.