About
Why RoverDrop exists
Field firms move critical files through a fragile handoff: a crew finishes work on site, sends the data to the office, and hopes someone deals with it. Usually that handoff is email. Email has no receipt, no owner, and no archive. When a file goes missing, the answer is always the same: “I thought you had it.”
RoverDrop is a small tool that fixes that one handoff. Generic file-sharing tools don't: they move bytes but track no owner and keep no archive. Crews submit files to a single intake queue. The office explicitly takes ownership of each packet. Every packet gets a numbered receipt, an append-only audit trail, and an automatic write-once archive copy. That is the whole product.
It works anywhere crews hand files back to an office: construction, land survey, subcontractor-to-office handoffs, insurance restoration and adjusting, civil engineering, and geotech.
Design principles
- One destination. No recipient field, no folder picker. Submitting always goes to the same queue.
- No silent failures. A packet does not count as submitted until every file is uploaded and verified. The submitter gets an explicit receipt.
- Only accepting transfers responsibility.Downloading or viewing files never does. Accepting is an explicit action, recorded with the acceptor's name.
- Locked at acceptance. Until the office accepts, the submitter can still fix their own packet — every change recorded. Once accepted, the record never changes underneath you; corrections after that are a new packet linked to the original.
- Visible aging. Unaccepted work is impossible to miss: color-coded by age, with escalating reminders.
Who builds it
RoverDrop is built and operated by an independent software company based in Illinois, United States. Questions, feedback, and support all go to the same place: support@roverdrop.com or the contact form.