Stop Chasing a "Predictable" Cleared Hiring Pipeline
Or: why the monthly number is lying to you.
Every recruiting leader I know gets asked the same question eventually: "Why is our pipeline drying up? We just had a great month, where are the next candidates?"
I get why leadership asks. A forecast lets you plan for scale, budget headcount, and catch bottlenecks before they get expensive. Forecasting isn't the problem. Leadership needs numbers, and they should have them. The problem is what we mean by "predictable."
I'm not talking about a directional forecast, a reasonable planning assumption, or a budget range. Those are useful, and I lean on all three. What I think is a fool's errand, especially in cleared staffing inside the IC and govcon space, is expecting a recruiting team to reliably hit a narrow monthly hiring number regardless of what's happening with the contracts underneath it. That's false precision dressed up as planning. And I say that as someone whose actual job is building that pipeline.
In cleared staffing, a single contract award or loss can rewrite a hiring forecast overnight, so holding a recruiting team to a narrow monthly number is false precision. Measure what the team actually controls, plan in a small set of scenarios instead of one confident guess, and judge performance year over year, not month to month.
The market doesn't move in a straight line
In most industries, hiring volume tracks fairly closely with sales pipeline and seasonal demand. You build a model, and you can mostly trust it. In our world, a single contract award can double a hiring need overnight, and losing one can erase the forecast just as fast.
Here are the forces that routinely throw a clean monthly model out the window:
One win can double a hiring need overnight. We don't hire preemptively expecting it, but we invest heavily in contingent offers tied to the award, and if it doesn't come through, that work disappears overnight.
When government funding contracts, the first casualties are usually open vacancies, not the people already billing on contract.
When a competitor loses a contract, their people land somewhere, sometimes with you, and hiring can spike in a way no monthly model saw coming.
When policy preference moves toward fixed price instead of cost plus, staffing models that worked for years can look completely different overnight.
A new administration can shift federal funding priorities within months, and hiring feels it first. Positions tighten or disappear around a transition well before any of it reaches a headline.
No five year staffing plan accounted for COVID freezing clearance processing and onboarding for months at a stretch.
A few years back we were the subcontractor on a recompete we genuinely didn't feel great about, so we didn't build that hiring into our forecast at all. We won it anyway. Our forecast got thrown out by mid year, and we spent the rest of it adding what we started calling stretch goals just to keep up.
Nobody executed poorly. The plan did exactly what a conservative forecast is supposed to do on a long shot. The long shot just didn't stay a long shot.
So what do you actually track
I'm not saying stop measuring. I'm saying measure at the right altitude, and measure the right things. Recruiting teams should absolutely be held accountable, just not for the parts of the outcome nobody on the team controls.
| Hold the team to this | Not this |
|---|---|
| Execution and sourcing quality | Whether a contract is awarded on schedule |
| Candidate experience and responsiveness | Whether government funding tightens |
| Relationship building | Whether policy shifts cost plus to fixed price |
| Submittals, interviews, offers, start dates | Whether a program gets scaled back |
None of this means execution stops mattering. It matters a lot. A strong recruiting team consistently outperforms an average one working the same market conditions, and slow follow up alone costs hires that a sharper process would have saved. But even the best team on its best day is still operating inside conditions somebody else controls.
Month to month, I still watch the standard numbers: submittals, interviews, offers, start dates. What those numbers alone can't tell you is whether a slow month is a performance problem or a market problem. That's where scenario planning earns its keep. Instead of one point forecast, I build a small set of them:
Built off steady state attrition and known open reqs.
If a pending award comes through.
If it doesn't, or if a program gets scaled back instead.
Leadership gets a range with reasoning attached, not a single confident guess dressed up as a fact. That's messier than a clean number in a slide deck. But honest beats confident when leadership needs real data to make decisions, which is the whole reason they wanted a forecast in the first place.
Compete with your former self
Here's the shift that actually helps me, both for my own sanity and for genuinely getting better at this job. Instead of asking "did we hit the monthly number," I ask a different question.
Did we do better than we did last year, at this same point, under similar circumstances? If the answer is no, I want to know why. If yes, I want to know what changed, and whether it actually moved the needle or just felt good in the moment.
Annual performance is where I hold myself accountable. A full year of these scenarios playing out washes out the monthly noise, and that year over year comparison dilutes a lot of what any single event creates inside one given month. Monthly and quarterly still matter day to day. They just don't tell the whole story in this market.
To be fair
I'll admit the annual view has a real cost.
The honest downside: it's a harder sell to leadership who want an answer this quarter, and it can feel like you're dodging accountability if you're not careful about how you present it.
The fix, I think, is pairing the annual view with the contingency scenarios above. You're not avoiding a number. You're giving a better one, with the "if this, then that" built in from the start.
The part I keep coming back to
Recruiting is, at the end of the day, an attempt to predict people. And people don't move in straight lines either. Some months are big. Some months are quiet. Clearance timelines shift without warning. Candidates get cold feet the week before their start date. Someone takes a counteroffer nobody saw coming.
Don't try to forecast one future. Plan for the handful of futures you can actually see coming.
The recruiters and staffing leaders who last in this market long term aren't the ones with the tightest monthly forecast. They're the ones who built a system flexible enough to be right more often than wrong, and honest enough to say so when they weren't. If you're building a pipeline model right now, I'd rather you build one that bends than one that breaks.
A forecast that bends needs real market signal
Scenario planning only works when you can see the contracts, recompetes, and clearance-market shifts moving underneath your pipeline. That's the signal we track across the Fort Meade cleared market.
