NPDESTracker

Implementation

A 30-day plan from kickoff to go-live.

What to prepare, what happens each week, and what NPDESTracker does versus what the customer controls.

Schedule

The 30-day onboarding plan.

Day 0

Kickoff call

A scheduled kickoff is included on the Guided Evaluation Workspace and above. We confirm the program goals, the workflows you want in first, and who plays each role.

Days 1 to 7

Admin setup, roles, configuration

Admin login, tenant configuration (time zone, permit framework, terminology), role assignment, module toggles. Walk through /docs/admin-setup.

Days 7 to 14

Data import

Sites, contacts, GIS layers (outfalls, BMPs, structures), and inspection history. Follow the recommended order on /docs/data-import.

Days 14 to 21

Inspector training and first inspections

Mobile workflow training, first inspections in the field, deficient-finding follow-up tasks, and closure evidence on the task itself.

Days 21 to 30

Notices, replies, reporting baseline, go-live

Notice and reply workflow walkthrough, reporting evidence baseline so counts trace to records from day one, and the go-live checklist below.

What to prepare

Before kickoff.

  • A site list as CSV (address, parcel, classification).
  • A contact roster as CSV (owners, operators, responsible parties).
  • Existing GIS layers as GeoJSON or shapefile for outfalls, BMPs, and structures.
  • Your permit framework reference (for example, your current Phase II permit).
  • A designated admin user with an agency email address.

Go-live checklist

Day 30.

  • At least one inspection logged with photo and GPS.
  • At least one follow-up task closed with evidence on the task.
  • At least one notice drafted from a deficient finding.
  • The readiness rollup populated for the current reporting period.
  • Admin invite confirmed for every named user.
  • Tenant configuration reviewed (time zone, permit framework, modules, terminology).
  • Export tested (CSV, JSON, GeoJSON where applicable).

Who does what

What NPDESTracker does, what you control.

NPDESTracker

  • Hosts the tenant on US-based cloud infrastructure.
  • Runs the workspace and the application code.
  • Ships product updates.
  • Provides email support during business hours.
  • Walks through the workflow on request.

You (the customer)

  • Roles and user accounts inside your tenant.
  • Configuration (modules, terminology, dropdowns, inspection fields).
  • Records (inspections, IDDE cases, notices, reporting answers).
  • Exports.
  • Notices and certifications. Submission to your state agency stays with your staff.

Honest list

What is not automated yet.

  • Native iOS field app (planned). Field use today is browser-based.
  • Automatic weather and rainfall autofill on inspection records (planned).
  • Sequential permit numbering (planned).
  • FOIA package builder (planned).
  • Permit-specific report templates beyond WA Phase II Western 2024-2029 (planned per state, scoped during onboarding).

Support expectations

How we work together.

Support is email-first at admin@npdestracker.com during business hours. There is no published response-time SLA. Escalations happen by reply on the existing thread; include municipality, plan, and what was tried. See /docs/support for the per-tier breakdown.

Need help? Email admin@npdestracker.com.