Week 10: Who benefits from the current rule?

Auditing the Priority Lane introduced in week 6 against a released synthetic dataset of its usage, rather than its stated intent.

26 April 2027

The Priority Lane was introduced in week 6 on the strength of its stated purpose: urgent matters served first, urgency self-declared in good faith. This lecture starts the course’s final movement — defending a waiting system — by auditing that lane against a dataset of what happened once it opened, not just what it was meant to do.

Outline#

• the gap between a policy’s stated purpose and its measured effect: this course has built the tools to close that gap (weeks 2–3’s statistics, week 6’s comparison method) and this week applies them to the Office’s own choice
• an audit needs more than a category breakdown of who declares urgency — today’s release also gives the total number of requests in each category, so a category’s share of Priority Lane use can be checked against its share of ordinary demand, not judged in isolation
• what a category-share comparison can and can’t show: it can identify a category whose share of Priority Lane declarations is larger or smaller than its share of ordinary demand; on its own, it says nothing about why
• the release’s one wait-time figure — Priority-declared tickets waited six fewer minutes on average than tickets that didn’t declare — describes the whole Priority Lane population, not any single category, and an association measured this way is not evidence of what caused it
• what this release cannot show: no within-category wait times, no independent record of which declarations were genuinely time-critical, nothing about when requests arrived or how long each category typically takes to serve, and nothing about how consistently the rule is applied at the counter — any of these could account for part of the six-minute figure on its own
• an audit is not automatically a condemnation: a rule can be used more than intended and still be defensible, or used exactly as intended and still be worth reconsidering — the Queue Lab asks you to conclude from the data, not from the fact that an audit was requested

Office of Everything file — synthetic case material. Released dataset, three months. All requests received, by category: “dispute a printer credit” 60, “collect a form” 600, “enrolment variation” 300, other 40 (1,000 total). Of these, requests where Priority Lane was declared: “dispute a printer credit” 8, “collect a form” 122, “enrolment variation” 60, other 10 (200 total). Over the same three months, tickets that declared Priority Lane waited a mean of 3 minutes before being served; tickets that did not waited a mean of 9 minutes — one figure for the whole Priority Lane population, not broken down by category. The lane’s stated purpose at launch was “for the small number of matters that are genuinely time-critical.” The release records neither why any individual ticket declared urgency nor whether any declaration was accurate.

The Queue Lab gives you that dataset and asks what it actually shows, and what it doesn’t, about who the lane has been serving, ahead of week 12’s full redesign.