City of Melbourne Public Service Requests and Resolution Times

City of Melbourne Open Data provides customer service requests logged by the public concerning waste, graffiti, parking, roads, parks, and assets. Each request includes fields like REQUEST_STATUS, DATE_RECEIVED, DATE_COMPLETED, SUBURB, CATEGORY, SERVICE_DESC, and calculated DAYS_TO_COMPLETE. The dataset was last updated in March 2026.

Use Cases

• Analyze DAYS_TO_COMPLETE across different CATEGORY types to identify service efficiency bottlenecks.
• Model REQUEST_STATUS transitions from NEW to CLOSED using DATE_RECEIVED and DATE_COMPLETED timestamps.
• Map request density by SUBURB to allocate resources for high-frequency SERVICE_DESC categories like waste or graffiti.
• Forecast future request volumes for categories like parking or assets based on historical DATE_RECEIVED patterns.

Strengths

• Includes a calculated performance metric DAYS_TO_COMPLETE for each request.
• Covers multiple service categories such as waste, graffiti, parking, roads, parks, and assets.
• Provides detailed status tracking with REQUEST_STATUS values like CLOSED, WIP, REASSIGNED, NEW, and ACTIONED.

Limitations

• Some SUBURB values are blank, limiting spatial analysis for requests without assigned locations.
• DAYS_TO_COMPLETE excludes time spent referring to other authorities or waiting for customer information, potentially underreporting total resolution duration.
• Sample data and row count are unavailable, hindering assessment of dataset scale and completeness.

Provenance

Source

City of Melbourne Open Data

Collection Method

Logs of customer service requests submitted by members of the public.

Freshness

Last updated March 2026.

Geography

City of Melbourne, with SUBURB field for location (some values blank).