An effective IMS schedule status process records what happened, forecasts the remaining work and calculates the effect on contractual milestones. Set a common status date, collect actual starts and finishes, update remaining durations, resolve invalid logic conditions and recalculate the network. Then analyze the resulting forecast before publishing the schedule.
Statusing does not mean changing the baseline to match current performance. It also does not mean entering a percentage and accepting whatever dates the scheduling tool calculates. A credible update separates actual facts, current forecasts and approved baseline changes.
What Does It Mean to Status an Integrated Master Schedule?
Statusing an Integrated Master Schedule (IMS) updates the current schedule with progress through a defined cutoff date. That cutoff is usually called the status date or data date. Deltek Open Plan uses the term Time Now.
The status date creates the boundary between recorded performance and forecast work. Actual starts, actual finishes and completed effort belong on the historical side of that boundary. Unfinished work belongs in the forecast period.
The GAO Schedule Assessment Guide treats regular updates using actual progress and current logic as a best practice for maintaining a controlled schedule. GAO also distinguishes status from revision. Status records actual events, while revision changes the plan for future execution.
This distinction matters. If a team changes logic, durations or forecast dates before it records the facts, management loses visibility into the cause of the movement.
Contractual Requirements Versus Scheduling Best Practices
No single status procedure applies to every federal contract. Reporting frequency, required fields, narrative thresholds and submission formats depend on the contract, Contract Data Requirements List (CDRL), applicable Data Item Description, reporting instructions, tailoring and the contractor’s approved procedures.
For example, DFARS 252.234-7002, when included in a contract, requires an Earned Value Management System (EVMS) that generates timely, reliable and verifiable information for required performance reports and the IMS. However, that clause does not establish a universal keystroke-level schedule update method.
Therefore, begin with the governing contract and the program’s documented scheduling procedures. Treat the workflow below as a recommended control process unless a specific requirement makes a step contractual.
IMS Schedule Status: A Step-by-Step Process
1. Establish the status date and reporting calendar
First, confirm the cutoff date for the cycle. Use one status date across the IMS, EVMS, subcontractor updates and supporting control-account reports unless approved procedures state otherwise.
Define the cutoff convention precisely. For example, a program may collect performance through close of business Friday and set the scheduling tool’s status boundary at the start of Saturday. Other programs use Friday as the displayed status date. The correct setup depends on the software, calendars and documented business rules.
Also freeze a copy of the schedule before entering status. Record the file version, status period, scheduling options and applicable calendars. This copy provides an audit trail and helps the team isolate changes introduced during the update.
2. Issue activity-owner status requests
Next, send each control account manager (CAM), integrated product team lead or activity owner a focused status request. A turnaround report should include activities that:
- were planned to start or finish during the period;
- were already in progress;
- have forecast dates within the near-term planning window;
- support critical or near-critical paths;
- have negative or low total float; or
- drive contractual, technical or customer milestones.
Ask for facts and forecasts, not just a color or subjective percentage. At minimum, request actual start, actual finish, remaining duration, expected finish and an explanation for significant movement. Also ask whether the current relationships still represent the way the team will perform the work.
The IMS should align with the program’s scope and responsibility structure. If that foundation is weak, review how to structure an IMS using the work breakdown structure before trying to repair the update process.
3. Validate status before entering it
Do not load every response without review. Check each update for internal consistency and question unsupported optimism.
- An activity with an actual finish must also have an actual start.
- An incomplete activity must have remaining work.
- An unstarted activity cannot have an actual finish or completed effort.
- An actual date should not fall beyond the agreed status boundary.
- A remaining duration should reflect the current estimate, not automatically repeat last month’s value.
- A milestone should only be complete when its defined event has occurred.
CAM judgment remains essential. However, the scheduler should challenge a five-day remaining duration that stays at five days for three consecutive periods. That pattern often indicates a static estimate rather than a current forecast.
4. Enter actual starts and actual finishes
Record the dates on which work actually started and finished. Do not substitute baseline or current forecast dates simply because the owner cannot provide the facts.
Actual dates should remain stable after validation. If the team later discovers an error, correct it through the documented process and retain the reason for the change. Repeated movement of historical dates weakens schedule credibility and can affect EVMS calculations.
Use objective completion criteria for significant milestones. A document is not necessarily complete when someone starts routing it. Likewise, a test milestone is not complete merely because the test window opened. The schedule’s milestone definition should identify the event that proves completion.
5. Update in-progress activities using remaining duration
For each in-progress activity, update the amount of time needed to finish the remaining scope. Remaining duration is a forecast made as of the status date. It is not simply original duration minus elapsed calendar time.
Ask the activity owner: Given the work completed and the resources now available, how many working days remain? Then verify that the answer supports a realistic forecast finish under the activity calendar.
Duration percent complete can help describe elapsed schedule progress. However, it does not automatically measure physical accomplishment or earned value. A 10-day activity with five elapsed days may be 50 percent complete by duration while only 30 percent of its technical scope is complete. Keep those measures distinct.
6. Handle unstarted activities with dates in the past
An unstarted activity whose forecast start is before the status date cannot remain in the past. Confirm why the work did not start and whether its driving logic still represents current conditions.
Then let valid network logic forecast the new start. Do not add a constraint simply to push the activity forward. If no predecessor explains the delay, the schedule may have missing logic, an unmodeled approval or an undocumented resource dependency.
This review often reveals broader planning problems. The methods in How to Build an Integrated Master Schedule provide additional guidance on activity definition, sequencing and milestone integration.
7. Evaluate out-of-sequence progress
Out-of-sequence progress occurs when a successor starts or finishes before the conditions represented by its predecessor relationships have been satisfied. The scheduler should not erase the actual event. Instead, record the fact and determine what happened to the original execution logic.
For example, engineering may begin a preliminary drawing before the associated interface approval finishes. If the work truly started, retain the actual start. Next, ask whether the original finish-to-start relationship remains valid for the unfinished portion. The team may need to add a remaining-work activity, revise the relationship or model a more accurate dependency.
Do not delete logic only to improve schedule metrics. Any logic change should describe the current execution plan and follow the program’s change-control procedure.
8. Recalculate and move remaining work into the forecast period
After entering status, run the scheduling calculation using the approved settings. No unfinished work should remain scheduled in the historical period, and actual performance should not appear in the future.
In Microsoft Project, the status date influences the placement of actual and remaining work. Microsoft’s guidance explains how to set the status date for project reporting. Project also provides an option to reschedule uncompleted work after a selected date. Test these settings in a controlled file because configuration choices can change how splits, actual work and remaining work appear.
In Deltek Open Plan, Time Now defines the progress boundary. Open Plan expects the user to identify whether an activity started, when it started, whether it finished and how much duration remains if it is incomplete.
9. Perform schedule quality checks
Do not publish the IMS immediately after recalculation. At minimum, inspect the schedule for:
- actual starts or finishes beyond the status boundary;
- incomplete work remaining before the status date;
- missing actual dates on progressed activities;
- completed activities with remaining duration;
- unstarted activities with forecast dates in the past;
- out-of-sequence progress;
- new or changed constraints, lags and relationships;
- invalid calendars or unexpected resource effects;
- open ends and broken driving paths;
- negative float and major changes in total float;
- changes to the critical and near-critical paths; and
- milestone forecasts that conflict with external reports.
Metrics identify where to investigate. They do not replace analysis. For example, an out-of-sequence activity may reflect poor status discipline, or it may reveal a legitimate change in execution strategy.
10. Analyze the forecast and communicate the result
A schedule update is not complete until the team understands its management implications. Compare current forecast dates with baseline dates, prior-period forecasts and contractual dates.
Explain what moved, why it moved and what happens next. Focus management attention on driving paths, lost float, missed starts, milestone trends and recovery actions. Also identify assumptions that could change the forecast.
Where the IMS supports an EVMS, reconcile schedule status with control-account status and the Performance Measurement Baseline (PMB). Review inconsistent actual dates, completion status, forecast dates and earned value claims before transferring data to the cost system. Deltek Cobra users should also verify the selected date and status mappings in the Cobra scheduling integration settings.
For a broader explanation of the relationship between schedule and budget, see how to build a robust Performance Measurement Baseline.
11. Archive the approved update
Finally, save the approved current schedule, the pre-status copy, status inputs, validation records, change logs and required reports. Use controlled naming and version conventions.
Do not overwrite the approved baseline during a routine status cycle. Baseline changes require separate authorization under the contract and the program’s change-control process. Status answers, “Where are we now?” Baseline control answers, “What approved plan are we measuring against?”
Example: Statusing a Flight-Test Support IMS
Consider a fictional avionics integration program with a status cutoff of May 29. The activity “Complete Environmental Test Procedure” had a baseline finish of May 22. The procedure actually started May 11 but remained incomplete at the cutoff.
The CAM reports that coordination comments added four working days of scope. The team has six working days remaining, and the successor test-readiness review cannot finish until the procedure receives approval.
The scheduler should:
- record the May 11 actual start;
- leave the activity incomplete;
- enter six working days of remaining duration;
- confirm the approval and review relationships;
- recalculate the network from the status boundary;
- evaluate the effect on the test-readiness review and downstream test window; and
- document the cause, impact and proposed action.
The scheduler should not enter 90 percent complete solely to preserve the original finish. Nor should the team move the baseline finish to match the new forecast. The updated IMS must show the consequence of current performance.
Common IMS Statusing Mistakes
Using percent complete as the only status input
A percentage without actual dates and remaining duration provides weak forecasting information. It can also hide a task that remains “almost complete” for several cycles.
Automatically accepting the prior remaining duration
Remaining duration should decline, increase or stay constant for a defensible reason. Repeating the same estimate without reassessment creates unrealistic finish dates.
Adding constraints to force preferred dates
Constraints can mask the effect of actual progress and broken logic. Use them only when a genuine external restriction or approved scheduling rule requires one.
Confusing status with replanning
Record actual performance first. Then evaluate proposed changes to future logic, resources or durations. Keep baseline changes under formal control.
Ignoring downstream effects
An activity can appear noncritical while it consumes float needed by another activity on the same path. Review the complete driving path rather than one activity in isolation.
Failing to reconcile the IMS and EVMS
A completed schedule activity paired with an incomplete work package may signal inconsistent status rules or mapping. Integrated project controls depend on common scope, dates and status assumptions. The article on integrated project controls in complex programs explains why these reconciliations matter.
IMS Schedule Status FAQ
How often should an IMS be statused?
Use the frequency required by the contract and the program’s approved procedures. Many programs use monthly accounting periods and more frequent internal updates. However, monthly status is not a universal requirement for every IMS.
Should the status date equal today’s date?
Not necessarily. The status date should represent the agreed reporting cutoff. A schedule updated on Tuesday may still use the prior Friday or month-end cutoff.
Can actual dates change?
Correct an actual date when evidence shows that the recorded date was wrong. Document the reason and follow the program’s correction process. Do not move actual dates simply to improve a variance.
Should the baseline move during every update?
No. A routine status cycle updates actual performance and the current forecast. The baseline changes only through the applicable authorization and change-control process.
What is the most important output of the status cycle?
The primary output is a credible forecast based on current facts, valid logic and realistic remaining durations. The schedule should tell management which milestones are at risk, what drives them and where action can still change the outcome.