PreparedDocs for insurance claims
After a fire or a flood the evidence arrives all at once and in the worst possible order: hundreds of phone photographs, a shoebox of receipts, three contractor estimates and a policy nobody has read since it was signed. The carrier asks for documentation supporting the claim. This is the part that decides what gets paid.
Built for public adjusters, restoration firms and claims teams.

The reality
Not the version in the process document. The version that turns up.
Shot on a phone over several days, many of them near duplicates, none of them labelled by room or by item. Nobody can tell what has already been documented.
Items claimed with no proof, receipts for items nobody listed, and figures that have to be reconciled line by line before submission.
A request for further information arrives weeks later, and the file is already spread across email, a phone camera roll and a shared drive.
Your firm sets its own checklist. This is the shape most of them take.
Send the claimant a link and ask for photographs, receipts and estimates
Photographs are grouped, deduplicated and dated as they arrive
Receipts and estimates are read, so figures can be reconciled against the inventory
Missing rooms, missing proof of ownership and gaps in the timeline are surfaced
The claim package is built with an exhibit index the carrier can follow
One engine
Collect the documents, work out what they are, say what is missing, organise what arrived, build the package somebody has to submit. That sequence does not change between a petition, a claim and a loan file. Only the vocabulary and the checklist do, which is why a firm that works across two of these does not need two products.
Every file is stored exactly as it arrived and is never rewritten. Anything the product produces is a new document beside the original, and you can take the whole file out whenever you want, as an archive with an index.