Last updated: November 2, 2026
By Robert Ardell, Co-Founder and Strategic Advisor, KORE1
A staffing SOW should be time and materials: named roles, an hourly bill rate per role, an hours cap, weekly timesheet approval, notice to end the assignment, IP assignment, and conversion terms. KORE1 contractors convert at no fee after 1,040 hours. Fixed-fee and overrun clauses belong to consulting contracts, not staffing.
Seven clauses. Most of them fit in two lines.
You should know what I get out of saying that. KORE1 runs a contract staffing desk and we bill by the hour, so naturally I think hourly paper is the right paper for hourly work. Your counsel has the final say on all of it. Not me. I’m not your lawyer.
This also isn’t the master agreement. Tom Kenaley already went through the staffing agreement terms worth reading before you sign, and that document is where non-solicitation, insurance, and indemnity live. It isn’t a fill-in form either, since Colin Boothe built the time-and-materials SOW template for exactly that. What’s here is the reasoning behind the SOW clauses for a staffing seat, plus the few lines I’d strike if I saw them in a draft.
Which Clauses Matter in a Time-and-Materials Staffing SOW?
A time-and-materials SOW for contract staff is a short document, issued under a master agreement, that names the seats you’re buying by the hour. Your manager directs the work, the contractor stays on the staffing firm’s W2, and you pay for approved hours at a stated rate up to a stated cap.
Virginia’s state IT agency draws the same line for its own buyers. Its short guide, Staff Augmentation or SOW: How to Decide, says that under staff augmentation the “Customer pays based on the number of hours worked.” On the other side, a consulting firm manages the project and gets paid a fixed amount when the work products are accepted. Virginia reserves the word SOW for that second purchase. Most of the commercial world uses it for both, which is half the confusion right there.
| Clause | Why it matters | Sample wording |
|---|---|---|
| Named roles | Fixes the seat and the level, so a senior who becomes a mid-level is a visible change. | “Provider supplies one [Senior Project Manager], working up to [40] hours a week under Client’s direction.” |
| Hourly bill rate per role | One rate per seat. A blended number hides what each seat costs. | “Client pays [$ rate] per approved hour for this role. The rate holds for the term and changes only by written amendment.” |
| Hours cap | Sets a number nobody bills past without a signature, and forces the talk before you reach it. | “Billed hours will not exceed [520] without a written change signed by Client. Provider alerts Client at [75]% of the cap.” |
| Weekly timesheet approval | Approved hours are what gets invoiced. A backup keeps one vacation from stalling the chain. | “[Name] approves or disputes each timesheet within [3] business days. [Backup name] acts when [Name] is out.” |
| Term and notice | An end date forces a renewal decision. Notice says how either side leaves. | “The term runs [start] to [end]. Either party may end an assignment on [10] business days’ written notice. Hours worked through the end date are billable.” |
| IP assignment | Copyright doesn’t move on payment. It moves on a signed writing. | “Provider hereby assigns to Client all right, title, and interest in work product created under this SOW, as set out in section [X] of the MSA. Tools listed in Exhibit [B] stay with their owner.” |
| Conversion | Says when you can hire the person yourself, and what that costs. | “Client may hire a resource with no conversion fee once that resource has worked 1,040 hours for Client. [Hours under earlier SOWs count toward the 1,040.]” |
Everything in brackets is a starting point for you and your lawyer. The 1,040 is the one real KORE1 term in that column. Only that one. None of this is legal advice.
Got a draft already, or just a req and a budget? Have us review your contract req and we’ll tell you which of these lines are missing.
The Rate Needs a Number Behind It
The benchmark I can hand you is our own. In the KORE1 Contract Rate Index 2026-Q4, an IT project manager, program manager, or scrum master billed at a median of $116 an hour, with the middle of the range running $105 to $124. That’s 21 placements started between 2023 and 2026, primarily in Southern California, so adjust before you lean on it in Chicago, which is a different market, and where my number would be the wrong one to put in front of your CFO. Run out over a full-time schedule, it comes to about $60,400 for three months and about $120,900 for six. The project manager and scrum master bill rates break that down by level and metro, and the index methodology explains what counts as a placement and what gets thrown out.
A Cap Limits the Invoice, Not the Clock
People misread this one, and the reason is that a contract seat is usually a real employee. The cap governs hours billed. It’s no instruction to anybody’s keyboard, and federal wage law doesn’t care what your SOW says about time a W2 worker actually put in. The Department of Labor’s fact sheet on hours worked is blunt about it: “Work not requested but suffered or permitted to be performed is work time that must be paid for by the employer.”
So picture the last week of a NetSuite cutover. Your manager mentions in a hallway that it’d be great if the load finished by Friday, and the contractor stays till nine, three nights running, without anybody ever opening the SOW. Those hours happened. No clause un-happens them, and by the time the invoice shows up the cutover is over, the manager has forgotten the hallway, and everyone is staring at a timesheet that’s completely accurate.
More contract language won’t fix that. A manager who knows the number will. Send the 75% alert to whoever directs the work, not only to the person approving timesheets, and tell the contractor the weekly limit out loud on day one, before anybody has a reason to be polite about it.
Timesheets Want a Name
Not a title. Not “Client’s project lead.” A person, and then a second person. We pay our contractors every Friday whether or not your approver got to it, so a stale queue doesn’t hit their paycheck, but it does stack up against your invoice and your burn alert, and then the number you thought you had on Tuesday is two weeks old. Not great.
Term and Notice
Our median contract assignment runs 116 days across 1,887 ended assignments, about 17 weeks. A quarter of them are done inside 44 days. Another quarter go past 227. You can see the full spread in our contract assignment length data, and what it says to me is that nobody knows on signing day which group they’re in.
Write the end date anyway. It’s a forced decision. That’s the point. We’ve had contractors with us for some 10 years plus, and I doubt anyone wrote a ten-year term on day one. Each renewal should be somebody actually asking whether to extend the engagement, not a date sliding by.
Notice is the easier half. Pick a number of days, require it in writing, and name who receives it.
And don’t let the paper be the slow part. Across 1,997 starts our median from offer to first day is 3 days. Three.
Who Owns the Work Product?
I already wrote the long version of who owns contractor code, so here’s the short one. Under 17 U.S.C. section 204(a), a copyright transfer isn’t valid without a signed writing. Software also doesn’t appear among the commissioned-work categories in section 101, so a “work made for hire” recital won’t carry it for a non-employee. Paying the invoice moves nothing.
On a W2 seat the chain has two links. Our contractors sign an assignment to KORE1 before their first day, and our client MSA assigns the work product forward to you. Good. Then why repeat any of it in the SOW?
Because the MSA doesn’t know what this job is. It was signed months ago, maybe years, by people who may have left, for a relationship that didn’t have this seat in it yet. The SOW does. It’s the one place that can say which pre-existing tools the contractor brought along and keeps, which of your GitHub repos count, and which AI coding tools, Copilot or otherwise, are allowed on the work, a question that barely existed when most master agreements were written. Keep it short, point at the MSA section, and check the verb. “Hereby assigns” transfers. “Agrees to assign” only promises to, later, and later can be a long way off.
What Should the SOW Say About Conversion?
KORE1 contractors can be hired directly at no fee after 1,040 hours, which is about 26 weeks at full time. Say so in the SOW even if you’ve got no plan to convert anyone. Plans change.
Two things go wrong here, and neither is the fee.
First, the cap. A 520-hour SOW is a perfectly good quarter of work, and it ends exactly halfway to the conversion line. That’s fine if you only need the quarter. If you’re secretly hoping to keep the person, write the hours you actually mean, because more than half of our ended assignments stop before 182 days, and 1,040 full-time hours takes 182 days to reach.
Second, the renewal. You sign SOW number two, the hour count quietly starts a fresh line on someone’s spreadsheet, nobody thinks about it again until your manager wants to make an offer in month eight, and then two parties remember it differently. That’s the bracketed sentence in the table. Decide whether hours under the earlier SOW count, and write it down either way. A hire before 1,040 follows whatever your MSA says, so go read that section too.
Across KORE1’s W2 contract placements from 2019 to 2026, 37.5% of contract-to-hire placements converted, 207 of 552. Our contract-to-hire conversion rate breakdown has the context on that number.
Don’t go looking in this clause for a replacement guarantee, by the way. There isn’t one on contract, and a SOW that implies otherwise is promising something nobody priced.
What Should a Staffing SOW Not Include?
Fixed fees. Milestone penalties. Overrun allocation. They’re all legitimate contract terms, and they all belong to somebody else’s contract.
My partner Devin Hornick said it plainly when this came up on a content call of ours. Fixed fee? “Generally staffing firms don’t get into that. That’s a professional services thing.” His version of what we do instead was just as short: “Hourly, which we prefer. It’s really more of a staffing model to do the hourly billing and you manage the person.”
That last clause is the whole argument. You manage the person. Not us. A vendor can only answer for a result it’s actually steering, and on a contract seat your manager sets the priorities every morning. So take the three in turn.
- A fixed fee pays one number for a finished thing. It only makes sense when the other party employs the people, manages them, and decides how the job gets done, which is how Virginia’s guide describes a consulting firm.
- Milestone penalty on a seat you direct? Who missed it, exactly? You moved that person to a production fire on Tuesday.
- Overrun allocation is the one I’d watch hardest. That language is how staffing firms get in trouble, and it has no business in the SOW for an hourly seat. Your hours cap isn’t this. A cap is a ceiling you both agreed to and can raise in writing, nothing more.
A list of deliverables is fine, for what it’s worth. It tells the contractor what the seat is for. Just don’t tie payment to it, because hours get billed weekly.
Actually need a result that someone else manages? Different purchase, different paper, and our page on SOW staffing services covers how that one gets scoped. Already holding a SOW that says deliverables while your manager runs the person’s week? Then it’s worth an hour with our piece on SOW spend that’s really staff aug.
What People Ask Before It Goes to Legal
Staff augmentation statement of work: is that even a real document?
It is, as long as it says plainly that you’re buying hourly seats your own manager directs.
What it can’t do is dress a staffing arrangement up as a deliverables project. Keep the seat-level facts in the SOW, meaning roles, rates, cap, term, and approver. The standing terms stay in the MSA.
Who has a statement of work for contract staffing worth copying?
We publish a free one, so discount my opinion accordingly: KORE1’s hourly SOW template has eight clauses and comes as a Word file with the blanks shaded.
It splits a few things differently than the list above, and it adds assumptions, exclusions, and acceptance. It also leaves IP to your master agreement. If yours is silent or vague on assignment, add the sample line from the table. Whichever version you start from, whether ours or something your legal team already has in a drawer, compare it clause by clause against the seven here, and have your own counsel read the result before anyone signs it.
Can’t we make it fixed fee so the number stops moving?
Not through a staffing firm, generally, because a fixed fee is a consulting term and you’d be buying a different service.
Want the number to hold still? That’s the cap. Pair it with a rate that holds for the term. Done.
Read your draft once more before it goes out. Can your hiring manager name the approver, the cap, and the end date without opening the file? Then it’s done. If not, send the draft to our recruiting team and we’ll mark it up with you.
Rate figures are as of October 2026 (KORE1 Contract Rate Index 2026-Q4, effective October 16, 2026). Next update January 2027.
