Field-to-office file handoff
Every handoff gets a receipt, an owner, and an archive copy.
RoverDrop is field-to-office file transfer that replaces email attachments for firms in construction, survey, insurance restoration, civil, and geotech. Crews submit to one queue. The office takes ownership of each packet. Every handoff is tracked from receipt to filing.
No account or email needed for the demo.
What it does
Submit files → confirm receipt → assign responsibility → archive proof.
The failure it prevents: “I thought you had it.”
The email workflow, fixed point by point
| With email | With RoverDrop |
|---|---|
| Sent to the wrong address | One destination. There is no address field. |
| “Did you get my email?” | Explicit receipt: packet number, file count, verified size. |
| Nobody knew whose job it was | One responsible person at all times, by name. |
| Attachment too big, upload died | Direct-to-storage uploads that resume after a dropped signal. |
| Files never made it to the job folder | “Filed” is a tracked step, and unfiled work is visible. |
| No proof of what was sent | Checksums, an append-only audit trail, and an automatic archive copy. |
Three states, one owner at every step
1. Submitted
The crew uploads files with a title and cover sheet. Every file is checksummed and verified before the packet counts as submitted. The submitter stays responsible.
2. Accepted
An office tech reviews the packet and accepts it. Their name goes on it and responsibility transfers to them. Only accepting transfers responsibility; downloading files to look at them does not.
3. Filed
The tech confirms the files are placed in their final destination. The packet is done, and the archive copy stays.
What's in it
Receipts
A packet is not submitted until every file is verified server-side. The crew gets a numbered receipt.
Custody
Ownership stays with the submitter until the office explicitly accepts. Downloads never transfer it.
Return for correction
The office can send a packet back with a reason instead of accepting it. The fix comes back as a linked supplement.
Aging queue
Unaccepted packets are color-coded by age. Reminder emails escalate until someone accepts.
Automatic archive
Every file is copied to write-once archive storage at submit. Retention rules never touch it.
Legal hold
Freeze a whole job's files, or a single packet's, against retention for a dispute or claim, until an admin releases the hold. Every covered packet's audit trail records it.
Audit trail
Submitted, returned, accepted, filed, shared. Every event with a name and a timestamp, append-only.
Photos and markup
Thumbnails and previews, capture time and GPS read from each photo, and annotation that never alters the original.
Sign-off signatures
Ask for a drawn signature on accept or file. It's stored with the custody event, not just a click.
Share with clients
Send an expiring, passcode-optional link to one packet. Every open and download is logged in the audit trail.
File requests
Give a sub, lab, or adjuster a link that uploads straight into your queue — no account, their name on the receipt, custody from the first byte.
Works offline
Packets composed without signal are stored on the device and sent when the connection returns. Push notifications reach the crew's lock screen.
Reports and API
Time-to-accept and time-to-file metrics, a queue map, plus webhooks and a read-only API for your tooling.
Live demo
Try it before you sign up
One click opens a working RoverDrop firm loaded with sample packets, in whichever role you pick. It's the real product: accept packets, submit new ones, undo things, change settings. Your demo is private, switchable between all three roles from a bar at the top, and deleted after 24 hours. Nothing you do affects anyone else.
Set up takes minutes.
Create the firm account, add your crew and office staff, and submit the first packet.