Most organisations measure vendor performance in the wrong place.
The quarterly review looks at contract adherence, rate compliance, and fill rates reported by the supplier themselves. The VMS stores the data. The procurement team reviews it. The supplier scores well enough to retain the contract.
Meanwhile, at site level, the same supplier is responsible for three no-shows last month, two workers sent without the right credentials, and a fill time that consistently runs forty minutes past the shift start. None of that appears in the quarterly review. It lives in a planner's memory, a WhatsApp thread, and a spreadsheet that nobody ever analyses.
The information exists. It lives in a system that was never connected to where decisions get made.
Vendor Management Systems were not built for planners. They were built for procurement teams — the people who negotiate rates, manage supplier relationships, and ensure the organisation's contingent spend is governed and visible. The VMS does that job well. It was designed to.
Shift planning tools were not built for procurement. They were built for site managers, operations supervisors, and frontline planners — the people who need to know, at 05:45 on a Tuesday, whether the morning shift is covered. Scheduling platforms evolved for speed and simplicity, because the people using them cannot afford to wait.
Each category optimised for a different buyer. Each solved a different problem. And for years, that made sense — because the buyers rarely sat in the same meeting, and the systems rarely needed to talk.
The contingent workforce has changed that. When agency workers, bank staff, and direct employees run through the same sites, against the same compliance requirements and the same shift patterns, the separation between how you procure them and how you deploy them becomes a structural liability. The commercial decision and the operational consequence are now the same event — managed in different systems.
The obvious loss is the one "The Gap" post covers — the planner filling shifts without access to vendor logic, the compliance check that happens after the assignment rather than before it. That is the operational cost.
The less visible cost is strategic.
When vendor governance and shift execution are disconnected, supplier accountability is measured on the terms most favourable to the supplier. Fill rate is reported as a percentage of shifts requested — not as a percentage of shifts where the right worker arrived on time with valid credentials. Response time is measured from request to confirmation, not from confirmation to actual show-up. Performance looks clean at the contract level because the contract level is where the data lives, and the contract level is never where performance actually fails.
The organisation ends up making vendor decisions based on a picture that is accurate but incomplete. The supplier who scores well in the quarterly review may be the one creating the most operational disruption at site level. Without a system that connects the two, there is no way to know — and no structured way to act on it even if you suspect it.
Most workforce technology still behaves like a system of record. It stores what happened. It documents what was agreed. It captures the transaction after the fact.
That was sufficient when contingent labour was secondary — a small proportion of headcount, managed at arm's length, reviewed periodically. It is not sufficient when contingent workers are central to service delivery and performance is measured in real time.
The shift workforce technology needs to make is from passive administration to active coordination. That means the system does not just record that a shift was filled — it influences how the shift was filled, by surfacing the right workers, enforcing the right rules, and flagging the right risks before the decision is made rather than after it.
It means a manager asking which suppliers are genuinely performing gets an answer based on shift-level data — fill rates, reliability, response time, credential compliance — not a summary from the supplier. It means a planner assigning a worker is working within rate logic that reflects the contracted framework, not acting on instinct and reconciling the cost later. It means a COO asking about site coverage sees an answer that is live, not eighteen hours old.
None of this requires new data. It already exists — in the VMS, the shift record, the attendance log. The requirement is that it operates as one coordinated model rather than separate systems sharing nothing.
A VMS without shift-level execution data is a governance layer that stops at the contract. It can define what was agreed. It cannot tell you whether it was delivered.
A shift planning tool without vendor governance is an operational layer without commercial control. It can fill work. It cannot tell you whether it was filled at the right cost, by the right supplier, with the right accountability in place.
Together, they answer questions that neither can answer alone. Which suppliers are performing where it matters? Which sites are at risk before the shortage materialises? Which shift patterns are consistently over-cost — and why? Where is compliance exposure concentrated?
These are not reporting questions. They are the questions that determine how well an organisation manages its workforce — and most organisations cannot answer them, because the data lives in systems that were never designed to share it.
The organisations that connect them will not simply reduce friction. They will manage their contingent workforce the way they manage every other strategic input: with visibility, accountability, and the ability to act before problems escalate.