What was said
What this says
Current to 11 Oct 26Onboarding call with Josh Fairburn, a data analyst, to connect the incident log. The first pull worked. Severity codes and records with no home need confirming with the customer's quality team before anything is summarised.
What happened: Hamza Akhtar added the incident log connector and ran the first pull. Records loaded and the field list looked right, but severity arrives as free text in some rows and as number codes in others.
Customer view: Josh is doing this alongside his day job and apologised that the home mapping was not finished. He is about two thirds through it and will add both names for the two homes renamed after a merger.
Open points: Josh will confirm the severity codes with the quality team. A few records have no home, probably raised by head office staff, and will show as unassigned rather than be dropped.
Watch: Josh is the only customer contact on the call and the work depends on his spare time. Family contact data is the next source and its owner is not yet known.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Josh to confirm the severity code list with the quality team and finish the home mapping.
- Josh to check the refresh status page first thing on Monday and report anything odd.
- Josh to find where family contact data lives and who owns it before the next call.
Risks
Current to 9 Oct 26- Severity codes are unconfirmed, so nothing can be summarised by severity until the quality team confirms them.
- Home mapping is unfinished and depends on Josh finding time next to his day job.
- Records with no home may be dropped or miscounted if their origin is not confirmed.
Opportunities
Current to 9 Oct 26- Showing unassigned records openly supports the evidence trail the customer's quality team wants.
- Family contact is the next source to connect, which would deepen the connectors in use.