Not ratings. Named work, named friction.
These notes come from people who had to take a pack into a room. One of them still wanted more on depot codes. That gap stayed in the method page.
The pack arrived with the maps folded so they sat on the blotter, which sounds petty until you have watched members tilt laptops. We could follow missed repairs by estate without Miriam in the room. I still wanted a longer note on why two parishes share a depot code; that gap is printed in the method page, to her credit, rather than smoothed over.
The afternoon was uncomfortable. The contact-centre supervisors and the waste supervisors described the same “escalation” as two different acts. We left with a disputed-steps list instead of a neat ribbon. That list is now on the wall in the hub, which is more honest than the process poster we had before.
Our group asked for every ward at once. Desktop Pathline refused until we confirmed the boundary set after the review. The wait annoyed two members and saved us from issuing packs that named streets now in the neighbouring ward. The supermarket-queue questions have not stopped; they have become shorter.
File 4 was a damp cluster that had been recoded twice. The timeline showed the recodes as breaks, not as progress. I used the gap list in the stage-two letter. I would not ask them to draft the letter; that is our job, and they would not have taken it.
A working-group afternoon in Lancashire
A district chair asked for missed repairs by estate, with the maps folded to the blotter. The pack held. The remaining argument was a shared depot code across two parishes — printed, not hidden. We now ask for depot-to-parish tables at scoping when housing and waste share a yard.
A hub that would not agree what “escalation” meant
The mapping workshop did not produce a ribbon diagram. It produced a disputed-steps list now pinned in the customer hub. That is a poorer poster and a better record of how a citizen request actually moves between waste and the contact centre.
