Integrated Baseline Review (IBR)

An Integrated Baseline Review (IBR) is a structured, joint government-contractor review conducted early in contract performance to verify that the performance measurement baseline (PMB) is comprehensive, realistic, and sufficient to execute the full scope of work within the approved budget and schedule.

What is an Integrated Baseline Review?

DFARS 252.234-7002 mandates IBRs on contracts requiring an Earned Value Management System (EVMS). The IBR must be completed within six months of contract award or the exercise of a contract option. Its purpose is to establish mutual understanding between the contractor and the government program office about the technical, schedule, and cost assumptions underlying the Performance Measurement Baseline.

During the IBR, the contractor walks through its Work Breakdown Structure (WBS), explains how each control account is planned, and demonstrates that resources are realistically budgeted against the Integrated Master Schedule (IMS). Government reviewers evaluate whether the baseline is logically structured, whether budget and schedule assumptions are supportable, and whether risk reserves (management reserve) are adequate.

Common IBR findings include underfunded control accounts, missing work packages for scope elements, schedule logic errors that create unrealistic critical path sequences, and insufficient management reserve for identified risks. Contractors must address formal IBR findings through a risk register and corrective action process. A well-executed IBR creates shared ownership of the baseline, reducing disputes later when variances occur.

Why the IBR matters for government contractors

A rigorous IBR protects contractors as much as it protects the government. An unrealistic baseline, whether due to overly optimistic scheduling, underfunded labor, or missed scope, will produce negative variance reports almost immediately. By surfacing and resolving baseline problems early, the IBR prevents the contractor from spending months explaining variances that were baked into the plan from day one.

Example

A defense systems contractor completes an IBR six weeks after contract award on a $75M development contract. Government reviewers identify three control accounts where the budget cannot realistically cover the planned labor hours without overtime assumptions that are not documented in the schedule. The contractor revises these control accounts, documents the revised assumptions in the risk register, and rebaselines with government concurrence before performance begins in earnest.

Frequently Asked Questions

Who participates in an IBR?

IBR participants typically include the contractor's program manager, control account managers, cost account managers, and schedule analysts. Government participants include the contracting officer's representative (COR), the EVMS analyst, and technical subject matter experts. DCMA often participates for DoD contracts.

How long does an IBR typically take?

IBRs for moderately complex programs typically run two to five days, with preparation taking several weeks beforehand. Larger programs may have IBRs spread over two weeks, covering different WBS elements in sequential sessions.

Can the performance measurement baseline change after an IBR?

Yes. Baseline changes occur through formal re-planning processes documented in the EVMS. However, changes to the PMB that exceed certain thresholds require government approval and are reported as Over Target Baselines (OTBs) or Over Target Schedules (OTSs). The IBR establishes the original approved baseline from which changes are measured.

What is the difference between an IBR and a baseline review?

An IBR is specifically the joint government-contractor review of the PMB at contract inception, mandated by DFARS. A baseline review (or internal baseline review) may refer to a contractor's internal validation process before the IBR or to subsequent government surveillance reviews of baseline changes during performance.