Scottish Water turned capital investment reporting into a conversational data experience with Databricks Genie
Scottish Water had plenty of capital investment data. The problem was getting the right answer to the right person quickly.
Project teams often had to search through a large collection of reports—or rely on analysts and data specialists to extract information from underlying tables. That created duplicated reporting work, slowed decision-making, and made valuable project data harder for non-technical users to access.
Their answer was SPARK, an internal natural-language interface built with Databricks Genie and embedded in Microsoft Teams through Copilot.
Instead of asking, “Which report has this information?”, teams can ask questions such as:
- Which open project risks are expiring this month, and who owns them?
- What is the current live risk score for a project?
- Which risk has the highest exposure?
- Who is the future contractor for a project?
Genie translates those questions into queries against governed data in Unity Catalog, using curated gold-layer data and metric views to keep business definitions consistent.
The governance and delivery details are especially interesting:
- Business rules, fiscal-period conventions, project IDs, and milestone logic were explicitly configured.
- Worked examples and benchmark queries were used to improve and repeatedly test answer quality.
- Adoption, conversation patterns, query performance, and cost per user are monitored in production.
- Databricks Asset Bundles and Azure DevOps support repeatable deployment across development, test, and production environments.
The reported efficiency opportunity is meaningful: if 100 users ask three questions per week, saving just two to five minutes per request could recover roughly 10–25 hours every week.
The broader lesson is that conversational analytics is not just about adding a chatbot on top of raw tables. The quality of the experience depends on the foundations underneath it: curated data, shared semantics, governance, testing, monitoring, and integration into the tools people already use.
It’s a useful example of how organizations can make governed data more accessible without giving up trust or control.
What has your experience been with natural-language analytics? Does embedding it in an existing collaboration tool make adoption more likely, or do users still prefer traditional dashboards?