Contingent Workforce Program Governance: What to Put in Writing First

Last updated: September 29, 2026

By Tom Kenaley, President and Senior Partner, KORE1

Contingent workforce program governance starts with six written pages covering who counts as a contingent worker, who may engage one, who decides classification, what every supplier must accept, what rates and conversion fees apply, and how managers treat contractors. Write those before any VMS demo or MSP request for proposal. Tenure policy, supplier tiering, and the reporting pack can follow over the next two quarters.

The first governance document most companies actually produce is somebody else’s. It’s the configuration workbook a VMS vendor sends over during implementation, a spreadsheet with a few hundred cells asking which approval chain a requisition follows, what the markup ceiling is, and how many days before an assignment ends the system should send a warning. Somebody in procurement fills it out in a week. HR never sees it. A year later, that workbook is the policy, because no other document ever wrote those decisions down.

That’s backwards. And it’s common.

I sit across the table from that workbook. For more than 20 years KORE1 has put contract IT and engineering people into client programs. Sometimes we’re a direct vendor. Sometimes we’re a tier-two supplier under a managed service provider, signing whatever supplier agreement the program hands down and working inside its rules. So a word on bias before I start. We’re a contract staffing supplier. We don’t write program policy for clients and we don’t sell governance consulting. What I can tell you is which pages we get handed, which ones are missing, and which missing ones cause the phone calls.

What Contingent Workforce Program Governance Covers

Contingent workforce program governance is the written set of decisions that controls how an organization engages non-employee workers, covering who counts, who can approve an engagement, who decides classification, what suppliers must agree to, how rates are set, and how managers behave. The VMS and the MSP carry those decisions out. Making them is your job.

Most of the guides ranking for this topic list the same components. Ownership, classification, contracts, training, audit, annual review. All real. What they skip is order. Order is the whole problem, because a company that writes its rate card before it has decided who is allowed to open a requisition ends up with a rate card that half the managers never use.

Our contingent workforce management guide covers when a formal program is worth building at all. This piece assumes you’ve decided it is, or that you’re running one that grew up without a policy and now needs one.

The First Six Pages, in Order

Six documents. None of them long. The order matters more than the polish.

Why that sequence? Dependencies. You can’t set engagement authority until you know which engagements are covered. You can’t assign classification until you know who is allowed to engage anyone. The supplier terms assume a classification default. The rate card assumes supplier terms. The manager page goes last. It’s written for people outside the program office, and it should describe rules that already exist rather than rules still being argued about.

1. Scope and Definitions

Short page. Hardest argument.

List the worker types the program covers. Agency temps and contractors on a supplier’s W-2. Independent contractors paid on a 1099. Consultants working under a statement of work. Workers engaged through an employer of record. Freelancers found on a talent platform. Then say which are out, if any, and who handles them instead.

The fight is always over the statement of work. Plenty of SOWs are staff augmentation wearing a costume, one person or three, billed hourly, taking daily direction from a client manager, with no deliverable anyone could accept or reject. Write a test into the scope page. If the SOW has no acceptance criteria, bills by the hour, and the client assigns the daily work, it’s staff augmentation and it goes through the program like any other contractor. We picked up a “cloud operations support” SOW at a manufacturer in the Inland Empire last year that had run for 31 months that way. Two engineers. Never touched the VMS. No one had checked whether the consulting firm paid them as employees. It didn’t. What a working SOW has to contain, from acceptance criteria to the pricing structure, is laid out separately.

2. Engagement Authority

This page decides whether the program is real. Most skip it.

It names who can open a contingent requisition, at what spend level a second approval is required, and the rule that nobody starts work without a requisition number and a written end date. That last clause does more than it looks like. An end date on every engagement is what lets IT expire access automatically, what lets finance forecast, and what forces somebody to make an extension decision instead of letting an assignment drift into its third year.

Write the exception path too. If there’s no written way to handle “the production system is down and I need a Kafka engineer by Monday,” managers invent one, usually a call to whichever recruiter they last worked with, and procurement learns about it from an invoice. A sanctioned emergency path with after-the-fact approval inside five business days beats a policy that pretends emergencies don’t happen.

3. Classification Ownership

One name. Not a committee.

The page should say that the default channel for any contingent engagement is a W-2 worker employed by an approved supplier, and that a direct 1099 engagement requires a written determination before the person starts, signed by the named owner. The IRS frames the question around three categories of evidence (behavioral control, financial control, and the relationship of the parties), and its guidance on independent contractor versus employee status is the right skeleton for the determination form. When a case is genuinely unclear, a firm can ask the IRS directly by filing Form SS-8. It’s slow. Few firms want to wait on it with a project starting Monday.

Federal standards moved this year. The Department of Labor published a proposed rule in February 2026 to replace its 2024 independent contractor test, and as of this writing no final rule has been issued. Don’t rewrite your policy around a proposal. Do write down who is responsible for watching it. Our piece on contractor tenure limits walks through what changed federally and why, and the cost of misclassifying a contractor is its own page, so I won’t repeat the penalty math here.

4. Supplier Floor Terms

These are the terms every supplier signs whether it’s a 4,000-person national firm or a boutique with two recruiters. Tiering can come later. The floor can’t.

• Every worker placed is the supplier’s W-2 employee unless the requisition says otherwise in writing.
• No subcontracting and no corp-to-corp layers without written consent for that specific worker. This is the clause I most often find missing, and it’s how a contractor three companies removed ends up on your network and nobody can say for certain who pays them.
• A named background check standard, written once, applied to every supplier the same way.
• Certificates of insurance on file before the first start date, renewed on a calendar the program office tracks, not the supplier.
• Confidentiality and intellectual property assignment that flows from the worker to the supplier to you. For W-2 agency workers, the supplier is usually the legal author of what its employee writes on the job, so the agreement has to assign that work onward to you. Our contractor IP ownership guide explains why none of it is automatic. What that flow looks like on a staffed engineering engagement is on our contractor IP protection page.
• Your right to audit pay records for workers on your assignments.
• The replacement terms if a worker leaves or doesn’t work out in the first weeks.

Seven clauses. Nine, maybe, in regulated industries. Not a long list. If a supplier won’t sign the floor, that tells you something useful before you’ve given them a single requisition. The questions to ask a staffing agency before signing overlap with this list and are worth running at the same time.

5. Rate and Conversion Schedule

A rate card doesn’t have to be precise. It has to exist. Most don’t.

Group roles into families, set a bill rate range or a markup ceiling for each, and say who can approve a rate above the range and how that approval gets recorded. Decide whether overtime is permitted, who approves it before it’s worked, and what multiplier it bills at, because for hourly non-exempt contractors the supplier owes overtime pay whether or not your manager remembered to ask. Put the rate review at extension on the same page, so a twelve-month contractor asking for more money gets an answer from a rule rather than from whichever manager hears it first. For local market numbers, our salary benchmarking tool gives a starting range for the permanent equivalent.

Then the conversion fee table. One table, identical across suppliers, declining with hours worked, and zero after a set point. I’ve watched a hiring manager try to convert a strong Salesforce developer in Sacramento and discover that the two suppliers on the program had wildly different conversion terms for nearly the same seat. One supplier’s fee dropped to zero after 1,040 hours. The other’s never fell below 15% of first-year salary. The conversion stalled for five weeks while procurement argued about it. The developer took another offer. Gone. When conversion terms live in the program policy instead of in each supplier’s paper, that argument never starts. The mechanics of a clean conversion are in our contract-to-hire guide.

6. Manager Conduct Page

Most of your managers will read this page and no other. Keep it to one screen.

What they can do. Assign the work, set the schedule the engagement calls for, give feedback on the work product to the supplier. What they can’t do without HR. Hold a performance review, promise a raise or a bonus, discipline or terminate directly, invite the contractor into employee-only benefits or events. The line between “managing the work” and “managing the person” is where co-employment risk lives, and the EEOC has said for decades that a staffing firm and its client can both carry liability for how a placed worker is treated, in its enforcement guidance on contingent workers. The day-to-day version of this, with the specific do’s and don’ts for a contractor’s first month, is in our contractor onboarding checklist.

One item doesn’t belong to managers at all, and procurement rarely thinks to ask about it. Have benefits counsel read the eligibility language in your 401(k) and stock purchase plan documents and confirm it excludes anyone not paid through your payroll, even if a court later calls them your employee. That sentence is a plan amendment, not program policy. It’s still on this list because the program is the reason it matters.

What Can Wait a Quarter

Plenty. The six pages above settle the decisions that are expensive to reverse. Most of what follows is tuning.

• A tenure policy. Our view, argued at length elsewhere, is that a review trigger at 12 or 18 months beats a hard cap, and you’ll write a better one after a quarter of seeing which assignments actually run long.
• Supplier tiering and how many suppliers you keep. That’s a data question, and you won’t have data until the engagement-authority page has been enforced for a while. The vendor consolidation argument makes more sense with six months of requisitions to count.
• The reporting pack.
• The offboarding runbook. It matters, but it’s an IT procedure that hangs off the end dates the engagement-authority page already requires.
• VMS configuration. Last on purpose. When the workbook arrives, you should be copying answers out of your policy into its cells, not the other way round.

The Checklist Version

Skip straight here if you just want the list. Each line should have a yes and a document you can point to.

• Is there a written list of the worker types the program covers, including SOW consultants?
• Does the scope page include a test for SOWs that are really staff augmentation?
• Is one named person able to open, or approve, every contingent requisition?
• Does every engagement require a written end date before start?
• Is there a written emergency path with a deadline for after-the-fact approval?
• Is the default engagement channel written down as W-2 through an approved supplier?
• Does a direct 1099 engagement need a signed determination before day one, and does one person own that signature?
• Has someone been named to track federal and state classification changes?
• Does every supplier sign the same floor terms, including no subcontracting without consent and IP assignment that flows through to you?
• Are certificates of insurance tracked on the program’s calendar?
• Is there a rate range for each role family, with a named approver for exceptions?
• Is there one conversion fee table that applies to every supplier?
• Do managers have a one-page list of what they can and cannot do with a contractor?
• Has benefits counsel checked the plan eligibility language?

Fourteen questions. A program that can answer yes to the first ten is in better shape than most of the programs we supply into, including some with very expensive software.

What We See From the Supplier Seat

We read a lot of supplier agreements. The ones that work share a trait that has nothing to do with length. They were written by someone who had decided things before the paperwork arrived, so every clause points back to a policy, and when we ask “who approves a rate exception,” the agreement already names a role. Our page on contingent staffing work inside MSP programs shows the same thing from the requisition side.

The ones that don’t work read like a stack of vendor templates stapled together. Insurance limits from one, a background check standard from another, conversion terms that contradict the MSP’s own rate card. Nothing in them is wrong, exactly. The decisions just never got made, so each question gets decided later by whoever happens to be in the room.

Our recruiters average more than 15 years in the seat, and in that time the pattern hasn’t changed much. Companies that wrote the six pages first got a program. Companies that bought the software first got a very organized version of the problem they already had, plus a license renewal.

Questions Procurement and HR Bring to Us

HR or procurement, whose name goes on the policy?

Both, on different pages. Procurement usually owns engagement authority, supplier terms, and rates, while HR or legal owns scope, classification, and the manager conduct page.

What fails is a policy with one owner who has no authority over the other half. If procurement writes the classification page alone, HR ignores it. If HR writes the rate card alone, finance does.

We have eight contractors. Is any of this overkill?

Mostly, yes, except for two pages. Even a small contractor population needs a named classification owner and a single set of supplier terms, because those are the two places a small company gets hurt.

Can the MSP write our governance for us?

It can draft it. It shouldn’t be the one who decides what it says, because several of those decisions (supplier access, rate ceilings, direct-sourcing carve-outs) affect how the MSP gets paid.

Take the draft. Really. Most MSPs have good templates and the people who wrote them have seen a lot of programs. Then have your own people go through it line by line and change anything that routes a decision to the MSP that should sit with you. An MSP that objects to that is telling you something.

How long should the finished policy be?

Twelve to fifteen pages for the six core documents is typical, and longer is usually worse.

The manager page should be one. The scope page can be one. The supplier floor terms run longest because they end up as contract language. A 60-page policy manual is a sign that no one decided what mattered. So everything went in.

Does a written policy protect us in a misclassification audit?

Not on its own. Auditors look at how the work was actually done, so a policy helps only when the records show people followed it, such as a signed determination on file for each direct 1099 engagement.

Where the policy earns its keep is before the audit. It stops the engagements that would have failed from starting at all.

Start With the Two Pages Nobody Can Argue About

If six feels like a lot for this quarter, start with scope and engagement authority. Nobody objects to knowing who counts or who is allowed to hire them, and once those two are written and enforced, the other four get much easier to agree on because everyone can see the same list of engagements.

KORE1 has been a contract staffing supplier since 2005, and 92% of our placements are with the same client twelve months later. We’ll sign your floor terms, bill to your rate card, and follow your conversion table. If you’re building a program and want a supplier that works inside one cleanly, talk to our contract recruiting team.