Sourcing
08 March 2026
Why "we'll find someone" is the most
expensive sentence in contracting


Procurement
Every contractor has heard it. The phone call from a crew lead, the day before mobilisation: we're short one materials controller, but don't worry — we'll find someone. The sentence is meant to be reassuring. It should be alarming.
The premium nobody quotes
When a workforce gap is filled at the last minute, the visible cost is the new hire's wages. The invisible cost is everything else: the pre-vetting that didn't happen, the briefing that got compressed, the documentation that lagged behind, the team that lost three days of cohesion bringing the new person up to speed, and the elevated risk of a no-show on day seven because the person was never properly screened in the first place. None of these costs appear on an invoice. All of them appear on the project's actual P&L.
The "we'll find someone" sentence is a euphemism for the absence of sourcing infrastructure. It means: we don't have a vetted bench, we don't have a pipeline, we don't have a backup process, so we'll lean on personal networks, fast turnover, and luck. The cost of that absence isn't paid by the workforce provider. It's paid by the contractor — in performance variance, retention churn, and contract overruns that look like bad luck but are actually the predictable output of an unstructured system.
Real workforce sourcing is unglamorous. It involves a continuously refreshed database of vetted candidates by role, region, and certification. It involves relationships with training institutions and trade unions maintained over years, not weeks. It involves cohort tracking — knowing which welder cohort from which programme tends to have the strongest documentation, the lowest no-show rate, the longest contract retention. It involves spending money on candidate engagement during the months when no contract is active, so that when one starts, the bench exists.
What proper sourcing actually costs
The contractors who think they're saving money by avoiding "expensive" workforce partners are usually paying that cost anyway, just at the back end of the project rather than the front. The bench gets built somewhere — either by the partner before the contract starts, or by the contractor in real time as the contract bleeds.
The objection: "we'll vet harder when it matters"
Some contractors and providers respond to this argument by claiming they vet rigorously when stakes are high — that the "we'll find someone" issue applies to junior roles, not critical ones. They have a quick-vet process for filler hires and a deep-vet process for key roles. The problem with the two-tier model is that workforce reality refuses to respect the tiers. The materials controller hired through a quick-vet process is the person who doesn't reconcile a delivery against the manifest, and three weeks later a critical valve assembly is missing and the project is on hold. The kitchen lead hired through a quick-vet process is the person whose food quality drives a 20% retention drop in month two. Junior roles in workforce contracting routinely produce senior consequences.
Active candidate database
The right model isn't tiered vetting. It's consistent vetting at a depth appropriate to the contract — meaning every role, no matter how junior on paper, gets vetted to the standard required for the contract to actually function.
Active candidate database
A continuously updated roster of vetted candidates across the three sectors, segmented by role, certification, region, and last engagement date. Candidates are re-verified at six-month intervals — not just held in a static list. The database is maintained between contracts as a standing capability, not built up reactively when demand arrives.
How VertiCore builds this
Standing relationships with training institutions, vocational programmes, and regional providers, refreshed quarterly. We track each cohort's performance metrics across deployments and use that data to weight sourcing decisions. New candidate intake runs monthly, not on-demand. Every month, regardless of active contract demand, a defined number of new candidates are sourced, vetted, and added to the database. This is the practice that distinguishes "having a bench" from "knowing some people."
Documentation standards
Every candidate in the database has a complete documentation pack — right-to-work, certifications, references, prior contract history — verified at intake and re-verified at six-month intervals. When a contractor needs a materials controller in 72 hours, the candidate exists, the documents exist, and the deployment timeline is set by mobilisation logistics, not by sourcing scramble.
The closing test
The next time a workforce partner says they'll "find someone," ask the question that exposes whether they have a system or a network: where will you find them, what's the average time-to-vet for that role, and how many candidates do you have currently active in your bench for this skill set in this region? The answer will tell you, in under two minutes, whether you're buying a sourcing operation or a phone-around. There's no shame in a phone-around — it's how a lot of contracting in Guyana has historically worked. But it should be priced and risk-rated as what it is, not bought as if it were sourcing infrastructure. The cheapest workforce partner is rarely the one with the lowest hourly rate. It's the one whose bench is real on the day the contract starts.

