Operating record
Scanner output is not a Title II operating record
Scans help find issues, but counties and cities need an auditable operating record that explains scope, ownership, remediation, vendor dependencies, exceptions, and evidence. PublicProof is built around that full record.
Comparison
| Need | Scanner-only output | Operating record |
|---|---|---|
| Scope | Usually focused on pages or URLs that were crawled. | Connects websites, PDFs, forms, mobile surfaces, and vendor systems to public-service workflows. |
| Ownership | Often leaves owners and departments outside the result set. | Assigns internal, vendor, procurement, legal, and ADA review paths. |
| Prioritization | Can over-index on raw issue counts. | Separates severity, service criticality, deadline posture, and owner path. |
| Remediation | Produces issue lists without durable work management. | Tracks tasks, blockers, verification criteria, and vendor dependencies. |
| Evidence | Shows what a tool detected at a point in time. | Produces reviewable evidence packs for leadership, ADA, legal, procurement, and digital services. |
Where scanners still help
- Scanners can identify repeatable technical patterns across large page sets.
- Scanner observations can become source inputs for deterministic findings.
- Automated checks can support regression monitoring when paired with human review.
- Tool output is useful when it is traceable to scope, owner, remediation status, and evidence.
What PublicProof adds
- Inventory coverage across public-service surfaces, not just crawlable pages.
- Deterministic findings with WCAG mapping, severity, service criticality, and owner path.
- Remediation queues for internal teams and vendor-owned issues.
- Exception and evidence records that stay human-reviewed.
- Evidence packs that explain progress, risk, blockers, vendor dependencies, and next priorities.