Chennai HQ · serving India, UAE, Saudi Arabia and Omaninfo@projectassure.inCall us 24/7 +91 94895 88922
Project Assure
Schedule Quality

What is the data date in Primavera P6, and why it matters

The data date splits a P6 schedule into what has happened and what is forecast. Here is how it drives every update, how it differs from the status date (it does not), and the mistakes to check for.

In short

The data date in Primavera P6 is the progress cut-off of a schedule update: actuals sit before it and remaining work is scheduled forward from it. Data date and status date mean the same thing in P6. Enter progress first, then move the data date and reschedule, and check that no actual dates fall after it and no forecast dates fall before it.

The data date in Primavera P6 is the cut-off date of a schedule update: everything before it is recorded as actual progress, and everything after it is the forecast of remaining work. When you reschedule (F9), P6 calculates the remaining work forward from the data date, so it sets where every forecast date, float value and earned value figure starts.

Many schedulers call it the status date or the as-of date. In P6 these mean the same thing. Getting it right is the first check on any update, because a wrong data date makes every forecast in the file wrong as well.

What is the data date in Primavera P6?

The data date is the point in time at which the schedule's progress is measured. In P6 it is the boundary between what has happened (actual dates, actual units and costs) and what is still planned (remaining durations and forecast dates). Every update, whether weekly, monthly or ad hoc, has one.

You can see it in the Project Details window on the Dates tab, and as a vertical line on the Gantt chart. You move it in the Schedule dialog (Tools > Schedule, or F9) by changing the current data date before rescheduling. On a new project it defaults to the project planned start.

It is normally set to the progress cut-off of the reporting period. Actual dates, percent complete and remaining durations are all entered as of that date. When the schedule is calculated, P6 does not leave remaining work before the data date: any work not yet done is moved to start on or after it.

What is the difference between the data date and the status date?

In Primavera P6 there is no difference. "Data date" is the field name in the software, and "status date" or "as-of date" are the terms many schedulers and contracts use for the same cut-off. In Microsoft Project the equivalent field is called the Status Date, which is one reason both terms are common. Whichever term the contract uses, it should be a single date stated in the update narrative.

How does the data date drive progress and forecasts?

  • Actual versus planned: work before the data date is recorded as actuals. Work after it is the forecast.
  • Remaining duration: for an activity in progress, the remaining duration is the work still to do. P6 schedules that remaining work forward from the data date, so its forecast finish is the data date plus the remaining duration on the activity's calendar (subject to logic).
  • Forward pass and critical path: the forward pass starts at the data date. Unstarted and in-progress activities are scheduled from it according to their logic and remaining durations, which is how the update shows the current critical path.
  • Float: total float is still the difference between late and early dates. The data date affects float because it sets the earliest date that remaining work can be scheduled: if work has slipped, moving the data date forward pushes early dates later and float falls, or turns negative.
  • Earned value: the data date is the status date for EVM. Planned Value is measured up to it, and Earned Value reflects the work actually done by it.

Can you move the data date without updating progress?

You can, but you should not. Moving the data date forward without entering progress tells P6 that nothing happened in the period: every incomplete activity is pushed to start after the new data date, and the forecast finish slips by the length of the period. The opposite error is just as common: using Update Progress to mark everything as done to plan, which hides real delay. The right order is to enter actual starts, actual finishes, remaining durations and percent complete as of the cut-off, then move the data date and reschedule.

How P6 handles progress that is out of sequence (an activity that started before its predecessor finished) also depends on the scheduling option you choose. Our guide to out-of-sequence progress in P6 covers retained logic, progress override and actual dates.

What are the common data date mistakes in schedule updates?

  • Not moving the data date: if progress is entered but the data date is left in the past, actual dates can fall after the data date, which is invalid, and the forecast still runs from the old date.
  • Setting a data date that does not match the progress: the data date should be the date the progress was measured. If it is later, the update assumes no progress in the gap and overstates delay. If it is earlier, actuals recorded after it are invalid and the forecast is wrong.
  • Different data dates across a programme: where several projects are rolled up or linked, each P6 project has its own data date. They should all use the same cut-off, or roll-ups and cross-project logic will mix periods.
  • Treating the data date as a baseline: the data date is not a baseline. A baseline is a saved copy of the plan to measure against. The data date moves forward with every update.

Before running reports or issuing the schedule, check the data date in Project Details > Dates and confirm it matches the reporting period.

How do you check the data date in an XER you receive?

When a contractor or team member sends a P6 XER file, check the data date first. A wrong data date undermines every forecast date in the file.

  1. Import the XER into P6 and open Project Details > Dates. In the XER file itself, the data date is held in the PROJECT table (the last_recalc_date field).
  2. Confirm the data date matches the cut-off of the reporting period stated in the update.
  3. Check for invalid dates: no actual start or finish after the data date, and no forecast start or finish before it. Check 9 of the DCMA 14-point assessment requires zero of both.
  4. Look for signs that the data date was never moved, for example a data date still at the project start while activities show actual dates.

A schedule-checking tool or a P6 report can list the data date and flag invalid dates across the whole file. An independent reviewer (Project Assure) does this as the first step of every schedule review; see our project controls and EVM services for how update reviews are run.

What are the best practices for setting the data date?

  • Use the agreed cut-off. Set the data date to the progress cut-off defined by the contract or reporting procedure, for example a set day each week or the last working day of the month, and keep it consistent from update to update.
  • Update all actuals before moving it. Enter actual starts, actual finishes, remaining durations and percent complete for every activity with progress, then reschedule.
  • Do not backdate. If an update is missed, do not set the data date earlier to catch up. Record progress as of the date it was measured and note the gap in the narrative.
  • State it in the narrative. Put the data date in every status report and schedule narrative so readers know the cut-off for the figures.

Get the data date right and the update shows where the project really stands. Get it wrong and the forecasts, float and earned value built on it are wrong too.

FAQ

Common questions

What is the difference between data date and status date in Primavera P6?
They are the same thing. P6 calls the field the data date, while many schedulers and contracts call it the status date or as-of date; Microsoft Project uses Status Date for its equivalent field. All refer to the cut-off at which the schedule's progress is measured.
Can I change the data date without updating progress?
Technically yes, but it is poor practice. Moving the data date without entering progress tells P6 nothing happened in the period, so all incomplete work is pushed out past the new date. Enter actual dates, remaining durations and percent complete first, then move the data date and reschedule.
How does the data date affect float calculations?
Total float is still late dates minus early dates, but the forward pass starts at the data date. If work has slipped, moving the data date forward pushes early dates later, so float falls or turns negative. A wrong data date therefore misstates float across the schedule.
What should I do if an XER's data date does not match the reporting period?
Treat it as a red flag and ask the sender to confirm the cut-off and reissue the update. Check also for actual dates after the data date and forecast dates before it, which DCMA check 9 treats as invalid dates and requires to be zero.
Is the data date the same as the project start date?
No. The project start date is when the project is planned to begin, while the data date is the cut-off of the latest update. On a new P6 project the data date defaults to the planned start, then moves forward with each update while the start date stays put.
Chennai city skyline at dusk under a vivid pink and violet sky

Bring this discipline onto your programme.

Every insight comes from live mandates. A principal replies within one working day.