What was said
What this says
Current to 11 Oct 26Paul Rigby chased a high-priority ticket on repairs still double-counted. Callie Brennan found the extract carries a line per status change and will key on job reference, keeping the latest line. Paul wants it counted once.
What happened: Paul showed the repairs dashboard still counting jobs more than once and cited his ticket, which had gone a day without reply. Callie accepted the delay and said the first refresh had landed cleanly and the counting error was her mapping.
Cause and fix: The sample showed one line per status stage, each treated as a separate repair. The fix keys repairs on job reference, keeps the latest status and retains earlier lines as history.
Customer view: Paul is patient but pointed, and Helen was absent with board papers. Adding users waits until the numbers have held for a few days.
Watch: The extract changed after the housing system upgrade and IT do not always say when. Whether a cancelled and re-raised job counts as one repair or two is open with Helen.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Callie to change the repairs mapping, test it on Paul's sample and send the repairs setup note.
- Paul to check his list of known wrong jobs before stand-up and send any refs still doubled.
- Callie to put the cancelled and re-raised question to Helen and brief Natalie on the extract change risk.
Risks
Current to 9 Oct 26- A ticket went a day without a reply, which strained patience with a user who is the day-to-day admin.
- IT changes to the housing system extract can break the mapping without warning.
- Helen was absent and the cancelled versus re-raised definition is unresolved, so board figures may still be questioned.
Opportunities
Current to 9 Oct 26- Once the numbers hold, Callie can run a walkthrough for the first small group, with sources shown for each figure.
- The setup note builds Paul's ability to run the brain himself.