Images are reused AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
Project management BAC means budget at completion: the total approved budget for the defined scope when the project is complete. PMI’s earned-value guidance distinguishes BAC from actual cost and forecast cost. For a freelancer, that distinction prevents the original budget from being rewritten every time the latest estimate changes. The baseline explains what was authorized; the forecast explains what currently appears likely.
Keep the approved scope attached to the number
A budget is meaningful only alongside its scope, assumptions and approval date. Record included work packages, relevant contingency and exclusions. If new work is approved, follow the budget-change process and retain the earlier baseline. Do not compare today’s larger scope with yesterday’s smaller budget as though the underlying work were identical.
Distinguish cost, price and forecast
BAC is a project-budget concept, not automatically the amount charged to the client or cash remaining in the bank. Actual cost records incurred project cost according to the chosen accounting approach. Estimate at completion forecasts the total cost of finishing. Mixing a sales price with an internal cost baseline makes a performance comparison misleading.
Use earned value only with reliable progress evidence
Earned-value analysis requires a defined budget and a defensible measure of completed work. A subjective statement that a project feels half finished is weak evidence. For small engagements, a simpler work-package review may be more useful than a formal model. Do not use precise ratios to disguise uncertain progress or incomplete cost records.
A practical checklist
- Record the approved scope and BAC date.
- Separate internal cost from client price.
- Retain actual-cost evidence consistently.
- Forecast remaining work separately.
- Approve baseline changes and keep their history.
Worked example
Illustrative example: the approved project cost budget is $4,000. The team later forecasts that completion will cost $4,500. BAC remains $4,000 unless an authorized baseline change is made; the $4,500 figure is the forecast. The difference is a $500 expected overrun against the original scope, not proof that $4,500 has already been spent.
Common questions
Is BAC the money left to spend? No. Does every project need earned-value analysis? No. Can the baseline change? Yes, with appropriate approval and history. Is a forecast a guarantee? No; its assumptions and uncertainty should remain visible.
What to do next
Use the terms consistently in client and internal reports. When presenting a variance, name the scope and baseline being compared. A clear explanation of the numbers supports better decisions than a dashboard that silently mixes budgets, invoices and actual costs.