How Staffing Decisions Erode Project Margins

A senior consultant gets put on a project that was priced for someone cheaper. The work gets done well and the client is happy, so nothing looks wrong. But that consultant's hours cost more than the project earns on them, and the gap doesn't surface until the month closes. That is how staffing decisions affect project margins. The number is largely set when someone picks who does the work, long before finance sees it, and most firms never look at staffing that way because they run it as a scheduling job and measure it by whether everyone is billable.

It stays hidden because the usual health checks miss it. A team can be fully utilized and the clients perfectly happy while the model still leaks, because utilization measures how busy people are while saying nothing about whether their time earns what you sold. Margin slips underneath a surface that looks fine, which is why it can be so hard to catch.

What does margin erosion actually look like on a project?

Margin erosion is the gap between the margin you planned for a project and the margin you actually earn. You scoped the work at a certain profitability, and by the time it closes the real number is lower. It opens through a series of small staffing and delivery choices, each reasonable on its own.

It helps to separate three things that often get treated as one. Utilization tells you how busy people are, realization tells you how much of that work you turned into billed revenue, and margin tells you whether the model still makes money after delivery costs. A team can be fully utilized, badly realized, and margin-negative at once, which catches leaders off guard. Project margin erosion lives between those three numbers, so this post stays on the staffing calls that move it.

Five staffing decisions that leak margin

Here are the calls that do the most damage. None of them looks like a mistake in the moment; each is a normal decision a busy operator makes under pressure, with a margin mechanism that shows up only later. In every case the decision is made for a delivery reason, and the cost is discovered at close.

1. Staffing to who's available, not who's right

Start with the most common call, which is also one of the most expensive. A project needs someone this week, the ideal person is booked, so you put whoever is free on the work instead. Sometimes that is fine, but often it means a senior person doing a job scoped for someone cheaper, or someone learning on the client's clock while a pricier colleague reviews their work.

The bill rate on the project does not change, but the cost rate does. When a consultant billed at a premium delivers work you priced around a much lower cost, the margin on every hour shrinks even though the invoice looks identical. It runs the other way too, because someone too junior on complex work makes the hours balloon until a fixed fee absorbs the rework. Neither shows up on the resourcing board, yet both show up in the margin. So before you commit the name, ask more than who is free; ask whether their cost rate fits the price you sold.

2. Carrying the bench instead of forecasting it

Every firm carries some bench, whether that is people between projects or people held for work you know is coming. Unbilled capacity is a real margin cost, because it is people you pay but do not bill, and the longer it sits unexamined the more it drags company gross margin below where your account margins say it should sit.

Some of that bench is deliberate and healthy. Mark Orttung, who led the software services firm Nexient to more than $130 million in revenue before its acquisition by NTT Data, is clear that at a mature firm a bench is what lets you say yes to the next good project without burning the team out. The problem is the bench nobody decided on, the capacity that exists because your resource allocation runs on guesswork. If you cannot see who rolls off in three weeks and what is coming to catch them, you are absorbing a bench rather than running one, and it is worth knowing what an idle consultant actually costs.

3. Saying yes to scope without re-staffing

Clients ask for more, which is normal and often a good sign. The margin damage comes from how firms say yes. A delivery lead agrees to an extra workstream to keep the relationship warm, adds people to cover it, and never raises a change order, so the team grows while the fee stays flat. Now more cost sits against the same revenue, and a project priced at a healthy margin subsidizes work you gave away.

This is scope creep in its purest financial form. Almost always it is a staffing decision dressed up as a delivery favor, because someone had to be assigned to the extra work. The moment that assignment happens without a matching change to the fee, margin starts to leak. If the work is worth doing, it is worth pricing, because re-staffing without re-scoping is a choice to earn less.

4. Letting delivery and finance live in different systems

The problem is timing. Delivery data sits in one tool and billing in another, so the two only line up at month-end, well after the work happened. Hours get entered late or missed, and delivered work slips off the invoice because nothing connects the record of what was done to what gets billed. Once that surfaces in the month-end numbers, chasing the unbilled hours is usually more trouble than it's worth.

Every ops lead will recognize this common scenario. You write a statement of work for $200,000, the team finishes the job at $170,000 of effort, and the last $30,000 never gets invoiced. The work was done and the margin was real, but it leaked out through the gap between doing the work and billing it. That is revenue leakage, and it maps straight onto realization, the effort you delivered but never turned into cash. The people closest to the work are the ones whose time has to be captured on time where finance can see it, and when the two run on separate spreadsheets, professional services margin leakage becomes a monthly habit.

5. Over-staffing to de-risk delivery

The last decision is the hardest to catch. Because it so often comes from good intentions, it usually evades scrutiny. A project starts to feel at risk, so to protect the relationship and your reputation, you add an extra person, or a senior lead shadows a delivery that could run without them. Maybe the project gets to a crucial point where you genuinely need to put your most senior people on it to progress. Particularly when the work is on an account that you cannot afford to lose, you may have no real choice in the matter.

More often, the extra capacity is insurance nobody priced. The project delivers well, everyone feels good about it, but the margin lands below plan because it carried a person it did not need. Over-staffing to de-risk is either real risk management or margin you gave away for peace of mind, and the difference is whether you decided it on purpose.

To put it plainly, not every staffing decision that erodes margin is a mistake. Sometimes it’s just the right call to make.

When eroding margin is the right call

Everything above frames margin erosion as a leak to plug, and most of the time it is. But some of the best decisions a firm makes show up as eroded margin on a single project, and they are still the right calls. Take an anchor client you are trying to grow: a stronger, more expensive team than the current fee justifies can be a deliberate investment in an account that pays back over years. The same logic covers a turnaround you take on to prove you can, or a new practice area where the first projects are really paid training for your team. On any single project, that shows up as eroded margin. Measured across the whole relationship, though, it can be the smartest money the firm spends. This is where the bench comes back as a strength rather than a cost.

Our bench wasn't overhead. It was a competitive advantage.

How to see the margin impact before you commit the staffing

Margin is not really won or lost at month-end; that is just when you find out. It is won or lost weeks earlier, when someone decides who goes on which project without the margin numbers in front of them.

Resource planning connected to live financials makes the margin implication of a staffing choice visible while it is still a choice, and the weekly resourcing meeting stops being a debate about who remembers what. None of this removes judgment; it gives that judgment something solid to stand on. An operator makes a better call with the margin math on the screen next to the resourcing board, not buried in a month-end report.

Projectworks already gives you that visibility today, but AI is where it goes next. Built into the workflow and grounded in your firm's live data, it weighs the margin impact of a staffing call as you make it, and stays advisory by design. The decision stays yours. Projectworks just makes sure you have everything you need to make the right one for your firm.

‍