200 Providers, One Screen
The Homefront network has over 200 active providers. Each provider carries a caseload, submits reports on per-client schedules, and is responsible for documenting outcomes that tie directly to state program compliance.
Before the portal, knowing who was on track and who was slipping meant calling, texting, and emailing. No aggregated view existed. If a supervisor wanted to know whether a provider had submitted a report due last Friday, the answer was: call them and find out.
That works at 20 providers. At 200, it is a full-time job.
What the Dashboard Shows
The supervisor view in the Homefront portal surfaces four things per provider:
- Reports due in the next 7 days
- Reports currently overdue
- Active client count
- Last documented session date
None of this is manually entered by supervisors. It derives from the same records providers update every day: session notes, report submissions, client enrollment dates. The dashboard is a read-only projection of the data that already exists.
When a report goes overdue, the row flags. The supervisor does not need to notice that a report was due and then check whether it arrived. The system tracks the schedule and surfaces the gap.
Why This Is Harder Than It Looks
The straightforward version of a report-due dashboard would run off a static schedule. Set report X to be due on the 15th of each month, check who submitted it, show the delta.
First Steps does not work that way. Every client has an IFSP, an individual service plan, and report schedules derive from enrollment dates and service authorization periods, not from a shared calendar. Provider A's client enrolled in February and is on a 90-day cycle. Provider B's client enrolled in June. The same report type, different due dates.
The dashboard generates due-date calculations from case records at query time, not from a separate schedule table someone has to maintain. When a new client enrolls or a service authorization period changes, the schedule adjusts automatically. The supervisor sees the accurate picture without anyone updating a spreadsheet.
What It Replaced
The practical replacement was a combination of: a spreadsheet someone updated by hand, text messages asking providers if they had submitted things, and a general reliance on supervisors knowing their providers well enough to sense when someone was falling behind.
That last one is the hardest to replace, and we did not try to replace it. Supervisors still bring judgment. The dashboard just removes the part where judgment was spent tracking down facts that the system already knows.
The number that matters: the agency went from fragmented manual check-ins to a single screen showing every provider's status. The staff who used to coordinate compliance across 200 providers do that same work without adding headcount as the network grows.
The Pattern
We have seen this in every portal we have built: the hardest part is not the automation. The report reminders we wrote about earlier handle the notifications. The hardest part is giving the people responsible for oversight a view that does not require them to manually assemble it from a dozen places.
When that view exists, problems surface earlier. Earlier is the whole point.