NEW

Project Costing: What Project Costs Are and How to Calculate Them

Take your project management to the next level
September 2026
Project Costing: What Project Costs Are and How to Calculate Them

A project cost is every dollar a piece of work consumes before it is finished: the hours your people put in, the tools and materials they use, a share of the rent and admin that keep the business running, and a reserve for the things nobody predicted. Project costing is the practice of putting a number on each of those, first as an estimate and then as a running record of what the work actually cost.

Most guides stop at a list of cost types. This one also shows how the types fit into a single calculation, walks through a worked example with real arithmetic, and points out where project costs usually leak in practice, so you can build a figure you would be willing to defend in front of a client or a finance team.

What is project cost?

Project cost is the total amount of money needed to complete a project, covering labor, materials, equipment, services, a fair share of overhead, and a reserve for risk. It is the figure you estimate before work starts, set as the project budget, and then compare against actual spending until the project closes.

Keep project cost separate from project price. Cost is what the work takes to deliver. Price is what a client agrees to pay, and it comes out of a negotiation that also involves margin, competition, and what the market will bear. A project can be priced well and still lose money if nobody knew its real cost, which is why costing comes first.

What is project costing?

Project costing is the process of identifying, estimating, recording, and allocating every cost that belongs to one specific project. It answers two questions at different times. Before the project, it answers “what will this cost?” During and after the project, it answers “what did this actually cost, and where did the difference come from?”

That second half is what separates project costing from a one off estimate. An estimate is a forecast. Project costing keeps a ledger per project, so actual labor hours, purchases, and allocated overhead land against the project they belong to rather than disappearing into company wide expense lines. The wider discipline that wraps planning, budgeting, and control around this ledger is project cost management, and the methods for producing the first forecast are covered in our guide to project cost estimation techniques.

The 5 types of project costs, plus contingency

Most project management references group project costs into five types: direct, indirect, fixed, variable, and sunk. The five come from Dan Epstein and Rich Maltzman’s book Project Management Workflow, as summarized on ProjectManagement.com. Contingency is not a cost type in the same sense, but every realistic estimate includes it, so it gets its own section here.

One thing the lists rarely say out loud is that these are two separate ways of sorting the same costs, not five buckets. Direct and indirect costs differ in traceability: can you tie the cost to this project? Fixed and variable costs differ in behavior: does the cost change as the project runs longer or does more work? A single cost carries one label from each pair. A developer’s hours are direct and variable. A software license bought once for the project is direct and fixed. Office rent is indirect and fixed.

Cost type What it means Example in a client services project
Direct Traceable to this project only Hours logged by the project team, a contractor hired for this job
Indirect Shared across projects, allocated as overhead Office rent, finance and HR salaries, company wide software
Fixed Stays the same regardless of duration or volume A one time license, a setup fee, a permit
Variable Grows as the project runs longer or does more Labor hours, equipment hire by the week, usage based services
Sunk Already spent and not recoverable Discovery work already paid for, a prototype that was scrapped
Contingency A reserve for identified risks An extra 10% on the subtotal for rework or delayed approvals

Direct costs

Direct costs exist only because this project exists. If the project were cancelled tomorrow, they would stop. The usual items are labor for people working on project tasks, materials consumed by the work, equipment bought or rented for it, subcontractor fees, project travel, and licenses bought specifically for the job.

In service businesses such as agencies, consultancies, and engineering firms, labor is almost always the largest direct cost by a wide margin. That makes the accuracy of logged hours, and the rate each hour is costed at, the single biggest driver of whether your project cost figure is right. A small error in material costs barely moves the total; a missing week of timesheets can move it by thousands.

Indirect costs

Indirect costs keep the company running and would exist whether or not this project happened: rent, utilities, admin and finance staff, insurance, general software, and management time spread across many projects. You cannot trace them to one project, so you allocate a share of them, usually as a percentage of direct labor cost or per hour worked.

A common allocation method is simple: add up the overhead for a period, divide it by the direct labor cost for the same period, and apply that percentage to each project’s labor. It is not perfectly fair to every project, but it is consistent, and consistency is what lets you compare one project’s cost with another’s.

A frequent question is whether the project manager’s own time is direct or indirect. It depends on how the role works. A project manager dedicated to one project is a direct cost and belongs as its own line in the budget. A project manager spread across several projects is often treated as overhead instead. Either way, the time is a real cost and has to appear somewhere, because leaving it out makes every project look cheaper than it is.

Fixed costs

Fixed costs do not change with project duration or output. A $1,200 license costs $1,200 whether the project takes six weeks or ten. Fixed costs are easy to forecast, which makes them useful anchors in an estimate, but they are also commitments: once you have paid them, a delay or a scope cut does not give the money back.

Variable costs

Variable costs move with the amount of work or time. Paying a team for a 12 month project costs more than paying the same team for 6 months, and renting equipment for 8 weeks costs more than for 3. Labor is the variable cost that matters most, because every extra week of work, every round of rework, and every hour of overtime lands here. When a project runs over budget, variable costs are almost always where the overrun shows up first.

Sunk costs

Sunk costs have already been spent and cannot be recovered, so they should not drive decisions about the project’s future. If a company has spent $1 million on a project and needs another $200,000 to finish something it no longer wants, the $1 million is gone either way. The only question is whether the extra $200,000 is worth spending. The trap is that sponsors often value finishing over usefulness, and continue projects because of what has already gone in.

A close relative is opportunity cost: the return you give up by putting people and money into this project instead of the next best option. It never appears on an invoice, but it is worth stating when you compare two projects competing for the same team.

Contingency reserve

Contingency is money set aside for risks you can name but not yet price precisely: design changes, delayed approvals, price increases, a key person leaving. A commonly cited range is 5% to 20% of the project budget, depending on complexity and risk. Treat that as a starting point rather than a rule. A better method is to list the specific risks, estimate what each would cost if it happened and how likely it is, and size the reserve from that list. Our guide to risk and contingency planning covers this in more detail.

How to calculate the cost of a project

The cost types above come together in one formula:

Total project cost = direct labor + other direct costs + allocated overhead + contingency

To fill it in, work through these steps in order:

  1. List the work.

    Break the project into tasks or deliverables, ideally with a work breakdown structure. You cannot cost work you have not listed, and missing tasks are the most common source of underestimates.

  2. Estimate hours per role and multiply by a cost rate.

    Use each person’s internal cost rate (what an hour of their time costs the company), not their billing rate. Add expected overtime at the overtime rate, not the regular one.

  3. Add other direct costs.

    Contractors, licenses, materials, equipment, and travel bought for this project.

  4. Allocate overhead.

    Apply your company’s overhead rate, usually as a percentage of direct labor cost.

  5. Add contingency.

    Size it from the project’s identified risks and add it on top of the subtotal.

If you need a structure for laying these lines out, a project cost breakdown organizes them by phase, task, and cost category.

Project cost example

Here is a worked example for a 10 week website redesign delivered by a small agency. The figures are illustrative, chosen to show the arithmetic, and are not industry benchmarks.

Developer: 300 hours x $55 = $16,500
Developer overtime: 20 hours x $82.50 (1.5 x $55) = $1,650
Designer: 120 hours x $50 = $6,000
Project manager: 60 hours x $60 = $3,600
Direct labor: $16,500 + $1,650 + $6,000 + $3,600 = $27,750
Other direct costs: $2,500 copywriter + $1,200 licenses + $300 stock assets = $4,000
Allocated overhead at 20% of direct labor: $27,750 x 0.20 = $5,550
Subtotal: $27,750 + $4,000 + $5,550 = $37,300
Contingency at 10%: $37,300 x 0.10 = $3,730
Total project cost: $37,300 + $3,730 = $41,030

Look at where the money sits. Direct labor is $27,750 of $31,750 in direct costs, about 87%. The licenses are the only fixed cost in the list, and they are under 3% of the total.

Now move one input. Say the developer’s work runs 20% over, from 300 hours to 360. That adds 60 x $55 = $3,300 in labor and $660 in overhead on top, a total of $3,960. The whole contingency reserve was $3,730, so a single role running 20% over consumes all of it and pushes the project $230 past its estimate before anything else goes wrong. This is why labor hours deserve the closest tracking of anything in the budget.

Tip:
A cost rate is more than salary divided by 2,080 hours. Add benefits and payroll taxes, and divide by the hours people actually have available for project work after meetings, admin, and leave. A $95,000 salary with 25% on top for benefits is $118,750 a year. Spread over 2,080 hours that is about $57 an hour; spread over 1,800 available hours it is about $66. Using the lower figure understates every project that person works on by roughly 14%.

Where project costs leak

An estimate can be arithmetically perfect and still be wrong by the end of the project. These are the places the gap usually opens:

  • Hours that never get logged. Quick calls, small fixes, and review rounds often go unrecorded, so the project looks cheaper than it was and the next estimate repeats the mistake.
  • Overtime costed at the regular rate. If overtime is paid at 1.5 times the base rate but costed at the base rate, every late week understates project cost by a third of those hours’ value.
  • Leave and bench time left out. Paid leave is a real cost of employing the team. If it is not built into the cost rate or allocated somewhere, it quietly erodes margin across all projects.
  • Stale cost rates. Rates set once and never updated after raises or new hires drift further from reality every quarter.
  • Overhead that is never allocated. Projects costed on direct labor alone always look profitable on paper, while the company as a whole does not.
  • Scope changes that never get costed. Small additions agreed in a meeting add hours without adding budget. Each one is minor; together they are often the whole overrun. Our article on the causes of cost overruns goes deeper on this.
  • Sunk cost reasoning. Continuing a failing project because of what has already been spent turns a contained loss into a larger one.

Tracking actual project costs against the estimate

The estimate is only half of project costing. The other half is recording actual costs as they happen and comparing them against the plan often enough to act on the difference. The full control process, including earned value and budget changes, is covered in our guide to project cost management. For most service teams, the practical question is narrower: how do you know what the labor on a project has cost so far?

That is the part actiTIME handles. You set a cost rate for each employee, with separate regular, overtime, and leave rates, and the team tracks time against customers, projects, and tasks. The Cost of Work Report then turns those hours into staff costs per user and project, including overtime and leave costs, so the two leaks above that are hardest to see by hand are counted automatically.

You can set a cost budget on any customer, project, or task, and its progress bar turns red once spending passes the limit, which gives you the early warning the sensitivity example above calls for. The Estimated vs. Actual Time Report shows which tasks are running over in hours, and the Profit/Loss Report compares billable amounts with costs by customer, project, or task. actiTIME tracks staff related costs; non labor items such as materials and contractor invoices still need to come from your accounting records. Our step by step guide on managing project costs in actiTIME shows the full setup.

See what every project really costs in labor, overtime, and leave, and catch overruns while there is still time to act

Try Free

Project cost tracking

FAQ

Should the project manager’s time be included in project cost?

Yes. Managing the project is part of the work needed to deliver it, so its cost belongs in the project figure. What varies is where it sits: a project manager dedicated to one project is usually a direct cost line, while one spread across several projects is often covered through the overhead allocation. Leaving the time out entirely makes every project look cheaper than it is.

What is the difference between project costing and job costing?

Both assign costs to a specific piece of work rather than to a period. Job costing is typically used for short, repeatable jobs such as a print run or a repair call, where each job is costed and closed quickly. Project costing applies the same idea to longer, one off efforts that run across months, have phases and budgets, and need actual costs compared against an estimate while the work is still going on.

Is project costing the same as cost estimation?

No. Cost estimation produces the forecast before the project starts. Project costing includes that forecast but continues through the project, recording actual labor, purchases, and overhead against it so you can see the variance and explain it. An estimate without that follow through tells you what you expected to spend, not what you spent.

Conclusion

Knowing the five types of project costs is useful mainly because it keeps you from missing a line. The real value comes from putting them into one calculation, costing labor at honest rates that include overtime and leave, allocating overhead consistently, and sizing contingency from actual risks. Then keep recording actual costs so each project’s estimate is better than the last.

If labor is the biggest cost in your projects, tracking it accurately is the fastest way to make your project costing reliable. Start a free trial of actiTIME to see cost of work, budgets, and profitability for your own projects.

Are you ready to drive your business growth with actiTIME?

Start Using actiTIME