Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the City Services topic
No spam. Unsubscribe anytime.
City rolls out 3‑1‑1 portal and reports early usage: 7,000 requests since March
Summary
City staff told council the new 3‑1‑1 system has handled more than 7,000 submissions since launch; most common categories were solid waste and potholes and the administration reported about 200 open items requiring follow‑up.
City staff briefed the Lowell City Council on the 3‑1‑1 citizen request system the administration launched in March, reporting more than 7,000 submissions to date and describing steps to refine reporting, reduce duplicate entries and improve resident notifications.
Why it matters: A consolidated 3‑1‑1 system increases transparency and gives councilors and residents a single place to report routine city needs and to track department responses. Early data offers staff and councilors a new tool for allocating maintenance resources and for tracking response times.
Key details from the administration: The vendor system currently tracks about 85 request types; closed requests in the report numbered more than 6,200 with roughly 212 open and 86 under investigation at the time of the presentation. City staff said some reporting discrepancies arose because the system’s canned reports use calendar days while the team prefers business‑day metrics; staff are working with the vendor, Tyler, to align reporting.
Common request types and backlog: Solid‑waste issues and potholes represented the largest share of requests. Staff estimated a small backlog of roughly 200 items pending longer lead‑time repairs or parts; departments are trained to respond to residents with status updates when a job requires extra time to complete.
User experience and next steps: Staff acknowledged earlier mobile app issues (drop‑down selections and occasional submission errors) and said a new vendor release addresses a number of interface problems. The web portal currently provides a map view of requests citywide; staff said they are testing options to restore limited map features in the mobile app while protecting privacy and safety.
Councilors praised the team for the rollout, asked for district‑level breakdowns and urged clearer resident messages for failed submissions. IT and operations staff said future reporting will include district‑level dashboards and a clearer distinction between resident‑submitted requests and internal proactive work orders.
Ending: Administration said it will continue vendor fixes, expand district reporting and issue regular updates as the tool matures; councilors requested future periodic reports and asked that the portal link be widely circulated.
