Cross-section links and the seasonal signal

What this article covers

Recruiting doesn't run as its own island. A hire you close here changes what Team shows about your bench. A staffing gap Team flags can turn into an open requisition here without you retyping the role from scratch. A new hire's certifications get checked against every carrier program you're enrolled in before anyone assigns them to that carrier's work. And once a year, Verinode tells you when your own hiring history says it's time to post ahead of your seasonal peak, before the surge hits, not after.

None of this is a separate feature you turn on. It's a set of links Verinode's signal engine draws automatically between Recruiting, Team, and Clients, plus one seasonal calculation that runs off your own hiring history. This article walks through all four, so you know what triggered a given signal, where else it shows up, and what to do about it. Recruiting itself, its six home rows and seven slider tabs, is covered in Recruiting: overview and how the section works; this article assumes you're already there.

Open Recruiting from the sidebar at /recruiting. Recruiting is a Premier feature and a switchable section; see the overview article for both gates. Everything below happens automatically once the section is active, there's nothing extra to switch on.

1. How a hire strengthens the bench

The moment an applicant's status flips to Hired, whether you mark that on the Applicants tab or it lands via the Hiring Advisor's own tracking, Verinode reads that applicant's certifications and years of experience and writes a signal about it. That signal is tagged to the team domain, not recruiting, on purpose: the comment in the code that emits it is explicit that signals surface where they matter to the operator, not where the code that emits them lives. A new hire changing your coverage picture is a Team-side fact, so it shows up on Team, specifically feeding your depth chart and succession planner, which both re-run overnight to reflect the addition.

The signal's title names the new hire directly and frames it as your bench getting stronger. If the hire brings certifications with them, the body lists them (in the same uppercase cert-code style you see everywhere else, like WRT or AMRT) and notes that the succession planner re-runs that night; if the hire has no certifications on file yet, the body just confirms the new member has been added to the depth chart. Either way, the recommendation nudges you to check depth for the roles the new hire can now cover, since that may be the moment to reallocate or retire a subcontractor backstop you no longer need.

The retention cascade

The same signal type fires again later, from a different trigger: capturing a retention checkpoint. On the Hires + Retention tab, the Awaiting Checkpoint list lets you log Retained, Departed, or Departing Soon against a hire's 30/90/180/365-day mark. What happens next depends on what you capture:

• Retained at the 90-day mark or later. Verinode fires the bench-strengthened signal again, titled around the hire clearing that day mark, noting the checkpoint passed and that it's now contributing to your peer retention benchmark. Nothing fires at the 30-day mark specifically; the reinforcement is reserved for the point where retention starts meaning something.
• Departed. Verinode reuses the signal type that normally flags a team member at elevated flight risk, since an early departure unwinds the very bench-strength signal the hire originally created. The title notes the day-count at which the departure happened; the body explains that a retention specialist retrospectively scores the original hiring decision, and that the outcome feeds the peer retention benchmark either way. The recommendation points you back to the succession planner to check depth coverage for whatever the departing hire was backing.

Both directions land back on Team, tied to the same team member record the hire produced, so the full arc, hired, strengthened, then either reinforced or unwound, reads as one continuous story on that person's record rather than two disconnected events.

2. How a team hiring decision spawns a requisition

Team's decision engine can conclude you need to hire, based on a workload or headcount signal it caught elsewhere on the platform. When it does, it writes a team_hiring_decision on Team, and Recruiting's Findings tab lists it under "pending hiring decisions still awaiting a requisition" until you act on it.

Opening that decision's workspace shows a Recruiting Bridge card. Before a requisition exists, it reads "Define the role and open a requisition," with a note that the flow walks you through role, comp band, timeline, and location, and that Verinode refuses to inherit the decision's own headline as the role name. The button reads Define + Create. Click it and a five-step modal opens:

1. 1Role. Name the actual position (the modal's own example is "Lead Water Tech" or "Estimator II"), plus an optional internal slug that gets derived from the title if you leave it blank. If what you type matches the decision's headline exactly, the modal blocks you with "That's the decision headline. Use the actual position name instead," and won't let you continue until you fix it.
2. 2Compensation. Annual low and high, in dollars. Leave both blank if you're still benchmarking, this step is optional.
3. 3Timeline. A target close date and a priority of Low, Normal, or High.
4. 4Location. State, city, and work arrangement (Onsite, Hybrid, or Remote).
5. 5Review. Every field you entered, plus a note when a job-description draft from the Hiring Advisor is going to land on the requisition automatically (you can still edit it afterward on the Recruiting page). Clicking Create Requisition submits.

Whatever the decision's evidence already had (a role slug, a comp band, required certifications, a draft job description) pre-fills the matching step, but every field is editable, and nothing silently becomes the requisition without you seeing it first. This mirrors why the guard rail exists at all: a decision headline like "Critical staffing gaps in Texas" is a problem statement, not a job title, and letting it slide through unedited would leave you with a nonsensical open role.

Once the requisition is created, the Recruiting Bridge card flips to "Requisition is open for this hire," with an Open Requisition button that jumps straight to it on the Open Roles tab. The new requisition also carries a link back to the decision that spawned it, which is what makes it show up on that decision's own trail from the Findings side later. If a requisition already exists for a given decision, revisiting it reuses that same requisition rather than creating a second one.

3. Carrier-program cert gates on a hire

If you're enrolled in one or more carrier programs (active or pending, tracked on the Carrier Programs tab under Clients), closing a hire triggers one more check: does this specific new hire meet the certification bar each of those programs requires. This runs independently of your team's overall coverage on the Carrier Programs tab, that page reads your whole roster's standing against a program; this check is scoped to the one person you just hired.

For every program you're enrolled in, Verinode compares its published list of required certifications against what the new hire holds. Wherever the hire is missing something the program requires, it writes a warning-severity signal naming the hire, the specific missing certification(s), and the program, with a body spelling out exactly what the program requires versus what the hire currently has on file (or that they have no certifications on file at all yet). The recommendation is concrete: enroll the hire in the missing certification training before assigning them to that program's work, and the Cert Renewal specialist can draft the enrollment plan.

This signal is tagged to the client domain rather than recruiting, again on purpose, and it surfaces in two places at once: on the hire's own record inside Recruiting, and on that carrier program's own detail under Clients > Carrier Programs. Wherever you happen to be looking when the question comes up (did this new hire clear the bar for the program we depend on) the answer is right there.

4. The seasonal post-ahead-of-peak signal

Restoration hiring isn't flat across the year, most operators have a month (or a short window) where hiring activity historically runs highest, driven by storm season, holiday staffing, or whatever your own market's pattern looks like. Verinode reads that pattern from the anonymized peer network's seasonal hiring data and turns it into a lead-time nudge: post the role before the peak hits, not after applicants are already scarce.

Verinode looks at the historical hiring-activity pattern by calendar month and picks the single month with the strongest seasonal pull as your next peak. It then works out how many days out that month's start is, rolling forward to next year if this year's occurrence has already passed. Once that peak is within 60 days, Verinode treats it as "post now" territory.

You'll see this in two places on Recruiting's home page:

• The hero panel, at the very top. Its usual subtext ("N applicants across N open roles") is replaced with a prompt naming the upcoming peak month and how many days out it is, once you're inside that 60-day window.
• The Seasonal row, the last row on the home page. Inside the window, it's a large double-width tile reading "Post for [Month]," with a line underneath naming how many days out the peak is and reminding you that opening roles now lands pipelines before the surge hits. Clicking it opens the Open Roles tab so you can act immediately. Outside the window, or if Verinode hasn't established a seasonal pattern for you yet, the row instead reads: "When your historical peak hiring month approaches, this row recommends posting ahead of the window."

The four links, side by side

| Trigger | What fires | Domain it surfaces on | What it's tied to | |---|---|---|---| | Applicant status flips to Hired | Bench-strengthened signal | Team (depth chart, succession planner) | The new team member record | | Retention checkpoint captured as Retained at 90+ days | Bench-strengthened signal (again) | Team | Same team member record; feeds the peer retention benchmark | | Retention checkpoint captured as Departed | Elevated-flight-risk signal (reused) | Team | Same team member record; retrospectively scores the original hiring decision | | Team's decision engine concludes you need to hire | Hiring-decision signal, then (once you build it) a linked requisition | Team, then Recruiting | The Recruiting Bridge card and the five-step wizard | | A hire closes while you're enrolled in a carrier program | Program-onboarding-gate signal, once per missing certification set | Client (also visible from Recruiting) | The hire's record and the carrier program's detail |

Best-practice example

Say you close a hire for a Lead Water Tech role that was itself created from a hiring decision Team flagged three weeks earlier. The moment you mark the applicant Hired, three things happen without you doing anything further: Team gets a bench-strengthened signal and re-runs the depth chart and succession planner overnight, the new requisition (already linked back to the original decision) shows the hire against it, and if you're enrolled in a carrier program that requires a certification this hire doesn't hold yet, a warning shows up both on the hire's record and on that program's detail under Clients. Ninety days later, capturing that hire as Retained on the Hires + Retention tab closes the loop with a second bench-strengthened signal, and that outcome starts counting toward your peer retention benchmark. If your seasonal pattern says your peak hiring month is coming up within the next two months, the Seasonal row on the Recruiting home page will already be telling you to post the next role now rather than waiting.

Related reading

• Recruiting: overview and how the section works
• Open Roles and requisitions
• Hires and retention
• The depth chart: service-line coverage and single points of failure
• Carrier Programs: eligibility, required certs, and vendor approvals
• The decision workspace
• How benchmarks work