A job's line items and pushback

Overview

The Line Items section of a job profile breaks the claim down to the individual lines: every priced item on the estimate, supplement, and invoice, each with its quantity, unit price, total, and how it fared with the carrier. Where The Numbers gives you the job's totals (see A job's line items' parent, the numbers section), Line Items shows you the parts those totals are made of, and where money is being cut line by line.

Everything here is built from your own documents. Verinode reads the priced lines on the job, maps each to a canonical service so the same work can be compared across jobs, and tracks what happened to it through the supplement chain. Nothing on this section is shared with carriers.

Where to find it

Open a job and select the Line Items section. The table loads on its own from the estimates and supplements already ingested for that job. While it loads you see "Loading line items…"

If the job has no priced lines yet, the section reads "Line items will appear here as estimates and supplements are ingested for this job. Drop a document on the dashboard to populate." If something goes wrong loading, it reads "We hit a snag loading lines for this job. Refresh the page to retry."

The pattern tile

When any of this job's lines match a pricing or pushback pattern that is already open across your book, a short tile sits above the table. It reads "This job touches active patterns," names how many lines match, and, when there is a dollar figure, shows the combined monthly exposure, for example "~$X/mo combined." Beneath it, up to three of the matched canonicals are listed with what they matched, such as "cut concentration" or "below-cohort pricing," and each one's monthly figure.

The tile is there for the operator who opens a job but never scrolls into the table. It reports which lines on this job already match a pattern; it never tells you what to bill. To walk the evidence trail behind any match, open the row below or visit the decisions workspace.

The line-items table

Each row is one priced line. The columns:

• Description, the raw text exactly as it appeared on your document, with a canonical chip beneath it. The chip is how Verinode groups the same work across jobs and carriers. It reads one of three ways:

- a canonical name with a pencil, marked as auto-mapped ("Auto-mapped, click to override") when Verinode matched it, or as your own ("Operator override, click to change") when you set it. - a dashed "Map this line" when no canonical is mapped yet. - The vendor name, when known, sits beside the chip.

• Qty · Unit, the quantity and the unit it is priced per (each, day, square foot, and so on).
• Unit price, the price per unit.
• Total, the line's extended total.
• Outcome, what happened to the line in the supplement chain: Approved (green), Cut (red), Partial (yellow), Withdrawn, or Outstanding. Anything not yet touched by a supplement response reads Outstanding.
• Pushback, a chip on lines that have been cut, covered in the next section. Lines with no pushback show a dash.

Two more columns appear when cost allocation is available, Cost (allocated) and Margin %, and an Insight column appears when Verinode has generated an AI summary for a line.

Long estimates load the first 50 lines with a "Show all N lines" button; oversized estimates stay snappy on first paint.

Fixing a canonical mapping

The canonical is what makes cross-job and cross-carrier comparison possible, so getting it right matters. Click any chip to open Map this line, where canonicals are grouped by category. Pick the one that best matches the line and choose Set override. The picker notes "Your choice sticks, automatic re-mapping won't override it," so your correction survives future ingests. Clear override returns the line to automatic mapping. Every override is recorded on the audit trail.

Cost allocation and margin

When the Cost (allocated) and Margin % columns are present, a toggle above the table lets you choose how job cost is spread across lines: Pro-rata (each line takes its share of the estimate, times the imported total cost) or Category-weighted (equipment-rental lines pull from the imported equipment cost; everything else falls back to pro-rata). The toggle carries a plain warning: "Allocated, not directly observed. Use as a directional read, not as a line-level P&L." Read the per-line margin as a direction, not as booked profit.

Line insights

When the Insight column shows a Read affordance, Verinode has an AI summary for that canonical on this job. Opening it shows a two or three sentence outcome narration, footed with "Outcome narration based on your trailing-90-day data plus the estimating-software cohort," its generation time, and a note that it is cached for seven days. These summaries report what the data shows; they do not tell you what to bill.

Supplements and pushback at the line level

A supplement is a request to add or revise scope after the original estimate. Pushback is what the carrier does back at the line level: cutting a line's dollars, approving it in part, or denying it. On the table, that shows up two ways: the Outcome column (Approved, Cut, Partial, Withdrawn, Outstanding) and the Pushback column.

The Pushback chip appears on lines that have been cut. It carries a colored dot (Ember Red when the cut share is high, Hard Hat Yellow otherwise) and reads "X% cut", the share of times this canonical has been cut on your submissions in the trailing window. The cut share is measured at the canonical level, across the job, not for the single row. Click the chip to open the pushback drawer.

The pushback drawer

The drawer opens the Pushback chain: the full supplement history for that canonical on this job, so you can see exactly where and why the money was cut. It is titled "Pushback chain, <line description>."

Each entry in the chain is one document that touched the canonical, laid out top to bottom:

• The document type and, when it is a supplement, its Supplement #.
• The date and the document's status (Approved, Partial, Denied).
• The Cut amount in dollars, in Ember Red, when the document denied part of the scope.
• A Reason line when the carrier gave one, for example "Reason: insufficient documentation."
• Lines on this document, each matched line with its description, quantity and unit, unit price, total, and its own disposition.

A denied or partial entry is accented in red or yellow down its left edge; an approved one in green. The chain reports what happened at each step; it never tells you what you should have done.

If nothing has come back yet, the drawer reads "No supplement activity recorded for this canonical on this job yet. As supplement responses are ingested, the chain will populate here." While it loads you see "Loading supplement chain…"; on an error, "We hit a snag loading the chain. Close and reopen to retry."

How this connects to pricing benchmarks

Line items are the foundation for cross-carrier pricing. Because every priced line is mapped to a canonical service, Verinode can put the same work's unit price side by side across the carriers you bill, so you can see who pays more and who pays less for identical work. That comparison lives on the Pricing view. It is built entirely from your own line items, and it is operator-private: your rate data is never shared with carriers.

See The Pricing view, cross-carrier rates for how the same lines you are looking at here roll up into a carrier-by-carrier rate comparison, and where your renegotiation leverage sits.

Data sources

Every line, mapping, and pushback here is built from your own documents against a shared service catalog. Verinode is an independent data trust: your line-item pricing is never sold to carriers. For the job's totals behind these lines, see A job's numbers and cohort comparison; for the cross-carrier rate view they feed, see The Pricing view.