What restoration files can crews send?

Whatever the loss produces: large before and after photo sets, moisture and psychrometric logs, thermal images, Xactimate ESX estimates and sketch exports, scope sheets, and signed authorizations. A packet keeps them together as one unit.

How does this prove documentation was delivered?

Every packet is checksummed on the server and issued a numbered receipt the instant it verifies. The received time and every later action are written to an append-only record, so there is a dated answer to whether the claim package arrived.

Can field techs submit from a phone on a job site?

Yes. Uploads go straight from the device to storage and resume after a dropped signal, so a full photo set sent from a loss with one bar of service does not have to start over.

For insurance restoration

File Intake for Insurance Restoration Teams

On a restoration job the documentation is the claim. A tech shoots before photos, logs moisture, and places equipment; the office builds the packet the carrier will pay against. RoverDrop makes that restoration file transfer provable: every set of photos and every moisture log arrives with a numbered receipt, one responsible owner, and an archived copy of exactly what came in.

Try the live demo Create your firm's account

No account or email needed for the demo.

The documentation is the claim

Restoration work is billed against proof. Carriers and adjusters do not pay for what was done; they pay for what was documented. A complete file shows pre-loss condition, shows the affected area drying day over day, and ties every line on the estimate to a photo. When a piece of that is missing, the claim does not fail loudly. It stalls, gets kicked back for more information, or gets paid short.

The weak point is almost never the field work. It is the handoff. The tech captured the before photos and the moisture readings on site, and then they had to travel from a phone at a flooded house to the estimator building the packet. Sent by text and email, that trip is where a photo set goes missing and a drying log develops a one day gap nobody notices until the adjuster does.

“We need the before photos before we can proceed.”

This is a specific version of the field-to-office file transfer problem, with higher stakes. The files are large, the connection at a loss is bad, and the record has to hold up to a party whose job is to scrutinize it.

A missing photo is a missing payment

The ways a restoration file handoff goes wrong are predictable, and each one has a cost measured in delayed or reduced claims.

The before photos never made it

The adjuster wants pre-loss condition. If the before set is stuck on a tech's phone or buried in a thread, the scope gets argued and payment stalls until someone drives back out.

A gap in the moisture log

Drying has to be shown day over day, down to a dry standard. Miss one reading day and the carrier can question the equipment charges for the entire drying period.

No proof the packet arrived

The office is sure it sent the file. The desk adjuster has no record of it. Without a receipt, that is one word against another, and the delay lands on your invoice.

The estimate and photos drift apart

The ESX says one thing and the photos show another, because they were sent at different times by different people, with no single packet holding them together.

What a complete claim packet contains

Everything the adjuster expects, in one packet

A packet is the files plus a short cover sheet, kept together and treated as one unit. For a restoration job, complete means the office can open it and find every part of the claim without chasing a tech for the one photo that is missing.

Photos

Before photos, every affected room
Progress and after photos
Detail shots of damaged materials
Thermal images of hidden moisture

Readings and logs

Daily moisture readings, by point
Drying log to the dry standard
Psychrometric log: temp, RH, GPP
Equipment placement and run sheet

Estimate and paperwork

Xactimate estimate (ESX) and sketch
Scope sheet and line items
Signed work authorization
Certificate of completion

For a version your crews can run before the packet leaves the site, use the restoration documentation checklist.

How the intake works

One intake queue, from the loss to the file

Techs submit every job to one central queue instead of a dozen inboxes. The office works that queue: review a packet, accept it by name, and mark it filed once it is in the claim system. The proof assembles itself along the way.

A receipt on submit

The moment a tech's files verify, the packet gets a numbered receipt with the file count and total size. The crew knows the office has the loss documentation before anyone has to ask.

One owner for the packet

The submitting tech is responsible until an estimator or admin accepts the packet by name. Opening or downloading a photo set to review it never quietly moves that responsibility.

An archive that outlives the job

Every file is copied to write-once storage at submit. When a claim is reopened or subrogated a year later, the original photos and logs are still there, unchanged and checksummed.

The receipt is the start of proof that the claim documents were delivered, the part carriers and desk adjusters actually ask for when a submission is contested.

Built for a phone at a flooded house

The person documenting the loss is standing in it, on a phone, on whatever signal the neighborhood has. A full before and after set can run to hundreds of photos. Uploads go straight from the device to storage and resume where they left off after a dropped signal, so a large photo set does not have to restart every time service dips. A packet composed with no signal waits on the device and sends itself when the connection returns.

The office side is just as plain. The estimator or admin sees the packet arrive, opens the photos and logs to review them, and accepts it when it is ready to work. Because accepting is separate from viewing, a reviewer can check a moisture log without becoming the owner of the whole claim by accident.

Resumes after a dropped signalHandles large photo setsComposes with no signalOne central intake queue

Questions restoration teams ask

What restoration files can crews send?: Whatever the loss produces: large before and after photo sets, moisture and psychrometric logs, thermal images, Xactimate ESX estimates and sketch exports, scope sheets, and signed authorizations. A packet keeps them together as one unit.
How does this prove documentation was delivered?: Every packet is checksummed on the server and issued a numbered receipt the instant it verifies. The received time and every later action are written to an append-only record, so there is a dated answer to whether the claim package arrived.
Can field techs submit from a phone on a job site?: Yes. Uploads go straight from the device to storage and resume after a dropped signal, so a full photo set sent from a loss with one bar of service does not have to start over.

Teams weighing a full document system against a purpose-built intake often start with our ShareFile alternative. For the workflow itself, see how crews can track photo and documentation handoff and keep documentation from going missing on a claim.

See it in motion

See a restoration packet arrive with proof

Submit a loss packet in the demo and watch the receipt appear the moment its photos and logs verify. Nothing to install, and no account or email required.

See pricing·Read the docs

Try the live demo Create account