Monthly IMS Status and Schedule Analysis Checklist

An effective IMS monthly status checklist does more than confirm that actual dates were entered. It verifies that the Integrated Master Schedule reflects current execution, produces a credible forecast and gives management a clear view of schedule risk.

The monthly review should cover the status date, actual progress, remaining durations, forecast dates, network logic, critical and near-critical paths, float trends, baseline changes, risk impacts and alignment with the Earned Value Management System (EVMS). The final result should explain what changed, why it changed, what it affects and what action management must take.

This checklist is a recommended program-controls practice. The contract, Contract Data Requirements List (CDRL), applicable data item description, schedule management plan and approved EVMS procedures determine the actual reporting frequency and required deliverables. For example, DFARS 252.234-7002, when included in a contract, requires management procedures that generate timely, reliable and verifiable information for the contract’s required schedule and performance reports. It does not establish one universal monthly checklist for every program.

IMS Monthly Status Checklist at a Glance

1. Preserve the prior-period schedule and establish the current status date.
2. Confirm calendars, reporting periods and status cutoffs.
3. Collect status from control account managers and responsible owners.
4. Enter valid actual starts, actual finishes and remaining durations.
5. Move incomplete work out of the past and resolve invalid future actuals.
6. Review out-of-sequence progress and revise logic only when execution changed.
7. Recalculate the network and run schedule health checks.
8. Trace the critical path, driving paths and near-critical paths.
9. Analyze float, milestone variance and forecast movement.
10. Review baseline changes and preserve baseline traceability.
11. Reconcile schedule status with EVMS and estimate-to-complete data.
12. Review risks, opportunities, mitigation activities and schedule margin.
13. Prepare a concise management narrative and delivery package.

1. Preserve the Prior Period Before Updating

First, save a controlled copy of the prior-period IMS. Retain its native format and any required export or reporting files. The archived version provides the reference for month-over-month comparisons.

Do not overwrite the only copy of the previous schedule. Without a prior-period file, the team cannot reliably identify logic changes, duration changes, deleted activities, forecast movement or unexplained float shifts.

• Record the file name, revision, status date and extraction date.
• Confirm that the schedule opens and calculates without errors.
• Retain relevant health-check and critical-path reports.
• Document any known corrections that will enter the new cycle.

2. Establish a Common Status Date

The status date, also called the data date or time-now date, separates completed work from remaining work. All participating schedules should use the same approved cutoff unless the program’s procedures define a controlled exception.

The Department of Energy’s EVMS Compliance Assessment Governance guidance describes a mature process in which the status date aligns with the accounting period and schedule updates follow a consistent business rhythm. This alignment supports meaningful schedule-to-cost analysis.

• Set the status date to the approved reporting-period cutoff.
• Confirm that the EVMS uses the corresponding accounting period.
• Check project, resource and subcontractor calendars.
• Verify that all schedule contributors used the same cutoff.
• Resolve late status inputs through the program’s documented process.

In Microsoft Project, explicitly set the Status Date rather than relying on the computer’s current date. Microsoft also documents functions that move completed or incomplete portions of tasks relative to the status date. However, the scheduler should review the results instead of treating a bulk reschedule command as a substitute for valid status.

3. Collect Status From the People Responsible for the Work

Next, collect status from control account managers (CAMs), integrated product team leads, subcontract managers and other responsible owners. Avoid accepting a percentage complete without supporting dates and a revised forecast.

For each active or near-term activity, request:

• Actual start or actual finish, when applicable.
• Remaining duration for work in progress.
• Expected start and finish for unstarted work in the execution window.
• The reason for any variance or changed forecast.
• New or realized risks, issues and dependencies.
• Required logic, resource or sequencing changes.
• Corrective actions and expected recovery dates.

Remaining duration deserves particular attention. Simply decrementing it by the number of elapsed workdays assumes that performance matched the prior forecast. Instead, the owner should estimate the time still required to complete the defined scope.

4. Validate Actual and Forecast Dates

After entering status, test the temporal integrity of the schedule. Completed work should fall on or before the status date, while incomplete work should remain after it.

• No actual start or actual finish should occur after the status date.
• No incomplete activity should retain an unsupported forecast finish in the past.
• An unstarted activity should not have a forecast start before the status date.
• A completed activity should have both a valid actual start and actual finish.
• An in-progress activity should have an actual start and a credible remaining duration.
• Milestone status should agree with the completion of its entry criteria.

Also review activities that started or finished out of sequence. Out-of-sequence progress can reflect legitimate execution. However, it may also expose missing logic, inaccurate status or work performed before prerequisite scope was complete. Do not delete the original relationship merely to remove a scheduling warning. Determine how the remaining work will now proceed, then model that plan.

For a deeper status procedure, see how to status an Integrated Master Schedule and the explanation of the IMS status date.

5. Recalculate and Check Schedule Health

Recalculate the schedule after status and logic updates. Then run the program’s approved health checks. These checks should identify conditions that can distort the forecast, including missing logic, leads, excessive lags, hard constraints, unusually long durations, negative float and incomplete work in the past.

Health metrics are diagnostic indicators. A DCMA-style assessment or another threshold-based test does not automatically create a contractual acceptance criterion unless the solicitation, contract or approved program procedures establish that criterion.

At a minimum, investigate:

• Activities missing predecessors or successors.
• New or changed constraints.
• Added, removed or modified relationships.
• Leads and lags that conceal work or waiting periods.
• High-duration activities in the near-term execution window.
• Invalid actual or forecast dates.
• Large positive or negative float values.
• Level-of-effort activities driving discrete work.
• Activities without baseline dates or required coding.

The DCMA 14-point schedule assessment guide provides a useful starting framework. However, the scheduler should interpret each result in the context of the schedule’s design, contractual requirements and execution strategy.

6. Trace the Critical and Near-Critical Paths

A monthly update is incomplete until the scheduler traces the current critical path. The path should form a continuous and technically credible sequence from the status date to the contractual completion milestone or another selected endpoint.

The GAO Schedule Assessment Guide recommends comparing the updated critical path with both the baseline path and the prior-period path. It also calls for evaluating total float trends and the effects of delayed activities on downstream work.

• Identify the current driving activity.
• Trace the path through each remaining relationship.
• Confirm that constraints or lags do not create an artificial path.
• Compare the path’s activities with the prior month.
• Explain changes in the path, completion date and total float.
• Assess the technical validity of the sequence.
• Identify actionable mitigation steps.

Do not stop at the primary critical path. Review paths driving major deliveries, test events, customer reviews, subcontract receipts and other key milestones. A near-critical path that loses float every month may represent a greater emerging risk than a stable critical path under active management.

Use near-critical path monitoring to identify these emerging drivers before they consume their remaining float.

7. Analyze Variance and Forecast Trends

Compare the current schedule against both the baseline and the prior-period forecast. Baseline variance measures execution against the approved plan. Prior-period movement measures forecast stability.

• Which baseline starts and finishes were missed?
• Which future milestones moved during the month?
• Did forecast dates move repeatedly without new technical information?
• Did remaining durations increase or decrease?
• Did future durations shrink without a documented execution change?
• Did float improve because of performance or because logic changed?
• Are unfinished activities accumulating near major milestones?

A milestone can remain on its baseline date while its supporting path loses most of its float. Therefore, milestone variance alone can hide deteriorating schedule risk. Pair variance analysis with driving-path and float analysis.

8. Review Baseline Changes Separately From Forecast Changes

Do not move baseline dates merely because current work is late. The current forecast should show the expected outcome, while the baseline remains the approved performance-measurement reference.

Review all baseline changes incorporated during the period:

• Confirm authorization and approval.
• Identify the affected scope, work packages and milestones.
• Compare the before-and-after schedule condition.
• Verify that the change entered the schedule and cost systems consistently.
• Confirm that historical actuals and performance remain traceable.
• Check that the change did not erase an unfavorable variance without authority.

If the remaining plan needs adjustment, distinguish routine forecasting from replanning or rebaselining. The article on replanning versus rebaselining explains the difference.

9. Reconcile the IMS With EVMS Data

On an EVMS program, the IMS and cost system should tell the same execution story. They do not need identical fields, but their status, scope and time phasing should reconcile at the appropriate control level.

• Schedule actual starts and finishes should support claimed accomplishment.
• Work-package dates should align with budget time phasing.
• Planning-package conversions should enter both systems consistently.
• Approved changes should appear in the same reporting cycle when practicable.
• Estimate-to-complete resources should support the forecast execution plan.
• Schedule slips should inform the Estimate at Completion when they affect resources or period of performance.

A difference between schedule percent complete and earned value is not automatically an error because they may measure different things. However, unexplained differences can reveal weak objective completion criteria, inaccurate remaining durations or status based mainly on elapsed time.

10. Connect the Monthly Update to Schedule Risk

The deterministic IMS identifies the current driving sequence. It does not, by itself, quantify the probability of meeting a date. Therefore, the monthly review should also identify changes that may require an updated Schedule Risk Analysis (SRA).

NASA describes schedule maintenance and control as the routine updating of progress, performance monitoring and execution of corrective actions. Its schedule management framework also treats the logic-based IMS as the primary schedule information source for management decisions.

Consider refreshing the SRA when:

• The critical or near-critical path changes materially.
• A major risk occurs or a mitigation plan fails.
• Key remaining durations change significantly.
• New scope or a major replan changes the network.
• Schedule margin is consumed faster than expected.
• A major milestone moves outside its approved risk tolerance.
• Management must select between competing recovery strategies.

For the full probabilistic process, see the complete Schedule Risk Analysis guide and the method for identifying schedule risk drivers.

Fictional Monthly Review Example

Assume the Falcon Ridge electronics program reports through July 31. During status collection, the hardware CAM reports that environmental qualification started on July 22 but will require 18 more workdays instead of the previous eight.

After recalculation, the qualification path replaces software integration as the critical path. Total float to the production readiness review falls from 12 days to negative four days. Meanwhile, three future test activities have shorter durations than last month, but the test lead has not approved a revised approach.

The scheduler should not accept the reduced future durations as an unexplained recovery plan. Instead, the monthly analysis should identify environmental qualification as the new driver, restore unsupported duration changes, quantify the milestone impact and document mitigation options. Those options might include added test shifts, earlier delivery of test articles or an approved overlap of selected analysis activities.

The team should also evaluate whether the changed uncertainty warrants an updated SRA. If recovery requires a new execution sequence, the scheduler should model that sequence with valid logic rather than deleting dependencies to force the milestone back to its baseline date.

Monthly IMS Delivery Package

Finally, deliver more than a schedule file. The Department of Energy’s IMS monthly review training recommends reviewing critical-path changes, schedule margin, health metrics, risk mitigations and baseline changes as part of the monthly submission process.

A useful package normally includes:

• The current native schedule file and required exports.
• The prior-period comparison or change log.
• Critical and near-critical path reports.
• Key milestone and float trend reports.
• Schedule health results with explanations and corrective actions.
• A baseline change summary.
• Risk, mitigation and schedule-margin updates.
• A concise narrative of drivers, impacts and management actions.

The narrative should answer four questions: What changed? Why did it change? What milestone or delivery does it affect? What action is required? A list of late activities without causal analysis does not answer management’s real scheduling questions.

Common Monthly Status Failure Modes

• Moving all incomplete work to the status date: This creates artificial date stacking instead of a resource-informed forecast.
• Using percent complete as the only status input: It can hide invalid actual dates and unrealistic remaining durations.
• Reviewing only the critical path: Emerging near-critical paths and interim delivery risks remain unseen.
• Changing logic to remove negative float: The schedule then conceals the problem rather than modeling execution.
• Reducing future durations without support: This creates an optimistic recovery assumption and pushes risk into later periods.
• Updating the forecast by changing the baseline: Management loses the approved reference for performance measurement.
• Reporting health metrics without analysis: Counts and percentages identify symptoms, not causes or consequences.
• Ignoring schedule-to-cost alignment: The IMS and EVMS may present conflicting versions of program status.

Final Review Questions

Before releasing the monthly IMS, the scheduler should be able to answer yes to the following questions:

• Does the schedule accurately separate actual work from remaining work?
• Does the forecast reflect current technical and resource conditions?
• Can the team explain every material change to the critical path?
• Are major milestone and float trends visible?
• Are baseline changes authorized and traceable?
• Does schedule status reconcile with EVMS status?
• Are risks and mitigations connected to schedule activities?
• Does the management narrative identify decisions and corrective actions?

A disciplined monthly update turns the IMS from a reporting artifact into a predictive management model. The objective is not simply to produce a clean file. It is to provide a credible forecast that helps the program act before schedule risk becomes an irreversible delay.