Blog · Territory, capacity and quota planning · Finance and FP&A teams
Cost and schedule control compares spending, accepted progress and forecast dates for the same work packages. Follow a shared-cutoff review with export layouts, spreadsheet formulas, a worked example and checks that separate delayed work from real savings.
Cost and schedule control puts actual costs, accepted work and forecast delivery dates into one review at one reporting date. The useful question is whether the remaining work can meet the approved budget and milestones, with the resources and dependencies now known. Spending below the full budget does not answer that question.
The US Department of Energy describes earned value management as integrating cost, schedule and technical scope. That same discipline helps a business running a simpler workbook: match the scope first, then read the financial and delivery evidence together.
Start with the approved work-package list. Each package needs a project code, package code, budget, baseline finish date and accountable owner. Preserve the baseline version; a revised finish forecast should not replace the original commitment.
Bring four dated exports to the review:
| File | Required fields | What the owner confirms |
|---|---|---|
| Budget | Project, package, approved budget, baseline version | Scope and approved changes |
| Cost | Project, package, posting date, amount, document ID | Posted costs and required accruals |
| Progress | Package, planned units, accepted units, evidence date | Units meet the agreed acceptance rule |
| Schedule and remaining estimate | Package, baseline finish, forecast finish, remaining cost | Dependencies and current delivery assumptions |
Use a single reporting cutoff, such as October 16, 2026. Include costs incurred through that date under finance's reporting policy, and progress accepted through the same date. Ask owners to identify incomplete submissions rather than filling missing estimates with zero.
Compare packages before rolling them up. Drawings, installed stations and accepted tests are different units; adding their counts would create a meaningless progress total. If the organization uses budget-weighted progress, the separate CPI and SPI guide owns those definitions and calculations.
Create a sheet with these columns: A package, B approved budget, C actual cost, D remaining cost, E forecast total, F forecast overrun, G baseline finish, H forecast finish and I calendar-day slippage. Store dates as dates, not text.
Enter these formulas in E2, F2 and I2, respectively, and fill down:
=C2+D2
=E2-B2
=H2-G2
Positive F means a forecast overrun; positive I means a later finish. Calendar days measure the date difference, not additional working days or a direct cost entitlement.
To populate actuals, suppose Costs has posting date in A, project in B, package in C and signed cost in D. Put the selected project in K1 and cutoff in K2:
=SUMIFS(Costs!$D$2:$D$10000,Costs!$B$2:$B$10000,$K$1,Costs!$C$2:$C$10000,$A2,Costs!$A$2:$A$10000,"<="&$K$2)
Microsoft documents SUMIFS as summing values that satisfy multiple criteria. Extend every range to cover the export, and keep its ranges the same size. Covirage is not affiliated with Microsoft.
The remaining estimate must include the full expected future cost. If it already includes open purchase orders, do not add those orders again. Keep accrual reversals and corresponding invoices on a consistent basis so the cost export does not count both.
A US distributor is changing its warehouse layout. Its reporting cutoff is October 16, 2026, and all amounts below are USD. The approved budgets and current remaining estimates cover the same scope, including expected support through the forecast finish.
| Package | Budget (USD) | Actual (USD) | Remaining (USD) | Forecast total (USD) | Overrun / (saving) (USD) |
|---|---|---|---|---|---|
| Design | 200,000 | 190,000 | 0 | 190,000 | -10,000 |
| Installation | 400,000 | 205,000 | 230,000 | 435,000 | 35,000 |
| Testing | 150,000 | 65,000 | 95,000 | 160,000 | 10,000 |
| Total | 750,000 | 460,000 | 325,000 | 785,000 | 35,000 |
The financial check is 460,000 + 325,000 = $785,000. The package variances also reconcile: -10,000 + 35,000 + 10,000 = $35,000. The forecast overrun is 35,000 / 750,000 = 4.7%, rounded to one decimal place.
Now put delivery evidence beside those amounts:
| Package | Planned accepted units at cutoff | Actual accepted units | Baseline finish | Forecast finish | Slippage, calendar days |
|---|---|---|---|---|---|
| Design | 20 drawings | 20 drawings | October 16, 2026 | October 16, 2026 | 0 |
| Installation | 60 of 100 stations | 50 of 100 stations | November 6, 2026 | November 13, 2026 | 7 |
| Testing | 10 of 40 tests | 4 of 40 tests | November 20, 2026 | December 4, 2026 | 14 |
Installation has accepted 50 / 100 = 50% of its scope against 60 / 100 = 60% planned. Testing has accepted 4 / 40 = 10% against 10 / 40 = 25% planned. These percentages describe physical acceptance, not the share of budget spent.
The project has spent less than its full approved budget because substantial work remains. It still forecasts an overrun, and testing finishes late. The design saving does not resolve the installation handoff or testing sequence.
Ask the installation owner to explain the remaining quantities, rates and crew availability behind the estimate. Ask the scheduler which installation activities release testing and whether testing can start in accepted areas. Require the testing owner to confirm that the remaining estimate covers the revised sequence.
Compare a recovery option with the current forecast using the same scope. List added labor, equipment and supervision costs, any removed extension costs, the revised dates and evidence for those assumptions. Do not multiply a delay by a daily rate unless that rate represents a cost the delay actually changes.
Record the selected response, its owner, decision deadline and expected effect. Keep an unapproved recovery proposal separate from the adopted forecast. At the next review, verify whether the promised handoff happened and whether the forecast moved for the stated reason.
For job-cost coding and commitments on building projects, use construction cost management. For other budget decisions illustrated through specific operating cases, see cost control examples.
Bring your budget, cost export and supplied progress and schedule files; Covirage maps the columns, and its tools compute and check the financial comparisons while the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data; creating the account takes about a minute.
See project cost control for the supporting file-based review.
The project manager owns the combined delivery response. Finance verifies costs and forecast assumptions, the scheduler maintains dependencies and forecast dates, and work-package owners provide completion evidence. A sponsor decides changes that exceed the authority delegated to the project team.
No. Spending can be low because work has slipped, invoices are missing or purchases have been postponed. Check accepted progress and the remaining cost estimate before calling a gap to the full project budget a saving.
No. An index summarizes progress using budgeted work, while a finish forecast depends on activity durations, dependencies and available resources. Keep critical milestone dates and their supporting schedule beside financial measures so a favorable total does not hide a late handoff.
Choose a cadence that matches reporting availability and delivery risk. Use a shared cutoff for the formal review, then escalate material changes between reviews. Label later information separately so a current schedule is not silently compared with an older cost file.