Budget vs Actual Template: Free Download, Sections and How to Use It

What is a budget vs actual template?

A budget vs actual template is a repeatable report for comparing what was authorized or planned with what has actually been incurred. It can be as simple as a spreadsheet, but a useful project version also shows the future: open commitments, remaining work, and expected final cost. Its purpose is not to prove that a team spent exactly the plan. Its purpose is to reveal differences early enough to make a decision.

The phrase “actual versus budget” is used in more than one way. Finance teams often compare actual expense with a period budget. Earned Value Management (EVM) compares actual cost with the budgeted value of work actually performed. These answer different questions. A period budget comparison says whether spending is above or below the timed plan. EVM cost variance says whether the completed work cost more or less than the budgeted value of that work. Label the method you use so readers do not confuse the two.

A report should identify its status date, currency, project, cost baseline version, and owner. Without these, two correct reports can disagree because they cover different cut-off dates, exchange rates, scopes, or approved changes. Keep the approved budget stable for performance measurement; update the forecast when evidence changes. If scope or funding is formally approved to change, document the new baseline version rather than silently rewriting history.

What should a project budget vs actual template include?

Use rows that align with your work breakdown structure or cost accounts, and columns that distinguish past cost from future exposure. The right level of detail is the lowest level at which someone can take action. If software licences are managed by one owner and one supplier, separate them from general overhead; if an individual office-supply line has no decision value, roll it up.

A template should also include a header for project name, sponsor, report period, status date, currency, baseline version, and approval/change reference. If the project has multiple currencies, show the source currency and the conversion rate/date as well as the reporting currency. Do not mix tax-inclusive and tax-exclusive amounts in different rows.

Which costs belong in the categories?

Choose categories that reflect how the project consumes resources and how managers can respond. Typical lines include internal labor, contractors, materials, equipment, software and licences, travel, training, testing, implementation, vendor services, facilities, and contingency. Add taxes, duties, shipping, currency exposure, or financing only if they are relevant to the approved project budget and your reporting convention.

For labor, document the rate basis: actual payroll cost, a standard loaded rate, or a contractual rate. Include hours as a useful diagnostic column when labor is a significant driver. For materials, separate quantity and unit price when possible. A single “materials over budget” total does not tell the buyer whether the cause was more units, a supplier price increase, expedited freight, or waste. For contractors, distinguish contracted fees, approved change orders, and unapproved claims instead of blending them together.

Contingency is not a generic plug to make the totals reconcile. Keep it visible, document what risks it covers, and follow the organization’s approval rules when drawing it down. Management reserve, when used, may sit outside the performance baseline; do not include it in a cost variance denominator unless your governance explicitly defines that treatment. Consistency and clear labels matter more than a universal spreadsheet layout.

How do you calculate variance in the template?

First choose and label a sign convention. In this guide, spending variance = actual cost − budget. Positive means unfavorable (overspend); negative means favorable (underspend). Some finance reports reverse the subtraction so a positive result means favorable. Either convention can work, but mixing them across tabs or periods guarantees confusion.

For a period comparison, calculate the difference and, where useful, the percentage:

• Variance ($) = actual cost − period budget
• Variance (%) = (actual cost − period budget) ÷ period budget × 100

If a category has a $12,000 period budget and actual cost of $14,400, the variance is $2,400 unfavorable, or $2,400 ÷ $12,000 = 20% over plan. If the budget is zero, do not divide by zero or show a fake percentage; report the dollar amount and explain that the line was unbudgeted.

Period and cumulative views should both be visible. A project can be $3,000 over in the current month but $8,000 under cumulatively because it was previously ahead of plan. Conversely, a month that appears under budget may only reflect an invoice timing gap. Always compare like with like: same scope, cut-off date, cost basis, and baseline version.

Is actual less budget the same as earned value cost variance?

No. For EVM, cost variance (CV) = earned value (EV) − actual cost (AC), and cost performance index (CPI) = EV ÷ AC. EV is the baseline value of completed work, not cash paid or the amount spent. CV above zero means the completed work cost less than its budgeted value; below zero means it cost more. If no reliable progress measurement exists, do not invent EV just to make an EVM ratio.

Consider a work package with an approved budget of $30,000. If only 60% is genuinely complete, EV is $18,000. If actual cost is $21,000, EVM CV is $18,000 − $21,000 = −$3,000 and CPI is $18,000 ÷ $21,000 = 0.857. The team has incurred $21,000, which is 70% of the package budget, but earned only 60% of the planned work value. A simple “actual spend is under $30,000” status would miss the unfavorable performance signal.

Use period-budget variance for a ledger-centered spending report. Use EVM cost variance when you have a time-phased baseline and defensible progress rules. You may show both, but give them different labels. PMI’s EVM guidance defines EV, AC, CV and CPI as distinct measures; the underlying lesson is straightforward: money spent, money planned by date, and budgeted value of work completed are not interchangeable.

How do you separate actual cost from committed cost?

Actual cost is incurred cost: work performed, goods received, or services used by the status date, recorded according to your accounting policy. A supplier invoice may arrive later, so an accrual may be needed for delivered work not yet billed. A cash payment can occur before the work is performed, such as a deposit; that payment is not automatically the same as cost incurred for progress measurement.

A commitment is an obligation created by an approved purchase order, signed contract, or similar agreement that has not yet become actual cost. Keep it separate from actuals so the team can see both what has happened and what is already contractually spoken for. The remaining commitment is not necessarily the full original purchase order: subtract amounts already incurred or invoiced, and include approved changes consistently.

The main trap is double counting. If your ETC already includes the remaining value of a signed contractor agreement, do not add the open commitment again on top. Choose one of two clear forecast methods:

1. Actual + remaining commitment + uncommitted ETC: use this when the ETC explicitly excludes the open commitments.
2. Actual + total ETC: use this when the ETC is a complete forecast of all remaining work, including commitments.

Write the definition next to the column. A forecast formula is only as reliable as the boundary between its inputs.

How do you build a filled budget vs actual report?

The following fictional example uses a six-month software implementation with a $120,000 approved baseline. It is the end of month four. The team has reviewed labor hours, supplier delivery, invoices, accruals, and the remaining work with each cost owner. Amounts are illustrative, not a benchmark.

The forecast formula is EAC = actual to date + open commitment + ETC excluding commitment. For contractors, that is $18,000 + $6,000 + $5,000 = $29,000. At project level, $67,000 + $11,000 + $40,000 = $118,000. The forecast is $2,000 below the baseline, but the line-level view still shows labor and migration pressure. A favorable total does not mean every work package is healthy.

The example’s $67,000 actual is not directly comparable with the full $120,000 baseline unless the report also shows time-phased planned value or work progress. If the schedule called for $80,000 of work value by month four, spending $67,000 could indicate lower spend than planned, but it could also mean the project is late. The status report should add planned value and earned value if schedule performance matters.

What does the variance say, and what action follows?

A useful variance note is a short causal statement, not “over budget; monitor.” For internal labor, the $46,000 EAC is $4,000 above the $42,000 line budget because two review cycles were added after requirements clarification. The owner can estimate whether remaining work will require all 15,000 dollars and ask the sponsor whether the extra review scope is approved. For migration/testing, the forecast is $1,000 over because the source data needs more cleanup; the action might be to validate the sample before the full migration rather than simply assign more hours.

The software line is $1,000 under forecast because a planned licence tier is not needed. Confirm that the lower tier still supports the required users and security controls; otherwise the “saving” may become a later change. Contingency remains visible at $7,000 forecast, rather than being spread invisibly across categories. If a listed risk occurs, the owner records the drawdown and the reason. If it does not occur, the remaining amount is not automatically spendable.

The decision record should capture: the cause, whether it is one-time or recurring, the scope affected, the proposed response, the decision maker, and the date to check the result. This turns the table into a control tool instead of a monthly collection of colors.

How do you forecast the cost at completion?

Estimate at completion (EAC) = actual cost to date (AC) + estimate to complete (ETC). This is the most practical relationship because the team can build ETC from remaining tasks, known rates, contracts, and risk exposure. EAC is the current estimate of the final total, not a promise and not the same as the approved budget. Variance at completion (VAC) = budget at completion (BAC) − EAC; with this convention, a negative VAC is a forecast overrun.

For EVM projects, common forecast methods include EAC = BAC ÷ CPI when current cost efficiency is expected to continue, and a bottom-up ETC when remaining work differs materially from completed work or the baseline is no longer credible. Do not select a formula simply because it is available in a spreadsheet. Explain the assumption and compare the result with a work-package estimate. Forecasts should change when facts change; the approved baseline should change only through formal authorization.

In the filled example, if the implementation BAC is $120,000 and the refreshed EAC is $118,000, VAC = $120,000 − $118,000 = $2,000 favorable. That is a forecast difference, not cash available to spend. The remaining budget may be needed for unplanned but authorized scope, and contingency is governed by its own rules. If a key vendor contract is signed for $16,000 instead of the $11,000 now forecast for migration and testing, update EAC to reflect that known obligation before the next committee meeting.

Use a bottom-up ETC when the cause of prior variance is temporary or the remaining work has a different cost profile. Use a performance-based EAC when historical efficiency is likely to persist. For high uncertainty, present a range with assumptions rather than a single number that implies more certainty than the evidence supports. GAO’s Cost Estimating and Assessment Guide emphasizes documenting assumptions, risk and uncertainty, updating estimates with actual costs, and linking contingency to analyzed risk; for a small internal project, a simple risk register and low/base/high estimate can apply the same discipline without simulation software.

How should contingency and changes appear?

Contingency should be connected to identified uncertainty and governed by a named decision owner. The table can show the approved reserve, amount drawn, remaining reserve, associated risk, and approval reference. Avoid adding a blanket contingency percentage to every line while also retaining a central contingency pool; that can hide duplicated protection.

Separate three events in the report: a risk occurs and contingency is used; scope changes through approval and the baseline is revised; or a cost overrun happens without approved scope change. The first may use reserve under existing authority. The second may update both budget and baseline after approval. The third is a variance and should not be erased by changing the baseline. Organizations differ in whether contingency is placed inside the performance baseline, so record your organization’s convention and do not casually compare values built on different definitions.

For example, suppose a $5,000 contingency item covers a documented data-conversion risk. If the risk occurs and costs $3,200, record the drawdown and leave $1,800 available for that risk. If the project also receives a new feature request estimated at $4,000, that request is not automatically a contingency draw: it is new scope and needs the appropriate approval. The distinction protects both the project manager and the sponsor from treating every cost pressure as an unforeseeable event.

How often should you update the template?

Set a regular cadence that matches the speed and materiality of the work. Monthly is practical for many projects; weekly or per sprint may be appropriate when costs and decisions move quickly. Stable, low-spend work may need less frequent detailed reporting, while a construction package with long-lead orders may need weekly commitment review even if the ledger closes monthly.

At every status date, freeze the cut-off, reconcile actuals with finance, capture accruals, refresh commitments, validate progress, update ETC, calculate EAC, and write explanations for material changes. Use event triggers between cycles: a signed contract above threshold, a schedule slip that extends labor or facilities, a failed test requiring rework, a scope change, a resource-rate change, or a forecast crossing the sponsor’s tolerance.

A concise monthly review can follow this sequence:

1. Reconcile actuals: compare the project cost ledger with finance and investigate uncoded or duplicate items.
2. Refresh commitments: check open purchase orders, contract balances, pending claims, and delivery status.
3. Confirm progress: ask work-package owners for evidence of completed work, not only confidence percentages.
4. Explain exceptions: identify price, quantity, productivity, mix, rework, schedule, or timing effects.
5. Reforecast: estimate remaining authorized work and avoid double counting commitments.
6. Decide and assign: approve a response, reserve use, or change request with an owner and due date.
7. Carry forward: at the next status date, check whether the action changed the driver.

The value is in the decision loop, not the reporting frequency alone. A weekly spreadsheet nobody trusts is worse than a monthly report that is reconciled and acted upon.

What mistakes make a budget vs actual report unreliable?

• Treating underspend as success. If less work is complete, low actual cost may signal delay, not efficiency. Add progress and schedule context.
• Comparing unlike periods. Align the status date, baseline version, scope, currency, and accounting basis.
• Using invoice date as incurred date. Record accruals for work performed but not yet invoiced according to finance policy.
• Counting commitments twice. Define whether ETC includes open orders and reconcile the EAC formula accordingly.
• Changing the baseline to remove a variance. Keep approved changes traceable; do not rewrite the original plan to make performance appear better.
• Hiding reasons in traffic-light colors. State a cause, impact, action, and owner in plain language.
• Applying one formula to every cost line. A fixed-price contract, time-and-materials work, and recurring subscription have different forecast evidence.
• Treating a favorable variance as money available. Savings may be temporary or required elsewhere in scope; spending authority comes from governance, not a green cell.

The most useful template is not the one with the most columns. It is the smallest report that preserves the distinctions your decisions require. If users cannot update a field reliably, simplify it or assign a source system and owner.

Can a spreadsheet handle this, or do you need project software?

A spreadsheet works well for a small project with a stable cost structure, a few owners, and a disciplined monthly reconciliation. It is transparent, easy to tailor, and has almost no setup cost. Its weaknesses emerge when several people edit different copies, formulas are overwritten, commitments sit in email, or actual costs and task progress are maintained in separate tools. Version control and ownership matter more than the file format.

A project platform becomes useful when cost data needs to be reviewed alongside tasks, owners, dependencies, risks, and progress reports. Doitify is an all-in-one platform for project management, team management, and goal achievement: teams can organize tasks and sub-tasks, assign owners and dates, track progress, manage project finances, and review work and performance reports in a shared workspace. We build Doitify, so this is a product description, not an independent endorsement. It is not a substitute for an accounting ledger or specialist earned-value controls on a large capital program; a well-owned spreadsheet may be the better fit for a one-off project.

Whichever tool you use, maintain one authoritative version, restrict who changes approved budgets, preserve a change log, and make the status date visible. A polished dashboard cannot correct missing costs or unreliable progress data.

What should you do before sharing the report?

Run a short review before the sponsor sees the numbers. Confirm the baseline and approvals, recalculate totals independently, verify that all rows use the same currency and tax convention, and check that the EAC reconciles to actual plus remaining forecast. Ask each owner to explain material movement in a sentence. Ensure the report distinguishes actual spend variance from forecast variance and, if used, EVM cost variance.

A useful decision-ready report states not only where the project is, but what choice is needed. For example: “The forecast is $7,000 over the approved baseline because the approved requirements added two review cycles; sponsor decision by 15 June: fund the scope change or remove the additional review.” That is more useful than a red total with no proposed next step.

Before closing the period, retain the source detail behind the roll-up: time records, invoices/accrual calculations, purchase orders, progress evidence, change approvals, and the ETC assumptions. This does not mean attaching every receipt to a steering deck. It means being able to trace a material number to evidence if someone challenges it or the forecast changes next month.

Conclusion

A strong budget vs actual template does more than show whether spending is above or below plan. It separates approved budget, incurred cost, commitments, remaining work, and expected final cost; it explains each important variance and gives someone authority to act. Start with a fixed status date and a stable baseline, use a sign convention everyone understands, and keep EVM measures distinct from simple ledger comparisons.

For the sample project, $67,000 has been incurred, $11,000 remains committed, and $40,000 is forecast for remaining work, giving an $118,000 EAC against a $120,000 baseline. That single reconciliation is more decision-ready than an “actual to date” figure on its own. Copy the columns, tailor categories to your cost structure, and update the report on a cadence the team can sustain. The aim is not a perfect prediction; it is an honest early warning while the project still has choices.

Sources and further reading

• Project Management Institute, Earned Value Management: A Guide to Reading the Numbers — definitions and formulas for PV, EV, AC, CV, CPI, EAC, and related measures.
• U.S. Government Accountability Office, Cost Estimating and Assessment Guide (GAO-20-195G) — cost estimate documentation, uncertainty analysis, risk and contingency, and updating estimates with actual costs.
• Carnegie Mellon University, Project Management for Construction: Cost Control, Monitoring and Accounting — cost reporting with actuals, commitments, forecasts, and variance analysis.

If this post on budget vs actual template was helpful, you might also enjoy How to Calculate Sprint Velocity: Formula, Steps, and Best Practices and Doitify vs Asana.