City dispatcher
Reviews a report, connects it to a site and assigns the responsible contractor.
Menu
Municipal operations
Qayta City
A map of collection sites, resident reports and contractor execution records.
- Municipal authorities
- City operators
- Collection contractors
Platform role
One module in an end-to-end process
Qayta City brings collection sites, containers, reports and contractor work onto one map. Municipal teams can follow an issue from registration to a recorded outcome.
Site data, complaints and collection evidence arrive through different channels, obscuring the operational picture.
Participants
Who does what
Contractor
Receives the job, updates status and provides the agreed completion evidence.
Service manager
Reviews timing, recurring reports and recorded outcomes by area.
Capabilities
What the operating layer covers
Asset map
Brings sites, containers, requests and available collection events onto one map.
Structured reports
Accepts location-based reports and attachments through connected channels.
Execution control
Relates due date, assignee and recorded result for each request.
Workflow
How the workflow runs
- 01
Register
A site or report receives a record and location.
- 02
Assign
The responsible team sends the work to the selected contractor.
- 03
Review
Status and completion evidence remain visible in the operational view.
Data and control
Inputs, outputs and human control
Inputs
- site and container registry
- location-based reports and attachments
- jobs and collection events
Outputs
- current-state map
- report and execution record
- operational views by area and contractor
Controls
- assigned owner
- due date and status
- completion evidence review
Integrations
Integration scope made explicit
The label shows the maturity of the public claim. Final scope is always agreed after discovery.
Reporting channels
Defined per projectConnected channels and required fields follow the municipal procedure.
Qayta Fleet
Configurable capabilityRoutes and checkpoints add evidence to the job record.
Qayta Sense
Configurable capabilityFill events support planning based on recorded site condition.
Implementation
Boundaries are agreed before the pilot
Implementation normalises the address and site registry, responsibility zones, report categories and evidence rules. Contractor scoring is not published without an approved method.
Expected outcome: One view of municipal waste infrastructure and request execution based on registered events.
FAQ
Common questions
Does City replace an existing resident portal?
Not necessarily. It can receive data from an existing channel and manage operational execution.
How is a contractor assessed?
Only under an approved method using recorded dates, statuses and outcomes.
Does a resident need an account?
Not for the base scenario. The reporting channel is defined by the project; a customer account is outside this website.