Decision record · DR-0031

Example Shire Council · resident issues

Rank repeat reports of the same issue above single reports

ApprovedLive from Fri 9 Oct 2026
Decision
Which resident issues reach the weekly operations meeting, and who decides
Logic
issue-ranking v1.4 · rule 3The Council’s, versioned
Data used
Web form, phone log, survey tool (weekly), ward boundaries
Why
Repeat reports were reaching the meeting late, because each channel counted them separately.
Alternatives
Rank by channel; rank by age. Both tested, both caught fewer repeats.
Accountable
Manager, Community Services
Review
Each July, or when ward boundaries change
Decision record · DR-0031

01Test evidence

The records list caught 104 of 111 repeat reports in four weeks. The manual list caught 81.

WardIssuesRepeat reportsCaught by records listCaught by manual listHeld for an officer
North Ward1403836296
River Ward1223331245
Hills Ward641918143
Coast Ward902119144
All four wards4161111048118
· Repeat reports caught, by ward, in a four-week test against the manual list. n=111 repeat reports among 416 issues, four weeks to Fri 2 Oct 2026. Source: customer request system and channel exports, read [date]. Example data: Example Shire is fictional.

02Trace

  1. Rule drafted and tested on eight weeks of past issues
  2. Test started alongside the manual list
  3. Test ended; results above
  4. Approved and published by the Manager, Community Services

03Approval

Approved byManager, Community Services · date
Prepared by[Delivery lead], NTWRK · date