The recruiting detail card: tabs by record kind

What it is

Recruiting tracks four different kinds of records at once: an open role you are hiring for, an applicant in your pipeline, a single interview step inside that pipeline, and a candidate sitting in your talent pool for later. Click any row, in any tab of the Recruiting cards slider, and it expands into one shared detail card. That card is the subject of this article.

The card looks the same regardless of which kind you clicked into (same hero, same tab bar, same agent-insight panel), but the tabs underneath it are not identical. Findings and Context always render. Pipeline only renders for applicants. Coaching only renders for applicants and talent-pool candidates. Which tabs you see, and what fills them, depends entirely on the kind of record you opened.

Where to find it

Open Recruiting from the sidebar at iq.verinode.ai/recruiting. The page presents your open roles, applicants, interview pipeline, and talent pool as tabs inside a cards slider. Click any row (a role, an applicant, an interview step, or a pooled candidate) and its detail card opens.

The four record kinds

| Kind label on the card | What it represents | Where it lives on the page | |---|---|---| | Open Role | A requisition you are actively hiring for, from posted through screening, interviewing, offered, hired, or closed. | The Open Roles tab | | Applicant | A candidate against a specific open role, with a fit score and a status from new through hired, declined, withdrawn, or ghosted. | The Applicants tab | | Interview Step | One step in an advanced applicant's pipeline (phone screen, on-site, reference check, decision, offer). | The Interview Pipeline tab | | Talent Pool | A past applicant kept warm for a future opening, or a candidate you sourced proactively, in cold, warm, engaged, hired, declined, or unsubscribed status. | The Talent Pool tab |

The kind label appears as a small uppercase eyebrow at the top of every detail card, so you always know what you are looking at.

The hero: a stance, not just a status

Above the tabs sits the hero. It carries the kind label, a colored stance pill, the record's title (the role title, the applicant's name, the step kind, or the candidate's name), and a subtitle.

While the card is still loading its detail data, the subtitle is the record's own short summary line (for example, an applicant's score and years of experience). Once the data lands, the subtitle switches to the Co-COO's read on this specific record: a plain-language line telling you what matters right now, not a restatement of the status field.

The stance pill is the fastest way to triage a long list of records. Verinode computes one of six stances for every record:

• Healthy (green): nothing to act on; the record is progressing the way it should, including terminal good outcomes like a completed hire.
• Progressing (teal): the normal "in flight" state. Work is proceeding; no action needed today.
• Watching (yellow): something is borderline. Not a problem yet, but worth a look (a thin pipeline, a nurture check-in coming due, cadence going quiet on a candidate).
• At Risk (red): action matters now. A top-tier applicant sitting unadvanced, a stalled requisition, a stalled interview step.
• Blocked (red): a legal guardrail or an external dependency has to clear before you can move forward. Verinode never advances a blocked record on your behalf.
• Closed (gray): a terminal state: hired, declined, withdrawn, unsubscribed, or a closed requisition.

The stance drives both the pill color and the agent-insight panel described below, so the two always agree with each other.

In the top-right of the hero, every detail card also carries a Quick Survey button. It opens a one-question survey you can send to a teammate about this record, the same lightweight feedback tool used across the platform.

The agent-insight panel

Directly under the hero sits a persistent insight panel, the same "always-visible recommendation" pattern used on every entity detail card on the platform. Its mood tracks the stance:

• On track (calm, green check icon) for Healthy, Progressing, and Closed records.
• Watching (yellow icon) for the Watching stance.
• Recommended (red spark icon) for At Risk and Blocked records.

The headline is the same action-oriented line as the hero subtitle. Below it, two lines of evidence: the first explains the "why", the reasoning behind the read (for example, why a stalled posting usually traces to title, comp, or channel). The second, in italic, is the consequence of leaving it alone (what happens if you do not act). When a stance carries a quantified monthly cost of inaction, the panel adds it as a dollar chip so the number sits next to the reasoning, not buried in a report elsewhere.

For blocked stances specifically (a ban-the-box legal flag, an above-range comp gap, an internal candidate worth calibrating against), the evidence line is explicit that Verinode is surfacing the situation, not deciding it. You clear the flag, choose the range, or run the calibration.

Findings

The Findings tab is the only tab that can disappear entirely. It is hidden whenever there is nothing to show: no recruiting-specific signals for this record and no linked decisions. When it does appear, its tab label carries a badge with the combined count.

Inside, you see two kinds of content:

• Tips, short rows drawn from Verinode's recruiting signals for this exact record. Each row shows a headline, an optional rationale line underneath explaining the reasoning, and, where there is one, a suggested action in bold.
• Linked decisions, pulled in from the platform's decision engine when a broader decision references this record. Each shows its action title and, when a dollar figure is attached, a line reading the monthly cost of inaction, for example "$X,XXX/mo cost of inaction."

Context

Context always renders, but its content is entirely different depending on the record kind.

Open Role context

A two-column grid shows Status, Priority, Location, and Target Close date. Below it, if the requisition has any, a row of Required Certifications chips and a row of Posting Channels chips (the boards or referral channels this role is posted on).

Underneath that sits the Job Description panel, an editable text area holding the requisition's current JD markdown. Three controls sit above it:

• Refine With Hiring Advisor hands the role title, location, work arrangement, required and preferred certifications, and comp range to the Hiring Advisor specialist and asks for a redraft aimed at fresher, more outcomes-oriented language while preserving the comp range and required certs. While it runs, the button reads "Refining…". When it returns, the redrafted text replaces what was in the box and you are prompted to review before saving.
• Copy for ATS copies the current JD text to your clipboard so you can paste it into whatever applicant tracking system or job board you post through. It briefly reads "Copied" after you click it.
• Save JD is disabled until you have changed something, then writes the JD back and promotes it to the live version operators see when the role is posted.

Before you have typed anything, the box shows this placeholder text: "The JD renders here. Edit inline or click Refine With Hiring Advisor to have the specialist redraft it against the requisition's current role / certs / comp range."

Applicant context

At the top of the panel sits a Draft Offer button. It opens the offer-construction tool: a peer comp range (p25, p50, p75) for the role, a full total-package breakdown (base, bonus target, truck and phone allowances, employer health contribution, PTO days, retirement match, and the fully burdened annual total), and a set of counter-offer scripts you can use if the candidate pushes back. The peer range stays visible the whole time. You choose the opening base; Verinode never picks it for you. If this applicant's resume carries a legal review flag (see below), the Draft Offer button is disabled until you clear that flag, with a tooltip explaining why.

If a criminal-history mention was detected in the resume, a Legal Review Flag callout appears above the grid: "Criminal-history mention detected in the resume. Verinode has not scored this attribute. You review and decide before advancing." This reflects the platform's ban-the-box handling: in states that restrict use of criminal history in initial hiring decisions, Verinode structurally withholds that field from scoring rather than scoring around it quietly.

Below the callout, a grid shows Years Experience, Location (city and state), Source Channel (where the applicant came from), and Score. The score is a clickable button, not plain text: clicking it opens the Why This Score breakdown, which shows the overall score out of 100 and the five weighted dimensions behind it, each with its own weight and the points it contributed:

• Certifications Match (30% weight): how closely the applicant's held certifications align with the role's required and preferred certs.
• Experience Band (25%): years of restoration field experience relative to what the role expects, treated as a signal rather than a hard floor.
• Peer-Profile Match (20%): how closely the applicant resembles peers who stayed past their first 90 days in this role and state.
• Location Fit (15%): proximity to your service area, weighted harder for on-site roles than hybrid ones.
• Compensation Fit (10%): whether the applicant's preferred range overlaps yours.

If any risks were flagged during scoring (a legal review flag, or a mention the scorer skipped for compliance reasons), they list underneath with plain labels like "Legal review flag" or "Criminal-history mention (scorer skipped)." A disclaimer at the bottom of that modal is explicit: Verinode does not make hiring decisions; the scorer surfaces relative evidence, you weigh it.

Back in the Context tab itself, below the grid: a row of Certifications Held chips when the applicant has any, a Work History paragraph summarizing their background, and, when score components were computed, a Score Components list repeating the same five dimensions as simple "X/100" rows for a quick scan without opening the modal.

Interview Step context

A grid shows Step (phone screen, on-site, reference check, decision, or offer), Status, Scheduled date, and Completed date. When Verinode has drafted outreach for this step, a Draft Email, For Operator Review block shows the subject line and body underneath, staged for you to review and send, never sent automatically. When feedback has been logged on a completed step, a Feedback block shows it (redacted the same way work history is).

Talent Pool context

A grid shows Status, Years Experience, Last Nurture date, and Next Due date for the next scheduled check-in. Below it, an Interested Roles row of chips shows which role types this candidate has expressed interest in, and any notes on the candidate follow underneath (redacted the same way).

Pipeline

Pipeline only appears for applicants; it is hidden for every other kind. It lists every interview step for this applicant in sequence: step kind, status, and, once a step wraps, its feedback recommendation and completion date.

If the applicant has not been advanced into a pipeline yet, the tab reads: "No interview steps yet. Advance the applicant to generate a 4-stage pipeline with specialist-drafted questions + outreach email."

Coaching

Coaching appears only for applicants and talent-pool candidates, the two kinds where Verinode can draft something actionable next: next-step interview prep and counter-offer scripts for applicants, nurture outreach for talent-pool candidates.

The tab itself is intentionally light. It reads: "Coaching content draft-on-demand via the action buttons in the cards slider. Advance / decline / nurture each invokes the corresponding specialist and writes the draft email or question set to this section." In practice, that means the drafting happens when you click an action button on the record's row in the cards slider (Advance, Decline, or Nurture), and the resulting draft lands here for you to review before it goes anywhere.

Peer scope: National vs. State

Where the card's reasoning depends on peer comparisons (a role's time-to-fill against the market, a comp range for an offer), you can switch the comparison scope between National and State. State narrows the comparison to peer operators in the same state. Both scopes draw on Verinode's operator peer network, never on carrier data, and the underlying benchmark contributes back to the network the same way every anonymized peer contribution does across the platform.

Best-practice example

Say you open an Open Role for "Lead Water Tech" and its stance pill reads At Risk, "Stalled." The agent-insight panel explains why: the posting has been live past a month with fewer than a handful of applicants, and stalled requisitions almost always trace to one of three levers, title, comp, or posting channel. The Context tab confirms the comp range and the two posting channels currently active. You widen a channel and, separately, check whether the comp range needs a look with the compensation benchmarker. A few days later an applicant scores 88 against this role; her card opens with an At Risk, "Top Tier" stance, because top-tier candidates typically have other pipelines running and speed-to-offer is the lever. You open Draft Offer, see the peer p25 through p75 range, set an opening base inside it, and send the offer for her to consider. Verinode built the case; you made the call.

Related reading

• How Verinode surfaces decisions across the platform
• How benchmarks work
• Reading a benchmark