City Infrastructure Dashboard
Executive view of stormwater risk, compliance gaps, inspection workload, and sensor prototype readiness.
Total Assets
128
Stormwater infrastructure records
Open Issues
14
Maintenance or inspection concerns
Overdue Inspections
6
Require immediate follow-up
High-Risk Locations
4
Priority infrastructure risks
Executive Risk Summary
Version 1 proves visibility. Cities do not need raw sensor data first; they need to know where risk is increasing, which assets need attention, and what should be documented before a compliance issue becomes expensive.
- Priority 1: Riverbend Road outfall erosion requires corrective action documentation.
- Priority 2: Oak Valley Drive culvert has not been inspected since February 2026.
- Priority 3: Six overdue inspections should be assigned to field staff this week.
Prototype Readiness
AI Intelligence Layer
These are placeholder AI agents that show where future intelligence will plug into the dashboard. They are simulated for now until connected to a real AI API.
StormRisk AI Analyst
Reviews assets, inspections, and sensor readings to identify priority risks.
AI Report Writer
Turns staff inputs and field notes into a city-ready compliance summary.
Compliance Assistant
Checks for missing documentation, overdue inspections, and reporting gaps.
Version 1 Goal
Do not build the full system yet. Version 1 proves one thing: “We can get data from inside stormwater systems and make it useful to cities.”
1. Fake the System
Use sample data, public city data, inspection logs, photos, alerts, and map views to prove the workflow before hardware.
2. Prototype Sensing
Start with one measurement: water level detection. Use simple off-the-shelf parts before inventing custom hardware.
3. Show Visibility
Turn raw readings into city-ready insights like flood risk increasing, possible blockage, or maintenance recommended.
4. Package a Pilot
Sell a small deployable stormwater monitoring pilot with dashboard visibility, alerts, and compliance reporting.
Tactical Product Roadmap
- Phase 1: Build without hardware. Create an asset map, field logging workflow, fake monitoring readings, and compliance output.
- Phase 2: Build one sensing prototype. Measure water level using an ESP32 or Arduino, waterproof ultrasonic sensor, battery pack, and IP67+ enclosure.
- Phase 3: Connect the prototype. Send readings to a simple dashboard using cellular, LoRa, Firebase, AWS IoT, or a basic API.
- Phase 4: Harden into a pilot. Improve waterproofing, mounting, battery life, underground signal reliability, and alert quality.
StormRisk Product Strategy
The goal is not to stay a small consulting tool. The goal is to enter through compliance, become essential through operations, and become hard to replace by helping cities plan spending, vendors, and contracts.
1. Compliance Layer
Entry Point
Tracking, reporting, inspection logs, documentation, and audit readiness. This is what gets StormRisk in the door because cities already have regulatory pressure.
2. Operations Layer
Stickiness
Work orders, maintenance tracking, contractor management, follow-up actions, and field accountability. This makes cities rely on the platform weekly or daily.
3. Financial / Contract Layer
Power Move
RFP generation, budget forecasting, vendor performance tracking, project oversight, and capital planning. This connects StormRisk to how cities spend money.
Strategic Position
Own the Niche
Do not position this as generic water software. Position it as stormwater compliance and risk management for municipalities under EPA MS4 requirements.
Real Scaling Play
- Step 1: Land 3–5 cities manually. Use pilots, direct conversations, and hands-on setup to learn what cities actually need.
- Step 2: Productize everything. Every spreadsheet, report, checklist, asset process, and workflow becomes a feature, template, or automation.
- Step 3: Turn the workflow into SaaS. The goal is for cities to log into StormRisk every week to run compliance, inspections, and reporting.
- Step 4: Own a specific niche. Use precise positioning: stormwater compliance for municipalities under EPA MS4 requirements.
- Step 5: Expand horizontally. After stormwater, expand into wastewater compliance, water treatment tracking, and broader environmental reporting.
Why This Makes StormRisk Hard to Replace
If StormRisk only tracks inspections, it is useful. If it manages compliance, daily operations, work orders, vendors, RFPs, and budget forecasting, it becomes part of how a city operates and spends money. That is where the platform becomes sticky, valuable, and difficult to replace.
Layer 1: Compliance Layer
This is the entry point. Cities already have stormwater compliance pressure, reporting obligations, inspection requirements, and audit risk. StormRisk gets in the door by helping them organize proof, track work, and generate reports.
Permit Profile
1
City, permit, reporting year, and responsible official.
Inspection Logs
42
Field inspections documented this period.
Corrective Actions
14
Open items requiring follow-up or proof.
Audit Readiness
72%
Documentation completion score.
Compliance Subpages
Use these subpages to organize county-specific rules and verified source materials before AI audit review.
1. MS4 Permit Profile Form
Identifies the municipality, permit, reporting period, and responsible compliance staff.
2. Stormwater Asset Compliance Form
Tracks the infrastructure asset, location, condition, inspection status, and proof documentation.
3. Inspection Log Form
Documents who inspected what, when, what was found, and whether follow-up is required.
4. Corrective Action / Maintenance Follow-Up Form
Proves the city acted after identifying a compliance or maintenance issue.
5. Illicit Discharge / Pollution Incident Form
Supports IDDE-style documentation for suspected pollution, discharge complaints, and investigations.
6. Public Education / Outreach Activity Form
Documents education, outreach, campaigns, workshops, and materials distributed to the public.
7. Public Participation / Involvement Form
Tracks public involvement, comments, volunteer activity, and follow-up from community events.
8. Construction Site Runoff Tracking Form
Tracks construction-related stormwater concerns, BMPs, violations, and follow-up actions.
9. Post-Construction BMP Form
Tracks long-term stormwater controls after construction is complete.
10. Pollution Prevention / Good Housekeeping Form
Documents how municipal operations prevent pollution from city facilities and activities.
Layer 2: Operations Layer
Once the city uses StormRisk for compliance, the next step is making the platform useful every week. The operations layer turns inspection findings into action, accountability, and maintenance follow-through.
Work Orders
Create work orders from inspection findings, sensor alerts, high-risk assets, or citizen complaints.
Maintenance Tracking
Track what was fixed, when it was fixed, who completed it, what evidence was uploaded, and what remains open.
Contractor Management
Monitor contractor assignments, job verification, photo proof, timestamps, service quality, and completion history.
Why It Becomes Sticky
If staff and contractors rely on StormRisk to manage daily tasks, the system becomes part of city operations.
Operational Workflow
- Step 1: Inspection or sensor reading identifies an issue.
- Step 2: Staff creates a work order or follow-up action.
- Step 3: Crew or contractor completes the task and uploads documentation.
- Step 4: StormRisk updates the compliance record and maintenance history.
Layer 3: Financial / Contract Layer
This is where StormRisk becomes hard to replace. The platform moves beyond tracking and operations into how municipalities plan projects, compare vendors, forecast budgets, and spend money.
RFP Generation
Generate project scopes, bid language, maintenance specifications, and documentation packages from asset and inspection data.
Budget Forecasting
Use asset condition, maintenance history, and risk level to forecast upcoming stormwater infrastructure costs.
Vendor Performance
Track contractor response time, completion quality, cost history, recurring issues, and documentation compliance.
Why It Is the Power Move
When StormRisk supports budgeting, procurement, and vendor oversight, it becomes connected to how cities allocate funds.
Future Financial Intelligence
The long-term opportunity is to connect infrastructure risk to financial decision-making. Instead of saying “this asset is high risk,” StormRisk can say “this asset may require funding, contractor review, or inclusion in the next capital improvement plan.”
Strategic Position
StormRisk should not be positioned as generic water software. The strongest position is specific: stormwater compliance and infrastructure risk management for municipalities operating under EPA MS4 requirements.
Not Generic
Do not lead with “water software” or “asset tracking.” Those sound broad and replaceable.
Specific Niche
Lead with stormwater compliance, municipal reporting, inspection visibility, and MS4-related documentation support.
Clear Buyer
Municipal public works, stormwater, environmental compliance, city managers, and infrastructure departments.
Expansion Path
After stormwater, expand into wastewater compliance, water treatment tracking, and environmental reporting.
Scaling Strategy
- Land 3–5 cities manually. Learn the exact workflows, reports, and pain points.
- Productize everything. Turn spreadsheets, reports, checklists, and manual processes into features.
- Turn it into SaaS. Cities should log into StormRisk weekly to run compliance and operations.
- Own the niche. Be known for municipal stormwater compliance and risk visibility.
- Expand horizontally. Add wastewater, treatment tracking, and environmental reporting later.
County Compliance Directory
This page is the knowledge base for each county or municipality. Staff can identify the county, assign a reviewer, track EPA/state/USDA/local sources, and prepare an AI audit-readiness review using approved source material.
Counties Tracked
5
Demo county profiles started.
Source Library
4
Federal, state, USDA, and local source categories.
Assigned Reviewers
3
Staff responsible for compliance review.
Audit Readiness
Draft
AI review is placeholder until connected to verified sources.
Add County / Municipality Profile
Use this to create a compliance profile for each county, city, or municipal MS4 program.
County Directory Table
| County | Municipality | MS4 Status | Assigned Reviewer | State Agency | Reporting Portal |
|---|---|---|---|---|---|
| Clayton County | City of Jonesboro | Phase II MS4 | Compliance Analyst | Georgia EPD | GEOS / Local Records |
| Gwinnett County | Lawrenceville | Phase II MS4 | Stormwater Manager | Georgia EPD | GEOS / Annual Documentation |
| Peach County | County Review | Rural / Non-MS4 Review Needed | Program Reviewer | Georgia EPD / USDA RD | State + USDA Source Review |
Approved Compliance Source Library
The AI should only analyze against verified sources entered here by staff or pulled from approved databases later.
AI Audit Review Setup
This placeholder shows how the future AI agent will review county-specific documents against federal, state, USDA, and local requirements before an audit.
Compliance Docs Library
This is a Layer 1: Compliance subpage. Staff use it to search plain-language compliance topics, open official source summaries, bookmark items for review, and verify the source set before any AI audit review is allowed.
Compliance Docs Library
Search, verify, bookmark, and prepare official compliance sources before any AI agent is allowed to review a file.
Federal / EPA Sources
Core federal rules, EPA program references, NPDES framework, and MS4 requirements.
USA State Directory
State-by-state environmental agency, MS4 source, reporting portal, and verification status.
Plain-Language Directory
Helps non-technical staff search by normal words like audit, missing photos, inspection, outreach, or construction.
Bookmarks / AI Review Queue
Staff bookmark only the sources that should be used for completeness checks and future AI review.
Stormwater Asset Inventory
Search and review sample stormwater assets. In Phase 1, this can use public city data or manually entered test records.
Add New Asset
Staff can enter a new stormwater asset into the inventory. In a real system, this would save to a database.
Current Asset Inventory
| Asset ID | Asset Type | Location | Condition | Last Inspection | Risk Level |
|---|---|---|---|---|---|
| SW-001 | Storm Drain | Main Street | Fair | 04/12/2026 | Medium |
| SW-002 | Outfall | Riverbend Road | Poor | 03/21/2026 | High |
| SW-003 | Retention Basin | North Park | Good | 05/02/2026 | Low |
| SW-004 | Culvert | Oak Valley Drive | Poor | 02/18/2026 | High |
| SW-005 | Pipe Segment | Peachtree Crossing | Fair | 04/28/2026 | Medium |
Inspection Tracking
This page shows how inspectors would log field activity and track whether corrective action is needed.
Add New Inspection
Staff can enter an inspection record after visiting a site or reviewing field conditions.
Current Inspection Log
| Date | Inspector | Location | Issue Found | Follow-Up Needed | Status |
|---|---|---|---|---|---|
| 05/10/2026 | J. Carter | Main Street | Debris buildup | Yes | Open |
| 05/08/2026 | A. Williams | Riverbend Road | Erosion near outfall | Yes | Urgent |
| 05/01/2026 | M. Johnson | North Park | No major issue | No | Closed |
| 04/25/2026 | S. Lewis | Oak Valley Drive | Standing water near culvert | Yes | Pending |
Water-Level Sensor Prototype
Version 1 should start with one measurement: water level detection. This page shows how simple readings could appear before a real hardware deployment.
Prototype Node
WL-01
Water-level sensor test unit
Current Reading
18.4 in
Latest water-level reading
Battery
76%
Target: months, not days
Signal
Good
Cellular / LoRa test status
Add New Sensor Reading
Staff can manually enter readings now. Later, this would come directly from an ESP32, Arduino, cellular device, LoRa gateway, Firebase, AWS IoT, or API.
Sample Readings
| Time | Location | Water Level | Condition | System Interpretation |
|---|---|---|---|---|
| 08:00 AM | Riverbend Road | 10.2 in | Normal | No immediate action |
| 10:00 AM | Riverbend Road | 14.8 in | Rising | Monitor closely |
| 12:00 PM | Riverbend Road | 18.4 in | Elevated | Possible blockage or flood risk increasing |
AI Agent Placeholders
These agents do not call a real AI API yet. They show the product vision and where the future AI logic will connect.
1. StormRisk AI Analyst
Purpose: Review assets, inspections, and sensor readings to explain where risk is increasing.
Future Output: Risk explanation, priority ranking, and recommended next action.
2. AI Report Writer
Purpose: Convert staff entries into professional report language for city leadership, compliance files, and audits.
Future Output: Executive summary, compliance narrative, audit notes, and recommended actions.
3. Compliance Assistant
Purpose: Identify missing documentation, overdue inspections, reporting gaps, and audit readiness issues.
Future Output: Missing item checklist and compliance readiness score.
4. Field Note Cleaner
Purpose: Turn messy inspector notes into clean professional language.
Future Output: Clean inspection narrative suitable for reports.
5. Work Order Recommender
Purpose: Suggest maintenance work orders based on risk, inspection findings, and sensor alerts.
Future Output: Suggested task, priority level, and assignment recommendation.
6. Sensor Alert Interpreter
Purpose: Explain what sensor readings may mean instead of showing raw numbers only.
Future Output: Plain-language alert interpretation and escalation recommendation.
Generate Compliance Report
Staff enter inspection results, simulated sensor readings, compliance concerns, and field notes. The system converts the entered information into a report summary.