Staff Augmentation: 6 Critical Legal Checks Vendors Skip

Staff augmentation and the two statutory clocks: twelve continuous weeks under the UK Agency Workers Regulations 2010, three months under South Africa's Labour Relations Act section 198A
Neither clock cares what the contract is called. Both look at who directs the work.

Every page on the first screen of results for staff augmentation is written by a firm that sells it. That is not a scandal, it is just who has a reason to publish. The effect is that an entire commercial model gets explained without anyone mentioning the statutes that govern it — and those statutes are the part that decides who your problem belongs to when something goes wrong.

We do not sell this model. Mimir does strategy, architecture and build; we are not a body shop and we do not pretend to be, which is what our piece on IT outsourcing to South Africa has said in public since the day it went up. This piece exists to help you buy the model properly from someone who does sell it.

What staff augmentation actually is

Staff augmentation is simple to state. A supplier places a named individual into your team. They work in your tools, to your process, under your direction, alongside your own people. The supplier keeps them on its payroll and invoices you for the time.

That is the whole model. Everything else in the category — outstaffing, team extension, resource augmentation, dedicated developer — describes the same arrangement in different marketing language. The distinction that matters is not between those words but between this and outsourcing, where you buy a defined outcome and the provider decides how to staff it. We have already drawn that line in detail and will not redraw it here.

What almost no vendor page says is that staff augmentation is a recognised legal arrangement in most of the jurisdictions it is sold into, with named provisions and running clocks attached. Those provisions do not care what you call the contract. They look at who directs the work.

Six contract checks for a placed worker: which clock is running, who determines status, who operates PAYE, who owns the code, who tells you they left, and who checks the terms
All six are contract questions. None of them are technical ones.

Two statutory clocks, and both of them start on day one

The single most useful thing to understand about staff augmentation is that the arrangement changes shape on its own after a period of time, without anybody signing anything.

In the United Kingdom, the Agency Workers Regulations 2010 define an agency worker as someone supplied to work “temporarily for and under the supervision and direction of a hirer”. That is a description of this model, not of outsourcing. Regulation 7 sets a qualifying period: the worker must work in the same role with the same hirer for 12 continuous calendar weeks. Once that is passed, regulation 5 entitles them to the same basic working and employment conditions they would have had if you had recruited them directly, and regulation 6 lists what that covers: pay, the duration of working time, night work, rest periods, rest breaks and annual leave.

In South Africa the equivalent clock is shorter and the consequence is larger. Section 198A of the Labour Relations Act, inserted by the Labour Relations Amendment Act 6 of 2014, defines a “temporary service” as work for a client for a period not exceeding three months, or as cover for someone temporarily absent. An employee who is not performing a temporary service is, in the words of section 198A(3)(b), “deemed to be the employee of that client and the client is deemed to be the employer”, and employed on an indefinite basis.

Two limits on that, both in the same section and both routinely omitted. Section 198A(2) says the section does not apply at all to employees earning above the threshold set by the Minister; that threshold is currently R269 600.90 a year, set by Government Notice 7384 in Gazette 54544 and effective from 1 May 2026. And section 198A(4) makes it a dismissal for the supplier to end a placement in order to avoid the deeming provision, so running people out at eleven weeks is not the workaround it looks like.

Whether the client became the sole employer or merely a second one was argued to the Constitutional Court. In Assign Services v NUMSA, decided 26 July 2018, the Court held for the sole employer reading, describing it at paragraph 75 as “not a transfer to a new employment relationship but rather a change in the statutory attribution of responsibility as employer within the same triangular employment relationship”.

Our own piece on outsourcing describes this model as one where the provider handles employment, payroll and compliance. That is true of the commercial arrangement and it is how staff augmentation is sold. What these provisions do is set out the conditions under which it stops being the whole story.

Off-payroll working: who decides, and who pays when the answer is wrong

Not every staff augmentation engagement runs through the supplier’s own payroll. If the person placed with you works through their own limited company instead, a different UK regime applies, and the duty sits with you.

HMRC’s guidance for clients, published 7 March 2023 and last updated 30 August 2024, is direct about it. You must communicate your determination in a Status Determination Statement, which must be passed to the worker and to the party you contract with, and must give your conclusion and the reasons for reaching it. You must take reasonable care in making it. And then the sentence that matters: “You must also provide reasons for your determination. If you do not, the worker’s Income Tax and National Insurance contributions become your responsibility.”

There is a second trapdoor next to the first. A worker or deemed employer can disagree with your determination at any point until the last payment for their services, and you must respond within 45 days. “Failure to respond within 45 days will result in the worker’s Income Tax and National Insurance contributions becoming your responsibility.” That is an administrative deadline with a tax bill attached, and it lands on whoever in your business is not expecting it.

Small clients are outside this and the duty stays with the worker’s own company.

Here is a discrepancy worth knowing about rather than resolving from a blog. HMRC’s page states the conditions as turnover above £10.2 million, a balance sheet total above £5.1 million and more than 50 employees. Those figures came from the Companies Act 2006 small companies regime, and regulation 9 of the Companies (Accounts and Reports) (Amendment and Transitional Provision) Regulations 2024 substituted £15 million and £7.5 million into that regime for financial years beginning on or after 6 April 2025. If your business sits anywhere near either line, that is a question for your accountant and not for your supplier — and certainly not for us.

The umbrella company rule that changed in April 2026

This is the newest piece of structure in staff augmentation and the one most likely to be missing from a proposal written last year.

Where an umbrella company employs the placed worker, HMRC’s guidance for supply chains including umbrella companies now states that from 6 April 2026 “the agency or end client is responsible for making sure PAYE is operated correctly”. Where there is no agency in the chain, that responsibility sits with the end client — which, in a direct engagement, is you. If the umbrella fails to account for the tax, HMRC can recover the underpayment from the responsible party rather than only from the umbrella.

The practical consequence is small to describe and expensive to discover. A supply chain you never mapped now determines who carries a PAYE liability, and the answer changed in the middle of contracts that were signed before it did.

The code they write is not automatically yours

An employee’s output belongs to you by default. A placed person’s does not, and this is where staff augmentation quietly differs from a hire in a way that surfaces years later.

Section 11(2) of the Copyright, Designs and Patents Act 1988 gives first ownership to the employer only where the work is “made by an employee in the course of his employment”. A person on somebody else’s payroll is not your employee, so the default does not reach them. Section 90(3) then closes the other end: “An assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor.”

South Africa’s Copyright Act 98 of 1978, as gazetted, carries the same requirement at section 22(3). We have not been able to retrieve a consolidated current text of that Act from a primary source, so we are not going to characterise the present South African position beyond that, and neither should the supplier selling you staff augmentation into it.

A purchase order is not an assignment. Neither is an invoice, a statement of work that says “all deliverables shall belong to the client” without a signature from the right party, or a supplier contract that assigns rights the supplier never held because its own employment terms did not capture them first.

The check is unglamorous and takes ten minutes: read the chain from the individual to the supplier to you, and confirm every link is in writing and signed. Do it at the start of a staff augmentation engagement, because doing it during a due diligence exercise three years later is where it usually happens instead.

Access that outlives the engagement

The placed person holds your credentials. They are in your tenant, your repositories, your ticketing system and quite possibly your production estate. And they are not in your HR system, so nothing fires when they leave.

NIST’s SP 800-53 Revision 5 names the gap precisely. Control PS-7 requires an organisation to “require external providers to notify [Assignment: organization-defined personnel or roles] of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges, or who have system privileges” within a defined time period. The control exists because that notification is the only thing that starts your offboarding, and it is a contractual obligation on the supplier or it does not happen.

Third-party accounts are a well-documented route in, which is the argument our analysis of identity attacks overtaking software exploits makes at length. A staff augmentation arrangement adds the specific twist that the account belongs to somebody whose employment you do not control and whose departure you may learn about weeks late.

Six checks worth making before anyone starts

None of these are hostile, and a good supplier will have answered all six before. A staff augmentation contract is negotiated once and lived with for years, so this is the cheapest hour in the relationship.

  1. Which clock is running, and from when. Twelve continuous weeks in the same role in the UK, three months in South Africa, and a different answer again wherever else you are placing people. Write the start date down.
  2. Who issues the status determination statement, and who responds inside 45 days. Name the person, not the department. This is the duty most likely to be nobody’s.
  3. Is there an umbrella company in the chain at all? Ask for the chain in writing. You cannot decide who operates PAYE until you know who is in it.
  4. Is the copyright assignment signed, by the individual as well as by the supplier? One signature in the wrong place breaks the chain.
  5. Is the supplier contractually obliged to tell you when the person leaves their payroll, and how fast? Put a number of hours in the clause.
  6. Who has compared your own terms against the placed person’s? After the qualifying period the comparison is not optional, and somebody has to have actually made it.

There is a seventh question that is not legal at all: who internally is going to direct this person day to day. Staff augmentation buys capacity, not management, and an unmanaged placed engineer produces very little at full rate.

When staff augmentation is the wrong answer

Four situations, all of which we have watched go badly.

When the requirement does not exist yet. Staff augmentation amplifies ambiguity rather than resolving it. Placing a person against an undefined problem produces an expensive discovery exercise conducted by somebody with no context. Define the work first, even roughly.

When what you actually need is judgement, not hands. A day of senior architectural thinking is not four days of a mid-level engineer, and buying the second because it is easier to price is the most common mistake in this category. That is an advisory purchase, described in managed IT services and, in its independent form, in a virtual CIO engagement.

When you have nobody to direct the work. This model transfers employment administration, not management. If nobody internal has the hours, you want an outcome contract instead.

When the placement is really a permanent role in disguise. If the work is indefinite, the role is core and the person is doing exactly what your employees do, both statutory clocks above are pointing at the same conclusion, and so is common sense. Hire them, or accept what the arrangement will become.

The day rate we are not going to publish

Search for what staff augmentation costs and you will find hourly and daily ranges by country, quoted with confidence. We chased several and could not get any of them to a primary source. They cite each other, or they cite a supplier’s own rate card presented as a market rate.

So we are not publishing one. A rate quoted without knowing the skill, the seniority, the notice period and the jurisdiction is marketing rather than information, and a range laundered through six blogs is worse than that. The same applies to the “save forty percent” figure attached to this model everywhere; we found no measured study behind it.

What is worth understanding is the shape. You are paying for time, so the cost moves with utilisation, and the things that actually change the number are seniority, notice period, whether the rate includes the supplier’s employment cost in the worker’s own country, and how much of your internal management time the arrangement consumes. That last one never appears on the invoice and is frequently the largest line.

Two other things we could not get to, named here rather than papered over. SAFLII, which hosts South African case law, returns 403 to automated requests from our infrastructure, so the Constitutional Court judgment above is cited from the Court’s own repository instead. The same applies to several government hosts we tried for the consolidated Labour Relations Act, which is why the statutory text here comes from Parliament’s published copy of the amending Act.

What is coming, and why the dates are soft

The statutory frame around staff augmentation in the UK is mid-change. The Employment Rights Act 2025 extends a right to guaranteed hours to qualifying agency workers, with the hirer responsible by default. The Government’s own implementation timeline, last updated 25 August 2026, places the right to guaranteed hours in 2027 with timings that “will be updated after consultation”, and states plainly that “all future dates remain subject to parliamentary processes and may change”.

We are not going to tell you what to do about a measure whose commencement date does not exist yet. What we will say is that the direction is consistent across both jurisdictions in this piece: the longer a placed person looks like an employee, the more the law treats them as one. Any staff augmentation arrangement designed on the assumption that this never happens is designed against the trend.

How we work with this

We are a consultancy. We do the layer above delivery capacity: architecture decisions that are expensive to reverse, the migration with a vendor deadline attached, the incident where the first hour of judgement matters. Distance is not a constraint on that work, as our piece on remote IT consulting across time zones sets out, and the estates it applies to increasingly have no office at their centre, which is the subject of distributed IT architecture.

For delivery capacity we work alongside a specialist partner, named in the outsourcing piece linked at the top. That separation is deliberate: the party specifying the work and the party resourcing it should not be the same party, for the same reason a vCIO should not be reviewing their own implementations.

It also means we have no reason to flatter staff augmentation or to rubbish it. Where you already have a capable internal person and the gap is cover rather than capacity, the arrangement you want is probably co-managed IT instead. Where the gap is genuinely hands on a defined body of work, staff augmentation is a perfectly sound way to buy it — provided somebody has read the six checks above before the first day rather than after the first year.