Incident history request
Email thread Corstorphine Building Society · exec
Euan Rattray asked for BB-Demo's incident history for the supplier review. After receiving the July outage review on 6 Aug 2026, he said on 10 Aug 2026 that he would keep the finding open until corrective actions are evidenced.
What was said
What this says
Current to 13 Oct 26Euan Rattray asked for BB-Demo's incident history for the supplier review. After receiving the July outage review on 6 Aug 2026, he said on 10 Aug 2026 that he would keep the finding open until corrective actions are evidenced.
Ask: Euan wanted dated incidents, root causes and how customers were told, and asked for evidence rather than a summary. Tom Ashdown sent the post-incident review and passed technical questions to Hannah Lowe.
Customer view: Euan called the review clear but asked for dated proof the corrective actions were completed, who holds standing access to the environment, and a written statement of any other material incidents.
Next: Hannah needs to answer all three points in writing. The refresh outage touches data freshness, which Enterprise is credited for.
The thread
Updated 9 Oct 26Messages
Euan Rattray 6 Aug 2026 09:35Tom, As part of our supplier review I need BB-Demo's incident history. Specifically: First, a list of material incidents affecting the service in the last year, with dates. Second, for each, the root cause and what was changed afterwards. Third, how and when customers were told. I am aware of the refresh outage in July. Please evidence what happened rather than summarise it. A written post-incident review would be the most useful thing to see. Euan Rattray
Tom Ashdown 6 Aug 2026 10:45Hi Euan, Thanks for being so specific, it makes this much easier. The post-incident review for the July refresh outage is attached. It is the document we wrote for customers at the time, and it sets out the timeline, the cause and the changes we made afterwards. I've copied Hannah, who will be able to take any technical questions on it properly. I'm not the right person to interpret the detail and I don't want to paraphrase it badly. On the wider list of incidents over the year, I'd rather not answer from memory. Hannah will confirm what we can send you in writing, and I'll make sure it reaches you. Best, Tom- Euan Rattray 10 Aug 2026 14:57Tom, Thank you for the review. I have read it. It is a clear document, but it leaves several things open for me: First, please evidence that the corrective actions listed were completed, not just planned. A dated confirmation would do. Second, who has standing access to the environment that the refresh runs in, and how is that access reviewed? Third, you have sent one review. What is the incident history beyond it? If there is nothing else material, please say so explicitly in writing. I will keep this finding open until I have those. Euan Rattray