Key takeaways
Ask a project manager what their project costs and you’ll usually get a confident answer. Ask what that number includes, and the confidence fades.
Most project budgets track the things that come with an invoice: hardware, licences, suppliers, contractors. The biggest cost on most projects rarely does. It’s the time of the people doing the work – the analysts, developers, product owners and PMO staff who log their days but never appear on the finance sheet.
That gap matters. A project can look on budget while quietly consuming twice what anyone approved, because the largest line was never on the page. This article looks at why internal resource costs go missing from project cost management, what makes it hard to count, and what organisations that get it right do differently.
Resource cost falls between two systems that rarely talk. Effort is planned and tracked in days, in a resource plan or timesheet tool. Money is tracked in pounds, in a finance spreadsheet or ERP. Nobody owns the conversion.
So timesheet costing happens by hand, if at all. Someone exports timesheets at quarter-end, multiplies days by a rate, and pastes the result into a finance pack. By then the number is weeks old, built on assumptions nobody can trace, and different from the version the PMO produced last month.
There are other reasons it slips through:
The result is that the governance board approves a budget, but nobody can say how much of the team’s time that budget actually covers.
Even when organisations do cost their people, a harder question follows: is that time capital (CapEx) or revenue (OpEx)? The answer changes how the cost appears on the balance sheet, and finance teams care about it a great deal.
Under accounting standards such as IAS 38, staff costs spent developing a lasting asset can be capitalised, while research costs are expensed. Time spent running the business or on early exploration usually can’t be capitalised either. The principle is simple. Applying it to a real project is not.
Across our client base, we see organisations draw the line in very different places:
| Approach | How it works | Strength | Watch out for |
|---|---|---|---|
| By stage | Time in build and test stages is capital; discovery and closure are revenue | Easy to apply and explain | Real work rarely respects stage boundaries |
| By task | Each task or work package is tagged capital or revenue | Precise and auditable | Heavy to maintain on large plans |
| By role | Some roles (e.g. developers) are always capital; others (e.g. PMO) never | Simple, predictable | A developer fixing live issues isn’t building an asset |
| By person | Individuals are tagged, sometimes with a fixed percentage split | Matches how some finance teams think | Splits drift from reality and are rarely revisited |
| By category | Costs are grouped into capital and revenue expenditure lines | Fits existing finance reporting | Needs a clear rule for which line people’s time lands in |
None of these is wrong. The problem comes when the rule lives in someone’s head or a spreadsheet macro, and not in the system where the plan is managed. Then every report needs a manual adjustment, and every audit question takes a week to answer.
The question worth asking is not “which rule is right?” but “is our rule written down, applied consistently, and visible in the numbers?”
Once you know what to count, you need to know what it costs. That sounds like one number per person. It rarely is.
Role rate or person rate? Many organisations cost by role: a business analyst is £450 a day. But the business analyst on your project might be a senior contractor at £650 or a graduate at £300. Cost by role and your total is tidy but wrong. Cost by person and it reflects who is actually doing the work.
Today’s rate or the rate at the time? Rates change. Pay rises, contracts renew, day rates are renegotiated. If a project runs for 18 months and you cost every day at today’s rate, you rewrite history. Work done last year at last year’s rate suddenly looks more expensive than it was, and your actuals no longer match what finance paid.
The defensible answer is a point-in-time rate: each day is costed at the rate that applied when the work was done. It’s more work to manage, but it’s the only way the project’s numbers will reconcile with the general ledger.
When resource cost is reported at all, it’s often a single figure: what we’ve spent. That answers the least useful question. A board needs three numbers to make a decision:
The value is in the gaps between them. Forecast above budget is an early warning, months before the money runs out. Actual running ahead of forecast tells you the plan is optimistic. And because these are resource costs, the gaps point straight to a cause: a role that’s overrunning, a person booking more than planned, a stage that started late.
One detail often trips people up: timing. Effort is planned weekly; finance reports monthly. A week that starts on the 29th and ends on the 4th has to land in one month or the other. Pick a rule, the month the week starts in is common, and apply it everywhere, or your monthly figures will never quite agree.
PM3 portfolio management
See how PM3 shows what your people really cost
Turn the resource plan you already manage into project costs, with resource budget, forecast and actuals alongside your other spend.
If you’re not sure whether resource cost is a blind spot for you, these questions will tell you quickly:
If you answered “no” or “not sure” to three or more, resource cost is likely the biggest unmanaged number in your portfolio.
These are the problems we set out to solve in Release 7.3 of PM3, our project portfolio management (PPM) software. The aim was simple: the resource plan you already manage in PM3 should tell you what your people cost, without a separate spreadsheet.
The capitalisation rules are still yours to decide. PM3 makes sure that once you’ve decided, the numbers follow them.
People are usually the largest investment in any project, and the one least likely to be fully counted. Organisations that cost their people properly make better decisions about which projects to start, which to stop, and where their teams’ time is really going.
Is resource cost a blind spot?
Find out what your people really cost
Book a demo to see how PM3 handles resource costs, or get in touch with the PM3 team to talk it through.
External costs come with an invoice: hardware, licences, suppliers and contractors. Internal costs are the time of your own people – the analysts, developers, product owners and PMO staff working on the project. Internal costs are often the largest on a project, yet most budgets only track the external ones.
A resource cost is what a person’s time on a project is worth in money. It converts effort, usually tracked in days in a resource plan or timesheet, into pounds that can sit alongside the rest of the project budget.
Multiply the days each person spends on the project by their day rate. For an accurate figure, use each person’s own rate rather than an average role rate, and cost each day at the rate that applied when the work was done, so your actuals reconcile with the general ledger.
Yes. Internal staff can feel “free” because their salaries are paid regardless, but leaving their time out means a project can look on budget while consuming far more than anyone approved. Including it lets the governance board see how much of the team’s time a budget actually covers.
It can be either. Staff time spent developing a lasting asset can be capital expenditure (CapEx), while time spent on research, early exploration or running the business is usually revenue expenditure (OpEx). Which applies depends on the work being done, not just who is doing it.
Yes, in some cases. Under accounting standards such as IAS 38, staff costs spent developing a lasting asset can be capitalised. Organisations apply this in different ways – by stage, task, role, person or expenditure category, so check the rule with your finance team.
Research costs are expensed rather than capitalised, and time spent running the business or on early exploration usually can’t be capitalised either. For example, a developer fixing live issues isn’t building an asset, even if their development work on a project is capitalised.
Write your capitalisation rule down and apply it in the system where the plan is managed, not by hand afterwards. That way every report reflects the rule automatically, and audit questions can be answered from the numbers rather than a spreadsheet macro.
Image Source: Astrid IQ

PM3 is a complete PPM ecosystem that is ideal for construction-based change management and transformation projects. Easy to use, fully customizable, and with deep integrations, you can deliver your projects your way while enhancing project delivery. With our in-house development team constantly refining existing workflows and developing new ones to better support industry needs, BestOutcome is a company that is one to watch.
Discover PM3 Schedule a demoOver the last 20+ years I've tracked the overall competency of organisations to deliver projects suc...
Read more >