Case study / Digital Construction
HoloBuilder: Progress Capture Intelligence Across a Major Construction Portfolio
Background
A 360-degree progress capture platform deployed across a major portfolio — with no way to see how consistently it was being used.
HoloBuilder is a cloud-based platform for construction progress capture — enabling project teams to record 360-degree photographs, link 2D images to locations, and build a structured visual record of a project's delivery. For a leading tier 1 contractor, HoloBuilder had become the standard tool for progress capture across the portfolio, supporting remote progress monitoring, design comparison and the evidencing of fire safety and building safety elements increasingly required by standards including BS EN ISO 19650.
The platform was deployed but its use was uneven. An internal policy required progress captures to be made on a weekly or fortnightly basis, with 360-degree images captured across the full build to maintain a continuous audit trail. But HoloBuilder's native reporting could not tell the business whether projects were meeting that requirement — which business units were maintaining consistent capture cadences, which projects had gone weeks without a capture, or how broadly the tool had been adopted across the portfolio. Acumine was engaged to build the reporting platform that made progress capture performance visible.
Capture compliance policy with no compliance monitoring
Internal policy required project teams to make progress captures weekly or fortnightly, with 360-degree images maintained across the full build regardless of change. But HoloBuilder's native tools could not surface which projects were meeting this cadence and which had fallen behind — making the policy unenforceable in practice without significant manual investigation by digital construction managers.
Portfolio adoption invisible to leadership
HoloBuilder had been deployed as the standard progress capture tool, but understanding how actively it was being used — across business units, regions and individual projects — required direct access to the platform. There was no aggregated view of weekly capture rates, active project counts, total image volumes or user engagement that leadership and digital construction teams could access without navigating HoloBuilder directly.
Data quality issues undetectable at scale
HoloBuilder projects relied on consistent metadata — valid project naming, GIFA (gross internal floor area) values, client attribution and business unit alignment — for regional reporting to work correctly. Without a systematic way to surface projects with missing or invalid metadata across the portfolio, data quality issues were only discovered when reports produced incorrect results, by which point correcting them required significant rework.
Limited native reporting not suited to portfolio oversight
HoloBuilder's built-in reporting was designed around individual project visibility — giving project teams a view of their own captures, locations and image counts. It was not designed to aggregate performance across dozens of live projects, compare business units against each other, track compliance with a portfolio-wide capture policy, or surface the data quality signals that a centrally managed deployment required.
What HoloBuilder captures
Structured progress capture data across locations, image sheets and users — project by project, with no portfolio view.
HoloBuilder holds a detailed, structured record of every capture made on every project — 360-degree images organised by floor plan, location and date, alongside user activity logs and project metadata. Acumine connected to the HoloBuilder API via an Azure Data Factory pipeline, structured this data into a governed reporting model, and surfaced it in Power BI across six report pages.
Progress captures
360-degree images by project, location and week — the complete capture record
Every capture in HoloBuilder was associated with a project, a floor plan, an image sheet and a specific location within that sheet — giving the reporting layer the structure to calculate location utilisation, image sheet coverage and capture frequency at project, business unit and portfolio level. Cumulative capture volumes and week-by-week trends enabled both current-state and historical performance views.
Capture compliance
Frequency of captures against internal policy — by project across its lifetime
HoloBuilder's data model recorded when each capture was made — enabling the reporting layer to calculate compliance with the business's weekly and fortnightly capture policy across each project's full lifetime. Both weeks-captured compliance and image-sheet-capture compliance were tracked, giving digital construction managers a structured basis for identifying which projects were maintaining the required cadence and which were falling behind.
User activity
Internal and external users — activity volumes, roles and adoption across business units
HoloBuilder tracked who had uploaded images and when — distinguishing internal users (by email domain) from external supply chain contributors. This user-level data powered the adoption reporting layer, enabling comparisons of active user counts, upload volumes and engagement rates across business units and over time — and surfacing the top contributors by image volume across the portfolio.
The solution
A six-page Progress Capture Report covering portfolio performance, compliance, project detail, data quality and user adoption
Acumine built an Azure Data Factory pipeline connecting to the HoloBuilder API — pulling capture, location and user data across all live projects and structuring it into a governed Power BI reporting model. The six-page report gave different audiences the view of progress capture performance they needed, from a portfolio summary for leadership to project-level detail for digital construction managers and a data quality view for system administrators.
Progress Capture Summary
Portfolio-level capture health at a glance
The summary page provided an immediate, high-level view of progress capture performance across all live projects — with key indicators covering the percentage of image sheets captured, overall location utilisation, user activity levels and a portfolio health check. Designed for senior leadership and digital construction leads, this page gave the quickest possible read on whether the portfolio was maintaining the capture standards the business required.
Business Unit Overview
Regional adoption and capture performance — compared across business units
The business unit overview gave regional leads a structured view of HoloBuilder adoption and usage within their area — total active projects, weekly capture rate, 360-degree image volumes by region, percentage of locations captured, and five summary counters covering active projects fully captured, total locations, image counts, internal user activity and external user engagement. This enabled consistent comparison of regional performance and helped identify which areas needed support in maintaining capture standards.
Capture Performance
Compliance with the capture frequency policy — across every project's lifetime
The capture performance page was the compliance monitoring view — showing projects captured in the last week by business unit, image sheets captured last week, and two lifetime compliance measures: overall compliance with the required capture frequency (weeks captured) and overall compliance with image sheet coverage across the project life. Supporting counters tracked active projects, open and active issues, supply chain versus direct engagement, resolution performance for high-priority items and deadline management — giving digital construction managers the data to hold project teams to account against the capture policy.
Project Overview
A single project's capture history — week by week from start to current
The project overview page allowed digital construction managers and project teams to drill into the full capture history of a selected project — with a cumulative chart of 360-degree images by week, image sheets captured per week, active locations and 360-degree images in image sheets, and locations captured per week. Six counters provided at-a-glance project context: date of last capture, date of last image upload, total captures, total 360-degree images, and active internal and external user counts for that project.
System Administration
Data quality across all projects — surfacing metadata issues before they affect reporting
The system administration page gave HoloBuilder administrators a structured view of data quality issues across the portfolio — with four configurable filters focusing on invalid project naming, missing or invalid GIFA values, projects with no capture activity in the last four weeks, and projects with no client name recorded. A supporting table listed by office the number of projects qualifying for each issue, and a separate view highlighted projects not aligned to a business unit — which directly affected the accuracy of regional reporting.
User Adoption
Who is using HoloBuilder, how actively, and where across the business
The user adoption page tracked platform engagement across the full user base — with the percentage of activated users active in the last 30 days, total users by business unit, a per-user activity breakdown by role showing 360-degree images uploaded, and a top-ten users ranking by image volume. This gave digital construction leaders a clear view of where HoloBuilder was embedded in day-to-day project practice and where uptake remained limited — enabling targeted support and training decisions.
Outcomes
Progress capture performance intelligence that HoloBuilder alone could not provide
Capture compliance policy enforceable for the first time
With the capture performance page tracking both weeks-captured compliance and image-sheet compliance across every project's lifetime, digital construction managers had a structured, evidence-based view of which projects were meeting the business's weekly and fortnightly capture requirements — and which were not. The compliance monitoring that had previously required manual investigation became an automated, always-current view available to anyone with access to the report.
Portfolio adoption visible to leadership without navigating HoloBuilder
The summary and business unit overview pages gave leadership and regional directors a consistent, always-current picture of HoloBuilder adoption and capture activity across the portfolio — active project counts, weekly capture rates, image volumes and user engagement — without requiring them to log into HoloBuilder directly. Regional comparisons that had been impossible became straightforward, enabling more targeted conversations about where deployment standards needed to be raised.
Data quality issues surfaced and resolved proactively
The system administration page transformed data quality management from a reactive discovery process into a proactive, continuous monitoring activity. Invalid project naming, missing GIFA values, absent client attribution and business unit misalignment — all of which affected the accuracy of regional reporting — were surfaced systematically, giving administrators a clear remediation list rather than discovering problems only when reports produced incorrect aggregations.
More insightful reporting than the platform could provide natively
The six-page Progress Capture Report delivered reporting depth that HoloBuilder's native tools were not designed to provide — combining capture compliance, adoption analytics, project-level history, regional benchmarking and data quality monitoring in a single, governed Power BI environment. HoloBuilder's subsequent designation as a strategic tool for the business reflected confidence in progress capture as a well-managed, reportable discipline rather than an inconsistently applied technology.
Technology
HoloBuilder progress capture data structured via Azure and surfaced in Power BI
The solution connected to the HoloBuilder API via an Azure Data Factory pipeline — handling a complex authentication flow and structuring capture, location and user data across all live projects into a governed Power BI reporting model. The six-page Progress Capture Report was delivered in Power BI, with filtering across business unit, project, date range and user type, and regular refresh ensuring all views reflected the current HoloBuilder position across the portfolio.
Progress capture is an increasingly important discipline for tier 1 contractors — supporting building safety evidencing, client reporting obligations and remote progress monitoring across large project portfolios. If your business uses HoloBuilder and lacks a structured view of capture compliance, adoption performance and data quality across your portfolio, Acumine can build the reporting platform that makes it visible.
Work with Acumine
Using HoloBuilder and missing portfolio visibility of progress capture performance?
If your projects are capturing 360-degree progress images in HoloBuilder but your digital construction and leadership teams have no consistent view of capture compliance, business unit adoption rates and data quality across the portfolio, Acumine can build the reporting platform that connects it — surfacing the performance intelligence HoloBuilder alone cannot provide.