A New Jersey home-care agency

The engagement · chapter 09 · in production

The run

Twelve weeks in production, measured as document 07 promised: the same four numbers, weekly, against the audit’s baseline. The stop rule stayed armed.

Before & after

Audit baseline (documents 02–03) vs. weeks 9–12 in production.

MetricBeforeAfterChange
Office hands-on per weekly cycle24 h 15 m5 h 00 m−79%
Week ends → reviewed, official, filed8 days · worst 162 business daysevery week since cutover
Packets in by the Sunday deadline74%97%+23 pts
Returned for correction15 a week, by phone tag3 a week, in-app−80%
Unbillable overrun hours~19 a quarter0 — blocked at entry−100%
The forms-platform bill$5,000 a month$0 — canceled at cutoverrun cost $1,350/mo
$6,100 a month back — 19 office hours a week + the platform swap 45 of 45 workers active by week 3 0 password resets — there are no passwords state-review records: under an hour — was three days

In line with the audit’s ≈ $73,000/year at the agency’s rates. The state-review find (document 06’s P2) mostly dissolved without ever being its own build.

Returns, converging

Share of packets returned for correction, by week. Every recurring return reason became a rule or onboarding fix the following Monday.

11% → 4.3% of packets returned — week 1 → week 1221% before the build
10% 5% 0% 11% · W1 4.3% · W12 W1W6W12

Before the build, 21% of packets came back — by phone tag. Reminders were tuned in week 4; steady state from week 8. Not zero now, on purpose: a stretch with no returns at all triggers a sampled re-review (document 05’s over-trust control).

The audit trail — one Monday morning, exactly as recorded

Every action with its actor and time; append-only, exportable, the agency’s property. Three entries as the log renders them:

08:02:11deadline · week 2026-W3468 of 70 packets in; 2 overdue named on the Monday view; reminders had gone out Saturday 10:00 and Sunday 17:00prepared
09:26:47review · worker 19 / participant 03Returned — Thursday’s outcome note missing; the reason delivered to the worker’s app, correction due before approvalreturned · named
09:41:03approval · worker 31 / participant 09Approved; official PDF generated (state revision 2025-11); filed to /participants/participant-09/2026/W34; pay & billing rows stagedhuman release

What the agency owns

The workflow is the agency's

Slate runs as the agency’s own workspace: its official form, its rules in plain language, no per-form or per-user fees. The $1,000/month agreement buys four hours of support and changes — not permission to use its own system.

The files were never anywhere else

Every official PDF lands in the agency’s own SharePoint, exactly where the old ones lived — the cabinet the state reviewer sees is simply always current now.

The data walks with them

Exports any day; access revocable in one place; the workspace isolated to the agency in its own Azure tenancy, under a business-associate agreement.

The stop rule never fired

Armed from cutover per document 07. The numbers held; had they not, the roadmap would have stopped with the agency keeping the audit, the rules, and its data.

Prepared by /analog · part of the home-care case study.
open daily · 24/7 · +1 (786) 370-9416 · hello@slashanalog.com · privacy notice