Reported time to a validated roof proposal
qualitative duration; sample not specified
Evidence
DataToday internal delivery portfolio, pages 2 and 11–12.
Baseline: Months

Extracting and validating complex technical information for source-linked answers and roof proposals.
Two document-intelligence routes share technical tests and expert validation: structured ATG extraction and source-cited knowledge answers. The source reports roof proposals in minutes rather than months, without a specified measurement sample.
Information was spread across text, complex tables and cross-document references. Experts needed reusable values and answers whose source they could inspect.
Extract technical values consistently, preserve references and validate output against expert expectations. Reuse the resulting information for technical questions and roof proposals.
Azure Functions reads ATG documents into structured extraction.
Values, tables and cross-references become reusable knowledge.
Experts test outputs against a fixed reference set.
Validated data supports roof proposals and source-linked answers.
The reported result and its evidence follow under The impact.
The ATG route reads documents with Azure Functions, extracts technical values and applies schema control. The question-answering route searches text, tables and images and supplies a cited answer. Both routes meet technical tests and Buildwise expert review against a fixed reference set. Re-uploads and overwrites are checked against the agreed structure.
The source reports validated roof proposals in minutes instead of months. It does not specify an accuracy rate or sample. Structured extraction, schema control and expert evaluation are the documented delivery mechanisms.
qualitative duration; sample not specified
DataToday internal delivery portfolio, pages 2 and 11–12.
Baseline: Months
Document intelligence earns trust through inspectable evidence and reusable structures. Expert validation is part of delivery, not an optional final check.
Telephone handling, planning, hours and contracts relied on separate systems and manual work.
Evidence status: Documented programme scope
Read the case: From disconnected operations to one intelligent enterprise.Sensor, GIS and maintenance data remained disconnected, limiting a coherent view of installations and operational needs.
Evidence status: Publicly reported scope
Read the case: Connected information for more responsive water management.40 Reporting time saved monthly
Evidence status: Publicly reported result
Read the case: Revenue insight without the monthly spreadsheet burden.Discuss how the delivery scope relates to your own priorities and operating context.