Scope
Public surfaces become named records.
Websites, public documents, resident forms, mobile surfaces, and vendor-managed services are registered with owner, service criticality, and review status.
Inventory first
Operating chain
Solution file
The product is the record that connects scope, owners, vendors, and proof.
PublicProof gives counties and cities serving 50,000+ residents a maintained Title II operating record: inventory, deterministic findings, remediation ownership, vendor accountability, exception inputs, and evidence.
Primary buyer
County and city review teams
Deadline frame
April 26, 2027
Product type
Service plus SaaS operating record
Operating chain
The record has to survive handoffs, vendor delay, and legal review.
PublicProof is designed for the operating reality of local government: public-service risk is distributed across departments, vendors, records workflows, and executive review.
Findings
WCAG issues become accountable work.
Findings carry deterministic references, severity posture, service context, owner path, due date, and evidence need.
Auditable logic
Owners
Internal and vendor work stay connected.
ADA, web, communications, legal, procurement, departments, and vendors can be tracked without treating vendor delay as closure.
Owner chain
Evidence
The record produces a review packet.
Scope, progress, unresolved risk, exceptions, vendor dependencies, and next priorities are assembled for leadership and legal review.
Forwardable file
Buyer distinction
PublicProof starts where scanner-only programs usually break.
The meaningful distinction is not whether PublicProof can find issues. It is whether the buyer can operate the record after issues are found.
Scanner
A scan finds reachable issues.
It usually does not own the county-wide record of documents, vendors, departments, exceptions, and evidence cadence.
Input, not system
Dashboard
A generic dashboard shows counts.
PublicProof keeps the review file that explains what those counts mean for services, owners, vendors, and procurement.
Record over chart
AI
AI cannot be the compliance authority.
PublicProof may use AI internally for drafting and summarization, but the final compliance record stays deterministic and human-reviewed.
Controlled boundary
Product artifact previews
What the operating record looks like in practice
PublicProof turns scanner output, manual review, vendor dependencies, remediation work, and executive proof into records a local-government team can actually operate.
Inventory
Record artifactSurface inventory register
A scoped baseline for websites, document libraries, forms, mobile surfaces, and vendor systems.
Main website
Resident service pages, alerts, and program entry points.
OwnedAgenda packets
Recurring PDFs tied to public meetings and records access.
PriorityPayment portal
Vendor-managed transaction path for bills and fees.
VendorFindings
Record artifactWCAG findings register
Deterministic issues with WCAG reference, severity, service criticality, owner, and due date.
1.3.1 structure
Agenda packet heading order assigned to the clerk record queue.
Review3.3.2 labels
Permit intake labels assigned to the web team with verification criteria.
Assigned1.4.3 contrast
Payment flow issue routed to vendor contact before renewal review.
VendorRemediation
Record artifactRemediation and vendor queue
Internal and vendor-owned fixes remain tied to blockers, verification criteria, and review status.
PDF templates
Replace recurring agenda packet template and verify tags.
In reviewForm labels
Update permit intake component and keyboard path.
AssignedPortal patch
Vendor milestone requested before renewal review.
BlockedEvidence
Record artifactExecutive evidence pack
A quarter-ready summary of scope, progress, open risk, exceptions, vendor dependencies, and next priorities.
Scope
Website, documents, forms, mobile surfaces, and vendor systems named.
BoundedProgress
Resolved, open, blocked, and deferred work summarized for leadership.
DraftedBoundary
Sample only, not legal advice or ADA certification.
ReviewEvidence file
The artifact structure mirrors the work a public agency must defend.
Evidence is only credible when the record says what is still unresolved, which exceptions are only review inputs, and which vendor dependencies remain open.
In-scope surfaces
Public websites, document workflows, forms, mobile surfaces, and vendor systems.
Remediation ownership
Internal and third-party work with blockers, verification criteria, and review dates.
Exceptions and limitations
Exception candidates stay explicit, linked, time-bounded, and separate from closure.
Executive evidence packet
Scope, progress, unresolved risk, vendors, exceptions, and next-quarter priorities.
Trust boundary
Deterministic records stay separate from workflow assistance.
PublicProof can assist with organization, drafting, and evidence assembly. It does not replace the public entity's legal, procurement, or compliance judgment.
Boundary
The operating record supports review. It does not certify ADA compliance, replace legal judgment, or delegate final public-sector decisions to AI.
Next step
Start with a bounded pilot scope so the entity can review records before committing to a full operating program.
Request pilot brief