Larger MS4 programs
For larger MS4 programs that need more than another spreadsheet.
NPDESTracker gives stormwater teams a connected workspace for inspections, sites, contacts, tasks, enforcement drafts, GIS context, and annual-report evidence — with configuration support for agency-specific workflows.
Browser-based MS4 software. Founder-led kickoff on larger pilots. Records export on every tier.
01 · Who it is for
Stormwater programs whose work no longer fits a spreadsheet.
Phase II cities with multiple staff
Programs with several inspectors, a coordinator, a supervisor, and a director who needs visibility across the year.
Counties, parks districts, and utilities with MS4 responsibilities
Public works, environmental services, and stormwater utilities running inspection programs across multiple departments.
Agencies moving away from spreadsheets and shared folders
Programs whose records currently live across inboxes, photo folders, GIS files, and printouts — and need a single connected workspace.
Programs that need better evidence chains before annual reporting
Coordinators who want every count in the annual report to trace back to the inspection, IDDE incident, BMP record, or enforcement action behind it.
02 · What exists today
A connected workspace, available now.
These are the modules and records the workspace ships with today. None of them are roadmap features; they are the daily product. Larger programs typically use most of them; smaller programs use the subset that matches their permit.
Modules and records available now
- Sites and contacts on one workspace
- Inspections with photos, GPS, and structured forms per kind
- Tasks and reinspections with due dates and assignees
- Complaints and IDDE incidents on a single thread per case
- Enforcement drafts started from inspection records
- Public education and participation activity tracking
- Annual report evidence linked to the underlying records
- GIS context on sites, outfalls, and BMPs
- Exports in CSV, JSON, and GeoJSON on every tier
- Custom modules built from the platform's configurable building blocks
03 · How it adapts
Configuration is built in. Setup support is part of larger pilots.
Agency-specific fields and forms can be handled through configurable modules and scoped setup. Core-record field configuration is part of the larger-program roadmap.
Module toggles
Turn on what the program runs, leave the rest off. The workspace only shows what your team uses.
Dropdowns and terminology
Edit BMP types, finding categories, enforcement actions, and labels so the workspace reads the way your permit and your team already write it.
Custom modules
Add record types and workflows specific to your agency — built from the platform's configurable building blocks during setup.
CSV import and export
Bring existing inventories in by CSV. Records remain exportable on every tier so your team is never locked in.
Scoped setup help
Founder-led kickoff on the larger pilots maps your current process into the workspace, with a written scope before work starts.
Configured reporting evidence structure
The annual reporting workspace is shaped around the permit framework your state agency administers. Counts come from the records you already kept.
04 · What larger agencies ask about
The questions directors, supervisors, IT, and procurement reviewers raise.
Short answers below; full substance lives on Terms, Security, Privacy, and the pilot scope.
Data export and portability
CSV and (where applicable) GeoJSON exports on every tier. Offboarding includes a clean export of what your team logged.
Reference: Terms
User roles and access
Per-user accounts with role-based access for read, write, edit, and export. Role scope is part of the kickoff conversation on larger pilots.
Reference: Security
Audit trail
Every create, edit, and override on key compliance records leaves a timestamped, user-attributed entry built to hold up in a state-agency review.
Reference: Security
Security and privacy posture
Browser-based access, US-region hosting, tenant isolation, encryption in transit, and an honest no-SOC-2-yet disclosure. Sub-processors are named on the Privacy page.
Reference: Security
Procurement and vendor setup
Operated by Wood Technologies LLC. Card, ACH, Stripe invoice, or letterhead invoice with W-9 on request. Vendor setup details and payment terms live on the Pricing page.
Reference: Pricing
Support expectations
Founder-led support by email and ticket during business hours. Founder-led kickoff is included on the Full Municipality Pilot and on quoted plans where the order form names it.
Reference: Contact
Implementation scope
The Full Municipality Pilot is a 90-day, founder-led evaluation. Larger or multi-department deployments are scoped around the actual program with a written scope before kickoff.
Reference: Pilot
05 · Honest growth path
Scoped implementation, not assumed out of the box.
Some larger-agency needs, such as department-level permissions, deeper audit expansion, advanced GIS administration, and enterprise integrations, are handled through scoped implementation planning rather than assumed out of the box.
The Full Municipality Pilot is the most direct way to put these on a written kickoff scope. Larger and multi-department programs are quoted around the actual program, with the order form listing which guided-setup items are included.
See it with sample data, then send a short email.
Open the sample workspace to walk inspections, IDDE, tasks, GIS, and the annual report on fictional Phase II data. If it looks like a fit for a larger program, ask about a pilot scoped around the agency.
Email goes to admin@npdestracker.com. The founder reads every message.