The Five Most Common Documentation Gaps in Virginia DD Waiver Services

If you operate a DBHDS-licensed residential or in-home service in Virginia, you already know documentation is the difference between getting paid and giving the money back. DMAS audits, DBHDS licensing reviews, and Office of Licensing complaint investigations all turn on the same question: does your paper match your practice?

Across provider files I've worked with under the Building Independence, Family and Individual Supports, and Community Living waivers, the same five gaps show up over and over. None of them are exotic. All of them are fixable. And every one of them has cost providers real money or real licensing exposure.

Here they are, in the order I see them most often.

1. Daily Notes That Don't Connect to the ISP

This is the single most common finding in any record review. A DSP writes a perfectly readable narrative note about what happened during the shift (Sarah ate breakfast, went to her day program, watched TV in the evening), but nothing in that note ties back to a specific desired outcome in the Individual Support Plan.

Under Virginia regulations, residential and in-home support services have to be delivered toward the outcomes documented in the ISP. If your daily notes don't reference those outcomes, you have a billing problem and a quality problem at the same time. An auditor reading the note has no way to know whether the service you billed was the service authorized.

The fix is structural, not stylistic. Your documentation system should make it impossible to close out a shift note without selecting an outcome the service supported and recording what progress (or lack of progress) occurred. If your DSPs are typing free-form notes into a Word template, this gap is almost guaranteed.

2. Service Delivery Details That Don't Hold Up Under Audit

Even when the note connects to an outcome, the service delivery specifics often fall apart. The most frequent issues:

• Times that don't match the schedule of supports.
• Locations that don't match the authorized service (a community engagement note that took place entirely in the home, for example).
• Staff signatures missing or applied in batches days after the service occurred.
• Hours billed that exceed what the schedule of supports permits.

Virginia uses Electronic Visit Verification for many in-home services, which has tightened the time and location piece, but EVV does not solve the alignment problem between the authorized service and the documented activity. A note that records the right time and the right GPS coordinate can still describe the wrong service.

Providers should run a weekly internal check that compares billed units against the schedule of supports, against the actual notes, and against EVV records where applicable. Catching the mismatch internally is much cheaper than having DMAS catch it three years later in a recoupment review.

3. Incident Documentation and CHRIS Reporting Delays

Serious incidents require reporting in CHRIS within strict timeframes, and the documentation chain (initial report, internal investigation, follow-up actions, close-out) has to be complete and contemporaneous. The most common failures:

• Incidents that get reported in CHRIS but never have an internal incident report attached to the individual's file.
• Internal reports that exist but were written days after the fact, with no clear timeline of who knew what when.
• Follow-up actions that are listed but never documented as actually completed.
• Patterns of similar incidents that go unanalyzed, even when they should trigger a formal review.

The Office of Licensing pays close attention to incident documentation during licensing reviews, and a pattern of late or incomplete reporting can land a provider on a corrective action plan very quickly. This is also the area where families and human rights advocates raise complaints, and a thin paper trail makes those complaints much harder to defend against.

4. Staff Training Files With Expired or Missing Documentation

Every DSP working under a DBHDS license has required training that has to be documented, current, and accessible. Orientation, annual refresher training, medication administration certification (where applicable), CPR and first aid, behavior support training, and specific competencies tied to the individuals being supported.

The two recurring problems:

• Certifications that expired and were never renewed, but the staff member kept working shifts during the gap.
• Training records that show completion but no evidence of competency verification, which is the part that actually matters under the regulations.

A DSP being CPR-certified on paper does not satisfy the requirement if there is no record that they were observed performing the skill. The training file should answer two questions for every required competency: when did this person learn it, and how do you know they can do it? Most provider files only answer the first question.

This gap also intersects with billing. If a DSP delivered a service while their required training was lapsed, the units billed during that period are at risk in a recoupment.

5. Quarterly Reviews That Are Templates, Not Reviews

The quarterly review is supposed to be a substantive look at progress toward outcomes, with adjustments to the support plan if the data warrants it. In practice, quarterly reviews are often the most copy-and-pasted document in the entire file. The same language appears across multiple quarters, the same rating appears against every outcome, and there is rarely any quantitative or behavioral data backing the narrative.

A reviewer reading three or four quarterlies in a row should see a story: what was the goal, what did the data show, what changed, what did the team try, what happened next. When all four quarters say the same thing, the most likely explanation is that no one was actually looking at the data, which raises questions about the underlying service delivery.

The cleanest fix is to require that quarterly reviews pull directly from the daily notes and outcome tracking data, rather than being written from memory or from a prior quarter's template. If your documentation system can generate a draft quarterly review from the actual progress data on file, the reviewer's job becomes editing and adding clinical judgment, not creating the entire document from scratch.

The Common Thread

Every one of these gaps comes back to the same root cause: documentation systems that were never designed for the specific regulatory structure of Virginia's DD waivers. Generic case management software, paper binders, and Word templates can all produce documentation that looks reasonable on first glance and falls apart on the second.

The providers who consistently pass licensing reviews and DMAS audits are the ones whose systems make it hard to do the wrong thing and easy to do the right thing:

• Notes that can't be saved without an outcome attached.
• Service delivery records that flag mismatches against the schedule of supports automatically.
• Training files that block scheduling when a certification expires.
• Quarterly reviews that pull from the underlying data instead of from the prior quarter.

Compliance is a system design problem, not a willpower problem. Providers who fix these five gaps spend the years ahead growing the program instead of defending it.

This is exactly what CareHub is built for. Daily notes link directly to PCP outcomes from the active plan, so the service delivered and the outcome billed connect on the same form. Quarterly ISP reviews load each outcome, each risk, and each routine support as a separate documentation block, pre-populated with the goal text and staff supports already in the plan, so reviewers are editing real data instead of writing from a blank page. If you want to see it, start a free 7-day trial at carehub.mydsplife.com. Free data migration is included during the trial.