How do construction teams create a single source of truth for site data?
TL;DR: A single source of truth for construction site data means one agreed, current version of drone surveys, site photos, and inspection records that every team references — instead of each team keeping its own copy. Building one requires a shared platform, a named owner, and rules for what counts as current, not just a shared folder.
Key takeaways
- According to Autodesk and FMI, poor project data and miscommunication cause 48% of all rework in the US construction industry, costing $31.3 billion in 2018 alone.
- Construction workers spend approximately 35% of their time — nearly two full working days per week — searching for project information or resolving conflicts caused by outdated data, according to the same Autodesk and FMI research.
- A separate Autodesk and FMI study estimated that bad data cost the global construction industry $1.85 trillion in 2020.
- According to IBM's Institute for Business Value, 77% of respondents say data silos hinder their organization's ability to perform real-time analytics and make data-driven decisions, and 83% believe silos undermine innovation.
- A single source of truth is a governance decision, not a storage decision — it depends on ownership and update rules as much as on the platform used.
What does "single source of truth" actually mean for site data?
A single source of truth for construction site data is one current, agreed version of the drone surveys, site photos, and inspection records that describe actual site conditions — a version every team references instead of keeping a personal copy. It answers a specific question: if two people check the same location, do they see the same thing?
The term gets used loosely. Many teams call a shared drive or a project management tool their single source of truth, but a shared location is not the same as a single source of truth. A folder that contains three versions of last week's drone survey, uploaded by three different people, is a shared location with no agreed current version — which is the opposite of what the term is meant to solve.
A true single source of truth has three properties: there is exactly one version that counts as current, everyone who needs it can reach it without depending on a specific person, and it is clear who is responsible for updating it. Miss any one of these and teams fall back to asking each other directly, which is the behavior a single source of truth is supposed to replace.
Why do construction teams end up without one?
Construction teams end up without a single source of truth because site data is produced by different people, in different formats, on different schedules — and nobody owns the job of reconciling it. The gap is organizational before it is technical.
A surveyor delivers a drone survey as a GeoTIFF attached to an email. A site foreman photographs a defect and texts it to the project manager. An inspector logs an observation in a form that never gets linked back to a location on the map. Each of these is a reasonable way for that person to do their job — but none of them produces a shared, current record that anyone else can rely on without asking around.
According to Autodesk and FMI's Construction Disconnected report, construction workers spend approximately 35% of their time on non-productive activities, including searching for project information and resolving conflicts caused by miscommunication or outdated data. That figure is a direct consequence of not having a single source of truth: when nobody can say with confidence which version of the site record is current, people default to double-checking, which is slow and still sometimes wrong.
The IBM Institute for Business Value found that 77% of respondents say data silos hinder their organization's ability to perform real-time analytics and make data-driven decisions, and 83% believe silos undermine innovation. Construction is a particularly acute case because the underlying reality — the physical site — changes daily, so a silo that was only slightly out of date last week can be badly wrong this week.
What actually needs to live inside a single source of truth?
A single source of truth for site data needs to hold drone and aerial survey outputs, site photographs, and inspection or observation records — the three data types that describe physical site conditions rather than project administration.
Drone and aerial survey outputs — orthomosaics, digital elevation models, point clouds, and 3D meshes — are the highest-value input because they are georeferenced and timestamped by default. The risk is treating each survey as a one-off deliverable rather than a layer in an ongoing record. A single source of truth needs every survey to sit alongside the ones before it, not replace them.
Site photographs are the hardest to bring in cleanly because they are captured by the most people, on the least standardized equipment. A phone photo has GPS and timestamp metadata embedded automatically, but that metadata is only useful once the photo is uploaded somewhere it can be searched by location and date — not left in a personal camera roll or a group chat.
Inspection and observation records — defect logs, safety observations, quality hold points — earn their place in the single source of truth only when they are tied to a location on the map or a specific survey date. An inspection record with no spatial reference is a note in a database; pinned to a location, it becomes part of the shared picture everyone else is working from.
What does not need to be in this specific single source of truth: contracts, RFIs, submittals, and design drawings. Those belong in formal document control, often a Common Data Environment (CDE) built for ISO 19650 compliance. Site data and document control solve related but different problems, and conflating them is a common reason single-source-of-truth projects stall — the scope becomes too broad to govern well.
How do you actually build one?
Building a single source of truth for site data starts with naming an owner, not choosing a platform. Software makes the rest of the work easier, but it cannot substitute for a decision about who is accountable for the record being current.
Name an owner before the first upload. Someone — often a site manager or project coordinator — needs to be responsible for site data being current, correct, and accessible. Without a named owner, currency decays the moment the person who happened to upload the last survey moves on to something else.
Agree what "current" means, in writing. A rule as simple as "the most recent survey for each date range is the one displayed by default, and older surveys are archived but not deleted" removes the ambiguity that causes teams to keep private copies "just in case."
Standardize naming and location before work starts, not after. A convention covering area, date, and data type — applied from day one — prevents the situation where three files are all called "site-survey-final."
Put it somewhere people without specialist software can open it. Drone outputs and point clouds are typically delivered in formats like GeoTIFF, LAZ, or GLB, which require specialist software to view. If the single source of truth can only be opened by the people who have that software installed, it has not actually solved the access problem — it has just moved the bottleneck. Platforms that render these formats in a browser, with shareable, view-only links, remove that barrier for project managers, owners, and clients who are not going to install GIS software.
Retire the workarounds. A single source of truth only works if it replaces the group chat and the personal folder, not sits alongside them. This is a change-management task as much as a technical one — it typically takes active follow-up for a few weeks before field teams stop defaulting to the old habit.
How do you keep it accurate once it exists?
A single source of truth stays accurate through routine, low-effort updates, not through one large setup effort. The record degrades the moment uploading becomes a task people postpone.
The most reliable pattern ties updates to an event that is already happening — a drone survey is flown, a site walk occurs, an inspection is completed — rather than to a calendar reminder that competes with other priorities. If uploading a survey or a set of photos is a two-minute task that happens as the last step of something the field team is already doing, it gets done. If it is a separate errand for later, it slips.
Version control matters more for site data than for many other project records, because two surveys of the same area a week apart are both potentially useful — one shows current conditions, the other shows the rate of change. A single source of truth should keep both accessible with a clear indication of which is current, rather than overwriting the earlier one.
Access review is the part most teams skip. As subcontractors and consultants rotate on and off a project, access to the site data record should be updated at the same time as their site access — otherwise the "single" source of truth quietly develops a shadow copy in whatever tool the departed team member left behind.
How should you choose a platform to support this?
The right platform for a single source of truth is one that field teams will actually use daily and that non-technical stakeholders can open without training — because a single source of truth that requires effort to access will always lose to the group chat.
For teams whose site data is primarily drone surveys, photographs, and location-based inspection records, a geospatial collaboration platform is usually a better fit than trying to force this data into a general document management system built for drawings and contracts. Birdi, for example, lets teams process raw drone imagery or upload already-processed outputs directly to a shared project map, where each new survey sits as a layer alongside the ones before it, comments can be pinned to exact locations, and clients or owners can view the current record through a shareable link with no sign-up required. Mirvac, one of Australia's largest construction groups, reported saving 32 hours per site per month on progress reporting after centralizing drone outputs this way. Teams that also need formal document control for drawings, RFIs, and submittals will still need a dedicated CDE alongside a geospatial platform — the two solve different problems, and a platform built for one is rarely a good substitute for the other.
Whichever platform you choose, the ownership and update rules from the previous section matter more than the feature list. A well-governed single source of truth on a simple platform beats a poorly governed one on an enterprise system.
Frequently asked questions
What is a single source of truth in construction?
A single source of truth in construction is one agreed, current version of a specific type of project information — for site data, this means drone surveys, photographs, and inspection records — that every team references instead of keeping separate copies. It requires an accessible platform, a named owner, and clear rules for what counts as current. A shared drive alone does not create one unless those governance elements are also in place.
Is a Common Data Environment the same as a single source of truth for site data?
Not exactly. A Common Data Environment (CDE) is a formal repository for the full project record — drawings, models, contracts, and correspondence — usually built for ISO 19650 compliance. A single source of truth for site data is narrower in scope: it covers the visual and spatial record of physical site conditions. Many construction projects need both, run as separate but complementary systems.
Who should own the single source of truth on a construction project?
Ownership usually sits with a site manager or project coordinator who is accountable for the record being current and accessible, not necessarily the person who captures the most data. The owner's job is to enforce naming conventions, confirm which version is current, and manage access as the project team changes — not to personally upload every survey or photo.
How is a single source of truth different from a shared folder?
A shared folder is a location; a single source of truth is a governance model. A shared folder can contain multiple conflicting versions of the same survey with no indication of which is current — the opposite of a single source of truth. The difference is whether there are agreed rules for what counts as current and who is responsible for keeping it that way, not where the files happen to sit.
How long does it take to establish a single source of truth for site data?
Most teams can put the basic structure in place — a platform, a named owner, and a naming convention — within a week. The harder part is behavioral: it typically takes several weeks of active follow-up before field teams stop defaulting to text messages and personal folders and start treating the shared platform as the default. Projects that skip this follow-up period often end up with a single source of truth that exists on paper but is not actually where the current data lives.
Sources
- Autodesk and FMI. "Construction Disconnected: The High Cost of Poor Data and Miscommunication." Autodesk Digital Builder, 2018. https://www.autodesk.com/blogs/construction/construction-disconnected-fmi-report/
- Autodesk and FMI. "Study from Autodesk and FMI Finds Better Data Strategies Could Save the Global Construction Industry $1.85 Trillion." Autodesk, 2021. https://investors.autodesk.com/news-releases/news-release-details/study-autodesk-and-fmi-finds-better-data-strategies-could-save
- IBM. "What Are Data Silos?" IBM Think, 2025. https://www.ibm.com/think/topics/data-silos