The way to keep site knowledge when experienced staff leave is to capture each of their sites (360 photos, a drone orthomosaic, or a scan), then walk that capture with them and pin what they know to the exact spot it applies to. Done while they are still on the payroll, a few hours per site, it turns knowledge that lives in one person’s head into a record on the location that the next person sees the moment they open the site.
That is the short version. The rest of this post covers why this kind of knowledge is so hard to capture, why a handover document on a shared drive fails at it, and what a practical handover looks like for a surveyor, engineer, site manager, facilities manager or mine surveyor who is about to retire.
Why is site knowledge so hard to capture?
Most knowledge-transfer advice is about process, which is easy to write down. Site knowledge is different, because it is spatial. It is an association between a place and a fact:
- “The drain near the north fence floods every winter, so don’t set up there in June.”
- “The survey mark on the east boundary was disturbed when the retaining wall went in. Use the one on the curb.”
- “The isolation valve for the north wing is behind the panel in the cleaner’s cupboard, not where the drawing shows it.”
Three things make this hard to write down.
It is triggered by being there. People do not know they know it until they are at the spot, or looking at it. Ask a retiring surveyor to write down everything about a site and you get a page. Walk the site with them and you get forty things.
Much of it is negative. What not to trust, what went wrong, what the drawing gets wrong. Official documents describe what is there. They rarely record what someone found out the hard way.
It was built up one visit at a time. Nobody asked for it to be recorded, so it exists as a mental map, and the map leaves with the person.
| Kind of site knowledge | Example | Where it usually lives |
|---|---|---|
| Hazards and conditions | Soft ground after rain, flooding, unstable edges | The person’s head; sometimes a toolbox talk |
| Hidden services and access | Where the valve really is, which gate opens, where to park | Head |
| Corrections to drawings | Pipe runs that differ from the as-built, moved survey marks | Head; occasionally a red-pen markup on a print |
| Site history | What was done in each phase and why, previous failures | Old reports, scattered across projects |
| People and relationships | Who the site contact is, which neighbor to call first | Email, phone contacts |
Everything in the right-hand column either walks out the door with the person or is filed where nobody will look.
Why do documents and shared drives fail at this?
The standard response to a retirement is an exit interview and a handover document. For site knowledge, both fail, for related reasons.
The knowledge is tied to a file, and the file goes out of date. A note in the 2019 survey report stays in the 2019 survey report. The next survey is a new file, the note does not travel to it, and within a year nobody opens the old one. Red-pen markups on a drawing are lost when the drawing is reissued.
Documents are organized by project. The next person works by place. Handover notes get written per job or per client. The successor’s first question is “what do I need to know about this site,” and nothing is filed that way.
Shared drives cannot be searched for a place. You cannot search a drive for “the drain near the north fence,” only for a filename. We covered this in why construction teams are moving spatial data off SharePoint; it is worse for knowledge than for files.
Text without a picture is ambiguous. “The drain near the north fence floods” is useless unless you already know the site. Which fence, and which of the four drains along it?
The pattern underneath all four is the same: the knowledge is about a location, and none of the usual tools are organized by location. A site record, which keys everything to the physical place and keeps it in date order, is the structure that fits.
What works: capture the site, then pin the knowledge to the location
1. Capture the site
The capture is the canvas. For most sites a 360 camera on a pole, walked through in an hour or two, is enough, and anyone can move around the result from the office. Large outdoor sites get a drone orthomosaic. Where precision matters (plant, structures, anything you will measure later), a laser scan. A recent capture from a job is fine, as long as it shows the site.
Attach the knowledge to a capture of the site rather than a drawing. Drawings show intent. Captures show what is there.
2. Pin each fact to the spot
Walk the capture with the person and record what they say at the place they say it. One fact per note. The drain gets a note at the drain. The disturbed survey mark gets a note on the mark, with a photo of the one to use instead. The valve gets a note on the panel it hides behind. “The drain near the north fence floods” becomes something a stranger can act on, because the location is the note’s address.
3. Make the notes outlive the capture
This is the part most teams miss. If the notes are attached to this year’s files, and next year’s capture is a new set of files, you have built another document that goes out of date. The notes have to belong to the place, so that when the site is captured again (next year, after the storm, at the next phase) they show on the new capture at the same spot, marked as coming from an earlier visit. Then every later capture inherits what the retiring person knew.
A practical checklist for capturing a retiring person’s site knowledge
The same sequence works for a surveyor with thirty sites or a facilities manager with three buildings.
- List their sites. Every site they are the go-to for, ranked by how often the team will return and how much of what matters there lives only in their head.
- Capture each site before they go. 360 walk, drone, scan, or whatever recent capture exists. Have it ready before the session, so the time with them goes on what they know.
- Walk the capture with them at a screen. Ask the same questions at every area: What would you tell a new starter standing here? What is wrong on the drawing? What floods, fails, moves or is hidden? What was done here before, and why? Who do you call?
- Pin every answer as a note at the spot. One fact per note, with a consistent color or icon per type: hazard, access, correction, history, contact. Attach the evidence while it is to hand: the 2014 photo, the old report, the drawing page that is wrong.
- Do one site walk in person for what the capture cannot show. Underground services, things behind walls, seasonal conditions. Photograph them and pin the photos.
- Record the people. Site contact, property manager, the neighbor to warn before a drone flight. A note at the site entrance with names and numbers beats a contacts file.
- Group the notes into lists. A new starter induction for the site. Known problems. Corrections to the drawings. Lists are how the successor will use this; a hundred loose notes are not.
- Hand it over as a walkthrough. Have the successor step through each list with the retiring person on a call and reply with questions on the notes themselves. The replies become part of the record.
- Make adding to it the habit. Assign an owner per site. Every visit after that adds a note or two, so the record stays current.
Budget two to four hours per site, plus the capture. For someone who is the go-to for twenty sites, that is a few weeks of part-time effort over a notice period, in exchange for twenty years of knowledge.
Pricing, client history and workflow habits are not spatial, and the normal handover document is the right place for them. The checklist is for the part documents fail at.
How Swyvl handles this
Swyvl is built around the site. Every upload belongs to a site, a physical place on a map, and captures sit on it in date order, so the retiring person’s sites are already the unit everything is organized by.
Geotagged 360 photos land on the site map by GPS, and connected 360s become a street-view-style walkthrough with a synced minimap, so a retiring site manager can walk the site from a desk. Orthomosaics open on the map, point clouds and scans open in the browser, and nothing needs installing.
Notes do the pinning. A note can be placed at an exact point, traced over an area, or attached to a sketch (a captured view you draw on). Each note takes a color and an icon, so hazards, corrections and history look different in the panel, and you can attach photos and documents, @mention a teammate, assign the note and resolve it. Notes work on point clouds, orthomosaics, 3D Tiles, XGRIDS scans, 360 photos, plain photos and video.
The part that matters for a handover is that notes follow the place, not the file. A note made on the March capture shows on the June capture at the same spot, drawn as a hollow pin and labeled with the capture it was made on and when. It is the same note on both, so a reply on either capture is part of the same thread. This works on captures with a known position on the ground: orthomosaics, georeferenced point clouds and scans, 3D Tiles and XGRIDS scans. Notes on a 360 photo stay on that photo, so pin the knowledge that has to last on the orthomosaic or scan of the site, and use the 360s to show what it looks like.
Lists cover the handover itself. A list can run across files, so a note on the point cloud and a note on the orthomosaic sit in the same walk, and it can be exported as a PDF or shared as a walkthrough link that steps through each note in turn. If the successor is a contractor, invite them to the share link by email; they verify with a code and can reply on notes without creating an account or taking a paid seat.
Among the firms we see, site knowledge almost always lives in people’s heads until someone retires. The free plan covers three sites and ten saved notes, enough to try the session on one site; a handover across a portfolio will need a paid plan. Files are stored in the region you choose.
The longer view
A retirement is when this problem becomes visible, but it is not really a retirement problem. People change roles, move firms and go on leave, and every site you return to has knowledge that is only in someone’s head today.
The fix is the same whether or not anyone is leaving: capture the site, pin what people know to the place, and keep doing it on every visit. Do it for the retiring person first, because the deadline is real. Then keep the habit, and the next handover takes an afternoon instead of a scramble.