Client Intelligence: your data vs the network, and peer ratings

What the Intelligence tab shows

Every carrier, TPA, private-pay, and commercial relationship in Verinode has an Intelligence tab on its detail card, and it is deliberately split into two labeled buckets that never mix: What Your Data Shows and What The Network Shows. The split exists because those two things are answered by different evidence and deserve different trust. What your data shows is derived entirely from jobs you have on file with this client, no one else's numbers touch it. What the network shows is the anonymized peer read, other operators working the same carrier or TPA, pooled and never traced back to any single operator or shared with the carrier itself.

Verinode does not decide whether this relationship is working. It reads the jobs, payments, and ratings already flowing into your account, adds the anonymized peer comparison where enough operators have contributed to make one, and lays both out side by side. You decide what to do with what you see.

This article covers the Intelligence tab in full, the carrier/TPA peer-rating widget that lives on Overview and feeds the network bucket, the carrier-scoped peer benchmark rows that recur across the card (Pushback, Approval Speed, and Intelligence all use the same building block), and the data-dividend model, what you get back for contributing.

Where to find it

Open Clients from the sidebar at iq.verinode.ai/clients. Click any client to open its detail card, then select the Intelligence tab from the tab row (Overview, Performance, Pushback, SLA & Programs, Jobs, Scorecards, Processes, Intelligence). The tab set is the same for every client type, but the network bucket only renders for carriers and TPAs, private-pay and commercial relationships aren't catalog entities in Verinode's network, so there is no peer cohort to compare against. See Client detail card for the rest of the tabs and hero actions.

Bucket A: What Your Data Shows

This bucket runs automatically from the jobs you have on file with this client, no peer data enters it at all. Verinode watches for three patterns and only shows a note when one actually fires:

• Payment velocity. Once you have at least five jobs with recorded days-to-pay for this client, Verinode compares your ten most recent paid jobs against the client's historical average. If the gap is five days or more in either direction, a note appears: slower reads as a warning ("Recent jobs took Xd on average, Yd slower than the historical mean (Zd). Worth checking whether invoicing or approval is breaking down."), faster reads as a positive ("Recent jobs paid in Xd, Yd faster than historical (Zd). Something's working; worth capturing what changed.").
• Category concentration. Once you have at least five jobs and one job category makes up more than 60% of them, a note flags it: "X% of jobs with this client are [category]. Concentration like this is worth double-checking: either you're their go-to for that category (good) or the mix is narrow (risk if they diversify)."
• Outstanding balance. When less than 90% of billed dollars have been collected, a note reports the outstanding total and the percentage still uncollected, flagged as a warning above a 20% gap: "$X still outstanding, Y% of billed revenue not yet collected. Check whether disputes are pending or if the relationship needs a payment cadence conversation."

Each note is color-accented on its left edge, green for a positive pattern, amber for a warning, gray for neutral context, so you can scan the column and see which notes need attention without reading every line.

Empty state. Until at least one pattern fires, the bucket reads: "Insights populate once you have at least 5 jobs with this client. The agent watches for payment trends, category concentration, and outstanding balance patterns."

Bucket B: What The Network Shows

This bucket only renders for carrier and TPA clients. It opens with a line naming exactly what the comparison is: "Your numbers on this [carrier/TPA] against the anonymized peer cohort working the same counterparty. Data flows back to you because you're on the same side as everyone contributing, never sold to the [carrier/TPA]." Underneath it, up to four carrier-scoped peer benchmark rows appear, each one only when there is something to show:

• Supplement approval rate, your dollar-weighted supplement win rate (approved dollars divided by submitted dollars with this client) against the peer cohort's approval rate on the same carrier or TPA. Higher is better. Always shown, since it's the flagship metric this bucket exists to answer.
• Cycle time, your average days from job assignment to completion with this client, against the peer cycle time on the same counterparty. Only shown when either your own value or a peer value exists. Lower is better.
• Supplement response days, how long the peer cohort waits for this carrier or TPA to respond to a supplement. Only shown when a peer value exists; there is no comparable operator-side value for this one in the bucket (response-day tracking on your own jobs surfaces separately, inside Pushback).
• Peer satisfaction, the peer cohort's satisfaction rating for this carrier or TPA, drawn from the multi-criteria peer ratings other operators have submitted (see below). Only shown when a peer value exists. Higher is better.

Below the benchmark rows sits a What unlocks as peers contribute list, three concrete unlocks framed as things that light up as more data flows in, not vague "coming soon" filler:

• Rejection patterns, forward denial letters and ROM disputes; Verinode extracts the reasons and surfaces the common patterns peers see with this carrier or TPA.
• Scorecard tier distribution, upload scorecards; Verinode shows how peers score on the same KPIs and what tier jumps require.
• Rate-realization vs. Xactimate, ingest estimates and approvals; Verinode publishes what share of Xactimate line items this carrier or TPA actually pays.

The carrier-scoped peer benchmark row

Every peer row across the client detail card, in Intelligence, in Pushback, and in Approval Speed inside Pushback, is built from the same component, so it behaves the same way everywhere you see it. Each row shows your value, the peer cohort's value, which peer scope backs the comparison, and how many operators are behind it, without ever naming a peer operator.

When both your value and a peer value exist, the row renders as a comparison: your figure, the peer figure, and a small delta reading (formatted for the metric, days as "+8d vs peer", percent as "+3.2pp vs peer", and so on). A short line underneath names the cohort: National peer cohort, In-state peer cohort, or Your network cohort, whichever scope the benchmark resolved at, followed by the operator count behind it, for example "National peer cohort · 14 operators." The scope token is never shown as a raw database value, always one of those three plain labels.

When you have your own value but the peer cohort hasn't formed yet, the row reads: "You: [your value] · peer cohort still forming. Contributions unlock the comparison." Nothing is hidden, but there is no number to compare against.

When you have no value of your own but a peer value already exists, the row flips the framing: "Peers on this carrier: [peer value]. Upload jobs with this carrier to see your own line." This is the honest reverse case, the network already has a read on this counterparty, your own line just isn't populated yet.

When neither value exists, the row still shows its label with the "peer cohort still forming" copy rather than disappearing, so the tab's shape stays predictable as data fills in over time.

Verinode never surfaces the specific threshold a cohort needs to clear before a comparison appears, only that contribution is what unlocks it. That is intentional: the exact peer-count floor is part of how Verinode protects individual operators inside the anonymized pool, not something to game toward.

The carrier/TPA peer-rating widget

The rating widget itself lives on the client's Overview tab (not Intelligence), titled Rate this carrier or Rate this TPA, and it is the direct input that feeds the network bucket's peer satisfaction row and the peer cohort behind every rated criterion. It only appears once the client is matched to Verinode's network catalog; if it isn't matched yet, the panel is replaced with a note: "This [carrier/TPA] isn't matched to the network catalog yet, so it can't be peer-rated."

The widget carries two distinct kinds of criteria, and it labels each one so you always know which is which:

Derived criteria are read-only, scored automatically from your own job data, and tagged From your jobs so you never mistake them for a control you forgot to fill in. Both carriers and TPAs get Payment speed, shown as your own average days to pay ("~28 days to pay") or "No job data yet" if you have none. Carriers additionally get Supplement approval, your own approval percentage ("88% approved") or "No job data yet." These derived values are real numbers pulled from your book, not opinions, and Verinode does the scoring band internally rather than asking you to self-assess something it can already compute.

Peer criteria are subjective judgments you or your team give on a labeled 1-to-5 scale, anchored so a given number means the same thing to every operator rating that criterion, no bare stars. For carriers: Scope fairness (from "Routinely cuts legitimate scope" at 1 to "Approves fair, complete scope" at 5), Communication & response (from "Unreachable / no response" to "Same-day, proactive adjuster"), and Estimate respect (from "Ignores your pricing" to "Fully respects your documented pricing"). For TPAs: Fee fairness (from "Excessive fees for the value" to "Clearly fair fees"), Scope & approval fairness (from "Routinely squeezes the estimate" to "Approves fair, complete scope"), Communication & response (from "Portal black box, no response" to "Proactive, easy to work with"), and Program requirement burden (from "Onerous, constant compliance load" to "Light, sensible requirements").

Tap a number to select it. The criterion's plain-language description for that number appears next to its name once picked; until then it reads Not rated. A caption above the whole panel states where the data goes: "Your ratings and job-derived metrics are anonymized and pooled with other operators to power this [carrier's/TPA's] peer score. Verinode never sells operator data." Hit Submit rating to save; the button reads Saved, thank you once it lands.

The data-dividend model

Verinode's north-star commitment is that every anonymized contribution to the network should produce a tangible return to the operator who made it, not just a "thanks for the data" message. That commitment shows up differently depending on where you contribute:

• On a private-pay or commercial client, rating the relationship's single Satisfaction control triggers a Data dividend callout directly under the rating, marked with a checkmark. If a peer comparison already existed for that client, it reads: "Your rating joined [N] peers contributing intelligence on [client name]. The comparison above got sharper because of you." If no comparison existed yet, it reads: "Your rating starts a peer cohort on [client name]. As more operators contribute, your benchmark on this relationship gets sharper." Either way, it closes with: "Verinode never sells raw operator data to carriers."
• On a carrier or TPA, the reciprocity is built into the peer-rating widget's own caption and into what unlocks in the network bucket described above, submitting your ratings and job-derived metrics is literally what grows the cohort that populates "What The Network Shows" for you and for every other operator working that same counterparty.

The mechanic is the same underneath either surface: your contribution is pooled anonymously with other operators' contributions, the pooled result is what Verinode publishes back as a peer benchmark, and the raw, attributable version never leaves your account, it is never handed to the carrier or TPA it describes, and it is never sold. That is the practical meaning of Verinode operating as an independent data trust rather than a vendor that just collects operator information: the benchmark exists because operators contributed to it, and it keeps working for the operators who keep it fed.

Best-practice example

You open a carrier whose Findings badge caught your eye. On the Intelligence tab, the your-data bucket shows one note, a Payment velocity warning: recent jobs are running 9 days slower than this carrier's historical average. You flip to Overview and see the Rate this carrier panel: payment speed already reads "~58 days to pay, From your jobs," matching the trend you just saw, and supplement approval reads "81% approved." The three peer-judgment criteria are unrated. You rate Communication & response a 2 and Estimate respect a 3, then hit Submit rating; the button confirms Saved, thank you.

Back on Intelligence, the network bucket now shows Supplement approval rate at your 81% against a peer cohort reading 88% (National peer cohort, a double-digit count of operators), with your line trailing peers by a few points. Cycle time isn't shown, because neither your value nor a peer value exists for this carrier yet. The unlock list reminds you that forwarding a denial letter would extract the rejection patterns; you use Add Data on the hero to forward the carrier's latest denial email before closing the card.

Data sources

Related articles

• Client detail card: the full tab set, hero actions, and the Overview/Performance tabs this article builds on.
• Pushback: the denial cut on carriers and TPAs: the carrier-scoped peer row also appears here, applied to denial and approval speed.
• Carrier Programs: eligibility, required certs, and vendor approvals
• Clients and carriers
• How benchmarks work
• Reading a benchmark
• Benchmarks overview
• The decision workspace
• Forwarding documents
• Connecting your data