Survey
Real zones, routes and frequencies, plus the complaint handling flow agreed with the department in charge. Without this step, the system is built on assumptions.
The planned route is compared with each vehicle's actual path. Your entity knows how much of the canton was covered, at what time and with what deviations. Citizens check their schedule, follow the vehicle on the map and report a critical spot from the browser.
Residents install nothing. Crews record evidence even with no signal.
Waste collection is one of the most visible municipal services and leaves little evidence. When a resident complains that the truck did not come, the entity has nothing to answer with: a paper route sheet, a driver who says it did pass and no record to settle the dispute. Without that evidence, a collection fee cannot be sustained, source separation cannot be justified and an oversight body cannot be answered.
Access is a web address. Requiring an app download just to know when the collector passes leaves part of the population out.
Day, time slot and waste type that apply to the registered address.
Live tracking of the vehicle assigned to that route, with the time of its last report.
When the vehicle approaches the registered point, within the radius your entity defines per zone.
If the route has not started or is running late, the notice goes out anyway and prevents waste being put out for nothing.
A photo and a location are enough to open the case. Residents can see what state it ended in.
Notices by messaging, email or browser notification, and also for those without a smartphone.
Your entity manages zones, routes and frequencies, with effective dates. Changing the layout of a zone is an edit in the panel, not a request to the provider.
Every boundary change is dated, and history is not lost when the service is reorganized.
Including waste type, which is what makes separate collection possible.
Route, vehicle and driver by date, the record that later backs up any complaint.
Each critical point with a status, an owner and a resolution. Reports about the same spot are consolidated into one case.
Crews on the route record what they serviced with a photo and a location. It works without signal and syncs on reconnect.
Coverage, punctuality and cases, ready for the accountability report.
Each shift leaves a measured execution: what percentage of the route was covered, at what time it passed each stretch, what was skipped and which complaints were handled. That comparison is what an authority can show month after month.
Coverage measured, not declared.A small municipality does not need to buy everything in the first year. The scope is agreed with your entity before writing the first line, based on the real zones and routes of your canton.
Real zones, routes and frequencies, plus the complaint handling flow agreed with the department in charge. Without this step, the system is built on assumptions.
Your entity's panel, citizen portal with schedule and live tracking, schedule and proximity alerts, critical-spot reporting and crew evidence.
Arrival estimates based on the history of each stretch, automatic classification of report photos and a publishable compliance dashboard.
Weighing, container fill sensors and dynamic routing remain a conditional phase: they depend on third-party equipment and are quoted separately, never inside the base scope.
And it is treated as such from the design. No ID number or name is requested to receive an alert, the phone number is recorded only if the citizen chooses that channel, and unsubscribing is immediate. Your entity accesses information aggregated by neighborhood, not a map of who lives where. Faces and license plates are blurred in report photos before they enter the panel, and no facial recognition is applied at any point in the process. All in line with Ecuador's Organic Law on Personal Data Protection.
Tell us how many collection vehicles your entity has and how many routes it runs. We reply on WhatsApp, with no forms.