How Long Do Contract Assignments Last? KORE1 Data on 1,887 Assignments

Last updated: October 29, 2026

By Mike Carter, Managing Director, KORE1

KORE1’s median contract assignment lasts 116 days, about four months, across 1,887 ended assignments from 2019 to 2026. A quarter end within 44 days and a quarter run past 227 days. IT assignments run longer, at a 136-day median (n=410). The data is 79% California-weighted, from KORE1’s job-activity report, October 2026.

Ryan McManus gets this question on almost every discovery call. “It’s going to be for a three-month contract,” he told me recently, walking through a client’s staffing plan. “If no one else has that data out there, and we do, KORE1 says this.”

He’s right that nobody else says it. Search this topic and you’ll find ranges. Three to six months. Six to twelve. Vague bands built for a search snippet, not for a budget line.

We pulled 1,887 ended contract assignments from our own job-activity report and ran the actual distribution. Not a guess. Not a rule of thumb borrowed from a trade group’s slide deck. A median, a spread, and the tail on both ends that nobody wants to admit exists. It’s the kind of thing you want in hand before you commit to contract staffing with KORE1, not after the invoice shows up for month five.

How Long Does a Typical Contract Assignment Last?

A contract assignment’s length is the number of calendar days between a contractor’s first day on a client site and their last, measured only across assignments that have actually ended. KORE1 tracked 1,887 of them this way, from 2019 through 2026, 79% of the rows from California engagements. The Bureau of Labor Statistics defines a contingent job as one expected to last a year or less, which is a useful floor, but it says nothing about how long contract work actually runs once it clears that bar. That’s the gap this data fills.

The shape surprises people who expect a bell curve centered neatly around three months. It isn’t one.

A quarter of assignments end inside 44 days. Call that the audit sprint, the parental-leave fill, the thing that was never going to run long. Half end by day 116. A quarter run past 227 days, long enough that the contractor has outlasted a reorg at some of the companies we’ve staffed. And a tenth, the real outliers, cross 444 days, fourteen months and change, at which point the paperwork usually starts calling it something else: renewal after renewal, a standing seat nobody’s gotten around to converting.

IT assignments sit above all that, at a 136-day median against 410 ended engagements. Not dramatically longer. Just enough to matter when you’re sizing a budget line in Q1 and the number you used was the generic one.

Want a quote sized to the length you’re actually planning for, not the generic one? Get a bill rate quote for the length you need and we’ll price the role, level, metro, and expected duration together.

Do IT Contracts Run Longer Than Finance or Support Roles?

Yes, but the gap between role families is bigger than the IT-versus-everyone split suggests. Financial analysts and FP&A contractors run the longest median in our data at 235 days. Accountants run the shortest, at 45. Same general ledger software, same client type sometimes, wildly different assignment lengths.

Look at the two ends of that table and the logic falls out on its own. Transactional work ends fast. AP and AR specialists close out a backlog or a system migration in 77 days, median. An accountant brought in for a specific close cycle wraps up in 45. Forecasting and planning work runs long, because FP&A doesn’t finish, it just continues, quarter after quarter, until someone on the finance team decides it’s permanent enough to convert.

Help desk sits almost exactly at the all-role median, 126 against 116 overall, and with 104 ended assignments it’s the second-deepest sample in the table after accountants. That’s not a coincidence. Desktop support is the role every mid-size company staffs continuously, so it drifts toward whatever the broad average happens to be.

DevOps and cloud roles run long for a different reason. Migrations don’t end on a calendar date. They end when the last workload has actually cut over, and anyone who’s lived through an AWS-to-Azure move, or the reverse, knows that date keeps sliding. 191 days median, only 27 ended assignments in our sample, so treat that number as directional rather than gospel. It’s directionally right every time I’ve staffed one, though.

Why Do Some Assignments End in Six Weeks and Others Run Past a Year?

Three different jobs get called “contract staffing,” and they don’t behave the same way.

Sprint work has a finish line built in. A close cycle, an audit, a system cutover weekend. The contractor knows the end date walking in, and so does the client. These are your p25 assignments, the 44-day crowd.

Project work has a scope instead of a date. Scope creeps. Everyone who’s managed a project knows this, and contract assignments attached to projects inherit the creep. A “three-month implementation” becomes five months the moment someone adds a module nobody scoped at kickoff.

Run support has neither a date nor a scope. It has a seat. Someone needs to be there every day doing the thing, and there’s no natural stopping point until the company decides to hire direct, automate the function, or cut the budget line. Robert Ardell, who’s placed more long-tenure contractors at KORE1 than almost anyone else on our team, put it simply on a recent call: “We’ve had contractors with us for probably some 10 years plus.”

Ten years on a contract. Not a typo. That’s run support, fully matured, and it’s the extreme end of the p90 tail that the distribution table above can only hint at.

What Does a Typical-Length Contract Cost?

Budget off the median, not off the headline bill rate. A three-month and six-month engagement at a typical 116-to-136-day range looks like this for two common seats.

National figures, both of them. Your actual number moves with metro, and a Bay Area or Orange County quote on the software engineer line runs well above this table. The point isn’t the exact dollar. It’s that a 116-day median assignment and a 227-day one aren’t the same purchase, and budgeting a help desk contractor at the 3-month figure when the role is actually going to run closer to p75 leaves a gap that shows up as a surprise invoice in month five.

When Does a Long Contract Become a Conversion Decision?

1,040 hours. That’s the number that matters here, because it’s roughly 26 weeks of full-time work, and it’s the point where most of our contract-to-hire agreements let a client convert the contractor at no additional fee.

Line that up against the p75 mark of 227 days and the overlap is obvious. A quarter of all assignments already run long enough to hit that conversion window on their own, without anyone planning for it. The contractor just keeps showing up, the scope keeps not quite finishing, and eventually someone in finance asks why this person still shows up on the staffing invoice instead of the payroll one.

37.5% of KORE1’s contract-to-hire placements convert (n=552). That’s not a small number. More than a third of the people who start on a contract end up direct hires, and the ones who do almost always cross that 1,040-hour mark first. See the full breakdown in our contract-to-hire conversion rates analysis if you’re trying to model what your own conversion odds look like.

Thinking further ahead than one role? The 2026 Contract Rate Card has the full bill rate table by role, level, and metro for planning next year’s contractor spend.

Should a Long-Tenure Contractor Sit on OpEx or CapEx?

Nobody asks this question about a six-week contractor. Everybody should ask it about a two-year one.

Devin Hornick, a partner at KORE1 who spends most of his week in exactly these conversations, frames it this way: “A long-tenure contractor charged to a capital project is fine. One sitting on the operating budget deserves a CFO conversation.”

The logic underneath that is pretty direct. A contractor billed against a capital project, a system build, a migration, a specific deliverable with a defined end state, is doing capital work even if the assignment itself runs 400-plus days. The accounting treatment can follow the work. A contractor who’s quietly become a permanent fixture on the operating budget, doing the same run-support job year after year at a contract markup, is a different animal, and finance teams that never revisit that line tend to be the ones surprised by it at audit time.

This is also, not coincidentally, where the CapEx-versus-OpEx question runs straight into the contract-to-hire math above. A contractor converted off OpEx and onto headcount changes which budget absorbs the cost, and for a lot of finance leaders that’s the real decision point, not the assignment length itself.

Setting the End Date (and Planning for the Extension You’ll Probably Need)

Stop defaulting to “three months.” We hear that number from clients who picked it out of habit, not out of anything they measured.

Here’s a real one. A client of ours ran the same close-cycle contractor engagement for two years, same 90-day term every single time, out of pure habit. The work wrapped by day 50 both years. Forty days of half-utilized contractor, every cycle, times two. Nobody caught it until we pulled the timesheets side by side. Write the audit and close-cycle work down at the honest 44-to-60-day window instead.

Project work is where things get messy, mostly because scope creep is close to universal once a contractor’s actually on the ground. Get the extension clause into the statement of work before anyone signs, not three weeks before a badge expires when the client’s stakeholders are already annoyed and everyone’s negotiating under pressure.

Then there’s run support, and this is the one that sneaks up on people. At some point you’ve stopped staffing a role. You’re staffing a seat, permanently, and it just happens to wear a contractor’s badge. Our piece on contractor tenure limits covers exactly where that 18-month-plus mark turns into real classification risk, not just a budgeting headache.

And if you’re sizing the next one from scratch, KORE1’s contract staffing model is built for exactly this kind of defined-length engagement, whether that length turns out to be six weeks or six years.

What People Ask About the 116-Day Number

So what’s actually typical, the median or the average?

The median, 116 days, is the more honest number here. A handful of multi-year run-support assignments pull the mathematical average up well past that, and reporting the average would make a four-month engagement look longer than it really is. We report the median for exactly that reason, and we show you the full p25-to-p90 spread so you’re not guessing at the shape either.

How long do IT contractors usually stay on a project?

136 days median across 410 ended IT assignments, about three weeks longer than the all-role figure. Software developers alone run closer to 169 days, and DevOps and cloud engineers run 191, so IT as a broad bucket understates how long the more technical specializations actually run.

How long does an interim CIO engagement typically last?

Interim CIO and other executive IT leadership engagements tend to run longer than line-level IT roles, often six months to over a year, because the work is tied to a leadership gap rather than a single project. The Bureau of Labor Statistics projects 16% growth for computer and information systems manager roles, which cover CIO-level positions, through 2035, with about 53,500 openings a year, so demand for that kind of interim coverage isn’t going away.

Does anyone else publish a median like this?

Not that we’ve found. The American Staffing Association publishes staffing employment and sales data at the industry level, and tracks turnover and tenure as a concept, but nothing we could locate breaks out a median contract assignment length the way this report does. Most of what’s published elsewhere is a range, three to six months or six to twelve, with no sample size and no source behind it.

My contractor’s been here 14 months. Is that unusual?

Not really. Fourteen months is well above our 116-day median, but it sits comfortably inside the p90 mark of 444 days. Fourteen months puts the assignment solidly in run-support territory, and it’s worth having the OpEx-versus-CapEx conversation above if nobody’s had it yet.

Ready to size a contract to the length you actually need instead of a guessed-at round number? Try the contract staffing cost calculator for a bill rate range and total cost by role, level, and metro.