See the operating surfaces utilities can use now.
BackflowCore.ai is broader than a submission form or a registry grid. The current platform spans registry, tester readiness, dynamic submissions, compliance notices, scoped portals, dashboards, maps, and survey follow-up workflows.
Registry + map foundation
Manage properties and assemblies with imports, coordinates, hazard context, due timing, inspection history, and map-based program visibility.
Tester + kit readiness
Run public onboarding, verification, credential documents, calibration evidence, and assignment-based test kit gating inside one readiness workflow.
Dynamic submissions + review
Capture the right form for the device, support drafts and attachments, then auto-approve or route to review with decision trace preserved.
Compliance + communications
Track compliance state, notice history, communication traceability, reports, and follow-up actions without rebuilding the record from exports.
The current platform is organized around the work, not around disconnected tools.
These are the operating surfaces the site should describe as current. They already exist in the backflow module and are strong demo anchors for utility buyers.
Property and device records
Backflow-owned records with imports, dedupe, data quality workflows, due-date context, and history.
Tester, provider, and kit eligibility
Approval, credential documents, calibration evidence, provider rosters, and kit assignments before work is accepted.
Dynamic forms and routing
Authenticated and public submissions routed to the right backflow form version for the actual device and program context.
Scoped external workflows
Certified tester, service provider admin, and customer experiences that stay inside strict access boundaries.
Dashboards, map, reports, and queues
Program overview, tester workspace, map layers, reporting, review queues, and communication trace pages.
Survey and corrective workflow support
Survey cases and hazard follow-up exist in the product today, while deeper jurisdiction-specific automation continues to expand.
From device lookup to compliance action.
The platform should be evaluated as an operating sequence, not as isolated screens. The current path is clear, concrete, and tied to the implemented backflow surface.
Find the right property and device
Start from the authoritative record with registry detail, map context, and device history already in place.
Validate the actor and equipment
Apply tester approval, credential checks, calibration evidence, and kit readiness before accepting the submission.
Capture the right form
Load device-type form logic, attachments, attestations, and draft-friendly field workflows rather than pushing generic PDFs through email.
Decide, notify, and report
Review or auto-approve, update compliance state, maintain notice history, and expose the result in dashboards, reports, and traceability views.
Concrete now, deeper policy and enforcement depth next.
Current platform claims should lead with registry, readiness, submissions, notices, portals, dashboards, maps, and survey workflow support. The safer expansion lane is deeper tenant policy depth, advanced enforcement automation, and later-phase dashboard customization.
Scheduling, payments, and unrelated utility workflows remain intentionally out of scope for the backflow product story.