Defense Market Playbook, Part 4: Post-Award Execution — EVM, Milestone Reviews, and Sustainment

Parts 1-3 walked the path from buyer-discovery through RFP capture to pricing and compliance posture. Part 4 closes the series with what happens after the award letter arrives — the contract-execution discipline that determines whether a programme finishes on schedule, on budget, and with a past-performance record that wins the next bid. Earned Value Management, milestone-review survival, engineering-change-proposal workflow, configuration-management discipline, CPARS ratings, sustainment-contract growth, and the lessons-learned cycle that closes one contract while feeding the next capture.

The pillar framing is in The Complete Guide to Defense Procurement; the prior bid-to-award arc is in From RFP to Contract.

Step 1: From Award to Kick-off

The award letter is not the finish line — it is the start of the 90-day window that shapes the rest of the programme. Vendors who treat award as victory and slow down in the first quarter spend the next two years recovering. Vendors who hit the ground sprinting in week one set a baseline that compounds through the contract's life.

The first-90-days discipline:

Contract baseline lock-in. The technical baseline, cost baseline, and schedule baseline are signed, version-controlled, and distributed to every stakeholder. Ambiguities in the contract language are surfaced to the contracting officer and resolved in writing — never deferred. The baseline is the contract's truth; everything later is measured against it.

Integrated Baseline Review (IBR). For programmes above the EVM threshold, the IBR is the formal government review of the integrated cost-schedule baseline within roughly 90-180 days of award. The IBR validates that the baseline is realistic, achievable, and properly resourced. A failed IBR triggers re-planning; a passed IBR sets the measurement framework for the rest of the programme.

Team mobilization. The capture team rolls off; the execution team rolls on. The handover is structural — capture-phase decisions, customer-relationship history, technical commitments, risk register — all transfer in writing, not in hallway conversation. A programme that loses capture knowledge at handover loses six months relitigating decisions already made.

Security-clearance staging. For classified work, clearance processing is the long pole. Engineers without cleared status cannot touch classified code, attend classified meetings, or enter cleared facilities. Clearance applications submitted on day one finish processing in months four-to-nine; engineers held back by clearance delays cost real schedule. See Security Clearance for Software Teams.

Classified workspace setup. SCIFs, cleared development environments, classified-network connectivity, accreditation of the engineering environment itself — these have lead times measured in months. The programme that plans for them in week one has them by month four; the programme that defers them adds them to the critical path later.

Step 2: Earned Value Management (EVM)

EVM is the cost-and-schedule discipline that government buyers use to measure programme health quantitatively. It is mandatory above contract-value thresholds (ANSI/EIA-748 compliance is typically required above roughly $20M cost-reimbursable, with national variations) and recommended below them as a management discipline regardless of mandate.

The three metrics that drive everything:

BCWS (Budgeted Cost of Work Scheduled) — the plan. What the programme planned to spend by this date, accumulated across the work-breakdown structure. The time-phased baseline.

BCWP (Budgeted Cost of Work Performed) — the earned value. The budget value of the work actually completed, measured against the same baseline. Completed work earns its budgeted value regardless of what it cost.

ACWP (Actual Cost of Work Performed) — the spend. What the programme has actually paid for the work performed.

From these three, the two indices buyers read first:

CPI = BCWP / ACWP (Cost Performance Index). Above 1.0 means under budget; below 1.0 means cost overrun. CPI below 0.9 sustained across reporting periods triggers contracting-officer attention. CPI below 0.8 triggers re-baseline conversations.

SPI = BCWP / BCWS (Schedule Performance Index). Above 1.0 means ahead of schedule; below 1.0 means behind. SPI below 0.9 triggers schedule-recovery planning.

The reporting cadence that buyers actually read: monthly Cost/Schedule Status Report (CSSR) or Integrated Program Management Report (IPMR), with variance explanations for any element trending outside threshold. Buyers do not read the numbers in isolation — they read the trendlines and the credibility of the variance explanations. A CPI of 0.92 with a coherent recovery plan reads better than a CPI of 0.98 with no narrative.

When EVM is genuinely optional (firm-fixed-price below threshold, time-and-materials at small value), running it internally anyway is the right call. The discipline itself catches problems early; the data is invaluable in claim or termination scenarios.

Step 3: Milestone Reviews — Surviving PDR, CDR, TRR

Defense programmes have formal technical reviews where the government decides whether to authorize continued work. The three that matter most for software-heavy programmes:

Preliminary Design Review (PDR). The architecture is presented for government scrutiny — major interfaces, major design decisions, major risk areas. The government decides whether the preliminary design is mature enough to authorize detailed design. Required artefacts: system specification, interface control documents, preliminary design documentation, risk register, requirements-traceability matrix.

Critical Design Review (CDR). The detailed design is presented before fabrication or full-scale coding. The government decides whether the design is mature enough to authorize build/code. Required artefacts: detailed design documents, interface specifications updated, test plans, configuration baseline, all PDR action items closed.

Test Readiness Review (TRR). The system is presented as ready for formal qualification testing. The government decides whether to authorize the test campaign. Required artefacts: test plans, test procedures, test environment readiness, prior test results, exit criteria.

What review-board criticism actually means: review-board members are paid to find problems. Finding zero problems means the board did not do its job. Vendors who treat every action item as a defeat exhaust themselves; vendors who treat the action items as the board's contribution to programme quality close them efficiently and move on.

When to push back versus when to fold: push back when the board's criticism rests on a misunderstanding of the design — present clarifying material and request reconsideration. Fold when the criticism identifies a real gap, even if it costs schedule or rework. Pushing back on real gaps converts them into discovery items later, at higher cost.

Step 4: Engineering Change Proposals (ECP)

Every long-running programme experiences change — emerging requirements, technology refresh, threat evolution, scope discoveries. The contractual mechanism that handles change is the Engineering Change Proposal.

Class I ECPs affect the contract baseline — cost, schedule, or contracted performance. They require formal contract modification, government approval, and (typically) negotiation on price and schedule impact. Class I ECPs are revenue events for the contractor; they also expand exposure if the price is wrong.

Class II ECPs are internal — they change implementation details that do not affect contracted performance, cost, or schedule. They require configuration-control-board approval but not contract modification. Class II ECPs keep programmes nimble.

The change-control board is where ECPs are evaluated. The board includes engineering, programme management, contracts, quality assurance, and (for Class I) the government's representative. The board's discipline is what keeps scope creep from destroying margins on one side and what protects vendors from doing uncompensated work on the other.

How to scope ECPs to add revenue without triggering buyer concerns: tie every ECP to a documented requirement source — a customer request, a threat update, a test finding. ECPs sourced from contractor convenience read as scope-padding; ECPs sourced from customer need read as professional response to evolving demand. The wording on the cover sheet matters.

Step 5: Configuration Management at Contract-Grade

Configuration management (CM) discipline aligned with MIL-STD-973 or ISO 10007 is the spine of any long-running defense programme. CM that exists only as a buzzword fails the first audit; CM as engineering practice survives the contract's lifetime.

The disciplines:

Baseline lock. Three baselines exist concurrently — functional (allocated to system specs), allocated (broken down to subsystem specs), and product (the as-built configuration). Each is version-controlled and audit-traceable.

Change-impact analysis. Every proposed change is analyzed for impact across the affected baselines. A change to a subsystem spec triggers impact analysis on every dependent test, document, and interface.

Traceability from requirement to delivery. Every contracted requirement traces forward to the design element that implements it, the test that verifies it, and the delivery artefact that demonstrates it. Audits that find broken traceability find systemic CM failure.

Configuration audits — Functional and Physical. FCA verifies that the system performs to the allocated baseline; PCA verifies that the delivered product matches the documented product baseline. Both are formal government audits; both have failure modes that cost months.

Step 6: Past Performance Building

The past-performance record built during execution is the single most important asset for the next bid. In the U.S., the formal record is CPARS (Contractor Performance Assessment Reporting System); other nations have analogous systems. The CPARS ratings drive past-performance scoring in future evaluations — sometimes weighted 25-40% of the technical evaluation.

The levers vendors actually control:

Quality of Product or Service. Does the deliverable meet specification? Is it accepted on first submission or after rework? Are defects discovered in test or in field?

Schedule. Are milestones met? When slips occur, are they communicated early with credible recovery plans?

Cost Control. CPI trends, variance management discipline, accuracy of cost forecasting.

Management. Programme manager responsiveness, problem escalation discipline, customer-relationship quality.

Small Business / Subcontracting / Regulatory. Compliance with subcontracting plans, small-business goals, regulatory obligations.

Step 7: Sustainment and Growth Paths

The contract that delivers the platform is rarely the contract that pays the bills. Sustainment — the multi-decade operations, maintenance, upgrade, and refresh phase — typically represents 60-80% of a system's lifetime cost. Vendors who position for sustainment from day one ride the flywheel; vendors who do not lose the sustainment work to incumbents.

The growth paths:

Performance-Based Logistics (PBL). The vendor is paid for outcomes (availability, mission readiness) rather than for parts or labour hours. PBL contracts reward vendors who reduce sustainment cost — strong incentive alignment.

Contractor Logistics Support (CLS). The vendor provides defined logistics services — repair, supply, training, technical assistance — under a sustainment contract structure.

IDIQ task orders. Indefinite-Delivery, Indefinite-Quantity contracts give the government a pre-negotiated vehicle to issue task orders against. An IDIQ position is procurement-grade leverage; task orders flow without re-competition.

Follow-on solicitations. The incumbent on the current contract has structural advantages on the next one — past performance on the exact mission, deep customer relationships, sunk-cost familiarity. Losing a follow-on is more painful than losing an initial bid.

The flywheel: single contract → strong CPARS → IDIQ position → task-order stream → multi-award contract (MAC) vehicles → portfolio of programmes. Each stage compounds. Vendors stuck at single-contract level grind; vendors who reach MAC-vehicle level scale. See Battle-Tested vs Lab-Tested for the credibility flywheel that parallels this commercial one.

Step 8: Closing Out — Final Audit, Lessons Learned

The closeout phase is unglamorous and structurally important. A contract that closes cleanly preserves the past-performance record; a contract that drags through unresolved issues for years tarnishes it.

The discipline:

Incurred-cost submission. For cost-reimbursable contracts, the final indirect-cost rates and incurred-cost submission close out the financial picture. Submissions that drag into the years past the contract end-date trigger audit attention and reserve obligations.

Final invoice and payment. The final invoice is submitted with all required documentation; the government's payment closes the financial baseline.

Contract closeout package. Property accountability resolved, classified material disposed of per security plan, deliverables formally accepted, warranties documented, intellectual-property rights confirmed.

Internal lessons learned. What worked, what failed, what cost real money, what would be done differently. The lessons-learned document feeds the next capture — it is the link between this contract's experience and the next contract's bid. Vendors who skip lessons learned repeat their mistakes; vendors who institutionalize them compound their advantages.

Closing the Series — and the Library

Four parts ago this series opened with the defense buyer's organizational logic. We mapped the buyer's interlocking offices and decision rhythms. We worked the RFP/RFI mechanics from solicitation through proposal mechanics. We built the pricing and compliance posture that survives evaluation. We close here with the execution discipline that converts an award letter into a sustainment-grade business.

This article also closes a larger arc. The Corvus engineering library now spans five engineering-pillar pairs (C2 Systems, Defense Data Fusion, AI in Defense, NATO Interoperability, Defense Cybersecurity) plus this business-side pillar pair — the Complete Guide to Defense Procurement paired with this four-part Defense Market Playbook. Six pillar+series pairs, twenty-four implementation-walkthrough parts, and the surrounding engineering essays that contextualize them. The architecture of the library is complete.