Use case

How do I turn one delivery into ongoing work?

Deliver into a site, not a folder. Every capture you upload lands on the same site as a dated collection, so the client keeps one link, under your logo, that fills up with each visit. When they need the next survey, the record and the relationship are already there.

Every job starts a new folder. Every folder ends up lost.

The client remembers the site. They do not remember which surveyor did it last time.

Last year's survey of the same site lives on a replaced laptop.

When the next job comes up, nobody, including the client, can find what was captured before, or who captured it.

A site is permanent.

March, June and September sit on one site as dated collections. The client keeps one link. The next job starts from what is already there, under your name.

The client forgets who did the last survey.

A Dropbox link carries Dropbox's name. A hard drive carries nothing.

Your logo on every visit, and a digest when they come back.

Branded links on every delivery. Every view is logged, and a weekly digest tells you when the client opens the site again, which is usually the moment they need something.

Progress means opening two files side by side and guessing.

Two orthos in two folders, no common reference, no way to check a stockpile or a wall without software.

Open March and June from the same site and measure what changed.

Every collection is dated. Open two captures from the same site, measure the same wall or stockpile on each, and the client can do the same on the link.

A Swyvl share link as the client opens it: an example survey delivery with the orthomosaic, 3D Tiles, an Xgrids scan, the point cloud, drone video, a site photo, the report and a site plan, grouped into a June and a March visit, each file with view and download buttons
Two visits on one share link, June and March, each a dated collection. The next visit lands beside them.

What builds the record

Anything you capture, from any tool, on the same site.

Drone orthomosaicsPoint cloudsLaser scansXgrids captures360° walkthroughsDrone videoPhotosDrawings and reports

In practice

An environmental consultancy running monitoring programmes

The same sites are visited again and again. Each visit lands as a dated collection on the site, so the record of a location builds over the life of the programme instead of scattering across project folders.

A real Swyvl account. Name withheld.

How it works

1

Create the site once

A physical location with an address and coordinates. It outlasts the job, the crew and the contract.

2

Deliver every visit into it

Each upload becomes a dated collection on the site. Nothing gets renamed, refiled or lost.

3

The client keeps one link

Set it to include future uploads and every new visit appears on the link they already have. Your logo, every time.

Nine in ten Swyvl share links get opened by the client. Free to start, no credit card.

Deliver into a site. Keep the client.

Free to start. No credit card required.

Get started free

Questions people ask first

What is a site record?
A permanent, dated history of one physical place: every capture, from every visit, anchored to the site rather than to a job or a folder. Read the explainer linked below.
Does the client see the history?
A share link set to include future uploads shows each new collection as it lands, so the client's one link fills up over time. In your workspace the site's timeline lays the collections out by date.
Can I hand the site to the client later?
Invite them as an editor, or they can hold the workspace and invite you as the contractor. Either way the record stays with the site, and access can end when the contract does.
Does an old link keep working?
Yes. Share links do not expire, and the activity log of who opened what is kept for two years.

Related: What is a site record? · For asset owners · Client sharing and share links · Why surveyors are ditching Dropbox · All use cases · What to look for