The compliance threshold most small contractors never read carefully
Before you spend a dollar on EVM tooling, know which side of the threshold you're on. DoD requires a formally validated EVMS — one that's been audited against the EIA-748 32 guidelines — on cost-reimbursement, fixed-price-incentive, and certain other contract types at or above $20M (with full validation kicking in at $50M and above for many programs).
If your contract is a $4M FFP delivery order with a CDRL for monthly status, you do not need Deltek Costpoint. You need a process you can defend, a CAM (Control Account Manager) who knows the WBS, and reports your customer can read.
What the customer actually wants to see
For most small contracts, the PCO and PM aren't auditing your earned-value system — they're trying to answer three questions:
- Are you on schedule?
- Are you on budget?
- If you're not, what are you doing about it?
Everything you build should make those three questions cheap to answer truthfully. The metrics matter; the tool doesn't.
A minimum viable EVM setup
Here's a setup we've seen work on contracts up to roughly $15M:
1. A real WBS, locked at award
Work Breakdown Structure to level 3 or 4. Every leaf is a Work Package or Planning Package owned by exactly one CAM. Don't restructure mid-contract unless you have a contract mod that justifies it.
2. A time-phased budget (PMB)
For each Work Package: Budgeted Cost of Work Scheduled (BCWS / PV) by month. Simple is fine. A spreadsheet column per month, summed up to control accounts, summed up to the contract. The Performance Measurement Baseline is the budget you said you'd spend, when you said you'd spend it.
3. Earned value rules per Work Package
Pick one earned-value method per WP and stick with it:
- 50/50: 50% credit at start, 50% at completion. Good for short, well-defined packages.
- 0/100: 100% credit at completion only. Good for milestone-driven work.
- % Complete (with milestones): Defensible only if milestones are concrete. Avoid "engineer's judgment %."
- LOE (Level of Effort): Earned value tracks planned value automatically. Reserve this for genuine LOE work like program management or technical support — not for engineering tasks.
Mixing methods is fine. Changing methods mid-contract is a giant red flag.
4. Actuals from the books, not from the PM's gut
BCWP (earned value) and BCWS (planned value) come from the WBS. ACWP (actual cost) has to come from your accounting system. If your bookkeeper can't produce labor and material actuals tagged to a WBS code, you don't have an EVM problem — you have a chart-of-accounts problem. Fix that first.
5. Three numbers, every month
For each control account, you publish:
- SV = BCWP − BCWS (Schedule Variance)
- CV = BCWP − ACWP (Cost Variance)
- EAC = Estimate at Completion (your honest forecast for total cost)
Anything more than ±10% variance gets a one-paragraph variance analysis: what happened, why, what's the corrective action, when does it land. That paragraph is the most important artifact in your entire EVM system. Write it like you'll have to defend it — because you will.
Tools that work for this scale
You can run a competent small-contract EVM with:
- Excel or Google Sheets for the time-phased budget and monthly variance reports. Honestly fine up to a few million dollars and one or two control accounts.
- QuickBooks or Xero with WBS-coded job tracking for actuals. Tag every transaction with a WBS code at the time you book it. Don't try to allocate after the fact.
- MS Project or Smartsheet for the IMS, exporting status into the same spreadsheet that drives EVM. The IMS and the cost baseline are two views of the same truth — if they disagree, your reporting is lying to someone.
If your reports are taking more than a day a month to produce, that's the signal — not contract size — that you've outgrown the spreadsheet stack.
When to graduate to real software
Move off spreadsheets when any of these are true:
- You have more than ~5 active control accounts at once.
- You're running multiple contracts and need a portfolio view.
- Your monthly close takes more than 2 days.
- You're approaching the $20M EIA-748 threshold and need a system you can defend in a validation review.
- The CAMs are spending more time updating the spreadsheet than running their work packages.
At that point your real choices are: (a) buy something off the shelf (Deltek, Unanet, Procas, Cobra), or (b) build something tailored to how your shop actually works. Both are valid. The mistake is jumping to either before the spreadsheet has clearly broken.
The honest tradeoff
A spreadsheet-based EVM is fragile. One person leaves and the institutional knowledge walks out the door. A custom tool fixes that, but costs upfront. Off-the-shelf GovCon software fixes that and handles validation, but costs a lot upfront and pulls your processes toward how the vendor thinks you should work.
For most small Defense contractors, the right play is: run lean for as long as possible, and graduate to real software once you know exactly what you need it to do. Most enterprise rollouts fail because the company didn't yet understand its own process when it bought the tool.
Need a sanity check?
If you're running EVM in spreadsheets right now and not sure if you've outgrown them, we offer free 30-minute teardown calls for small Defense contractors. Bring your current setup — we'll tell you straight.
FAQ
Does my contract require an EIA-748-compliant EVMS?
For DoD, formal validation is generally required at $50M and above on cost-type and fixed-price-incentive contracts. Reporting is required at $20M and above. Below those thresholds, requirements are flowed down through specific contract clauses — check DFARS 234.2 and your contract's Section H/I clauses. When in doubt, ask the PCO in writing.
Can I use Microsoft Project as my EVM tool?
MS Project can produce earned-value calculations from a properly resource-loaded schedule, but it's not an accounting system. You'll still need to reconcile actual costs from your books against what Project reports. For small contracts that's a manageable monthly task; for larger ones it stops scaling.
What's the most common mistake small contractors make?
Letting the WBS drift. Someone renames a work package or splits it informally, the time-phased budget no longer matches the IMS, and three months later the variance reports are nonsense. Lock the WBS at award; require contract mods to change it.