Blog

Schedule Update Reviews: 8 Hidden Indicators for Maintaining Data Integrity

While most people check schedule quality by looking at the single schedule being updated, true analysis isn’t complete until the next schedule shows up.

While most people check schedule quality by looking at the single schedule being updated, true analysis is not complete until the next schedule shows up.

A construction schedule can appear reasonable when reviewed in isolation. However, comparing it with the previous update may reveal changes to actual dates, percent complete, remaining duration, float, or the data date that alter the project’s history and distort the critical path.

Several hidden indicators can affect the reliability and accuracy of what your schedule is telling you once construction starts. If these issues are not caught during schedule update reviews, the result can be data integrity problems, inaccurate reporting, and an erroneous critical path.

This article examines eight common red flags: backdated activities, changed actual dates, decreased percent completes, remaining duration increases, activities riding the data date, future actual dates, activities started with 0% complete, and a high concentration of low-float activities.

Quick Answer: What Is a Schedule Update Review?

A schedule update review compares the current construction schedule with the previous update to validate how the project record has changed. The review checks reported progress, actual start and finish dates, remaining durations, schedule logic, float, and critical-path changes before the update is accepted or used for reporting. This comparison helps identify inconsistencies that may not be visible when reviewing the current schedule by itself.

 

Table of Contents

 

What Is Data Integrity in Construction Scheduling?

Data integrity means maintaining the accuracy, consistency, and reliability of project data throughout its lifecycle. It requires schedule-related information to be accurate, up to date, and consistently entered and managed within the project management system.

For construction schedules, data integrity applies not only to the current plan but also to the historical record created across successive updates. If actual progress, dates, or durations are entered inconsistently, the schedule may no longer provide a reliable account of project performance.

Why Is Data Integrity Critical to Project Success?

Reliable schedule data makes forecasting, reporting, and stakeholder trust possible. Once actual progress is entered incorrectly, every analysis built on that update inherits the error.

Accurate data supports:

  • Accurate forecasting: Reliable progress information helps project teams anticipate upcoming work and make the right resources available at the right time.
  • Reliable reporting: Consistent schedule data provides a clearer view of where the project stands at a given point in time.
  • Stakeholder confidence: Accurate updates help manage expectations and support informed planning for the future of the project.

During schedule update reviews, these benefits depend on whether progress has been captured accurately and consistently from one update to the next.

Why Is the DCMA Check Not Enough for Schedule Updates?

DCMA-style schedule quality checks primarily assess the planning and structural quality of a schedule. Update-cycle errors, however, emerge when actual progress is entered or when previously recorded progress is changed.

From an industry standpoint, schedule quality has defaulted to using the DCMA methodology as the standard in many ways. Schedule quality is also typically viewed as a static analysis focused on the planning side of the schedule. That analysis looks at issues such as missing logic, high durations, and too many constraints.

Those checks remain important, but they do not tell the entire story once updating begins. When discrepancies occur in actual progress rather than in the planned side of the schedule, the story of the past can change.

A complete schedule update review must therefore examine how the current file differs from the previous update, not only whether the current schedule passes structural quality checks.

 

8 Schedule Update Review Red Flags at a Glance

#

Indicator

What it is

Core risk

1

Backdated Activities

Actual start falls before the prior update's data date

Misrepresented progress and payment

2

Changed Actual Dates

A recorded actual start or finish is edited later

Unseen delays and manipulation risk

3

Decreased Percent Completes

Reported progress drops between updates

Hidden delay creeping onto the critical path

4

Remaining Duration Increases

An in-progress activity is given more time

Timeline extension acting as a fragnet

5

Activities Riding the Data Date

A ready activity keeps getting pushed to the data date

Float erosion and hidden compression

6

Future Actual Dates

Actual dates recorded beyond the current data date

Constraints that override CPM logic

7

Started with 0% Complete

Activity marked started but showing no progress

Bypassed sequence checks; masked delay

8

Low Float Activities

Too many activities with under ~10 days of slack

Volatile critical path and resource strain

1. Backdated Activities

What it means

Backdated activities occur when the initial actual start date for an activity falls before the previous schedule’s data date.

For example, in schedule number one, there is a planned activity in the future. Then, in schedule number two, that same activity receives actual start and actual finish progress dated before schedule number one.

Why it matters

This practice can distort the project’s timeline, affect data integrity, and lead to misleading conclusions about project progress and performance. Backdating actual dates creates a false impression of project status and can lead to misinformed decisions.

It can also complicate the identification of real issues. If delays are not accurately reflected, the project team may not recognize the need for timely mitigation.

What to check

During the schedule update review, compare new actual start and finish dates with the previous update’s data date. Pay particular attention to:

  • Inaccurate progress reporting: If actual dates in progress reports do not align with previous curves, earlier progress and performance analyses may be rendered invalid.
  • Misaligned payment applications: If activities are marked complete and in need of reimbursement or payment based on an inaccurate status update, the project may face unexpected costs later.
  • Out-of-sequence work: Certain schedule specifications restrict out-of-sequence work. If actual start and finish dates were not included in the appropriate previous updates, out-of-sequence work may appear later.

Core risk

Misrepresentation of project progress, including inaccurate reporting, payment misalignment, and an unreliable historical record.

2. Changed Actual Dates

What it means

Changed actual dates refer to modifications to the start or finish dates of activities already recorded as having started or completed.

For example, a scheduler may mark an activity as having actually started on July 30th. In a later update, the July 30th date is changed to July 25th. Doing so changes the reporting of when the activity actually started or finished.

Why it matters

Changing actual dates can create unseen delays and manipulation risk because it obscures the project’s true progress.

Suppose you are performing a forensic analysis and studying the historical critical path. If the correct date was not in place at the time of the original update, the change can affect the result of the analysis. You may also have to spend extra billable hours determining which date was correct.

This creates manipulation risk because the historical record can be changed to fit a narrative developing on the project.

Changed actual dates can also alter resource allocation or efficiency models by changing the understanding of how long it takes to finish an activity.

Consider a simple electrical roughing activity. If each floor of a building was planned to take seven days but is actually taking five days, that actual progress should inform the remaining electrical activities. If historical dates keep changing, however, studying that performance becomes more difficult because you do not know whether the information is consistent from one update to the next.

What to check

Compare all actual start and finish dates in the current schedule with the previous update. Investigate:

  • Actual dates that moved earlier or later
  • The reason each recorded date changed
  • Whether the revised date affects historical critical-path analysis
  • Whether the change alters resource or production assumptions

Core risk

Unseen delays, unreliable forensic analysis, and the possibility of manipulating the project’s historical record

 

3. Decreased Percent Completes

What it means

Decreased percent completes occur when the reported progress percentage of an activity is reduced after being recorded in an earlier update.

For example, if an activity is marked 50% complete in schedule one and 30% complete in schedule two, the change raises several questions. Was the original 50% complete accurate? Is the revised 30% complete accurate?

Percentages do not typically decrease unless something is being removed from the project or the earlier progress was reported incorrectly.

Why it matters

Changes to an activity’s percent complete often indicate that the schedule is not being properly maintained, bringing the reliability of progress data into question.

In P6, when this happens to duration-based activities, the change can create fragments or time-impact activities. The duration extends back out, alters float values, and may cause the activity to move onto the critical path.

A decreasing percent complete is also a flag for delay. It may reveal a delay that was not recognized during the previous schedule update review, or it may reflect a new cause such as added scope.

What to check

During the schedule update review:

  • Compare percent-complete values with the previous update.
  • Confirm why any activity’s reported progress decreased.
  • Check whether the remaining duration was adjusted to reflect the revised progress.
  • Review the effect on float and the critical path.
  • Determine whether the change reflects corrected reporting, added scope, or another cause.

If a percent complete was misreported in an earlier schedule and the activity was not as complete as originally thought, ask whether it should receive more remaining duration. That adjustment will not necessarily happen automatically.

Core risk

Unseen delays and misrepresented progress, including duration changes that can alter float and move onto the critical path.

4. Remaining Duration Increases

What it means

Remaining duration increases refer to extensions of the expected time required to complete an activity already in progress.

Changing remaining durations should be considered alongside decreased percent completes because the two often go hand in hand. Increasing the remaining duration on an activity decreases its calculated progress, extends the timeline, and can effectively create an impact or fragnet.

Why it matters

A remaining-duration increase can occur because of unforeseen issues, resource shortages, or scope changes. Whatever the cause, the project team needs to understand how the change is reflected in reporting.

Key questions include:

  • How reliable are the remaining-duration estimates?
  • Why was the duration increased?
  • Was the earlier estimate inaccurate?
  • What effect does the change have on float and the critical path?

Duration-based changes can disrupt the flow of the schedule by creating mini-networks that affect the overall timeline.

Mini-networks that appear by accident behave differently from a deliberate fragnet, where the added activities, durations, and tie-in points are documented and traceable to the project record. (fragnet schedule)

What to check

Review every increase in remaining duration and confirm:

  • The reason for the increase
  • Whether the percent complete changed at the same time
  • Whether the prior period’s remaining duration was inaccurate
  • How the increase affects progress reporting, float, and the critical path
  • Whether the change has effectively added an undocumented impact to the schedule

Frequent changes in percent complete or remaining duration can create doubt in progress reports and reduce trust in the accuracy of schedule updates.

Core risk

An undocumented timeline extension that acts like a fragnet or impact activity, changing float and potentially affecting the critical path.


5. Activities Riding the Data Date

What it means

Activities riding the data date are activities that can start based on their current logic but continue to be pushed out by the data date. This can indicate missing or erroneous logic.

If an activity has not started because another activity later in the schedule is holding it up, the appropriate relationship should be added to represent that dependency.

Why it matters

As an activity rides and moves with the data date, its float can collapse if everything else remains equal. That creates a compression risk.

Activities can begin to stack on top of one another, creating a period in which project resources may be stretched thin. This is a hidden version of compression because it happens unintentionally.

Schedule compression is often associated with an overt change intended to accelerate the project, mitigate delay, or shorten the schedule. In this case, activities riding the data date compress the remaining work naturally as long as the end date remains in place. (schedule compression techniques)

Identifying these activities early gives the project team an opportunity to review the sequencing, find missing predecessor work, and correct the schedule logic.

What to check

Use the following practices when reviewing activities near the data date:

  • Build adequate float: Ensure activities are not all planned to start exactly on the data date. Allow some margin for unexpected challenges and delays.
  • Use realistic scheduling: Build detailed schedules with defined start and finish dates based on accurate data. Historical data can help inform realistic durations.
  • Maintain data integrity protocols: Move the data date regularly and logically, and make sure activity progress is accurately captured.
  • Conduct scenario planning: Use what-if scenarios to understand the effects of scheduling decisions and adjustments.
  • Review schedule logic: Determine whether predecessor work or a missing relationship explains why an activity has not started.

Automated compression analysis can help identify deliberate and unintentional compression by comparing the remaining workload with the baseline at each update, regardless of how the compression entered the schedule.

Core risk

Float erosion and hidden compression, which can cause activities to stack together and increase resource strain.

 

6. Future Actual Dates

What it means

Future actual dates occur when actual start or finish dates are recorded beyond the current data date.

This practice tends to rely on approximations rather than what has actually happened, resulting in a non-responsive plan. It may also include activities marked as completed even though the work had not occurred at the time of reporting.

Why it matters

Sometimes planners and schedulers enter actual starts and finishes on the planned side of the schedule. Theoretically, those activities have not happened at the time of reporting, but they are marked as actually started or finished.

For example, suppose you completed a site walk on January 1st but did not update the schedule until January 5th. Because several days passed between the site walk and the update, you assume an activity was completed during that period and mark it accordingly.

The information included in reports is then inaccurate because the status was assumed rather than observed.

Future actual dates also ignore the methodology behind CPM. Setting future actual dates creates constraints in the schedule, forces activities to appear in certain places, and removes some of the value of CPM.

CPM performs the calculations needed to indicate how and when work should be executed. Future actuals instead tell the schedule when the work was executed before that execution has been confirmed.

What to check

  • Compare every actual start and finish date with the current data date.
  • Flag actual dates that occur beyond the data date.
  • Confirm whether the reported status was observed or assumed.
  • Remove unsupported future status and allow schedule logic to calculate the remaining plan.
  • Review whether future dates have forced activities into specific positions.

Core risk

Inaccurate reporting and date constraints that override CPM logic.

7. Started With 0% Complete

What it means

“Started with 0% Complete” refers to activities marked as started while showing no reported progress. Logically, this is inconsistent. If an activity has started, some form of progress would normally be expected.

Why it matters

This condition can occur for two primary reasons:

  • Lack of progress information: Progress data is unavailable, so the activity defaults to zero.
  • Circumventing sequence checks: An actual start date is entered without real progress to avoid sequence reporting issues.

For example, starting an activity with lag may lead someone to enter an actual start date to bypass out-of-sequence reporting.

Unseen delays can also arise because remaining durations may be manipulated while the percent complete remains at zero. That leaves no clear progress flag to signal the issue during the schedule update review.

What to check

  • Identify activities with an actual start and 0% complete.
  • Confirm whether physical progress has occurred.
  • Determine whether the actual start was entered to bypass sequence reporting.
  • Review the remaining duration for unsupported changes.
  • Check whether the activity is masking an out-of-sequence condition or delay.

Core risk

Bypassed sequence checks, manipulated remaining durations, and masked delay.

8. Low-Float Activities

What it means

Low-float activities are activities in a CPM schedule with minimal slack time, making the schedule more rigid and less flexible.

Schedule quality reviews often investigate high float, including how many activities have more than 60 days of float. That analysis can be flipped to examine the percentage of the remaining schedule with low float.

For this article’s review, that means asking how many remaining activities have less than approximately 10 days of float. This is a review reference used in the article, not a universal threshold for every project.

Why it matters

The higher the percentage of low-float activities, the more volatile the critical path can become. With little available slack, relatively small changes to progress, remaining duration, logic, or sequencing can affect which path is critical in the next schedule update.

A high concentration of low-float activities can also increase resource strain because more work has limited flexibility in when it can occur.

What to check

  • Determine the percentage of remaining activities with less than approximately 10 days of float.
  • Compare the concentration of low-float activities with the previous update.
  • Identify where low-float activities are stacking or converging.
  • Review whether logic, progress changes, or duration increases are driving the reduction in float.
  • Recheck the critical path after evaluating low-float concentration.

Core risk

A volatile critical path, reduced scheduling flexibility, and increased resource strain.

How Do You Catch Hidden Risks During Schedule Update Reviews?

Shorten the update cycle to roughly two weeks, create interim updates even if they are not published, and train schedulers to status fewer activities more accurately while fresh.

The best thing you can do to avoid these risks from appearing is to have a quicker update cycle. That way, they can be caught easier during your schedule update reviews.  While most schedules are contractually updated once a month, shortening this down to two weeks, even if it is not officially published, is so important. Create interim updates. That way, you will have far fewer activities to status—and by having less time between updates, you are more accurate with them because they are fresher in your memories.

Additionally, empower your schedulers to create accurate updates by providing necessary training and establishing robust scheduling processes and procedures. Understanding the potential impacts of errors is crucial to prevent them from going unnoticed. Implementing internal checks and balances, along with utilizing tools that support these checks, offers significant benefits.

Maintaining Schedule Data Integrity with SmartPM

While most people check schedule quality by looking at the single schedule being updated, true analysis isn’t complete until the next schedule shows up. At the end of the day, schedule update reviews create a snapshot of your project at any given moment so that you can continue to manage efficiently and get the job done. Ultimately, what is best for any organization is finding a sweet spot that maximizes time savings and minimizes risk.

“We also use SmartPM to ensure schedules are updated correctly – we have a mandatory requirement of twice monthly. If I see a huge variance from one update to the next, I will check in with the project director to see what’s going on there. At my level, it really helps track everything in one spot.”

– Kerry Lorts, Director of Operations at S.M. Wilson“

With SmartPM’s customizable approach to schedule quality, you can decide the metrics you want your schedules to be graded on, ensuring these metrics, and all the others relevant to your business, are accounted for throughout your project’s lifecycle. If you’d like to start your journey towards achieving data integrity on your projects, request a demo, and we’d be happy to show you how we can help you accomplish just that.

Frequently Asked Questions

Previous Post: Construction Reporting: Custom, Consistent, and Automated
Construction Reporting: Custom, Consistent, and Automated

Construction Reporting: Custom, Consistent, and Automated

Next Post: 10 Must-Haves in Your Scheduling SOP for Update Reviews
10 Must-Haves in Your Scheduling SOP for Update Reviews

10 Must-Haves in Your Scheduling SOP for Update Reviews

Related Stories