Model Essay

Source A

Source B (analysis of BinSync article)

BinSync’s pilot operating rules state that routing decisions should be “data-led but reviewable.” The system generates daily routes automatically using sensor readings and prediction models. A supervisor can adjust routes if there is local knowledge (construction, blocked access, or public events). The rules also specify two distinct reporting channels: residents can submit service requests (“missed pickup”) or hazard flags (“overflowing bin attracting animals”). Hazard flags are prioritized, even when the sensor reading is low, because some items (light packaging) can create overflow without a high fill-level. The hotline exists for residents without the app, but callers may receive fewer real-time updates than app users. Drivers must scan a QR code at each pickup; unscanned pickups are treated as incomplete unless a supervisor overrides the record.

Source C (community-posted metrics)

Missed pickups in the pilot district fell from 7.4 to 4.9 per 1,000 households per week.

Fuel use per tonne collected fell by 11%, but average route length increased by 6% on days after major events.
15% of bins had at least one “sensor silence” period longer than 6 hours each month; these streets showed higher complaint rates.

Resident reports increased by 33% after push notifications were introduced, with the largest increase in “missed pickup” requests.

The hotline accounts for 19% of reports, but only 6% of “completed” status notifications.

Source D (criticism of BinSync in local opinion column)

BinSync is described as a “smart system,” but it often feels like a system that makes residents do more work. When notifications warn that pickups are delayed, people respond by filing reports, creating the appearance of engagement while quietly shifting responsibility onto the public. The system also privileges what it can measure. A silent sensor becomes a “non-event” until a complaint arrives, and streets where people are less likely to complain can become invisible. The city celebrates fuel savings, but the pilot also shows how fragile the system is: network gaps, QR scans that fail, and event spikes that produce longer routes anyway. Systems thinking should mean looking at the whole loop, including incentives. If supervisors are pressured to trust the routing engine, “reviewable” becomes a slogan rather than a practice. Riverton isn’t just buying sensors; it is building a new set of dependencies between contractors, dashboards, and resident behaviour. Before scaling up, the city should ask: who benefits from the automation, and who carries the cost when the system is wrong?

(d) With reference to all the sources (A–D) and your own knowledge of the Digital Society course, evaluate whether Riverton should expand BinSync citywide.