The Job file export: a job's full record as a PDF

What the Job file export is

The Job file button turns one job into one document: a branded PDF that compiles the job's full record, the claim identification, the lifecycle from intake to payment, what the carrier disputed and why, the correspondence linked to the job, and an index of the documents on file. It is the record you hand your own counsel when a claim turns into a fight, and it is built entirely from data you already have. You click the button, and the finished PDF downloads; nothing is drafted, summarized, or interpreted along the way.

The document is assembled server-side from lanes the job card never renders on screen, including the full text of the emails linked to the job, which is why it is a dedicated export rather than a print of the page. The header carries your company name and logo when you have set them, so what your lawyer receives reads as your record, not a platform screenshot.

Where to find it

There are four ways in:

• The job hero. Open any job and the Job file button sits in the action row at the top, beside the margin review and Export PDF. A small caret beside it opens the export options covered in sharing a job file safely.
• A client's Jobs tab. On a client's detail card, every row in the Jobs table carries a compact Job file download, so you can pull a record straight from the client's file without opening the job first.
• The "Open a job's file" launcher. The Apps row on both the Jobs and Compliance pages holds a launcher tile that opens a searchable job picker in place. See opening a job's file from the Apps row.
• Asking IQ. IQ can pull a job's file into the conversation, summarize the dispute and the correspondence, and point you to this export when you want the complete document. See asking IQ for a job's file.

The eight sections, in order

The document always runs in the same order. Four sections are always present; the middle four appear only when the job has something real to put in them, so an empty section is left out rather than rendered blank.

1. 1What this is. A plain-language cover stating what the document is and the promises it makes (below).
2. 2The claim. The identification block: claim number, carrier, insured, client, type of work, status, the money (estimate submitted, approved by the carrier, billed, collected), and the key dates from assignment through payment.
3. 3The job, start to finish. The full chronology in the order it happened, stitched from your lifecycle dates, field work, carrier supplements, costs, correspondence, and documents. This is the same story the Job File tab tells on screen.
4. 4What the carrier disputed. Where the carrier pushed back on a supplement: the reason given, who handled it, what was taken off of what was submitted, the documentation demanded, negotiation rounds, reassignments, and the contested line items.
5. 5Correspondence on the job. Every email linked to the job, reproduced in full in the order received, with sender, date, and party.
6. 6Exhibits index. A numbered list of the documents and attachments the record references, with PDFs and images appended after the index as real pages. Covered in depth in exhibits.
7. 7What this record does and does not cover. The honest scope statement: the record is limited to what your systems captured, and an absence in it is not evidence a thing did not happen.
8. 8Provenance. When the document was generated and a fingerprint that ties it to a retained snapshot of the source records, so a produced file can be matched back to the records it came from. The export record behind this is covered in sharing a job file safely.

The two promises the document makes

The cover page states them, and the way the document is built enforces them:

• Nothing in it is model-authored. Every date, figure, and line is read directly from your records and placed into fixed wording. No AI writes, paraphrases, or summarizes any part of it, which matters because a document like this outlives the login: it gets forwarded to people who never saw any caveats.
• No comparison to anyone else, ever. The document contains no peer figures, no cohort or network reads, and no Verinode scores. It is your own record and nothing else, by construction: the builder only reads named fields from your job, so a benchmark cannot leak in by accident. The recipient may be opposing counsel, and the network's intelligence is never something a document you hand across the table should carry.

The file you get

The PDF downloads named after the claim: the claim number plus "-job-file.pdf", for example clm-2024-8841-job-file.pdf. When no claim number is on file, a short description of the job stands in. The default export is the full record, intended for your own counsel; for sharing more broadly, the caret menu offers a redacted copy, covered in sharing a job file safely.

Data sources