The Surveyor's Guide to Professional File Delivery

Professional file delivery for surveyors means your client receives a branded link, views every deliverable in their browser without installing software, and you get an audit trail of exactly who accessed what and when. If you are still zipping folders and uploading them to Dropbox, you are solving the transfer problem while ignoring the delivery problem — and it is costing you repeat business.

I have been in the spatial data industry for eight years. I have watched teams capture extraordinary LiDAR scans, process stunning orthomosaics, and then undermine all of it by dumping files into a shared Google Drive folder. The gap between capture quality and delivery quality is the biggest missed opportunity in surveying today.

This guide covers the full delivery workflow — from understanding why generic tools fail for spatial data, to building a repeatable delivery process that makes your clients want to work with you again.

The delivery problem surveyors don’t talk about

Here is a scenario I have seen dozens of times. A surveyor completes a topographic survey. They produce a LAS point cloud, a GeoTIFF elevation model, DXF contours, and a PDF report. Total: roughly 6 GB of data across four formats.

They create a Dropbox shared folder, upload everything, and email the link to the client’s project manager. Job done — right?

Three days later, the project manager replies: “I downloaded the files but I can’t open most of them. Can you just send me some screenshots?”

The surveyor has delivered the data. The client has received the data. But the client has not actually seen the data. The delivery has technically succeeded and practically failed.

This is not the client’s fault. LAS files require CloudCompare or QGIS. GeoTIFFs need a GIS viewer. DXF files need a CAD application. None of these are tools that a property developer, project manager, or asset owner has installed — or should be expected to install.

What professional delivery actually looks like

Professional delivery is not just about getting files from A to B. It is about the complete experience your client has when they receive your work. Here is what that looks like in practice:

Branded presentation

Your client clicks a link and sees your company name, your logo, and your colours — not a Dropbox interface or a WeTransfer countdown timer. This is your work. It should look like your work.

Browser-based viewing

Every file type opens in an appropriate viewer directly in the browser:

The client sees the data. They interact with it. They understand what you captured. No downloads required for viewing.

Organised by session

If you survey a construction site monthly, your client should see each capture session clearly separated — not a flat list of 200 files with date-stamped filenames. Grouping deliverables by session gives the client a timeline of the project and makes it easy to find the data they need.

Audit trail

You know exactly who accessed the link, when they opened it, what they viewed, and what they downloaded. This matters for compliance, for invoicing (“you said you never received the data”), and for understanding how your clients actually engage with your work.

Permanent access

Links do not expire after 7 days. The data is there when your client needs it — whether that is tomorrow, next month, or two years from now during a dispute resolution.

The file types surveyors deal with

One of the reasons generic file sharing tools fail for survey work is the sheer diversity of file formats. Here is what a typical survey practice produces:

Point clouds

• LAS — the standard point cloud format. Uncompressed, large files (500 MB to 5+ GB per scan)
• LAZ — lossless compressed LAS. 60-80% smaller than LAS. The format you should be delivering in
• E57 — common output from terrestrial scanners (FARO, Leica). Includes imagery and intensity data

For a deeper comparison of these formats, see LAS vs LAZ vs E57: Which Point Cloud Format Should You Use?.

Raster data

• GeoTIFF — orthomosaics, DSMs, DTMs, hillshades. Georeferenced imagery on a map
• JPEG / PNG — non-georeferenced imagery, site photos, 360 panoramas

To understand what makes GeoTIFFs special, read What Is a GeoTIFF?.

Vector data

• DXF — CAD drawings, contour lines, boundary surveys
• SHP — GIS vector data, feature boundaries

3D models

• OBJ / GLB — textured 3D meshes from photogrammetry
• 3D Tiles — tiled 3D datasets for streaming large models

Documents

• PDF — survey reports, certificates, compliance documents, annotated plans

Video and imagery

• MP4 / MOV — drone footage, inspection video
• 360 photos — spherical imagery for virtual site walkthroughs

That is at least a dozen distinct file formats, each requiring different viewing software. No generic file sharing tool handles all of them. Most handle none of them.

Why generic file sharing tools fail for spatial data

I wrote a detailed comparison of Dropbox vs WeTransfer vs Swyvl that covers this in depth. Here is the summary.

No viewers

Dropbox can preview a PDF and play a video. It cannot render a point cloud, display a GeoTIFF on a map, or show a 3D model. For the most valuable deliverables a surveyor produces, Dropbox shows a filename and a download button.

Google Drive is the same. WeTransfer is worse — it does not even attempt previews.

No spatial organisation

Survey work is inherently spatial. You work on physical sites. You capture data in sessions. Your deliverables are tied to locations and dates.

Generic file sharing gives you folders. You can create a folder called “Smith Property - March 2026” but that is a naming convention, not a data structure. There is no map view, no session timeline, no site-level organisation.

No branding

When you share a Dropbox link, your client sees Dropbox. When you share a WeTransfer link, your client sees WeTransfer (and increasingly, WeTransfer’s advertising). Your company is invisible in the delivery experience.

For a profession where trust and professional reputation are everything, this is a significant problem.

No audit trail

You cannot prove delivery. You cannot see if the client actually reviewed the data. You cannot demonstrate that a specific person accessed a specific file on a specific date. For compliance-heavy industries — construction, infrastructure, environmental monitoring — this is not optional.

No client feedback

When your client reviews a deliverable, they might want to approve it, request changes, or ask a question about a specific file. Generic file sharing has no mechanism for this. You end up in an email thread trying to figure out which file they are referring to.

What to look for in a delivery platform

If you are evaluating platforms for professional survey data delivery, here are the criteria that matter:

Format support

The platform should handle the formats you actually produce. At minimum:

• LAS / LAZ point clouds with browser-based viewing
• GeoTIFF orthomosaics on an interactive map
• PDF inline viewing
• Video playback
• 3D model viewing (OBJ, GLB, or 3D Tiles)

If it only handles generic files (PDFs, images, videos), it is not built for survey work.

Branding

Your clients should see your company when they receive deliverables. Look for custom logos, colours, and branded URLs — not a platform’s branding wrapped around your data.

Access controls

You need to control who can view and download your deliverables. At minimum: password protection, email-gated access, and the ability to revoke access. Some projects require more granular controls for compliance.

Activity tracking

You should be able to see who accessed the link, when, what they viewed, and what they downloaded. This is essential for compliance and useful for understanding client engagement.

Organisation

The platform should organise deliverables the way survey work is structured: by site and by capture session. If you are doing repeat surveys, your client should see a clear timeline of deliverables, not a flat file list.

File size handling

Survey data is large. A single LAS file can be 5 GB. A full project might be 50 GB or more. The platform needs to handle multi-gigabyte uploads reliably — ideally with multipart upload that resumes after network interruptions.

Permanence

Links should not expire. Survey data is a contractual record. Your client might need to access it months or years after delivery.

Building a repeatable delivery workflow

Here is the workflow I recommend for any survey practice that wants to deliver data professionally.

Step 1: Organise before you upload

Before you touch any delivery platform, organise your output folder. Group files by type or purpose:

Smith Property - March 2026/
  Point Cloud/
    site_survey.laz
  Orthomosaic/
    ortho_5cm.tif
  Contours/
    contours_0.5m.dxf
  Report/
    survey_report.pdf
    flight_certificate.pdf

This takes two minutes and makes the delivery significantly clearer for your client.

Step 2: Compress where possible

Deliver LAZ instead of LAS. The compression is lossless — no data is lost — and files are 60-80% smaller. Your upload is faster, your client’s download is faster, and your storage costs are lower. See LAS vs LAZ vs E57 for details.

Step 3: Upload to a delivery platform

Use a platform that provides browser-based viewing for your spatial formats. Upload your files, organise them into a session or collection, and add any notes or descriptions your client needs.

If you are evaluating options, Swyvl is built specifically for this workflow — spatial file viewing, branded delivery links, and audit trails for every file. See our pricing for plan details.

Step 4: Share the link

Send your client a single link. They click it and see everything — point clouds in 3D, orthomosaics on a map, reports inline. No software to install. No “which file do I open first?” confusion.

Step 5: Track engagement

Check whether your client has actually viewed the deliverables. If they have not opened the link after a few days, follow up. If they have viewed the point cloud but not the report, you know where to direct the conversation.

Step 6: Handle feedback

When your client has questions or requests changes, keep the conversation tied to the specific deliverables. A proper delivery platform lets clients comment on or approve individual files — no more “see attached markup of the thing we discussed on the call last week” emails.

Before you send your next deliverable: a checklist

Use this before every delivery. Print it out. Stick it on your wall.

• Files are compressed: LAZ instead of LAS. COG instead of raw GeoTIFF where applicable.
• Files are organised: Grouped logically by type or purpose, not dumped in a flat folder.
• Files are named clearly: site_survey_point_cloud.laz, not output_final_v3_FINAL.laz.
• Delivery is branded: Your client sees your company name, not a third-party platform.
• Files are viewable: Your client can see the data in their browser without installing software.
• Access is controlled: Only the intended recipients can view the deliverables.
• Tracking is enabled: You can see who accessed what and when.
• Links are permanent: The delivery link will still work in six months.
• Client knows what they are looking at: Include descriptions, labels, or a cover note explaining each deliverable.
• Feedback mechanism exists: Your client can approve, comment, or request changes within the delivery — not via a separate email thread.

The ROI of professional delivery

Upgrading your delivery workflow is not just about looking professional — though that matters. It directly impacts your business:

Fewer support requests. When clients can view data in their browser, they stop emailing you asking how to open files. I have seen teams reclaim hours per week just from this.

Faster approvals. When a client can see the data immediately, they respond faster. Projects that used to wait two weeks for “client review” now get approved in days.

More repeat business. Clients remember the experience. A surveyor who delivers a branded, interactive portal stands out from one who sends a Dropbox link. The data quality might be identical — the perceived quality is not.

Compliance confidence. When you can prove exactly what was delivered, when it was accessed, and by whom, you have a defensible record. This matters for contractual disputes, insurance claims, and regulatory compliance.

Where to go from here

If you are currently delivering via Dropbox or WeTransfer, start by reading the detailed comparison to understand what you are missing. If you are delivering drone survey data specifically, the drone delivery guide covers format-specific workflows.

For sharing specific file types, we have detailed guides for LAS files, FARO and Leica scan data, and GeoTIFFs.

And if you are ready to upgrade your delivery workflow, create a free Swyvl account and see what professional spatial data delivery looks like. Check our pricing page for plan details, or visit Swyvl for asset owners to see the delivery experience from your client’s perspective.

The data you capture deserves a delivery experience that matches its quality. Stop sending zip files.