---
title: "Jurisdiction scorecard"
method: GET
path: "/analytics/scorecard"
tags: ["analytics"]
---

# Jurisdiction scorecard

`GET /analytics/scorecard`

Per-jurisdiction rollup (incident volume, clearance speed, severity mix, construction schedule drift, road-condition coverage, source uptime) with a 0-100 composite score, optionally ranked. Returns all active jurisdictions by default. Requires Pro+ plan.

**Construction fields.** `construction_overrun_avg_days` is the average **net movement of the published end date** — the last end date the source published for a job minus the first one it published, in days. Positive means jobs are typically pushed later, so a DOT reporting +6 has historically needed about six days more than it first advertised. It is derived from the recorded per-revision history, not from when the job disappeared from the feed.

`construction_reschedule_avg` counts only **material** reschedules — moves of at least one day. Feeds that publish a rolling ETA (an end time creeping forward by minutes on every poll) are not rescheduling anything, and those steps are excluded.

Jobs whose end-date revision history is no longer retained are **omitted from both averages** rather than counted as zero. Both figures therefore describe jobs with observable revisions; `construction_jobs` is the full count of tracked jobs and will usually be larger.

## Query parameters

- `jurisdiction` string
- `country` 'US' | 'CA'
- `from` string, date
- `to` string, date
- `rank_by` 'score' | 'incident_volume' | 'avg_clearance_minutes' | 'source_uptime' | 'construction_overrun_avg_days'
- `order` 'asc' | 'desc'
- `limit` integer

## Response `200`

Ranked jurisdiction scorecards

---

[API](https://skmtc.net/road511/apis/road511-traffic-api.md) · [All operations](https://skmtc.net/road511/apis/road511-traffic-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/road511/road511-traffic-api/versions/39a088b9c155/schema)