The audit · document 07 of 07
Roadmap & measurement
The build order with written acceptance criteria, who does what, and the four numbers that prove the claim — or disprove it. The audit is the deliverable; everything below was a separate decision.
Recommended next move
Proceed with the build — option B, the purpose-built workflow. The arithmetic in document 03, the comparison in document 04, and the owner’s recorded requirement — own the workflow, end the dependency — all point the same way. No build is a valid outcome of an audit, and renting cheaper was priced to the end; here, the measured numbers justified building.
The plan, on one line
Entry & review core
workers enter, packets check themselves, the office reviews — beside the old way, nothing official yet
Official form, filing, exports
the parallel run — accepted when a full week needs zero re-keying and the PDF matches field for field
The recorded finds
training paperwork, rollover hours — own audits first; the AI layer only after its compliance gate
The build order
Each phase is accepted by the agency's own people against a written criterion — not by demo.
Phase 1 · Entry & review core
Passwordless sign-in, the week entered in 15-minute steps during visits, self-checks at submission, the review queue with in-app returns. Runs beside the old way: workers enter their real weeks, the office reviews them — but the official record still comes from the old process.
Phase 2 · The official form, filing, exports — and the parallel run
The official PDF engine pinned to the state layout, SharePoint filing by participant and week, pay & billing exports, deadline reminders, the workforce view. Two weeks of parallel run: both systems produce the week, and the outputs are compared line by line.
Phase 3 · Approved out-of-scope items
Training paperwork, rollover hours, review-prep binders — each starts with its own map entry and its own proposal. The AI assist layer sits behind an additional gate: the agency’s compliance review, in writing. Nothing here is committed by this document.
Who does what
| The agency | The builder |
|---|---|
| Approves each phase against its written criterion — and owns every approval, every day. Names the official form's current revision and confirms it; one hour a week of the coordinator's time during the build; the office runs the parallel-run comparison. | Does not advance a phase until its criterion is met in writing. Builds inside the agency's own tenancy, runs the parallel run, reports the comparison numbers weekly, fixes what the office flags. Does not touch the platform contract until acceptance. |
How we prove it — four numbers, checked weekly
Pulled from the system's own logs every week and compared with what the audit measured (document 02). If the numbers don't improve, everyone sees it.
open daily · 24/7 · +1 (786) 370-9416 · hello@slashanalog.com · privacy notice