The Job File: one job's story, intake to pushback

The Job File leads the job

Open any job and the first tab you land on is Job File: one chronological rail telling the whole story of the claim, from the loss through intake, estimating, the work itself, the carrier's pushback, billing, and payment. It used to be called "The Journey" and sat deeper in the card; it now leads the detail because the story is the job, and any links you saved to the old tab still open the same place.

Everything on the rail is your own record, laid out in the order it happened. A composition line at the top reads what the story is stitched from, for example "5 stages · 3 events · 8 emails · 2 documents," and when a claim carries a lot of paperwork a Show paperwork toggle keeps the attachments folded away so a fifty-document claim still reads as a story rather than a file list.

The chronology: up to twelve stages

The lifecycle rail maps up to twelve stages, in this order: Loss, Received, Contacted, On site, Authorized, Assigned, Estimate submitted, Carrier approved, Started, Completed, Billed, Paid. Each stage you have a date for appears with the elapsed time since the previous one, for example "12d from Assigned," or "Same day as Assigned" when two stages land together. The stages where a dollar figure belongs to the moment carry it on the stage itself: the estimate amount on Estimate submitted, the approved amount on Carrier approved, the billed and collected amounts on Billed and Paid.

The intake front half (Loss through Authorized) and the estimating pair (Estimate submitted, Carrier approved) are optional stages. Most tools only export the core dates, so a job missing them is simply bridged: the rail runs straight from the stages it has, and nothing is marked as skipped or incomplete. As intake and estimate dates start flowing in from your tools and documents, those stages light up on their own.

Between the stages, the rail interleaves everything else that happened: each supplement's submitted-to-responded sub-cycle, days the crew was on site (with hours and crew size, and a note when the crew came back after the job had gone quiet or worked a weekend), drying milestones, payments as they were observed, costs as they landed (labeled with where the dollars came from, such as "Invoiced" or "Allocated"), the emails linked to the job, and the documents on file. Where peer timing exists for a stage, it appears beside your own, with the comparison arriving as more operators contribute the same lifecycle data; it is never invented to fill a gap.

The pushback block

When the carrier pushes back on a supplement, the response entry carries the dispute in full, flowing directly under the stage line:

• The reason given, in the adjuster's own words where they were captured.
• Who handled it: the adjuster's name and role (for example, a desk adjuster).
• The dollars cut, read as "Cut $4,200 of $18,500 submitted."
• The documentation demanded before the carrier would pay.
• Negotiation rounds, and how many times the carrier reassigned the file.
• Paid on ACV when depreciation was withheld.
• Overturned on escalation when you escalated and the carrier reversed its position.
• The contested line items themselves, each with its disposition (Denied, Reduced, Removed, and so on), the cut type, and the submitted amount, with a "+N more contested lines" note when the list runs long.

A supplement the carrier has not responded to yet carries whatever pushback facts already exist on its submitted entry, so a pending fight is visible before the response lands.

Party chips on correspondence

Each email on the rail shows its subject and sender, and where Verinode can match the sender against the parties known on this job, a small chip names which side it came from: Adjuster, Carrier, Customer, Sub, or You. The matching is deliberate, not guessed: an adjuster is recognized from the addresses on your supplements, a sub from the vendors billed on the job, and your own side from your connected mailbox. A sender that matches nothing gets no chip at all, rather than a wrong one.

When no emails are linked yet

The correspondence strand is the richest source of a claim's story, and on many jobs it starts empty. When it is, the rail says so plainly: "No emails are linked to this job yet," with a link to connect your inbox. Connect Microsoft 365 or Google, and matching adjuster and subcontractor threads join this file automatically as they are found; there is nothing to file by hand.

The same honesty applies elsewhere on the rail: a cost line with no date is counted in a note rather than silently dropped, so the timeline never implies it shows all of a job's cost when it does not, and a job with no entries at all reads "As lifecycle dates, supplements, payments, and paperwork flow in from your inbox and tools, this job's full story maps itself here."

Data sources