Esc

↑↓ move↵ openIndex · Pagefind
Project management

Data Date

Definition

The status cutoff separating recorded progress from the remaining work forecast in a schedule update.

Topic: Scheduling

Updated

The data date splits actual progress from forecastA vertical line marks the October 31 data date. Level 2 framing is shown as an actual bar from October 13 to October 27, entirely left of the line. Level 2 ductwork has an actual start on October 28, a solid actual portion up to the data date, and a forecast portion of 11 remaining working days after it. The above-ceiling inspection is a forecast milestone after ductwork finishes. Nothing actual sits right of the line and nothing unfinished sits left of it.ACTUALFORECASTData date Oct 31L2 framingL2 ductwork11 days leftInspectionActual dates: on or before the lineRemaining work: after it
Illustrative October update. Actual progress sits left of the data date; remaining work is forecast forward from it.

The data date is the cutoff a schedule update is statused to. Everything before it is history: actual starts, actual finishes and progress recorded from the field. Everything after it is forecast: remaining work scheduled forward using the network logic, calendars and scheduling settings. A reviewer should be able to read the data date and know exactly what “as of” the update means.

The data date is different from the file export date, the report print date and the submission deadline. A report printed on November 5 can describe progress through October 31.

How it works

At each update the scheduler:

  1. Collects progress as of the cutoff. Actual start and finish dates, and for work in progress, an estimate of the remaining duration, from the superintendent, foremen and daily logs.
  2. Enters it against the new data date. Actual dates must fall on or before the data date. Remaining durations describe work still to do after it.
  3. Moves the data date and recalculates. The engine schedules all unfinished work from the data date forward. Incomplete work that was planned in the past is pushed out to start no earlier than the data date.
  4. Reviews the result. New forecast dates, changes in float, changes to the critical path and any out-of-sequence progress.
  5. Explains it. The update narrative names the data date and the reporting period it covers.

How the engine treats work that started before its predecessors finished depends on settings such as retained logic or progress override. The same progress can give different forecasts under different settings, so they should stay consistent between updates.

In Primavera P6 the field is called the data date and shows as a vertical line on the Gantt chart. Microsoft Project uses a status date for the same purpose. Some planners call it time now.

Worked example

Illustrative: the October update has an October 31 data date, on a five-day calendar.

Activity Plan Field record How it goes in the update
Level 2 framing Oct 13 to Oct 24 Started Oct 13, finished Oct 27 Actual start Oct 13, actual finish Oct 27
Level 2 ductwork Oct 27 to Nov 14 (15 days) Started Oct 28, about 11 working days of work left Actual start Oct 28, remaining duration 11 days, forecast from Oct 31 forward
Level 2 above-ceiling inspection Nov 17 Not started Forecast after ductwork finishes

Two things the update must not do:

  • A rough-in inspection that passed on November 3 belongs in the November update. Recording it as an actual finish in the October 31 update puts an actual date after the data date.
  • If ductwork is still in progress at the cutoff, its remaining work can’t be shown finishing on October 30. That would be a forecast before the data date.

The remaining duration is the team’s estimate of the time left, not a calculation from percent complete. A duct crew that is 60% through the installed footage may have more than 40% of the time left if the hardest areas remain.

Why it matters

Every comparison between updates depends on the data date. Two schedules with the same file date but different data dates describe different points in the project. Two exports of the same update look like separate updates if nobody checks the data date. For delay analysis, the data date of the update you start from decides which events are history and which are still forecast, so it is often one of the first things a reviewer checks.

The data date also anchors the update period. Monthly updates are common on construction contracts, but the contract or the project’s procedures set the cycle.

What to check

  • Compare the schedule’s data date with the reporting period in its narrative.
  • Look for actual dates after the cutoff and unfinished work forecast before it. The invalid dates check in the DCMA 14-point assessment tests exactly this.
  • Reconcile remaining durations with field records rather than assuming percent complete determines time remaining.
  • Confirm the data date moved forward since the last update, and by the expected interval.
  • Compare updates using a consistent status basis; a later export is not necessarily a later update.

Common mistakes

  • Forgetting to move the data date, so a month of progress is entered against last month’s cutoff.
  • Statusing to the print date instead of the end of the reporting period.
  • Entering actuals after the cutoff because the information was available when the update was being prepared.
  • Recalculating before entering progress, which pushes all planned-but-unstatused work to the new data date and makes the schedule look worse than it is.
  • Mixing cutoffs across trades, for example statusing one sub’s work to the 31st and another’s to the 7th.

Read how to write a monthly schedule narrative and how P6 settings affect the forecast. The Schedule Forensics learning hub connects the review steps and worksheets.

FAQ

What is the data date in a schedule?

The data date is the point in time a schedule update is statused to. Everything before it is recorded history: actual starts, actual finishes and progress. Everything after it is forecast: remaining durations scheduled forward from the data date using the network logic and calendars.

Is the data date the same as the status date?

They mean the same idea. Primavera P6 calls it the data date. Microsoft Project uses status date for the date progress is measured to. Some planners call it time now. Whatever the label, it is the cutoff between actual and forecast.

Can an actual date be after the data date?

No. An actual start or finish after the data date records something that hadn't happened as of the cutoff, which makes the update internally inconsistent. Scheduling checks, including the invalid dates check in the DCMA 14-point assessment, flag actual dates after the data date and forecast dates before it.

How often should the data date move?

Once per update cycle, to the end of the reporting period the contract or project procedures specify. Monthly is common on construction contracts, and many teams also status weekly for internal look-aheads. Each update should move the data date forward to the new cutoff.

What happens to unfinished work when the data date moves?

Remaining work can't be scheduled in the past. When the data date moves forward, the scheduling engine pushes any incomplete work to start no earlier than the new data date, which can move successors and the forecast finish. That is why progress has to be entered before the schedule is recalculated.

Sources

Open file