ISP dates and staff ratio: the two note items the 12-element list doesn't name
County boards expect a note to show the plan it was delivered under and the staffing it was delivered at. Neither phrase appears in the rule — here is what the rule does say, and where each requirement actually bites.
Two items every county form asks for that the rule never names
Ask a county board of developmental disabilities what a homemaker/personal care note must show, and two items come up that are nowhere in the 12-element list of OAC 5123-9-30(E): the dates of the individual service plan the service was delivered under, and the staff-to-individual ratio it was delivered at.
Both expectations are real. Neither is phrased the way providers repeat it. The plan dates live in the rule as a service-delivery condition, not a documentation element, and the ratio lives in the payment-standards paragraph, not the documentation paragraph. A provider who copies the 12 items onto a form and stops there will pass the list and still fail the county's review.
This page quotes what each rule paragraph actually says, then shows where each expectation turns into a denial or a recoupment. The distinction matters: one is about whether the service was authorized at all, the other about whether the rate was.
ISP dates: a delivery condition, not a line on the note
The coverage condition is OAC 5123-9-30(D)(1): homemaker/personal care will be provided pursuant to an individual service plan that conforms to the requirements of rule 5123-4-02. The documentation tie is element (E)(10): the note must describe the services delivered that directly relate to the services specified in the approved individual service plan. Approved is the operative word — a note describing a service no approved plan specifies does not validate payment.
The plan itself runs on a twelve-month clock set by the service and support administrator, not the provider. OAC 5123-4-02(K)(4) requires the SSA to review and revise the individual service plan at least once every twelve months, and (J)(2)(b) requires the SSA to verify by signature and date, prior to implementation, that each plan identifies the provider, frequency and funding source for each service.
One honesty note most pages skip: no Ohio rule says the note itself must print the plan's dates. DODD's billing guidance is where the requirement actually bites — a claim is paid only when the service is identified on an approved ISP and recommended through PAWS, and the eMBS error list rejects a claim whose service date is not within the authorized PAWS span.
So why do county forms carry the ISP dates anyway? Because a reviewer holding one page should be able to confirm, without pulling the plan, that the service date falls inside a plan that was in effect. Printing the plan's effective dates on the note is county-board practice that pre-answers the question eMBS error 9 asks. It costs one line and it is what the checklist item means.
This error can mean: the service date entered is not within the authorized PAWS span.
Ohio DODD, eMBS error (9), Billing and Claims
Check one of your own notes against this
Paste a shift note into the audit on the homepage and see every missing required element, with the standard behind each one. No account, no cost. Remove the person's name and Medicaid ID first.
Run a free auditNot ready to paste anything? Read a full audit of one real note — every gap, with the standard behind it.
Staff ratio: the rule prices it, the note shows group size
The phrase staff-to-individual ratio appears exactly once in the HPC rule, and not in the documentation paragraph. OAC 5123-9-30(F)(3), under payment standards, adjusts the payment rate to reflect the number of individuals being served and the number of people providing services: two individuals served by one person bill at 107% of the one-to-one base rate, three at 117%, four or more at 130%.
What the note must contain is element (E)(9): the group size in which the service was provided. On the claim, the same fact travels as a staff size field. DODD's eMBS error list rejects a claim whose staff size is missing or invalid (error 45), whose staff size disagrees with the service code (error 46), or whose staff size exceeds 5 (error 47). As with the unit-limit errors, that list sits behind a portal that does not always load for automated readers; the numbers above match the list as indexed and reproduced in county billing guidance.
The recoupment risk is the mismatch, and it runs in one direction. A service authorized at 1:1 but delivered in a group of 3 pays at a lower apportioned rate; documentation that shows a fuller group than the staff size billed is evidence the rate was richer than the delivery. A note that omits group size makes the delivered staffing impossible to prove either way — which in an audit defaults to the payer's reading.
That is why the checklist item says to record the ratio actually delivered where the service is authorized at a ratio: the note's group size, the claim's staff size and the PAWS authorization have to agree, and the note is the only one of the three the provider writes after the shift.
What to put on the note
Print the plan's effective dates once per person
Not a rule element, but the county form asks for it and it pre-answers eMBS error 9. When the plan is reviewed and the dates change, the form changes with it — a stale plan date is worse than none, because it documents that the writer knew a plan existed and did not check it.
Record the group size every shift
Element (E)(9) is a documentation element, and it is the fact the rate depends on. One individual, two, three, four or more — written, not implied by the narrative.
Make the staffing on the note match the staff size billed
If two staff delivered the service, the note should show it and the claim should carry staff size 2. Where they disagree, the fix is a corrected claim or a corrected note — never a silent one.
Check the note against the plan, not just the shift
The narrative must describe services specified in the approved individual service plan. If the support delivered is not in the plan, the problem is the plan, and the call goes to the SSA before the next shift — not the wording of the note.
Where ClearShift fits
Paste a note into the free audit on our homepage and it flags missing plan dates, missing ratio or group size, and the other elements a county review looks for. It is a documentation check, not legal advice — we do not see your PAWS record.
Questions providers ask
Does Ohio require ISP dates on a shift note?
No rule says the note itself must print the individual service plan's dates. The rules require the service to be provided under an approved, conforming plan (OAC 5123-9-30(D)(1)) and the note to describe services the plan specifies (E)(10); a claim whose service date falls outside the authorized PAWS span is rejected. County boards ask for the plan dates on the form so the reviewer can confirm coverage without pulling the plan.
Does Ohio require the staff-to-individual ratio on service documentation?
The rule's documentation list requires the group size in which the service was provided (OAC 5123-9-30(E)(9)). The staff-to-individual ratio is a payment construct: rates are adjusted by the number of individuals served and staff providing services (OAC 5123-9-30(F)(3)), and on the claim it is a staff size field that must match the service code.
What happens if the note shows a bigger group than the rate billed?
Rates are apportioned by group size — serving more individuals at one staff rate pays less per person than one-to-one service. Documentation showing a fuller group than the staffing billed supports a finding that the rate was richer than the delivery, and the difference can be recouped after the fact.
How often is an individual service plan reviewed in Ohio?
The service and support administrator must review and revise the individual service plan at least once every twelve months, and sooner when needs change, the individual requests it, or services are reduced or terminated (OAC 5123-4-02(K)(4)).
Sources
- OAC 5123-9-30 — homemaker/personal care
- OAC 5123-4-02 — service and support administration
- Ohio DODD — Billing and Claims (PAWS payment conditions)
- Appendix A to OAC 5123-9-30 — billing units, service codes, payment rates
This page summarizes published rules and reports as of September 24, 2026. Requirements differ by state, waiver and service, and rules change. Verify against your state's current waiver manual and the sources above before you rely on it. ClearShift is not legal advice and does not decide what a payer will pay.
Run this week's notes before you bill
One note takes about ten seconds. Paste it, see the gaps and the standard behind each one, and fix the note while it still costs nothing.
Run a free auditNot ready to paste anything? Read a full audit of one real note — every gap, with the standard behind it.