Loading Lifted

Contingent workforce

Reactive vs proactive hiring: how to plan ahead when demand is hard to predict (6 steps)

Portrait of Lee Willoughby

Lee Willoughby

Senior Marketing Director, Lifted

Portrait of Lee Willoughby

Lee Willoughby

Senior Marketing Director, Lifted

Portrait of Lee Willoughby

Lee Willoughby

Senior Marketing Director, Lifted

Published

Published

Read

Read

11 min

11 min

Team planning a project
Team planning a project

Key takeaways

  • This guide covers six steps for planning hiring when you can't forecast demand with confidence, plus what reactive hiring tends to look like in practice.

  • Some hiring will always start reactively. What helps is having budgets, approvals and routes ready, so a sudden need doesn't turn into a scramble.

  • Using your past hiring patterns to set budget ranges with Finance, and agreeing in advance what will start the sourcing process, can make a sudden hiring request much easier to handle.

  • Flexible talent, such as independent contractors or staff augmentation, can cover a spike without forcing a rushed permanent hire. It works best when you have already agreed the engagement route, approval path and onboarding steps before the request lands.

Let’s say it’s planning season and your leadership team has just approved three initiatives. One has a start date of “sometime in Q2.” One depends on a customer contract that hasn’t been signed yet. The third is a launch that could move up by six weeks if the product team gets ahead of schedule. Your job is to write a hiring plan for all of them. Where do you even start?

Many talent, HR or contingent workforce program leaders are asked to plan hiring around demand they cannot see clearly. Hiring managers bring forward requests as projects move, customers sign and teams change course. The plan gets written anyway, and then the real requests start arriving in a different order, at a different size and on a different timeline than anyone expected. That is often the moment hiring turns reactive: the planning happened, but the plan had no ready response when the business changed.

This guide walks through what reactive hiring looks like in practice and six steps for building a plan that bends. A perfect forecast isn’t realistic for most teams. A few decisions made ahead of time, such as budget ranges, trigger points, approval paths and engagement options, can give you a starting point when a hiring manager or functional leader brings you a new request.

What does reactive hiring look like in practice?

Let’s say a senior engineer hands in notice on a Thursday. The requisition goes out on Friday marked urgent, because the project that person owned has a deadline. Interviews get squeezed into two weeks, and the offer can go to the first reasonable fit. This is how a lot of hiring works, and nobody did anything wrong. The role opened only after the gap did, so everything that followed carried that urgency.

Or take a project that gets approved on a Monday with a start date four weeks out and no budget set aside for the people it needs. Finance asks where the money comes from, hiring managers ask where the people come from, and the answer gets worked out one conversation at a time.

It can also build up quietly across teams. Say that in one quarter, five different teams ask for contractors to cover project work. Each request looks reasonable on its own, but Finance sees requisition counts rather than a plan, so every request turns into a negotiation.

Skills gaps can build up quietly too, as some needs only become visible once work begins. A team may realize mid-project that it needs a skill it doesn’t have in-house, and the request arrives already urgent.

What these situations share is that the hiring program wasn’t ready when the need appeared. Some hiring will always start reactively, because people resign and projects change course, and proactive planning can’t stop that. What it can change is what happens next. With cover options, budget and approvals already agreed, a team can bring in short-term cover while the permanent search runs at a normal pace, instead of rushing the offer. The six steps below are how you get there.

6 steps to plan your hiring when demand is hard to predict

Where do you start when the demand you’re planning for keeps moving? These steps go in order, and each one makes the next easier.

1

Sort your hiring demand by how predictable it is

A good first step is sorting your hiring demand into three groups, because each one calls for a different kind of plan:

  1. Steady demand: the work that goes on month after month, year after year, such as the roles that keep your core teams running.

  2. Predictable peaks: demand you can see coming on a calendar, like a product launch, a seasonal rush, a budget cycle or a fiscal year-end.

  3. Surprises: requests nobody saw coming, like a sudden regulatory change, an acquisition or an unplanned departure.

Take a global technology company, for example. Core engineering and finance roles are generally a steady demand, a product launch every spring is a predictable peak, and an acquisition that adds a new business unit can often be seen as a surprise. Sorting by predictability, rather than by role, can make planning feel more manageable, because each group points toward a different kind of answer. We come back to how each group might be covered when we look at engagement models below.

To make this useful, meet with the functional leaders and hiring managers behind each major area of demand. Ask what initiatives, launches, contracts or seasonal patterns they expect over the next two quarters, and which roles are most likely to be needed if those plans move forward. Their input will not remove uncertainty, but it can turn a broad category such as “predictable peaks” into a short list of scenarios you can plan around.

Looking at the last year, how much of your hiring was steady, how much was a peak you could have seen coming, and how much was a true surprise?

If you want help deciding which roles tend to suit flexible talent in the first place, our guide on which roles are better as contractors covers that.

2

Use your own hiring history to forecast future demand

How do you forecast hiring demand? If you already have a formal forecast, your requisition history is a useful way to sense-check it. If you don’t, it can be a good starting point. It can help to pull the last 12 months and look at when requisitions opened, which skills they needed, which business units asked and how many started out marked urgent. Include contingent requests, such as contractor and statement of work requests, alongside permanent requisitions, since that is where many “unexpected” needs show up.

Patterns tend to show up faster than leaders expect. Maybe the same two teams account for most of the urgent requests. Maybe demand jumps every March and September. Maybe one scarce skill keeps coming up and takes the longest to fill each time. None of this requires a forecasting model, only a short working session and someone who knows the story behind the numbers.

Looking back also answers a useful question: does this year’s “unexpected” request look a lot like last year’s? If so, it may be one you can plan for next time. It can also show which of the three demand groups above each request belonged to.

3

Plan hiring in ranges with Finance

When demand moves, a single headcount number is often the first thing to change, and ranges tend to hold up better. It’s often good to work with Finance to build a low, a likely and a high scenario, each with a headcount range and a budget range attached. A simple way to build them: steady demand sets the low scenario, predictable peaks bring you to the likely one, and surprises stretch it to the high one.

One approach many teams find helpful is agreeing a flex budget in advance: a defined amount or range that can be used for unplanned hiring demand without requiring a fresh approval each time. The exact approval threshold should reflect your organization’s own financial controls. Without an agreed approach, every spike can turn into a separate negotiation. With one, a hiring manager’s request can move more quickly to the question that matters: what is the best way to cover this need?

Could you take a range instead of a single estimate to your next budget discussion?

4

Agree hiring trigger points before you need them

What is a hiring trigger point? A trigger point is an “if this happens, then we start that” rule agreed in advance, so the hiring conversation begins when a signal appears instead of when someone notices a gap. Here are a few examples an enterprise might use:

  • A project is approved or funded: preliminary sourcing for the likely roles starts that same week, within the agreed flex budget, even if the final headcount isn’t confirmed.

  • A team’s open requisitions pass an agreed number: the program owner reviews whether flexible capacity makes more sense than adding permanent hires.

  • A requisition stays open past an agreed number of weeks: someone reviews whether short-term cover makes sense while the search continues.

  • A critical-skill employee gives notice: a short-term cover option is raised that same week, while the permanent search begins.

  • A launch date moves up: the program owner reviews the capacity plan within a few days.

Triggers can help because they remove the waiting. In many enterprises, the gap between “we know we will need people” and “someone starts looking” is where much of the urgency gets created. Decide which signals matter in your business, who can approve action when one appears, and how quickly that approval should happen. A short list is usually plenty.

For example, if a customer contract is signed on a Tuesday, the hiring manager may raise the need for additional delivery capacity. Under a pre-agreed trigger, the talent or program leader can approve preliminary sourcing for the likely roles by Wednesday, within the agreed flex budget, while the final headcount, budget and engagement model are confirmed. The details can still change, but the response has already started.

5

Agree your routes for each kind of demand ahead of time

Once demand is sorted, a simple routing guide can help: for each kind of need, which routes would you consider, and what can you agree before a request arrives? Start with how long the work is likely to last, who will direct it and whether you need extra capacity or a defined outcome. Here is one way to set it up:

Kind of need

Routes to consider

Agree ahead of time

Steady, ongoing work

Permanent hiring where the need belongs in your core team

Headcount, budget and approval path

Predictable peak

Staff augmentation, or independent contractors engaged through an Agent of Record (AOR) where the work suits an independent engagement

Rates, engagement checks, onboarding steps and how far ahead sourcing needs to start

Surprise (unexpected request)

Staff augmentation for extra team capacity; independent contractors or managed delivery where the work fits

Budget limits, who can approve action and which suppliers can support the likely need

Project with a defined outcome

Managed delivery under a Statement of Work (SOW), with the supplier responsible for delivery

Scope, deliverables, acceptance criteria and who owns delivery

Role that needs an employment arrangement, such as a time-limited role or no local entity

Employer of Record (EOR), depending on the role and country

Expected duration, employment terms, total cost, country coverage and compliance review

One useful question is whether you need someone to join your team’s workflow or an outside supplier to own the result. That is often what separates staff augmentation from managed delivery. For independent contractors, how the work will actually run matters too, since using an AOR does not make every engagement suitable for independent contracting.

The same request can also fit more than one row. An unexpected project, for example, may still have a clear outcome that a supplier can deliver. The table above is a starting point, not a rule. The right choice depends on the work, location, duration and working relationship, so review the details with your own legal and tax advisors.

If sourcing speed is the sticking point, our guide to ways to accelerate your contingent talent sourcing process goes deeper on that.

A routing guide can also help with a common habit: going back to the same staffing agency by reflex. Lifted’s General Manager, Ernesto Lamaina, calls this the capacity trap, and he explains why it happens and how to break out of it in his newsletter.

Having a small set of pre-agreed options, such as independent contractors, staff augmentation, managed delivery or an EOR, means that when a hiring manager or functional leader brings a request, you can match the work to a suitable route rather than starting from scratch.

6

Track planned vs rushed hires every quarter

How will you know the plan is working? Many teams find it helpful to look, each quarter, at the share of hires that were planned and the share of hires that were rushed, such as hires where the requisition was marked urgent or opened only a few weeks before the start date. Comparing what you forecast with what actually came in, and noting how often a trigger fired and whether it led to action sooner, can show where the plan needs adjusting.

You’re generally looking for direction, not precision. If the rushed share is shrinking and your ranges are getting closer to reality, the plan is doing its job. If one kind of demand keeps landing outside your range, that range may be the one to adjust, instead of the whole plan. This is also where late-surfacing gaps get caught: a skills area that keeps showing up in the rushed column may be worth a closer look before it affects a deadline.

Keep this quarterly check focused on hiring demand and hiring outcomes. If you also want to review the wider contingent program, our blueprint for building a contingent workforce strategy covers the longer-term review cadence.

Where flexible talent fits in a proactive enterprise hiring plan

A hiring plan may not cover every situation, and that’s okay. Having your ranges, triggers, approval path and engagement options in place can help a surprise request move faster, because you’re not building the response from scratch.

Flexible talent, such as independent contractors or staff augmentation, is often the piece that gives you room to answer without forcing a rushed permanent hire. The work gets covered now, and the permanent question can wait until you know whether the need is lasting.

Many enterprises already use a vendor management system (VMS), such as SAP Fieldglass, or a managed service provider (MSP) to source and manage contingent talent. Flexible talent can sit alongside that setup rather than replace it. If your current route already gives you the speed, visibility and choice you need when demand shifts, you may only need the plan around it. If it doesn’t, an additional supplier can fill that gap.

For example, Lifted, an Upwork Company, is a tech-enabled contingent workforce supplier that supports independent contractors, staff augmentation and managed delivery from one supplier, with an average time-to-fill of under 3 days, depending on role, location and compliance requirements.

That kind of speed can make it more realistic for a role approved early in the week to start soon after, instead of a search that runs past the project’s start date. If your questions go beyond hiring habits, such as whether your overall staffing model still fits, our guide on whether your staffing model is ready for what’s next is a good place to look.

Want to see how flexible talent could fit into your hiring plan? Talk to Lifted about your options.

See why leading enterprises choose Lifted

Explore Lifted's full CWMS platform or review our client case studies to see how enterprise organizations are transforming their contingent workforce programs with Lifted.

See why leading enterprises choose Lifted

Explore Lifted's full CWMS platform or review our client case studies to see how enterprise organizations are transforming their contingent workforce programs with Lifted.

See why leading enterprises choose Lifted

Explore Lifted's full CWMS platform or review our client case studies to see how enterprise organizations are transforming their contingent workforce programs with Lifted.

Frequently asked questions

  • What is the difference between reactive and proactive hiring?

    The difference between reactive and proactive hiring is how much is decided before a need appears. Reactive hiring starts working out budgets, approvals and routes once the need is urgent, while proactive hiring settles them in advance, so a new request has a plan to follow. Some hiring will always start reactively, and proactive planning aims to make it less of a scramble.

  • How can enterprises plan hiring when demand is unpredictable?

    Enterprises can plan for unpredictable demand by preparing responses rather than trying to predict every request. That usually means sorting demand by how predictable it is, using hiring history as a guide, agreeing low, likely and high scenarios with Finance, setting a few trigger points, clarifying who can approve action, and identifying which engagement models could cover each kind of need. The six steps above walk through each one.

  • How can an enterprise move from reactive to proactive hiring?

    An enterprise can move from reactive to proactive hiring by changing the order of decisions, so approvals, budgets and engagement routes are settled before a request arrives. A practical starting point is a look at last year’s requisitions, a conversation with Finance about a flex budget and a couple of trigger points. Agreeing which engagement model fits which need, such as independent contractors, staff augmentation, managed delivery or an EOR, also lets you match a sudden request to a route quickly, instead of starting a new search.

  • How can enterprises stop reactive hiring?

    Enterprises can reduce how often reactive hiring happens, even though surprises will always be part of the picture. A good place to start is tracking the share of hires that were rushed, looking at which kind of demand keeps landing there, and adding a trigger point or a pre-agreed engagement route for it.

  • Can contingent talent help enterprises hire proactively?

    Contingent talent can help enterprises hire proactively by giving them a way to cover a spike while they decide whether the need is lasting. It tends to work best when the engagement route and onboarding steps are thought through in advance, so a request doesn’t turn into a new procurement process. You can learn more about options such as independent contractors, staff augmentation, or outsourcing (managed delivery).

  • How often should an enterprise update its hiring plan?

    Many enterprises update their hiring plan quarterly, and sooner after a major business event such as a new market, an acquisition or a large project approval. A quarterly check of planned vs rushed hires and forecast vs actual demand is often enough to keep the ranges realistic.

Author

Portrait of Lee Willoughby

Lee Willoughby

Senior Marketing Director, Lifted

Lee Willoughby is the Senior Marketing Director at Lifted, an Upwork company helping enterprises source, engage, and manage contingent talent across every contract type. With a background as a co-founder and workforce technology entrepreneur, Lee focuses on the future of contingent workforce management, helping organizations navigate the complexities of global talent, compliance, and workforce transformation.

This content is for general informational purposes only, and is not intended to be and should not be viewed as legal or tax advice. Readers should contact their attorney or tax professional to obtain advice with respect to any particular legal or tax matter. Information discussed can change frequently, and Lifted cannot guarantee that all information is current at all times.

Get insights from global industry leaders.
Get insights from global industry leaders.
Get insights from global industry leaders.