MSP (Managed Service Provider)

What does an MSP change for the hiring manager?

The manager stops calling a preferred contact and starts raising a request through the programme, which routes it, collects submissions, and applies the agreed rates. The gain is consistency and visibility of what is being spent across the organisation. The loss, at least initially, is the informal shortcut that experienced managers relied on. Programmes that survive contact with hiring managers make the standard route fast enough that nobody needs the shortcut, rather than simply forbidding it.

How should a supplier evaluate a panel seat?

By what it costs to serve rather than by the headline opportunity. The questions worth answering before joining are how many suppliers see each role, whether submissions are capped, what turnaround the programme commits to on feedback, what any funding deduction takes out of the rate, and what the contract obliges the supplier to carry in insurance and administration. A seat on a crowded panel with slow feedback and a thin rate can consume more recruiter time than it returns.

Where does an MSP sit relative to an RPO?

They outsource different things. An RPO runs the employer's own hiring process, usually for permanent roles, with provider recruiters working in the employer's name. An MSP manages the external suppliers who provide contingent workers, and generally does not recruit at all. Large organisations frequently run both at once, which makes it worth defining clearly which arrangement owns a given category of hiring before the two overlap on the same role.

What is actually outsourced to an MSP?

The subject of the outsourcing is the supply base. An MSP does not usually recruit; it decides which suppliers are on the panel, how work reaches them, whether their submissions meet the agreed standard, whether their rates match the agreed terms, and whether their workers hold current compliance documents. The hiring managers still choose who they want, and the suppliers still find the people.

That distinction is the source of most misunderstanding when a programme is introduced. Suppliers who expect the MSP to be a client discover they are dealing with an administrator of someone else's rules. Hiring managers who expect faster hiring sometimes find the opposite in the first months, because a programme replaces informal relationships with a process. Both reactions are predictable and both are worth setting expectations about before go-live.

Neutral vendor or master vendor: who else is allowed to fill the role?

Under a neutral vendor arrangement the MSP administers the panel but does not place its own workers, so it has no interest in which supplier wins. Suppliers usually prefer this because the referee is not also a player. Under a master vendor arrangement the managing organisation has first opportunity to fill roles and passes on what it cannot cover to subcontracted suppliers.

Each has a real trade-off. Neutral vendor removes the conflict of interest but adds a layer that fills nothing itself. Master vendor can be faster and simpler for the client to manage but concentrates dependency on one organisation and puts it in the position of judging competitors for work it also wants. Whichever model is chosen, the point to settle explicitly is what happens to a role the primary route cannot fill and how quickly it moves on.

How is an MSP paid, and what does that change?

There are two broad funding routes. In a supplier-funded programme, suppliers pay the managing organisation a share of what they bill, so the client sees no separate line item. In a client-funded programme the client pays a management fee directly. Supplier-funded looks free to the buyer and is not: suppliers price the deduction into their rates or absorb it out of margin, and either way it shows up somewhere.

The funding route also shapes behaviour. A supplier-funded arrangement ties the programme's revenue to contingent spend flowing through it, which is worth being conscious of when the programme advises on whether spend should grow. Client-funded arrangements make the cost visible and the incentives easier to align, at the price of a budget line somebody has to defend.

How does work reach suppliers, and how is that rule set fairly?

Roles are released according to distribution rules the programme configures: to the whole panel at once, to a tier at a time with a delay before the next tier sees it, or to named suppliers for specialist categories. The rules encode a judgement about speed against fairness, since releasing to everyone gets the fastest response and also produces the most duplicated effort across suppliers who mostly will not win.

The part suppliers care about most is what happens after submission. Submission caps, a stated turnaround for feedback, and visible reasons for rejection are what let a supplier decide whether a panel seat is worth working. Programmes that release volume and return silence train their better suppliers to deprioritise them, which shows up months later as declining submission quality that looks like a supplier problem and is not.

Which obligations does a programme pass down to suppliers?

Programme agreements typically require suppliers to hold stated insurances, to verify a worker's right to work, to complete role-specific checks, to keep documents current, and to engage workers in a way the client considers acceptable. The programme then audits those obligations rather than performing them.

This is the area where generic guidance is most dangerous. What a supplier must do to engage a worker lawfully, how a worker's status is classified, and who bears liability if that classification is later challenged all differ by country and frequently by state or province, and the rules change. An MSP agreement can allocate contractual responsibility between the parties, but it cannot change what the law in a given place requires. Both client and supplier should have the arrangement reviewed by counsel in every jurisdiction it touches rather than relying on the programme's standard wording.