Why your pipeline stops meaning anything

Ask five recruiters how many candidates are out on submission right now. If you get five numbers, the problem is not your team. It is that you let everyone build their own pipeline.

It always starts reasonably. Someone runs a healthcare desk and needs a Credentialing step, because that really is a distinct wait state with its own chaser. Someone on the contract desk adds Client Hold, because a candidate parked for two weeks is not the same as one moving. Both are correct. Both are useful. And each one is a small tear in your ability to answer a simple question about the whole firm.

The number quietly becomes an opinion

A year later there are nineteen stages. Four of them mean roughly “waiting on the client” and each is used by a different pod. Two mean “we submitted” — one added when the CV goes out, one when the client confirms receipt.

Now your submission count depends on who logged it. Not a little: a desk that counts at send and a desk that counts at acknowledgement can differ by days of work, and days are where a weekly number lives. When your ops lead builds the Monday report, they are not measuring the business. They are averaging several teams’ filing habits.

The tell is that nobody argues about the number itself. They argue about whether it counts the people at Northwind. Once a metric needs a caveat to be understood, it has stopped being a metric and become a talking point.

Renaming is fine. Adding is not.

Here is the distinction that matters, and most systems get it backwards.

Renaming a stage is a vocabulary problem. If your firm says Client Review and the software says Submitted, that is friction with no upside. Your people should be able to change the label to the words they actually say out loud. Nothing about the shape of the funnel changes.

Adding a stage is a reporting problem. A new column changes what the funnel is. Every historical comparison now spans two different definitions, and no report will tell you that, because the report does not know a definition changed. It just quietly returns a different number than it would have last quarter.

So the rule worth holding: labels are yours, structure is not.

That is a genuinely unpopular position. It is also why a fixed set of stages can be reported on and a configurable one cannot. You are trading a small amount of local convenience for the ability to compare desks, quarters and recruiters without an asterisk.

What to do if you are already nineteen stages deep

You do not need a migration project. You need one afternoon and a whiteboard.

Write your current stages on it and sort them into the smallest set of states that are genuinely different decisions, not different feelings. Most firms land on six or seven: screening, submitted, a couple of interview rounds, offer or hold, done. Everything else is usually either a note, a flag, or a wait that belongs inside one of those.

Then check the merges against a real question: “if these two stages became one, what report would I lose?” If you cannot name the report, they were never two stages.

The team will resist for about two weeks and then stop noticing. The reporting improves immediately, because for the first time in a year, the number means one thing.