A heritage agency managing a portfolio of listed buildings sits in an unusual spot. The work is high-stakes — irreplaceable cultural assets, statutory obligations, public scrutiny — but the documentation infrastructure supporting it is, in most cases, whatever shared drive was set up a decade ago plus a Dropbox account someone created during the pandemic. The asset is national heritage; the file management is the same as a small consulting firm.
That’s a gap worth closing, and it can be closed without enterprise-scale procurement or a five-year IT project.
The portfolio scale problem
The shape of the problem changes dramatically with portfolio size. A conservation architect looking after one building can hold the documentation in their head and on a project drive; a small council managing a dozen sites can get by with disciplined folder structures. But a state-level or national heritage agency typically manages somewhere between 50 and 500 listed properties, often distributed across multiple regional offices, with documentation contributed by:
- Internal heritage officers doing inspections and condition assessments
- External conservation architects working on specific properties
- Restoration contractors documenting work in progress
- Specialist scanning firms producing point clouds and photogrammetric models
- Volunteers and historical societies contributing archival material
- Tourism teams capturing 360° tours and promotional imagery
- Planning officers handling development applications adjacent to listed sites
Six or seven contributors per site, hundreds of sites, decades of accumulated material. The volume isn’t the problem — modern cloud storage handles it easily. The problem is organisation. After ten years of contributions distributed across regional offices, no single person can answer “what do we have on this property?” with confidence.
What documentation actually needs to capture
A useful heritage record for a single listed building usually contains:
- Original heritage listing documents — significance statement, listing inventory, historical research
- Periodic condition surveys — inspection reports with photos, often quarterly or annually
- Restoration and conservation work records — before, during, and after photos of every intervention
- Architectural drawings — measured surveys, conservation management plans, proposed works
- 3D records — point clouds from terrestrial LiDAR, photogrammetric models, occasionally Gaussian splats for high-value detail
- Aerial documentation — drone orthomosaics for context, condition records of roofing
- Archival material — historical photographs, original construction drawings, oral history audio
- GIS data — boundary polygons, archaeological zones, view corridors, planning constraints
- Compliance and grant records — funding agreement documentation, statutory consents, inspection certificates
The list is long but the underlying need is simple: the ability to ask “show me everything on this property” and get a coherent answer organised by time.
For background on the spatial formats that increasingly appear in heritage documentation, see how 3D mapping is transforming cultural heritage and what is LiDAR.
Where shared drives fall short
Most heritage agencies are running on some combination of SharePoint, a network file share, and ad-hoc cloud accounts. The system mostly works for documents — Word files, PDFs, CAD drawings — but breaks down across four areas.
Spatial data is invisible
A point cloud from a 2024 LiDAR scan sits in a folder as a 4 GB LAS file. Nobody on the conservation team can open it. The scan was commissioned at significant cost, and unless someone produces a video walkthrough or a series of screenshots, it goes unviewed.
Same for orthomosaics. Same for 3D photogrammetric models. Same for IFC files from BIM teams. The more sophisticated the spatial data, the less likely it is that the heritage officers who need it can actually see it.
No portfolio-level view
Each property tends to have its own folder, but there’s no easy way to ask portfolio questions. Which properties have had a condition survey in the last 24 months? Which have outstanding restoration grants? Which have 3D scans on file? These questions require either a separate spreadsheet that someone maintains by hand, or a sustained spelunking expedition through the file shares.
Public and stakeholder access is awkward
Heritage agencies frequently need to share material with people outside the organisation: tourism partners, researchers, descendants of original owners, community groups, the public. The default mechanisms — emailing zip files, granting SharePoint guest access, creating public Dropbox links — are clumsy and provide no audit trail. Most agencies end up sharing far less than they should because the friction is too high.
Records can be modified without trace
Heritage records sometimes need to be defensible against challenge. When a planning dispute hinges on the documented condition of a building before alterations, the record needs to be demonstrably unaltered. Generic file storage can be made to support this with enough configuration, but the default behaviour is permissive — anyone with edit access can replace, delete, or modify files without leaving an obvious trail.
What a purpose-built heritage record looks like
A platform built around the site record concept addresses each of these gaps, and a few others.
One site per property
Every listed building, archaeological site, or culturally significant area becomes a site in the platform. The site has an address, geographic coordinates, and a permanent identity that persists across personnel changes, contractor changes, and reorganisations. Every contribution to that property — from anyone, at any time — is filed against the site.
A 200-property portfolio becomes 200 sites on a map. Heritage officers can visually browse the portfolio, click any property, and see its full record.
Time-indexed sessions
Every capture is grouped into a session — the natural unit of “everything from this inspection on this date.” Five years of quarterly inspections produces 20 sessions, sortable chronologically. The conservation team can pull up the property in 2022 and 2026 side by side and see what’s changed.
For restoration work, this is particularly valuable. Each phase of work — pre-intervention, during, post-intervention — becomes its own session, providing the before/during/after record that grant funders, statutory bodies, and successor conservation teams will all reference for the rest of the building’s life.
Browser viewers for every format
This is the change that unlocks the spatial data sitting unused on existing shared drives. Point clouds load in a browser-based 3D viewer; the conservation team can orbit around a Victorian gable, measure the masonry, and reference the scan during planning meetings. Orthomosaics display on a map. 3D photogrammetric models render in browser-based viewers. IFC models from BIM consultants display without anyone needing Revit. Gaussian splats — the new generation of photoreal 3D capture — display with full fidelity.
The data was always there. Now it can be used.
Audit trail and immutability
Every access event — view, download, modification — is logged with timestamp, IP address, and approximate location. When the question becomes who saw what and when, the answer is in the activity log. When records need to be defensible against later challenge, the immutable history of contributions provides the chain of evidence.
Public sharing via branded links
Each site can be shared via a branded link that opens in any browser, with no account creation required. The agency’s own branding appears on the share page, not the platform’s. Access can be controlled with optional passwords, expiry dates, and download permissions per link.
This makes the public-facing dimension of heritage work much easier to support. A tourism partner can be given access to the public-facing material for a property without any access to internal condition reports. A researcher writing a doctoral thesis can be given access to a curated subset for a fixed period. A community group can be given access to the historical photographs for an interpretive project. Each share is scoped, audited, and revocable.
Compliance and grant reporting
Heritage funding programmes — government grants, lottery funds, philanthropic awards — typically require documented evidence of work undertaken. The reporting burden falls on the agency or the conservation contractor, and the documentation requirements have only grown over time.
A site record makes the reporting straightforward. The grant reporter pulls up the relevant property, selects the relevant time window, and exports the captures from that period. The before/during/after documentation is already in chronological order. The funder receives evidence that’s both comprehensive and verifiable.
For agencies subject to statutory reporting — heritage councils, planning authorities, audit offices — the same record supports those obligations. The data exists in a form that can be selectively exported, audited, and verified, without requiring a forensic data archaeology project for every report.
The public access angle
Heritage agencies have a public mission as well as a custodial one. The same documentation that supports conservation decisions also has value for tourism, education, research, and public engagement.
A site record makes this dual use natural rather than awkward. The same captures that the conservation team uses for technical decisions can be presented to a wider audience via a public-facing share link, optionally with curated commentary, restricted to the appropriate subset of material. Tourists can take a virtual tour of a 360° capture of the interior. Researchers can examine high-resolution photogrammetric models. Schoolchildren can compare historical photographs with present-day captures.
None of this requires duplicating the data into a separate public-facing system. The same record serves both audiences with appropriate access controls.
For more on how this delivery model works, see Swyvl for heritage.
Getting started
Most heritage agencies don’t transition the entire portfolio at once. The pattern that works is:
- Pick five to ten properties — ideally a mix of high-traffic, high-significance, and currently-active sites.
- Set them up in the platform with their existing records ingested. Don’t backfill exhaustively; bring in what’s actively referenced.
- Route new contributions through the platform. Inspectors upload after each inspection. Contractors upload as work progresses.
- After a quarter, evaluate. Most agencies discover that the structure has paid for itself in time saved on a single grant report or a single planning enquiry.
- Expand to the rest of the portfolio in tranches, prioritising the properties with the most active documentation.
The ten-year payoff is the part that matters most. A heritage record that has been actively maintained for ten years is, for most purposes, irreplaceable. The agencies that start the clock now are the ones that will have those records when the next generation of conservation work needs to reference them.
The work that goes into the record today is work that compounds for as long as the building stands.