How Many People Do You Have? Why Nobody in Your Organization Can Answer That Question

How many times have you sat in this meeting?

Finance says headcount is 94. Ops says it's 107. HR has a third number nobody can explain. The first 20 minutes of what was supposed to be a strategy discussion turns into a debate about whose spreadsheet is right.

They're all technically right. Finance counts FTEs by cost center. Ops counts bodies by contract. HR is pulling from a system that probably hasn't been reconciled since the last migration.

And that's the part most leadership teams miss. The argument isn't about who's wrong. It's about the fact that nobody has ever decided which number answers which question.

Three numbers, three jobs

Each of those counts exists for a reason, and each one is valid depending on what you're trying to figure out.

Your FTE count is finance's number. It feeds your indirect rate calculations and your incurred cost submissions. When DCAA reviews your rates and compares what you proposed to what you actually incurred, this is the labor base they're looking at. If you've been calculating benefit rates using a different headcount, you've got a variance sitting in your cost structure that you may not even know about until an auditor finds it.

Your contract headcount is ops' number. It feeds proposal staffing, utilization tracking, and contract performance reporting. This is the number your PMs and contracting officers work from. It includes subcontractors and part-time support that don't show up in the FTE count, and that's fine. It's measuring something different.

Your employee count is HR's number. It feeds benefits administration, workers' comp, and EEO/AAP compliance reporting. It includes everyone on payroll regardless of what contract they're billing to or whether they're currently utilized.

All three are doing their job. The problem is that nobody has written down which number belongs where.

What happens when you grab the wrong one

This might sound like a meeting that runs long and a spreadsheet that needs another tab. It's not.

When headcount doesn't tie, the downstream damage is real and it's quiet. It doesn't announce itself. It accumulates.

Benefit rates get built on the wrong labor base. Your finance team calculates the rate using one count, but the actual cost is spread across a different population. The numbers look close enough month to month, but over a fiscal year the gap compounds. By the time it surfaces in an incurred cost submission, you're explaining a variance you didn't know existed.

Proposals get staffed against a count that doesn't match what your contracts team is actually managing. Ops says you have capacity for a new task order because their spreadsheet shows 107 people. Finance says you don't because their budget only supports 94 FTEs. Both are looking at accurate data. Neither is looking at the same data.

Incurred cost figures don't tie because finance and ops were never counting the same thing to begin with. And that's the one that really costs you, because DCAA doesn't care which spreadsheet you prefer. They care whether your numbers reconcile.

I worked with a firm last year that had been carrying a $600K discrepancy in their benefit pool for two fiscal years. Not because anyone was doing anything wrong. Because finance and HR were pulling labor data from two different sources, and nobody had ever sat in a room and asked which one was the real number.

Why the usual fixes don't work

The instinct is almost always to build a better spreadsheet. Or buy a tool. A dashboard that pulls from all three systems and presents "the number."

The problem with a dashboard is that it's a display layer. It doesn't resolve the underlying conflict. If finance and ops are counting different things for different reasons, a dashboard just shows you both numbers side by side in a prettier format. You still don't know which one to use for your rate calculation. You still can't hand an auditor a single source and say this is our labor base, here's how we got there.

The other common move is to assign someone to "own the data." Which sounds right, except that ownership without authority doesn't change anything. If the person who "owns" the headcount number doesn't have the authority to tell ops they need to stop maintaining a separate count, you've just added a fourth version of the truth.

What actually works

The fix isn't picking one number and throwing the others away. It's building a reconciliation layer.

One place where all three counts live, with clear labels for what each one measures and which decisions it feeds. Finance's FTE count feeds the indirect rate calculation. Ops' contract headcount feeds proposal staffing and utilization tracking. HR's employee count feeds benefits administration and compliance reporting.

Each number keeps doing its job. But they all tie back to a single reconciliation that explains the differences.

The 13-person gap between finance and ops? Subcontractors who appear in the contract-level headcount but aren't included in the FTE labor base. The 7-person gap between finance and HR? Employees in overhead or G&A roles who aren't allocated to a direct cost center. Not an error. A design choice. And now it's documented.

Building this isn't complicated. It takes about two weeks of focused work: mapping each source, identifying the gaps, documenting the logic, and publishing a reconciliation schedule that gets updated on a defined cadence. The hard part isn't the mechanics. It's getting three department heads to agree that one reconciliation replaces three separate arguments.

That's a decision-rights conversation, not a data conversation. And it's where most organizations stall, because giving up your number feels like giving up your authority.

The organizations that resolve it don't do it by consensus. One person decides. Everyone else aligns. The argument is over. Not because anyone was wrong, but because everyone finally knows which number to reach for and when.

What changes on the other side

Once headcount ties, the Monday morning meeting gets shorter. But that's the least of it.

Your indirect rates are built on labor figures you can actually defend. Your proposals use the same workforce data your contracts team is managing against. When DCAA pulls your incurred cost submission, the numbers tie back without a two-week scramble. Your leadership team stops burning the first hour of every week relitigating data and starts spending it on decisions that move the business forward.

And the next time your CEO asks "how many people do we have?" the answer is clean, it's fast, and it's the same answer no matter who you ask.

One reconciliation. Document it once. Update it monthly. Everything else follows from there.

If your leadership team is still having this argument every month, it might be time to build the reconciliation layer underneath it. I'm happy to talk through what that looks like.