Two months after a wall is closed, someone asks a simple question: where does the pipe run? Someone remembers taking a photograph. Another person finds an image in a WhatsApp group. But nobody is sure which room it shows — or whether it captures the final condition before closure.

The problem is not a shortage of cameras. It is the time required to find a dependable answer, and sometimes the fact that the answer was never recorded.

Clients do not want to manage 360. They want answers. A panoramic tour is a means to that end. Its value comes from connecting what is visible to the right place, the right date and the question that needs answering.

In this article

Six problems documentation needs to solve

1. No accessible memory of concealed work

Pipes disappear into walls. Ducts disappear above ceilings. Waterproofing is covered, sleeves are embedded in concrete and infrastructure is buried under backfill. Once concealed, the earlier condition may be difficult to inspect without additional work.

Pre-close documentation can preserve what was visible at capture time. To be useful, it must be clear, located and dated, and show the relevant detail. A photograph of a room is not necessarily adequate documentation of a small connection within it.

2. The photographs exist, but nobody can find them

Phones, email, cloud folders and messaging groups may hold thousands of images. Without a floor, room, viewing direction and date, retrieval becomes guesswork.

The issue is not just image quantity. It is context. A capture point connected to an identified area lets a team start from the place in question rather than trying to remember who photographed it.

3. Disagreements begin with different memories

“We installed it before closure.” “The damage happened later.” “The pipe was somewhere else.” Relevant imagery may help investigate these questions.

A dated visual record can provide a shared basis for review. It does not by itself establish responsibility, prove what was outside the frame or guarantee legal admissibility. Retain original files, capture information and context rather than relying only on repeatedly forwarded images.

4. Travelling to site for a visual answer

A project manager wants to check a plant room. An architect needs to understand a completed space. An inspector asks whether a ceiling has been closed. The request may trigger a journey or another “send me a picture” call.

Current documentation can support some remote enquiries, provided the relevant area and detail are visible. It does not replace a visit when physical inspection, measurement or assessment of conditions since the capture is needed.

5. Images without continuity

A single image shows a moment. Managing a project requires understanding a sequence: what was here at the start of the month, what changed halfway through it and what exists now?

When capture does not return to consistent areas, comparison becomes difficult. Switching dates is useful only when viewers can identify the same location and account for differences in viewpoint, lighting and obstruction.

6. Missing coverage discovered too late

A skipped room, a dark corner, a blurred image or an unseen ceiling void can leave a question unanswered after an entire capture round.

The important question is not only “did we capture it?” It is what did we need to record, what is actually visible, and what is still missing? Human review should happen before the area changes or is closed. A 360 tour is not, by itself, confirmation of complete coverage.

The same place on another date

Imagine the same corridor at the beginning of September, mid-month and the start of October. The value lies not in the number of panoramas but in returning to the same area and understanding how it changed.

Consistent area names, identified capture points and clear dates help build that history. Where safe and practical, repeating a route and similar viewpoints makes comparison easier.

This is the difference between a gallery and a spatial memory of a project: start with the place, choose a date and review the relevant record. Visual comparison still needs judgement; changed lighting or a different angle is not necessarily changed construction.

Documentation for insurance claim review

Builders Risk claim review is another reason to retain a site history. In its October 6, 2026 article, OpenSpace highlights pre-loss condition, location and timing after fire, water damage or theft. It also discusses potential policy conditions such as fencing, fire watch and protective systems. Its four record qualities are consistent capture, complete coverage, date and location, and retained history after concealment. Read the OpenSpace source.

These are documentation objectives, not confirmation that every tour achieves full coverage. A periodic image captures a moment; it cannot alone establish continuous fire watch or an operational protection system at the time of loss. Coverage and documentation requirements depend on the policy and circumstances and should be clarified with the broker or insurer.

Risk / Insurance Evidence Playbook

For Skylens, this suggests an additional Capture Playbook use case: define likely review questions and the records needed to investigate them before an incident occurs.

  • Requirements matrix: connect each requirement confirmed with the insurance professional to an area, owner, review time and record type. Do not assume imagery is sufficient for every requirement.
  • Gap review: explicitly identify uncaptured areas and undocumented periods rather than treating a wide-angle capture as continuous proof.
  • Supporting documents: associate relevant shift logs, inspection certificates and maintenance records with the visual material where needed.
  • Retention and access: define original-file retention, versions, permissions and retention periods. Do not describe a record as tamper-resistant without a verified mechanism.

This is a proposed procedure, not a validated Skylens insurance module. It does not promise claim acceptance, premium reductions or proof of policy compliance. The aim is to prepare an organized record for investigation, not determine its outcome.

One record, different questions

  • Project manager: what is the area’s condition without requesting more photographs?
  • Site manager: how do we document consistently without overloading the routine?
  • BIM manager: where on the plan does this view belong?
  • Inspector and QA/QC: what appears to have been completed, and what needs further inspection?
  • Developer: what record supports the progress update?
  • Subcontractor: what was recorded before my work was concealed?
  • Dispute review team: what condition was captured, where and when?
  • Future facilities team: was the service installation recorded before closure?

Four important jobs

Show me what was here before it was covered

Pre-Close Evidence starts by defining the elements that need to be visible. A panorama provides broad context; close-up photographs supplement details that cannot be adequately examined within it.

Show me this exact place on another date

Same-location history connects a place to its capture sequence. Useful history depends on consistent identification, not merely a folder named with dates.

Show me where this is in the project

Spatial context can begin with a building, floor, room and identified point on a plan. BIM linkage may add context, but requires alignment and review. A 360 image does not automatically establish reliable model correspondence.

Help me check what is missing before closure

Define required areas and details in advance, then compare that list with the resulting record. This is a Capture Playbook: a capture and review procedure. Automatic gap detection is a separate capability that must be validated, not a promise inherent in a viewer.

A pre-close checklist

  1. Define the questions: what will we need to know after concealment? Which connections, penetrations or services must be visible?
  2. Identify the place: building, floor, room or zone, and a known capture point. Record the capture date too.
  3. Assign responsibility and timing: who captures, who reviews and when is the record required relative to closure?
  4. Capture context and details: use wider views and close-ups as needed, with adequate light and safe, authorized access.
  5. Open and review the files: confirm more than a successful upload. Check that files are readable and required details are visible.
  6. Mark gaps: missing areas, obstructions and unclear details remain explicitly missing. Supplement them before closure where possible.
  7. Retain and share responsibly: define original-file retention, context, access permissions and retention periods. Documentation review is not engineering approval to close the work.

Do not turn the camera into another burden

360 capture has friction too: remembering the routine, preparing equipment, uploading large files and checking usability. Poor lighting, people in frame and obstructions do not disappear because the view is panoramic.

Start with a defined area and decision point rather than a demand to record everything continuously. Choose a manageable route, an assigned owner and questions the material must answer. Plan access and retention while minimizing exposure of workers and sensitive information.

Suggested internal measures include time to retrieve a relevant record, gaps found before concealment and the proportion of capture rounds reviewed. These are proposed process measures, not proven Skylens performance figures.

How this connects to Skylens

The approach behind Skylens Site Record is to bring repeated project documentation into an accessible viewing environment. The objective is not another panorama folder but a process that makes returning to the relevant place and date easier.

A Skylens Viewer demonstration is an opportunity to examine the workflow for your project: area identification, uploading and revisiting records. BIM correspondence, automated coverage checks and progress analysis require separate verification for the configuration and data concerned. This article does not claim that these are validated capabilities in every project.

A useful starting point is a floor or area approaching closure. Define what needs documenting, capture it, review it and try answering a real question from the material.

Before closing an area, check that there is useful documentation of what is about to disappear from view.

Frequently asked questions

Does 360 replace close-up photography?

No. It provides broad context, but small details may need dedicated photographs, additional lighting or on-site inspection.

Does a photograph prove that work is compliant?

No. It records what was visible at capture time. Quality, dimensions and compliance may require separate professional checks.

Can we start without BIM?

Yes. A process can use a building, floor, room and identified plan. Verify how that context is actually retained in the selected workspace.

How frequently should we capture?

Follow the pace of work and the questions that need preserving. Capturing before a service is concealed may be more important than a fixed schedule that misses the relevant construction stage.

Does a tour guarantee complete coverage?

No. Review the material against requirements and mark gaps even when the upload and tour themselves work correctly.

Start with the next question your team will ask

Which detail is about to disappear behind a wall, ceiling or backfill? Start there.

Book a 30-minute demo — explore a documentation process built around real questions from your project.