Green publishes different contacts for a stormwater-quality concern and a flooding problem, while its service form has a roadway-flooding category. A resident should report observations without diagnosing the source or choosing the wrong public desk.
Green: what each official source establishes
The records do different evidentiary jobs. Reading them together answers the routing question; it does not turn a general instruction into an address-specific decision.
| Official record | Limited job in this file |
|---|---|
| Storm Water Division | separates water-quality and flooding contacts and identifies prohibited storm-drain materials |
| Make a Service Request | supports location, request type, picture, comments, and roadway-flooding fields |
- The Storm Water Division sends observed water-quality problems to one contact and flooding problems to the Service Department. Storm Water Division
- The form requests an identifying location and supports a photograph and comments. Its roadway-flooding option is an intake category, not a technical finding about cause or responsibility. Make a Service Request
Green evidence ledger: Observed Symptom to Result
The useful record is a chain, not a single screenshot. Keep the source date and the agency’s exact wording beside each entry so a later response can be compared with what was submitted.
| Evidence field | What to retain |
|---|---|
| Observed Symptom | Identify the exact observed symptom and tie it to the property, account, project, or observed event before choosing a route. |
| Water Quality Or Flooding Route | Save the dated water-quality or flooding route as a separate item and preserve who supplied it; do not infer it from the prior entry. |
| Location | Save the dated location as a separate item and preserve who supplied it; do not infer it from the prior entry. |
| Photograph | Save the dated photograph as a separate item and preserve who supplied it; do not infer it from the prior entry. |
| Request Category | Save the dated request category as a separate item and preserve who supplied it; do not infer it from the prior entry. |
| Agency Response | Save the dated agency response as a separate item and preserve who supplied it; do not infer it from the prior entry. |
| Result | Retain the official result; do not substitute an application receipt, scheduled event, or verbal expectation for the outcome. |
Green boundary and unresolved facts
The router applies to City of Green non-emergency concerns. Immediate hazards require the appropriate emergency route rather than delayed form submission.
No conflict was found. The division page classifies the concern, and the service form records the flooding request; they serve different stages.
Those boundaries matter: a form, portal category, published rule, permit, scheduled inspection, or public event is evidence of one stage only. It does not prove a later approval, diagnosis, payment, service action, collection, completion, or responsibility decision.
Source and method
On August 29, 2026, Local Service Ledger reviewed the issuing agencies’ cited records and compared their jurisdiction, intake, evidence, decision, and closeout fields. Build a symptom-not-diagnosis router separating quality, flooding, location, evidence, contact, request, response, and result records. We did not submit a case, inspect a property, diagnose infrastructure, or receive a case-specific government or utility decision.