Understanding how Oracle Primavera P6 date fields work is crucial to planning, reporting, and updating accurate project schedules. This guide will help you understand the various date fields used by P6, including Actual Start, Late Finish, and Data Date. You can then use them to interpret your schedule correctly. Many planners also review these fields during Oracle Primavera P6 workflows and P6 scheduling processes to ensure accurate Primavera date calculations.
The P6 activity schedule has a Start Date and a Finish Date that reflect the actual scheduled dates. Once work starts, you can manually set Actual Start or Actual Finish. Calculations of Early Start/Early Finish and Late Start/Late Finish are based on calendars, logic, and constraints. The baseline dates or targets that do not change when work starts are the planned Start/Planned Finish. The Data Date drives what remaining portions are calculated from, and Constraint/External/Suspend/Resume dates provide special exceptions or inputs. Use the right field to achieve the desired result. These principles are often emphasized in Primavera P6 training, especially when discussing Primavera dates and how schedule logic affects a Primavera date during updates.
Primary Date Fields
Primavera P6 activities begin with the foundational date fields as Start Date, End Date, and Actual Values. It is important to control schedule accuracy by understanding the difference between manually and calculated fields. Professionals managing Oracle Primavera P6 schedules frequently review Primavera dates here to validate their P6 scheduling accuracy.
Actual Start and Actual Finish
Actual Start and Actual Finish are the dates on which an activity is actually begun and completed. These dates override the schedule logic, locking the event into the past. Once Actual Start has been entered, many P6 calculations no longer treat the activity as not started. This is especially critical when working in Primavera P6, because mismanaging a Primavera date can distort float values.
Start Date and Finish Date
In P6, the Start Date and Finish Date are dates that have been scheduled for an activity. Start is often the same as Early Start, or Planned Start, depending on your configuration. The Start Date becomes Actual Start once the work actually begins (with the “A” suffix on P6). These fields are core in Oracle Primavera P6 and are often analyzed during P6 scheduling updates when verifying Primavera dates.
Early and Late Date Fields
The forward-backward passes of P6 automatically generate them. These fields are the backbone of critical path and float analysis. Anyone involved in Primavera P6 training learns early how central these Primavera date calculations are.
Early Start and Early Finish
The earliest possible date the remaining work for the activity can start, based on the calendars, logic, and constraints, is the Early Start, and the finish date is the Early Finish. To illustrate, when an activity has a predecessor that completes on 10 Oct and no lag, the Early Start of the activity will be the workday after 10 Oct. Correct evaluation of Early Dates is essential in Oracle Primavera P6, especially for reliable P6 scheduling forecasting and managing multiple Primavera dates during progress updates.
Late Start and Late Finish
Late Start is the latest date on which the remaining work can be commenced without postponing the completion of the project. Late Finish is also the latest date of completion. The difference between the Late Finish and the Early Finish is the Total Float, which is one of the most important parameters used to manage the flexibility of the schedule. Critical-path procedures in Primavera P6 training emphasize how Late Dates influence every Primavera date and are integral to P6 scheduling consistency.
The Role of Planned Dates in P6
Planned Start and Planned Finish are stable references that serve to define the original intention before progress and updates changed the schedule. These are foundational in Oracle Primavera P6, as they set expected Primavera dates before variances begin to appear.
Planned Start and Planned Finish
Planned Start and Planned Finish in P6 are the target or budgeted schedule dates as opposed to dynamic calculated dates. Start and finish may then be initially equal to un-progressed schedules. Planned dates tend to cease upon initiation of progress, and a baseline develops. Users often compare these against actual Primavera date values during P6 scheduling reviews.
Common Issues When Planned Dates are Modified
Any changes to Planned Start or Planned Finish after the work has started may lose the connection to logic and calculated fields. According to one expert, it is so: “A change in the Planned Start changes the Start date,” although the Planned Start may be earlier than the original Start date. Unless the setting of the planned and at-completion on the not-started activities is activated, disparities might occur. These issues are common discussion points in Primavera P6 training and highlight the importance of maintaining planned Primavera dates.
Constraint, External, and Suspend/Resume Date Fields
P6 offers several date fields that are based on constraints or exceptions. They introduce boundaries manually that can override the natural sequence or interruptions in records. The placement of constraints affects nearly every Primavera date and is a core concept in Oracle Primavera P6 usage.
Constraint Date Usage and Types
The Constraint Date field is linked to the type of constraint of activity (e.g., Finish On, Start On, or After). A Constraint Date will indicate the date in case an activity has a “Finish On” date of 20 Nov. The constraint dates are capable of making the schedule as well as decreasing the float. Constraint usage must be carefully evaluated during P6 scheduling, as it can override multiple Primavera dates.
External Early/ Late, Suspend Date, Resume Date
Fields that are added to P6 are External Early Start or External Late Finish (when external relationships are lost on import), Suspend Date/ Resume Date to indicate when work is suspended. When a procurement activity is put on hold on 28th July and gets back on 11th Oct the dates are used to compute non-work periods and correct durations. This is also shown in the image below. These fields frequently appear in complex Oracle Primavera P6 scenarios involving multi-project Primavera dates.
Table: Summary of Date Fields in P6
| Field | Description | Typical Use |
|---|---|---|
| Start Date | Scheduled start of activity (or Actual if started) | Gantt and reports |
| Finish Date | Scheduled finish | Gantt and reports |
| Actual Start | Date work actually began | Audit, progress tracking |
| Actual Finish | Date work was completed | Audit, progress tracking |
| Early Start | Earliest feasible start given logic | Logic/float analysis |
| Early Finish | Earliest feasible finish | Logic/float analysis |
| Late Start | Latest start without delaying project | Float/critical path review |
| Late Finish | Latest finish without delaying project | Float/critical path review |
| Planned Start | Target or budget start date | Baseline comparison |
| Planned Finish | Target or budget finish date | Baseline comparison |
| Constraint Date | Date tied to an activity constraint | Force milestone or date lock |
This snapshot from Primavera P6 is showing all of these fields for a fabrication project.
Best Practice Tips for Date Field Usage and Reporting:
Follow disciplined procedures when entering date fields and checking them. The rules below ensure consistency and float integrity across all updates. These best practices apply directly to Oracle Primavera P6, especially when monitoring Primavera dates and performing P6 scheduling reviews.
Use Actual Finish and Actual Start to lock your work. Do not edit them after they are entered, unless you need to correct.
For logical or schedule assessments, float analyses, and health assessments, use Early and Late Dates.
Use Planned Dates as a baseline reference or as a target date.
Document the reasons for setting Constraint dates and consider their impact on floats.
Before rescheduling, ensure that your data date is set correctly. Work in progress should also be updated so as to prevent unintended changes.
Choose the field for the report that corresponds to the metrics: for example, Late Finish is used for “dates without delays”, finish for “planned finishes”, etc.
Audit your date fields periodically and look for any anomalies. For example e.g., Start = Actual Start, but Early Start much earlier might signal a logic error. This process supports accuracy across all Primavera dates.
Date Field Usage Before Schedule Update
Confirm the Data Date is correctly set and reflects the current reporting period.
Enter Actual Start for newly started activities.
Enter Actual Finish for completed activities.
Review Planned dates, are they still valid as targets?
Check any Constraint Dates recently added or changed.
Verify finish dates for in-progress activities haven’t unintentionally shifted due to the Data Date move.
These checks reinforce better P6 scheduling control and prevent errors across your Primavera date management.
Wrapping Up:
Managing complex project schedules in Primavera P6 can be challenging, especially when multiple date fields, dependencies, and progress updates interact. But mastering how date fields behave gives you full control, clarity, and confidence in your reporting, forecasts, and delay analysis. Accurate handling of Actual, Planned, Early, and Data Dates ensures your schedule reflects reality and supports sound project decisions. Whether you’re learning through Primavera P6 training or applying Oracle Primavera P6 on job sites, understanding how each Primavera date interacts with logic is essential.
If you’re looking for expert guidance in Primavera P6 schedule development, CPM Scheduling, or construction scheduling services, turn to Leopard Project Controls. With over 20 years of experience in CPM and Oracle Primavera, our consultants help general contractors, owners, and project managers maintain schedule integrity, prevent slippage, and deliver projects with precision through best-in-class P6 scheduling practices.
