Every program decision I have seen go wrong had the same root cause: someone made it before they knew where they stood.
Companies pick a technology, issue an RFP, or sign with a provider based on a general sense of their spend. Then the real numbers surface, and the design no longer fits. I have seen many implementations over the years where the procurement leader was convinced they only had 10 suppliers across the country. A month later, when we were getting ready to communicate to the business and the supplier community that the program was being implemented, we uncovered 15 more suppliers that managers have been getting talent from. Leadership was shocked.
A baseline fixes that. It is not a big project. For a company with $10-50 million in contingent spend, it usually takes a few weeks of part-time effort, and it makes every later decision cheaper and better.
What a baseline answers
Four questions:
- How much are we spending, and on what?
- Who are we buying from?
- What are we paying?
- What have we agreed to?
Everything else, including model, technology and governance, builds on those answers.
By the numbers: why it pays to know your picture
In the same People2.0 survey of larger enterprises:
- 75% said contractors, freelancers and temporary workers make up at least 11% of their workforce, and 43% said more than 20%.
- 53% ranked controlling costs while keeping workforce agility as their biggest contingent workforce challenge.
Source: People2.0 research, reported by Staffing Industry Analysts, Sept. 25, 2026.
What to gather
Spend. Pull 12 months of contingent labor spend from accounts payable and finance. Break it down by supplier, department, location and worker type (staff augmentation, project-based, statement of work, independent contractors). Do not expect it to be clean. Contingent spend often sits across several accounts and cost centers, and some of it is coded as services or consulting.
Suppliers. List every supplier you paid in the period. For each, note total spend, number of workers, who manages the relationship, and how long you have worked together. Most companies find a long tail: many suppliers with small spend, a few with most of it.
Rates. For your highest-volume roles, compare what you pay across suppliers and departments. Look at bill rates and markups. Where the same role carries different rates, find out why. Sometimes there is a good reason, such as location or skill level. Often there is not.
Contracts. Collect every agreement with every supplier. Note the term, markup or fee structure, conversion fees, insurance and indemnification requirements, and anything unusual. Also note which suppliers have no current agreement.
Workers. Where you can, find out how many contingent workers you have at any point in time, how long they have been with you, and who they report to. Long-tenured contingent workers are both a cost and a compliance question.
Process. Write down how a hiring manager actually engages a contingent worker today: who approves, which supplier they call, how onboarding works, how invoices get approved. Describe what really happens, not what the policy says.
Baseline checklist
- ☐ 12 months of contingent spend, by supplier, department and worker type
- ☐ Complete supplier list with spend and worker counts
- ☐ Rates for top 10-15 roles, compared across suppliers
- ☐ Copies of all supplier agreements, with gaps noted
- ☐ Current headcount and tenure of contingent workers
- ☐ The real engagement process, from request to invoice
- ☐ Names of everyone who manages a supplier relationship
- ☐ Open compliance questions (classification, tenure, co-employment)
Who should be involved
You need a small group: someone from finance or accounts payable who can pull the data, someone from procurement, contracts or HR who knows the suppliers, and a sponsor with the authority to ask hiring managers for information. A baseline led by one person with no sponsor stalls at the first department that does not respond.
What to do with what you find
Three outputs matter:
- A one-page summary of total spend, supplier count, rate variation and contract gaps. This is what leadership needs to approve the next step.
- A list of quick wins, such as consolidating suppliers on the long tail, fixing missing agreements or correcting obvious rate outliers.
- A set of requirements for the model and technology decisions that follow.
The baseline also gives you a starting point for measuring results. If you do not record where you started, you cannot show what changed.
Common mistakes
- Waiting for perfect data. It will not be perfect. Aim for good enough to see patterns.
- Skipping the process review. Spend data shows what happened, not why.
- Treating it as a one-time project. Keep the baseline updated, because it becomes your reporting foundation.
Next step
Once you know where you stand, you can evaluate technology with real requirements instead of a vendor’s feature list. That is Article 4.
If you would like help running a baseline, I am happy to talk about how I can help. Email me at becky@ennisbader.com to schedule a 20 minute discussion.




Leave a Reply