About
Built from inside the work.
NPDESTracker is municipal stormwater compliance software for small and mid-sized Phase II MS4 permittees. It was built from firsthand experience running NPDES compliance work at the local level, then turned into a product because the spreadsheets and binders kept getting in the way of the actual job.
Origin
The product started with a stormwater coordinator's problem.
NPDESTracker began as a working answer to a real frustration: small Phase II MS4 programs spend most of their year doing the work, and most of March reconstructing the year from spreadsheets, photo folders, email threads, and binders. The annual report is built from memory and copy-paste, and the records that should support it live in five places. None of that is the program's fault. It is what happens when generic tools are asked to do permit-aligned work.
The first version of the workflow was designed by someone working through that exact problem. Inspections needed to be capturable on a phone, with photos and GPS, and survive a long day of no signal. IDDE complaints needed to live on a single thread from intake to closure. Annual report counts needed to come from the records, not from a fresh blank cell each March. The outline of what NPDESTracker is today came out of writing those workflows down and refusing to let them drift.
The product is small and serious on purpose. It is built around what Phase II MS4 coordinators actually do. The pages on this site describe what is in the product today, not what is on a roadmap. If a feature is not described, it is not in the product yet.
Team
A small, expert-built product.
NPDESTracker is intentionally small. The advantage of that is direct contact: the person designing the workflow is the same person customers email when something needs attention.
Founder
Nathaniel Wood
Founder & CEO
Nathaniel founded NPDESTracker from firsthand municipal stormwater and NPDES compliance experience. He designed the product's workflow and outline around how Phase II MS4 programs actually run, from field inspections through the annual report. He answers buyer and procurement questions directly at admin@npdestracker.com.
How we build
The principles the product is built on.
Built from inside the work, not from outside it.
Every workflow in NPDESTracker reflects how the work actually happens at a small or mid-sized Phase II MS4 program. The inspections module is shaped by inspections that happen in the field, not by what an inspection theoretically should look like.
Counts come from records, not invented scores.
Annual report numbers come from the actual records logged through the year. There is no manufactured compliance percentage, no traffic-light theatre, and no fields auto-populated to make a dashboard look complete.
Audit-defensible by default.
Every create, edit, and override leaves a timestamped, user-attributed entry. The product is built on the assumption that a state-agency reviewer will eventually read the audit log, and that everything in it should hold up.
Honest scope.
If a feature is not built, the page does not say it is. If a security control is not held, the security page says so plainly. Smart Draft is described as assistive and never as a replacement for staff review.
Product, plainly
What NPDESTracker is, in one paragraph.
NPDESTracker is a browser-based compliance documentation tool for municipal MS4 programs. It tracks sites, outfalls, BMPs, drainage structures, inspections, IDDE incidents, complaints, activities, training, and enforcement actions across the six Minimum Control Measures, then assembles the annual report from those records with full audit trails. The first complete annual reporting template wired in is the Western Washington Phase II 2024-2029 template, with adjacent state programs covered in the permit pages.
See the platform overview for what is in the product, the security page for how access and tenancy work, the Smart Draft and AI page for how the optional AI feature is scoped, and pricing for pilot and annual-platform pricing.
Talk to the person building it.
Procurement question, security questionnaire, pilot inquiry, or feature feedback from a coordinator running the work. Email goes to the founder, not a queue.