Home / Aerospace and defense program execution / Front-end planning for aerospace and defense programs
The integrated baseline review is the first time the customer looks closely at how a program plans to deliver. It is not really a test of documents. It is a test of whether the people running the program understand their own plan. Programs that treat it that way usually find it straightforward.
What the review is trying to establish
The government and the contractor walk through the performance measurement baseline together. The questions are consistent from program to program:
- Does the baseline cover the entire scope of the contract, and nothing outside it?
- Is the schedule realistic, with logic that reflects how the work will really happen?
- Are the budgets and resources adequate for the work assigned to them?
- Have the technical, schedule, cost and resource risks been identified, and are they being managed?
- Are the management processes that will keep the baseline honest actually in use?
The review ends with a shared view of the baseline and a list of any findings to resolve. The real product is confidence: the customer's confidence that the plan is credible and the program team's confidence that it can execute it.
How the review usually runs
Most IBRs combine an overview of the program and its management approach with a series of discussions at the control account level. Reviewers pick control accounts, often those carrying the most budget, the most risk or the critical path, and ask the control account manager to walk through the work: what it is, how it is scheduled, how the budget was built, how progress will be measured and what could go wrong.
These discussions reveal quickly whether the baseline was built by the people doing the work. A control account manager who can explain the logic of their schedule, the basis of their estimate and their top risks without reaching for notes is the strongest evidence a program can offer.
Preparing so the review is uneventful
Start with the schedule. An integrated master schedule that passes the structural checks, shows a believable critical path and traces to the work breakdown structure removes the largest single source of findings.
Make the budgets traceable. Every control account budget should connect to a basis of estimate and to the scheduled work. Reviewers will follow the thread from contract value to control account to work package.
Choose earned value methods deliberately. Objective measures, such as weighted milestones within a work package, are easier to defend than percent complete estimates. The method should suit the work and be decided before the review, not during it.
Put the risks on the table. A risk register that is honest about the program's real exposures is more credible than one filled with generic entries. Reviewers are reassured by teams that know where the danger is.
Rehearse the control account managers. Mock interviews, run by someone who asks the questions a government reviewer will ask, are the most effective preparation there is. They expose gaps while there is still time to fix them, and they give the managers confidence walking in.
What the review is not
It is not an audit of the accounting system. System compliance is assessed separately. The IBR is about whether this program's plan is credible, and reviewers will steer away from process debates that do not touch the baseline.
It is not a pass or fail certification. The output is a shared understanding and a set of agreed actions. A review with findings that are closed promptly is a normal outcome; a review where findings linger is what damages trust.
It is not a one-time event. The baseline keeps changing as options are exercised and the contract is modified, and significant changes can bring another review. Keeping the baseline disciplined between reviews is what keeps each later one short. Programs that let the baseline drift after the first review usually find the second one much harder than the first.
What documents do reviewers usually ask for?
- The work breakdown structure and its dictionary
- The responsibility assignment matrix, linking work to control account managers
- Control account plans with budgets, work packages and earned value techniques
- The integrated master schedule and, where used, the integrated master plan
- Basis of estimate documentation for budgets and durations
- The risk and opportunity register with handling plans
- Management reserve and undistributed budget logs
- The baseline change log and change control procedure
Having these consistent with each other before the review is most of the preparation. Reviewers quickly notice when the schedule, the control account plans and the budget describe different versions of the work.
What will control account managers be asked?
Questions tend to follow the same thread: describe the scope of your control account and how it traces to the statement of work; walk through the schedule logic and what drives your key dates; explain how the budget was built and what it assumes; show how you will measure progress and why you chose that earned value technique; name your top risks and what you are doing about them; and explain how a change to your scope would be handled. Managers who built their own plans answer these easily, which is why involving them in the baseline from the start matters more than any rehearsal.
How are baseline risks rated?
Review teams commonly assess the baseline in categories such as technical, schedule, cost, resources and management processes, rating each as low, moderate or high risk and recording the reasons. The ratings are not a grade; they are a shared view of where the baseline is most likely to break, and they should flow straight into the program's risk register and handling plans.
What happens after the review?
Findings and action items are recorded and agreed with the program office, each with an owner and a date. Closing them promptly, and showing the evidence, matters as much as the review itself, because it demonstrates that the baseline is actively managed. The risks the review identified should move straight into the program's risk register, and the change control process agreed for the baseline should be used from the first change onward.
What is actually in the performance measurement baseline?
The performance measurement baseline is the time-phased budget plan that progress will be measured against for the life of the contract. It is built from a small set of parts, and reviewers check each one. Knowing what they look for in each part is the fastest way to find your own gaps first.
| Part | What it is | What reviewers check |
|---|---|---|
| Contract budget base | The negotiated contract cost plus the estimated cost of any authorized but unpriced work | That the baseline plus management reserve adds up to it, with no unexplained difference |
| Control accounts | The points where scope, schedule and budget meet, each owned by one control account manager and each collecting actual cost | That every piece of contract scope sits in exactly one control account, and that the manager owns it in practice |
| Work packages | Near-term tasks with their own budget, start and finish dates and an earned value technique | That dates match the integrated master schedule and that the technique measures real progress |
| Planning packages | Later work inside a control account that has a budget but is not yet planned in detail | That there is a clear plan to convert them to work packages before the work starts |
| Summary level planning packages | Far-term work that has not yet been assigned to control accounts | That they are time-phased, tied to scope, and will be distributed as the work gets closer |
| Undistributed budget | Budget for authorized scope that has not yet been assigned to a control account | That it is temporary, logged, and distributed promptly rather than parked |
| Management reserve | Budget held outside the baseline for work within scope that cannot yet be identified | That it is controlled through a log and not used to hide overruns or fund out-of-scope requests |
If the numbers do not reconcile from the contract budget base down to the work packages, that is usually the first finding. It is also the easiest one to prevent, because the reconciliation can be done well before reviewers arrive. The EIA-748 guidelines describe how these parts are meant to work together.
Which findings come up most often, and how do you prevent them?
Most findings fall into a handful of patterns. None of them are exotic, and almost all of them come from a baseline that was assembled for the review rather than built to run the program.
| Common finding | What reviewers see | How to prevent it |
|---|---|---|
| Schedule and budget out of step | Control account budgets spread over months that do not match the dates in the schedule | Time-phase budgets directly from the integrated master schedule, not from a separate spreadsheet |
| Scope gaps or extra scope | Statement of work tasks with no home in the work breakdown structure, or baseline work the contract does not require | Trace every statement of work paragraph to a WBS element before budgets are set |
| Too much level of effort | Measurable work planned as level of effort, so progress is reported as earned simply because time passed | Reserve level of effort for genuine support work and use discrete methods for anything with a product |
| Unsupported budgets | Control account budgets with no basis of estimate, or estimates that no one on the team can explain | Write a basis of estimate for each control account with the people who will do the work |
| Risks that live only on a list | A risk register whose handling actions do not appear in the schedule or the budget | Put funded mitigation activities into the schedule so they are planned and tracked like any other work |
| Weak schedule structure | Missing logic, hard constraints, unrealistic float and a critical path that does not make sense | Run a structural check such as the DCMA 14-point assessment and fix the schedule before the review |
| Managers who cannot explain their plan | Control account managers deferring to schedulers or analysts on basic questions about their own work | Have managers build their own plans, then rehearse with realistic questions |
Notice that the fixes are mostly about how the baseline is built, not how it is presented. A baseline built with the people doing the work, from a sound schedule, tends to survive the review without much drama.
Should you hold an internal baseline review first?
Yes. A program that runs its own baseline review before the customer does finds its problems while they are still cheap to fix. Treat it like the real thing, with someone outside the program team asking the questions.
- Read the contract first. Confirm the earned value clauses, the expected timing of the review and any data deliverables, so the internal review targets the right date and scope.
- Reconcile the numbers. Walk from the contract budget base to management reserve, undistributed budget and every control account, and explain any difference.
- Check the schedule structure. Confirm logic, constraints, float and the critical path, and confirm that every work package date matches the schedule.
- Trace scope both ways. Every statement of work requirement should land in a control account, and every control account should trace back to the contract.
- Sample control accounts the way reviewers will. Pick the ones with the most budget, the most risk or work on the critical path, and interview their managers.
- Review the risk picture. Confirm the top risks are real, owned and reflected in the schedule, not just listed.
- Close the gaps and rehearse again. Fix what the internal review found, then run a shorter second pass with the managers who struggled.
An internal review is also the best way to find out whether the program can answer the basic health questions that sit underneath every baseline. If it cannot, the baseline is the wrong place to start.
Related guides
- EVMS and EIA-748 for defense contractors
- Building an integrated master schedule that works
- Scope control and technical baseline management
- Front-end planning
How Set Boundaries prepares a program
Set Boundaries prepares programs for the IBR as part of front-end planning: building or repairing the schedule, tracing budgets to the work, tightening the risk register and running mock reviews with each control account manager. The aim is a review with few surprises because the baseline was built to be used, and a team that can explain it because they built it.
If an IBR is on the calendar and the baseline is not ready, schedule a call.
References
- US Department of Defense, Earned Value Management System Interpretation Guide (EVMSIG).
- US Department of Defense, Earned Value Management Implementation Guide (EVMIG).
- National Defense Industrial Association, Integrated Program Management Division, Integrated Baseline Review (IBR) Guide.
- SAE International and the Electronic Industries Alliance, EIA-748, Earned Value Management Systems.
- Defense Federal Acquisition Regulation Supplement, 252.234-7002, Earned Value Management System.
- US Department of Defense, DI-MGMT-81861, Integrated Program Management Data and Analysis Report (IPMDAR).
- US Government Accountability Office, Schedule Assessment Guide: Best Practices for Project Schedules, GAO-16-89G.
- US Government Accountability Office, Cost Estimating and Assessment Guide, GAO-20-195G.
Questions
Common questions
What is an integrated baseline review?
An integrated baseline review, or IBR, is a joint review by the government program office and the contractor of the performance measurement baseline. Its purpose is to reach a shared understanding that the baseline covers the full scope of work, that the schedule and resources are realistic, and that the risks are understood. It is a review of the plan, not an audit of the accounting system.
When does an IBR happen?
On contracts with earned value requirements, the IBR is generally expected within about six months of contract award, and again after the exercise of significant options or major modifications. The contract clauses set the actual timing, so check them early; teams that discover the date late usually find the preparation rushed.
What happens if the IBR goes badly?
Findings are documented and the contractor agrees corrective actions with the program office. A weak IBR rarely stops a program, but it sets the tone of the customer relationship for years and often leads to closer scrutiny of every later report. It is far cheaper to prepare properly.
Who has to take part?
The program manager and the control account managers carry most of the review, because the discussions are about their work: its scope, its schedule, its budget and its risks. Schedulers and financial analysts support them, but a review where only the support staff can answer questions is a warning sign.
What documents should be ready for an integrated baseline review?
Typically the work breakdown structure and dictionary, the responsibility assignment matrix, control account plans with budgets and earned value techniques, the integrated master schedule, basis of estimate documentation, the risk and opportunity register, management reserve and undistributed budget logs, and the baseline change log. Most of the preparation is making sure these documents are consistent with each other and describe the same work.
What questions are control account managers asked in an IBR?
Usually how their scope traces to the statement of work, what logic drives their key dates, how their budget was built, how progress will be measured and why that earned value technique was chosen, what their top risks are and what is being done about them, and how a scope change would be handled. Managers who built their own plans answer these confidently.
What is the format of an IPMDAR?
The Integrated Program Management Data and Analysis Report is defined by data item DI-MGMT-81861 and is delivered mainly as structured data rather than formatted reports. It generally has three parts: a contract performance dataset with cost and earned value data, a schedule performance dataset drawn from the integrated master schedule, and an executive summary with narrative analysis. The datasets follow a government file format specification. Set Boundaries helps programs set up schedules and control accounts early so the data behind the IPMDAR is consistent from the first submission.
What are the 32 EVMS guidelines?
The 32 guidelines come from the EIA-748 earned value management standard and are grouped into five areas: organization, which defines the work and who does it; planning, scheduling and budgeting; accounting considerations; analysis and management reports; and revisions and data maintenance. Together they describe a management system that integrates scope, schedule and cost, measures performance honestly and controls changes to the baseline. Set Boundaries uses these guidelines as a practical checklist when preparing aerospace and defense programs for an integrated baseline review.
Is EVM required on a FFP contract?
Generally no. Under DFARS policy, earned value management system requirements are generally not applied to firm-fixed-price contracts, because the contractor carries the cost risk. Applying EVM to a firm-fixed-price effort normally needs a specific justification and approval at a senior level. A customer may still ask for schedule reporting or milestone tracking on a fixed-price program. Set Boundaries recommends earned value style tracking as a management tool on large fixed-price work anyway, because it shows cost and schedule trouble early even when no one requires the report.
Have a question that is not here? Ask Holly on a short call
