Effective cost management starts with a clear baseline: your Budget at Completion (BAC).
BAC defines the total approved budget for your project and acts as a reference point for cost tracking throughout execution. Without it, you’re flying blind when performance questions arise.
In this guide, you’ll learn what BAC means, how to calculate it using estimating techniques, and how to interpret it against EAC for accurate forecasting.
You’ll also see a worked BAC example and get access to an interactive online calculator that lets you run scenarios and download your results.
What Is Budget at Completion (BAC) in Project Management?
BAC represents the total authorized budget for completing all project work. It forms the foundation of cost performance tracking in Earned Value Management (EVM).
BAC is set during the planning phase and includes all approved costs for labor, materials, and resources. It excludes management reserves, which are held separately for unforeseen risks.
It answers a simple question: “How much should the project cost in total?”
As work progresses, BAC is compared to Earned Value (EV) and Actual Cost (AC) to track efficiency and performance. These comparisons reveal whether you’re on track, overspending, or ahead of schedule.
A fixed BAC ensures consistency in cost control unless scope changes occur. Think of it as your project’s financial finish line. Everything revolves around staying close to that number.
Without a clear BAC, you can’t measure cost variance, calculate performance indices, or forecast final costs with confidence. It’s not just a budgeting figure. It’s the anchor for every cost decision you make during execution.
How to Calculate Budget at Completion (BAC)
There’s no single formula for BAC. It’s derived from the sum of all estimated costs for authorized work.
The method you use depends on the data you have, the complexity of your project, and how much uncertainty you’re dealing with. Most projects use one or a combination of the following approaches.
1. Analogous Estimating
This method uses data from past, similar projects to estimate total cost.
It’s fast and useful when you have limited details but strong historical records. The trade-off is accuracy, especially if project conditions differ.
Example: A prior web project cost $100,000. A similar one now is expected to cost slightly more due to added features. You estimate BAC at $120,000 based on that comparison.
2. Parametric Estimating
This approach multiplies known parameters by cost rates.
It’s more accurate than analogous estimating when you have reliable unit cost data and measurable work quantities.
Example: You’re building a system with 5 modules. Each module costs $3,000 to develop. BAC equals $15,000.
This method works well for repetitive or standardized work where cost drivers are clear and consistent.
3. Expert Judgment
You consult domain experts to estimate cost for activities, especially when historical data is thin or the work is unique.
This works best for projects with custom deliverables or evolving requirements. Combine it with historical insights wherever possible to improve accuracy and reduce bias.
Experts bring real-world context that raw data can’t capture.
4. Combined Approach
Most projects mix techniques. You might use parametric estimating for known work and expert judgment for new or uncertain elements.
This layered approach creates a more realistic BAC baseline that reflects both data and experience.
BAC Formula and Example
Let’s illustrate BAC with a real-world example.
You’re a project manager developing a new mobile app. Your team has broken down the work and estimated costs for each phase.
Here’s what the breakdown looks like:
- Research: $5,000
- Design: $8,000
- Development: $55,000
- Testing: $7,000
- Launch: $10,000
BAC = $85,000 (sum of all cost estimates).
This figure becomes the cost baseline for tracking earned value metrics such as EV, AC, and CPI throughout execution. It’s the number you’ll reference every time you assess cost performance or forecast final outcomes.
During execution, the BAC remains constant unless the scope changes. This consistency ensures accurate comparisons with actual performance metrics.
If scope expands and you add a new feature costing $10,000, your revised BAC becomes $95,000. But that change requires formal approval through your change control process.
Without a stable BAC, your cost tracking loses its anchor. You can’t measure variance or performance reliably if the baseline keeps shifting without justification.
BAC vs PV vs EAC
BAC often gets confused with other earned value terms like Planned Value (PV) and Estimate at Completion (EAC). Here’s how they differ.
Each metric serves a distinct purpose in cost and schedule tracking. Understanding the differences helps you interpret project health accurately.
| Metric | Definition | Purpose | Changes Over Time | Example |
|---|---|---|---|---|
| BAC | Total approved budget for all planned work. | Serves as project cost baseline. | Fixed unless scope changes. | Total project = $85,000. |
| PV | Value of planned work by a given time. | Measures schedule progress. | Increases as project progresses. | After 1 month: PV = $20,000. |
| EAC | Revised estimate of total cost based on current performance. | Forecasts actual final cost. | Updates regularly. | EAC = $95,000 due to overruns. |
BAC is the foundation. It tells you what the project should cost if everything goes according to plan.
PV tracks plan adherence. It shows how much value you planned to earn by a specific point in time.
EAC forecasts final cost. It uses actual performance data to predict where you’ll land when the project finishes.
Together, they ensure strong financial governance. BAC gives you the target, PV keeps you honest about schedule, and EAC warns you early when costs are trending off track.
If you’re managing a project without tracking all three, you’re missing critical insights that could prevent budget overruns before they escalate.
Want to dive deeper into the difference between BAC and EAC? Read our full guide: BAC vs EAC Explained.
When Does BAC Change?
BAC should remain fixed during project execution, but there are cases when it needs adjustment.
Stability is crucial. If BAC shifts constantly, you lose the ability to measure true cost performance or compare planned versus actual results meaningfully.
BAC changes only when:
- Scope increases or decreases significantly through approved change requests.
- Major assumptions in cost estimation prove inaccurate and require formal rebaselining.
- Contractual amendments alter deliverables or budget allocations.
Each BAC revision must follow change control procedures to maintain traceability and cost integrity. Document the reason, approval authority, and impact on performance metrics.
Frequent changes indicate issues with original estimates or scope management. If your BAC shifts multiple times, it’s worth revisiting your estimating process and stakeholder alignment before the next project.
BAC and PMP Exam Preparation
BAC is a common topic on the PMP exam, forming the basis for several cost management questions.
You’ll see it referenced in scenarios involving earned value calculations, cost forecasting, and variance analysis. Understanding BAC isn’t optional if you want to pass confidently.
Key exam takeaways:
BAC represents the total approved project budget. It’s set during the Determine Budget process and remains your cost baseline throughout execution.
It supports Earned Value formulas, such as:
- CPI = EV ÷ AC
- EAC = BAC ÷ CPI (when future performance is expected to match current trends)
BAC changes require formal scope control. Any revision must go through integrated change control and be documented in the cost management plan.
Exam Tip: Questions often present partial project data. You’ll need to identify which metric is being referenced: BAC, PV, or EAC. Look for clues like “original approved budget” (BAC) or “forecasted total cost” (EAC).
Understanding BAC helps you predict final costs and interpret earned value results quickly. It’s foundational knowledge that supports broader cost control competency on the exam and in practice.
Learn more about Earned Value Management metrics: Earned Value Metrics Explained.
FAQs
Is BAC the same as project budget?
Yes, BAC represents the approved cost baseline for all authorized project work. It’s the total budget you’ve committed to spending if the project executes according to plan.
Does BAC include management reserves?
No. BAC includes contingency reserves (funds allocated for identified risks) but excludes management reserves. Management reserves are controlled by senior management and released only when unforeseen events occur that weren’t part of the original risk assessment.
Can BAC change mid-project?
Yes, but only through formal change control. If approved scope changes increase or decrease the work, your BAC must be rebaselined to reflect the new total. Simply going over budget doesn’t change BAC. The original figure stays intact so you can measure true cost variance against what was planned.
Is BAC part of Earned Value Management?
Yes. BAC is foundational to EVM. It’s used in nearly every earned value calculation, including Cost Performance Index (CPI), Schedule Performance Index (SPI), Estimate at Completion (EAC), and variance analysis formulas.
What’s the difference between BAC and contingency reserve?
BAC is the total approved budget. Contingency reserve is a portion of that budget set aside for known risks identified during risk planning.
Think of contingency as built into BAC, while management reserve sits outside it. If you have a $100,000 BAC with a $10,000 contingency, that contingency is already part of the $100,000.
How does BAC relate to the cost baseline?
BAC and the cost baseline are closely related but not identical. The cost baseline is the time-phased version of your approved budget, showing when costs will be incurred. BAC is the total sum of that baseline.
The baseline helps with cash flow planning, while BAC helps with overall cost performance tracking.
What happens if my actual costs exceed BAC?
Exceeding BAC doesn’t change the BAC itself. It signals a cost overrun. You’ll calculate a new Estimate at Completion (EAC) to forecast your final cost, and that EAC will be higher than your original BAC.
This variance triggers corrective actions, stakeholder communication, and potentially a formal change request if scope adjustments are needed.
Do I need to track BAC if I’m using Agile methods?
Yes, though it may look different. Even in Agile projects, you typically have a total approved budget for the initiative or release. That’s your BAC.
You might track it at the epic or release level rather than for detailed tasks, but the principle remains: you need a financial baseline to measure performance and forecast outcomes.
Interactive BAC Calculator
Calculate your Budget at Completion instantly. Enter your project cost estimates below, and the calculator will compute your BAC baseline. You can run multiple scenarios and download your results as a formatted report.
Launch BAC Calculator →Conclusion
The Budget at Completion (BAC) is your project’s financial anchor. It defines how much the project should cost and serves as the benchmark for EVM tracking.
When used alongside EAC, EV, and CPI, it enables precise forecasting and proactive cost control. You catch overruns early, justify adjustments with data, and keep stakeholders informed with credible numbers.
Use the interactive BAC calculator below to simplify your next project’s budgeting and forecasting. Run scenarios, compare outcomes, and download your results for reporting.
Understanding BAC isn’t just PMP theory. It’s practical project control in action, and it works when you apply it consistently.
![Tuyota Manuwa [SAFe, CSM, PSM, Agile PM, PRINCE2]](https://secure.gravatar.com/avatar/db5d7f9dcb30834fa1a2233afd2599baed692852fbfb7acddda0272c1a52bb7c?s=120&d=mm&r=g)
