Ask a CHRO how many contractors are doing work that has quietly become permanent, and the answer may be less certain than it should be. Ask who decided that work should become permanent, and the answer may be nobody.
That is how a shadow permanent workforce forms. Not through deliberate workforce strategy, but through decisions that made sense individually: another six-month extension, a specialist retained after a project ended, a temporary requirement never formally reassessed. Eventually, precedent begins doing the work that strategy should be doing.
For South African employers, the distinction matters commercially and, in some circumstances, legally. Permanent employment provides continuity and retained capability. Contract employment provides access to skills and capacity for a defined need. Both become expensive when applied to the wrong work. The useful question is not which model is better, but what the business needs from the role, for how long, and what happens when that need changes.
Start with the work
A permanent employee leaves, so another is recruited. A project falls behind, so a contractor is added. A specialist skill is urgently needed, so the fastest hiring route becomes the default. Each decision may solve the immediate problem while creating a longer-term workforce issue.
Employers should first establish whether the work is genuinely ongoing, how predictable demand will be, how quickly the capability is required and whether it needs to remain inside the organisation. A role carrying institutional knowledge and long-term accountability calls for a different approach from specialist expertise needed for a defined project. At its simplest, the decision is whether to build capability or access it.
That distinction becomes easier to lose over time. A six-month requirement becomes twelve because a programme runs late, then eighteen because the contractor holds knowledge nobody else has. Extending may still be right, but it should remain a decision rather than an administrative continuation of the last one.
When each model makes sense
Permanent hiring is strongest when the work itself has permanence. Roles central to operations, leadership, customer relationships, intellectual property or long-term strategy benefit from continuity because people accumulate context: why decisions were made, which relationships matter and where processes tend to fail.
The problem arises when permanence is assumed rather than tested. If funding is temporary or workload is likely to decline, permanent headcount creates rigidity that outlasts the need.
Contract hiring works when the requirement is clearly defined: a transformation programme, system implementation, regulatory deadline or short-term demand spike. It lets capacity expand and contract with the work and can provide faster access to specialists than a permanent search. Months spent searching for the ideal candidate carry their own commercial cost.
However, flexibility can become dependency. When contractors remain in business-critical positions year after year, the temporary label stops reflecting reality. Without deliberate handover, specialist expertise also leaves when they do.
Contract hiring therefore requires governance. Someone needs visibility of who is working across the contingent workforce, what they cost, how long they have been there and why contracts keep being extended. Procurement, HR or the workforce function should track tenure and original scope, while the accountable business leader justifies material extensions against the current requirement. A contract moving materially beyond its original timeframe or scope should trigger an explicit decision: extend for a defined reason, convert the capability, transfer the knowledge or end the requirement.
Without that discipline, a flexible workforce can become a shadow permanent workforce.
Beyond salary versus day rate
Cost comparisons are often too simplistic. A permanent employee carries salary, benefits, recruitment and training costs. A contractor may have a higher visible rate, but the organisation is purchasing capability for a defined period.
Time has a cost too. If a specialist can start within weeks and prevent a programme losing several months while a permanent search continues, the premium may be commercially rational. The reverse also holds. Paying contract rates for stable work over several years makes little sense once the capability could have been built internally at lower total cost.
The relevant comparison is total cost and value over the requirement’s expected lifespan, not two headline rates side by side. How long will the work genuinely exist, and what will the organisation spend over that period? What is the cost of waiting for the capability, and what happens to the knowledge when the engagement ends?
Most functions need both models. A technology team can retain permanent architects while contracting specialist capability for a cloud migration. A finance function can maintain its permanent core while engaging contract professionals through a systems change. The discipline is matching the model to the work, then revisiting that match as circumstances change.
When temporary stops being temporary
Consider an illustrative South African financial services organisation replacing its core banking platform over 18 months. At peak delivery, it brings in 25 contract specialists across integration engineering, data migration, testing and regulatory remediation. These are defined requirements linked to a programme with an expected end point, so contract engagement makes commercial sense.
After go-live, eight specialists remain for three months of stabilisation. Three months becomes six. A year later, five are still supporting integrations, resolving production issues and maintaining processes now firmly inside business-as-usual operations.
There was no meeting at which executives decided to create five long-term contract positions. Each extension could be defended individually. Collectively, however, the work changed while the workforce model did not.
During build, migration and testing, the organisation needed temporary specialist capability. After go-live, it needed something different: stable ownership of production systems, retained knowledge and ongoing accountability. The work moved from programme delivery to business-as-usual support.
That should have triggered a workforce decision.
Instead, the organisation can continue paying contract rates for permanent work, end the contracts and lose critical knowledge, or recruit permanent employees while paying contractors to maintain the function during transition.
The problem is not that contractors stayed beyond go-live. Stabilisation is legitimate, and extending specialist support can be entirely rational. The problem is that there was no defined point at which stabilisation had to prove it was still stabilisation.
That is how the shadow permanent workforce grows: through reasonable extensions that are never considered together.
The test worth applying
Before the next contract extension is signed, ask yourself a different question.
Not “do we still need this person?”, which usually gives the same answer as last time, but: does this contract still describe what is happening, or a decision the organisation made once and stopped reviewing?
Call it the scope test and apply it before renewal becomes automatic. It forces the organisation back to the question it should have answered before precedent took over: what work needs to be done now, and what workforce model actually fits it?
If the answer is uncomfortable, the extension is not a scheduling formality. It may be the moment a temporary solution quietly becomes a permanent liability.