IDDE, complaints, incidents.

Complaint intake

Intake captures what the program needs to act: the address or mapped location, the reporter (named or anonymous), an initial classification, and any initial photos. The complaint is mapped on creation so it shows up in the workspace map alongside related sites and assets.

Four triage paths

• IDDE case. Suspected illicit discharge. The complaint moves into the six-stage IDDE workflow.
• Non-IDDE complaint. A stormwater concern that is not an illicit discharge (for example, a maintenance issue). It tracks as a complaint with its own resolution path.
• Referral. The issue belongs to another agency or department; the record captures who it was referred to and when.
• Unfounded. Investigation showed no discharge or no actionable issue; the record is closed with reasoning.

Six-stage IDDE workflow

1. Complaint received.
2. Screening.
3. Source tracing.
4. Enforcement linkage.
5. Closure.
6. Outfall timeline.

Each stage records who acted, when, and what evidence was attached. The outfall timeline groups cases by outfall so recurring patterns are visible at the asset level, not buried in a long list of tickets.

One thread per incident

Every incident lives on a single thread: intake, screening notes, source-tracing photos, enforcement linkage, closure documentation, and any related inspection records. There is no split between a ticketing system and a separate enforcement file. The thread is the case record.

Closure documentation

Closure captures the final status, the responsible party (where one is identified), the corrective action taken, and the closure date. The closed incident remains in the workspace for reporting evidence and audit review.