Without proper budgeting and cost management, your project will run out of money before it is finished, forcing you to deliver incomplete work or ask stakeholders for emergency funding. This concept matters for the PMP exam because cost is the second most important constraint after scope — and exam questions love to test your ability to calculate variances and predict final costs. You need to understand how to plan, track, and control the money in a project so you can pass the PMP and manage real-world IT projects.
Jump to a section
A simple way to picture Budgeting and Cost Management
You and your partner plan a 14-day holiday to Italy with a total budget of £5,000. This is your project budget — the total authorised cost for the whole trip. On day one, you spend £200 on flights. That is an actual cost (AC), money you have already spent. Your plan says flights should cost £250, so you are £50 under budget — a positive variance. But on day three, you book a more expensive hotel (£800 instead of the planned £600). Now you have a negative variance of £200 on accommodation. The question is: can you recover that overspend elsewhere? Maybe you eat at cheaper restaurants or skip the boat tour. This is cost management in action — tracking what you spend against what you planned, and making adjustments to stay within the total pot of £5,000.
Your partner is the project manager. You check the budget every morning (weekly status reporting). Sometimes you find a variance and need to decide: cut costs elsewhere or request more money from the 'bank' (the sponsor). If you overspend early and ignore it, you might run out of money before the last day — a cost overrun. The entire holiday budget is your cost baseline, and the £5,000 cap is your cost performance baseline. Every decision you make — whether to pay for a guided tour or walk instead — is a cost management decision. This analogy maps directly to IT project budgeting because in both cases you have a fixed pot of money, you track planned vs actual spending, and you need to forecast if you will finish under or over budget.
Budgeting and cost management is the process of estimating, allocating, and controlling the costs of a project so that it can be completed within the approved budget. Think of it as the financial blueprint for your project: you decide how much money you need, where it will be spent, and how you will ensure you do not overspend.
The first step is cost estimation. This is where you predict how much each activity or work package will cost. For example, if your IT project needs to buy 10 servers at £2,000 each, that is a £20,000 cost estimate. You also need to estimate labour costs for developers and testers, software licences, cloud services, and any other expenses. The PMBOK Guide recognises several estimation techniques. - Analogous estimation: using a previous similar project's cost as a basis. If a past mobile app project cost £100,000, a similar new app might also cost around that amount. This is quick but not very accurate. - Parametric estimation: using a mathematical model based on parameters. For instance, if building a website costs £500 per page, and you have 20 pages, the estimate is £10,000. This is more accurate if your data is reliable. - Bottom-up estimation: estimating each individual task or component and then rolling them up into a total. This is the most accurate but also the most time-consuming. - Three-point estimation: using optimistic (best-case), pessimistic (worst-case), and most likely estimates to calculate a weighted average. The formula is: (optimistic + 4*most likely + pessimistic) / 6. This accounts for uncertainty.
Once you have estimates, you create the cost baseline. The cost baseline is the approved version of the budget, broken down by time period. It is a time-phased budget that shows how much money you plan to spend each month or week. For example, you might spend £10,000 in month one on design, £30,000 in month two on development, and £20,000 in month three on testing. This baseline becomes the standard against which you measure actual performance.
Then you move to cost control. This is the ongoing process of monitoring the project's spending and performance. You track two key metrics: actual cost (AC) — the money spent so far — and earned value (EV) — the value of the work actually completed. The planned value (PV) is the amount of work you planned to have done by this point. These metrics allow you to calculate variances and performance indices. - Cost variance (CV) = EV - AC. If positive, you are under budget; if negative, over budget. - Schedule variance (SV) = EV - PV. Positive means ahead of schedule; negative means behind. - Cost performance index (CPI) = EV / AC. A CPI > 1 means you are getting more value per dollar; CPI < 1 means you are overspending. - Schedule performance index (SPI) = EV / PV. > 1 means ahead of schedule; < 1 means behind.
These calculations are part of a technique called earned value management (EVM). EVM integrates scope, schedule, and cost to give you a single, objective measure of project health. For example, if your CPI is 0.8, you are only getting 80 pence of value for every pound spent — meaning you are 20% over budget. You can then forecast the estimate at completion (EAC) — the expected total cost when the project finishes. There are several formulas for EAC, but the most common is EAC = BAC / CPI, where BAC is the budget at completion. If your BAC is £100,000 and CPI is 0.8, your EAC is £125,000 — meaning you will be £25,000 over budget.
Why does all this exist? Projects historically ran over budget because nobody tracked spending against a plan in real time. EVM forces you to measure progress objectively, not just count how much money you have spent. Without it, you might think you are on track because you have only spent half the budget, but you may only have completed 30% of the work — a dangerous situation. Cost management replaces guesswork with data-driven decision making.
In IT projects, common costs include hardware, software licences, cloud subscriptions, contractor fees, employee salaries, training, and travel. You also need to include contingency reserves (set aside for known risks) and management reserves (for unknown risks). The total of all these is the project budget. The cost baseline plus management reserves equals the total project budget.
Cost management is not a one-time activity. You constantly review actual costs against the baseline, update forecasts, and recommend corrective actions like reducing scope, finding cheaper suppliers, or requesting a budget increase. The ultimate goal is to finish the project within the approved budget while delivering all the agreed scope.
Plan Cost Management
This is the first step where you define how costs will be estimated, budgeted, and controlled throughout the project. You create the cost management plan, which sets the rules for measuring performance, reporting thresholds, and escalation procedures. Without this plan, cost tracking will be chaotic.
Estimate Costs
Here you develop an approximation of the monetary resources needed to complete each project activity. You use techniques like analogous, parametric, bottom-up, or three-point estimation. This step produces a detailed cost estimate that includes direct and indirect costs, with a level of accuracy typically within -10% to +25%.
Determine Budget
In this step, you aggregate the individual cost estimates into a total project budget. You add contingency reserves and management reserves. The output is the cost baseline — a time-phased, approved version of the budget that you will use for measuring performance. The baseline is usually an S-curve showing cumulative spend over time.
Control Costs
This is the ongoing step during project execution. You monitor actual costs against the cost baseline, calculate variances (CV and SV), and compute performance indices (CPI and SPI). You also forecast the estimate at completion (EAC) and recommend corrective actions if needed. This step happens weekly or monthly throughout the project.
Forecast and Update
Based on current performance data, you estimate the final project cost (EAC) and the remaining cost to completion (ETC). You update the cost baseline if approved changes occur. This step ensures stakeholders are always informed of the most likely financial outcome and can make informed decisions.
An IT project manager at a mid-size company is overseeing the development of a new customer relationship management (CRM) system. The project has a budget of £250,000 and a timeline of 6 months. Here is how budgeting and cost management plays out in the real world.
First, the PM works with the finance team and technical leads to create a detailed cost estimate. They identify all cost categories: software development labour (£120,000 for 4 developers over 6 months), project management labour (£30,000), cloud infrastructure (£40,000 for AWS servers and databases), third-party integrations (£20,000 for API licensing), testing and QA (£25,000), and contingency (£15,000). They use bottom-up estimation for most items, giving a total estimate of £250,000.
The PM then builds the cost baseline. They break down the £250,000 across the 6 months: Month 1 (planning and design) = £30,000, Month 2-3 (development) = £100,000, Month 4 (integration) = £50,000, Month 5 (testing) = £40,000, Month 6 (deployment and training) = £30,000. This baseline is approved by the project sponsor.
During execution, the PM tracks actual costs weekly. In Month 2, the development team finishes 40% of the coding work but has spent £55,000 of the planned £50,000 for that month. The PM calculates:
Planned value (PV) for Month 2 = £50,000 (the planned cumulative spend by end of Month 2).
Earned value (EV) = 40% of total development cost (£100,000) = £40,000.
Actual cost (AC) = £55,000.
Cost variance (CV) = EV - AC = £40,000 - £55,000 = -£15,000 (over budget by £15,000).
Schedule variance (SV) = EV - PV = £40,000 - £50,000 = -£10,000 (behind schedule by £10,000 worth of work).
CPI = EV / AC = 40,000 / 55,000 = 0.73 (only getting 73 pence of value per pound spent).
The PM presents this data to the project board. The board asks for a recovery plan. The PM analyses the root cause: the lead developer underestimated the complexity of a module. Options include:
Adjusting the development approach to use more efficient tools.
Adding a junior developer to speed up work (but this increases cost further).
Reducing the scope of a non-critical feature.
Requesting a budget increase of £15,000 from the contingency reserve.
The PM decides to use the £15,000 contingency reserve to cover the overrun and also reassigns a tester to help with development. The PM updates the cost performance baseline and the forecast EAC: BAC = £250,000, CPI = 0.73, so EAC = £250,000 / 0.73 = approximately £342,000. This is a significant overrun, so the PM escalates to the sponsor. The sponsor approves an additional £92,000 from the management reserve, bringing the total budget to £342,000. The PM then revises the cost baseline and updates the stakeholder communication on the new budget.
Each week, the PM repeats this process: check actual hours logged, review invoices from cloud providers, compare to plan, calculate variances, and update the forecast. At the end of Month 3, the CPI improves to 0.85 because the team has become more efficient. The PM continually refines the EAC and reports progress to the steering committee. This scenario demonstrates that real-world cost management is not a set-and-forget activity — it requires constant vigilance, data analysis, and proactive decision making.
The PMP exam tests budgeting and cost management heavily. You will see 10-15 questions from this domain. The exam expects you to know the formulas, the terminology, and the correct sequence of processes. Here is exactly what you need to focus on.
Key concepts the exam loves:
The difference between cost baseline, project budget, and total project cost. The cost baseline is the approved time-phased budget, usually without management reserves. The project budget includes management reserves. The total project cost is what you actually spend.
Earned value management (EVM) formulas: CV = EV - AC, SV = EV - PV, CPI = EV / AC, SPI = EV / PV. You must memorise these.
The three estimates at completion (EAC) formulas: EAC = BAC / CPI (if the CPI will remain the same), EAC = AC + (BAC - EV) (if the current variance is atypical), and EAC = AC + [(BAC - EV) / (CPI * SPI)] (if both cost and schedule performance affect the future).
Types of costs: direct vs indirect, fixed vs variable, sunk costs. Remember: sunk costs should never influence future decisions.
Question types:
Calculation questions: They give you PV, EV, and AC, and ask for CV, CPI, or EAC. Trap: they might give you irrelevant numbers. Always extract only the numbers you need.
Scenario questions: They describe a project situation (e.g., 'the project is behind schedule and over budget') and ask what the PM should do first. Correct answer is nearly always 'analyse the situation and calculate variances' or 'perform root cause analysis', not immediately ask for more money.
Definition questions: They ask which document contains the approved cost baseline (answer: the cost management plan or the project management plan).
Common traps:
Confusing cost baseline with project budget. The cost baseline excludes management reserves; the project budget includes them.
Mixing up EVM formulas. Example: using AC instead of EV in the CV formula. Remember: CV = EV - AC, not AC - EV.
Thinking that a negative cost variance is always bad. It is — over budget — but a negative schedule variance is also bad (behind schedule). They may test both.
Offering 'ask for more budget' as the first action. The correct pattern is always to analyse first, then take corrective action.
Concepts to memorise for the exam:
Cost management plan: describes how costs will be planned, structured, and controlled.
Cost baseline: the approved budget, usually in an S-curve shape over time.
Contingency reserves: for known unknowns (risks). Managed by the PM.
Management reserves: for unknown unknowns. Controlled by management or sponsor.
BAC (budget at completion), EAC (estimate at completion), ETC (estimate to complete), VAC (variance at completion).
The exam also tests the process groups where cost management occurs: Plan Cost Management (planning), Estimate Costs (planning), Determine Budget (planning), and Control Costs (monitoring and controlling). You need to know which process belongs to which group and what outputs each produces.
The cost baseline is the time-phased budget against which you measure project performance, and it excludes management reserves.
Earned value management (EVM) gives you an objective measure of project health by comparing planned value, earned value, and actual cost.
Cost variance (CV) is earned value minus actual cost; a negative CV means you are over budget.
Schedule variance (SV) is earned value minus planned value; a negative SV means you are behind schedule.
The cost performance index (CPI) below 1 indicates you are getting less value per pound spent and will likely finish over budget.
Always analyse variances before taking corrective action — do not immediately ask for more money from the sponsor.
Contingency reserves are for known unknowns and are managed by the project manager; management reserves are for unknown unknowns and require sponsor approval.
Sunk costs should never influence future project decisions; evaluate each remaining task on its own benefits and costs.
These come up on the exam all the time. Here's how to tell them apart.
Cost Baseline
Excludes management reserves
Time-phased and approved for measuring performance
Used to calculate cost variance and CPI
Project Budget
Includes cost baseline plus management reserves
Total authorised funding for the project
May include extra funds for unknown risks
Contingency Reserves
For known risks (known unknowns)
Managed by the project manager
Part of the cost baseline
Management Reserves
For unknown risks (unknown unknowns)
Controlled by management or sponsor
Not part of the cost baseline
Cost Variance (CV)
Formula: EV - AC
Measures cost performance (over/under budget)
Negative means over budget
Schedule Variance (SV)
Formula: EV - PV
Measures schedule performance (ahead/behind)
Negative means behind schedule
Estimate at Completion (EAC)
Forecast of total project cost when finished
Calculated during project execution
Updated as project progresses
Budget at Completion (BAC)
Original total approved budget
Determined at project start
Fixed unless scope changes
Direct Costs
Directly attributable to the project (e.g., salaries, software licences)
Easily traced to specific project activities
Included in the cost baseline
Indirect Costs
Shared across multiple projects (e.g., rent, electricity, admin overhead)
Allocated proportionally, often using a cost pool
May not appear in the project's direct estimates
Mistake
The cost baseline and the project budget are the same thing.
Correct
The cost baseline excludes management reserves, while the project budget includes them. The baseline is a subset of the budget.
Many beginners assume 'budget' means the total money available, but the PMBOK distinguishes between the two for control purposes.
Mistake
If the CPI is less than 1, the project is behind schedule.
Correct
CPI measures cost efficiency, not schedule. A CPI < 1 means the project is over budget. Schedule performance is measured by SPI.
Beginner confusion between CV and SV, or between CPI and SPI, is common because both indices start with 'C' and 'S'.
Mistake
You should stop spending money on a task that is already over budget to avoid further loss.
Correct
Sunk costs are irrelevant to future decisions. You should evaluate each remaining task on its own merit. Stopping a partially completed task may waste the money already spent.
People naturally want to cut losses, but project management principles say you should ignore sunk costs and base decisions on future value.
Mistake
EVM is only useful for large, complex projects.
Correct
EVM can be scaled to any size. Even a small project with a £10,000 budget benefits from tracking planned vs earned vs actual costs.
Beginners think EVM is overwhelming, but the core idea — compare planned work to actual work to actual cost — works for any project.
Mistake
Contingency reserves and management reserves are the same thing.
Correct
Contingency reserves cover known risks (e.g., a possible price increase) and are managed by the PM. Management reserves cover unknown risks and require sponsor approval.
The terms sound similar, and beginners often use them interchangeably, but the PMP exam demands clear distinction.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The cost baseline is the approved, time-phased budget excluding management reserves. The project budget includes both the cost baseline and management reserves. Management reserves are for unknown unknowns.
Yes, you must memorise CV, SV, CPI, SPI, and the three EAC formulas. The exam will test you on calculations and scenario-based questions that require these formulas.
It means for every £1 you spend, you only get £0.80 worth of work completed. You are 20% less efficient than planned, indicating a cost overrun.
Yes, contingency reserves are included in the cost baseline because they are allocated for known risks. Management reserves are not part of the cost baseline.
Use EAC = BAC / CPI if the current cost variance is expected to continue. Use EAC = AC + (BAC - EV) if the variance is a one-time event. If the question mentions both cost and schedule factors, use the formula with CPI * SPI.
A sunk cost is money already spent and cannot be recovered. The PMP principle is to ignore sunk costs when making future decisions. Do not continue a failing project just because you have already spent money on it.
You've finished Budgeting and Cost Management. Continue through the PMP study guide to build a complete picture of the exam.
Done with this chapter?