Client file delivery
Deliver the files, and keep the receipt.
The last step of a job is usually the least tracked one: the office emails the finished files to a client or adjuster, or drops them on a link, and the record ends there. A RoverDrop share link sends one packet to someone without an account, expiring or not, passcode-protected or not, revocable whenever you want — and logs every time they open or download it, so proof of delivery follows the files all the way to the client.
No account or email needed for the demo.
The handoff to the client is the blind spot
Everything inside the firm can be tracked — who submitted a packet, who accepted it, when it was filed — and then the finished work goes out to the client as an email attachment or a public link, and the tracking stops cold. Nobody can say for certain whether the client opened it, and if the files were sensitive, the link that carried them may still be live in an inbox somewhere with no way to pull it back.
A share link closes that gap without asking the recipient to create an account. It is the same packet the office already holds, exposed to exactly one outside party under rules you set, with its own line in the audit trail every time it is touched.
You set the rules, the link enforces them
Office and admin users create a link on any accepted or filed packet. The token is long and random, and only its hash is stored, so the link works but a database read never yields one. From there, three controls decide how far it reaches.
Expiry
7, 30, 90 days — or never, for a deliverable you want to stay reachable.
Passcode
Optional. Tell the recipient separately, so the link alone is not the key.
Revocation
One click ends the link, immediately, regardless of its expiry.
What a share link is, and is not
A delivery you can prove and take back
A share link is not a public folder and not an open-ended dump of your data. It is a narrow, controlled window onto one packet, and everything done through it is on the record.
One packet, nothing else
A link exposes a single packet's files and notes. The recipient never sees your queue, your other jobs, or anything about your firm beyond what you sent.
Expiring or permanent
Set a link to lapse after 7, 30, or 90 days, or to never expire for a deliverable you want kept reachable. You choose per link, by how sensitive the files are.
Passcode optional
Add a passcode for anything that travels by email, so the link alone is not enough to open the files. Leave it off when a plain link is fine.
Revocable at any time
Sent the wrong link, or done with it? Revoke it and it stops working immediately, whether or not it had an expiry date.
Logged as it is used
Every open and download through a link is written to the packet's audit trail, so the record of delivery reaches the recipient and comes back with their name on it.
The last mile of the handoff
In land surveying and civil engineering, the deliverable that goes to the client is the whole point of the job, and being able to show it was delivered — and re-share it years later — is worth as much as producing it. For insurance restoration teams, an adjuster who needs the file set can get it on a passcode link instead of an open one. Because each open and download lands in the audit trail, client delivery becomes part of the same chain of custody as the rest of the packet.
For a step-by-step version, read how to share project files with a client and keep proof of delivery.
Related
- Proof of deliveryThe receipt that starts inside the firm and now reaches the client.
- Audit trail for file transfersWhere each open and download by an outside party is logged.
- Field-to-office file transferThe full handoff that client delivery is the last step of.
- Share project files and keep proof of deliveryThe practical how-to for the last mile.
See it in motion
Send a share link in the demo
File a packet in the demo, create a share link with a passcode and an expiry, and open it in another tab to see the delivery logged. No account or email required.