What Data Date Actually Is (And Why It Matters)
There is a common misconception that data date is a feature of scheduling software - a field you fill in because Primavera asks for it. It is not.
Data date is a logical concept. It answers the most fundamental question any project record can be asked: "As of when is this true?"
When a scheduler advances the data date, they are making a formal declaration: "Everything to the left of this line has happened. Everything to the right is still planned." Without that declaration, the schedule is not a project record. It is a planning artifact that was never tethered to reality.
The Association for the Advancement of Cost Engineering (AACE International) defines the data date in Recommended Practice 10S-90 as "the date up to which actual data has been incorporated into the schedule." AACE RP 29R-03, Forensic Schedule Analysis, goes further, establishing that the integrity of any retrospective schedule analysis depends on the demonstrable reliability of the data date across update cycles. Without it, the baseline-to-update comparison that forms the foundation of virtually every delay methodology collapses.
The DCMA 14-Point Assessment - the schedule health standard developed by the Defense Contract Management Agency and widely adopted across federal construction and major owner-driven projects - explicitly evaluates whether the data date is current and whether logic flows correctly from it. A schedule that fails this check is not merely imperfect. It is formally assessed as unreliable for progress measurement and forecasting.
Three Moments When the Missing Data Date Fails You
1. During Progress Updates: Your Schedule Has No Memory
A schedule without a maintained data date cannot tell you where you actually are. It can show you what was planned, but it has no reliable way to distinguish between work that should have started, work that has started, and work that is late. Every calculation downstream - total float, critical path, resource demand - is being run against a fiction.
AACE RP 52R-06 (Time Impact Analysis) is explicit: a TIA requires a valid, contemporaneously maintained schedule with a clearly established data date to model the prospective or retrospective impact of a change or delay event. When the data date is absent or inconsistent, the TIA has no credible starting point. You cannot measure displacement if you don't know where you were standing.
2. During Execution: You're Building a False Record
Here is what most field teams don't realize: the schedule they are circulating is a contemporaneous document. It timestamps what you knew, and when. If you are sending schedule updates to an owner every month with no data date, you are telling the world that you cannot distinguish between what happened and what was planned.
The Society of Construction Law Delay and Disruption Protocol - used extensively in international arbitration and increasingly referenced in U.S. disputes - emphasizes that delay analysis can only be conducted reliably when there is a "contemporaneous record of progress" captured in the schedule at the time of each update. Reconstructed schedules, or schedules updated retroactively in bulk without a maintained data date, are treated with significant skepticism by adjudicators; they cannot demonstrate that the record reflects real-time knowledge.
3. During Disputes: You're Unarmed
Construction disputes live and die by contemporaneous records. The question is never just "did the delay happen?" It is "what did your schedule show at the time, what were the downstream impacts at the time, and what decisions did you make at the time?"
AACE RP 29R-03 identifies eight recognized methodologies for forensic schedule analysis. Of these, Windows Analysis - also called the "time slice" or "contemporaneous period" method - is broadly considered the most defensible. Rather than comparing the original baseline to the final as-built in one retrospective sweep, Windows Analysis divides the project into discrete time periods and analyzes delay within each window using the schedule that was actually current at that moment. Each window gets its own critical path analysis, its own delay attribution, its own causation story.
It is the closest thing construction disputes have to a reliable forensic instrument. And it is categorically unavailable when the data date was never properly maintained.
Here is why: each window is defined by the data date of consecutive schedule updates. The critical path you analyze within that window is the one that existed at that data date. If the data date was never advanced, or was advanced inconsistently, you cannot define the windows. You cannot establish what the critical path was at any given moment. The entire methodology collapses.
A schedule without data date discipline doesn't just weaken your Windows Analysis - it eliminates it. Every other methodology available to you is a step down in credibility: more reconstructive, more assumption-dependent, more vulnerable to attack. The GAO Schedule Assessment Guide rates data date discipline as a foundational criterion under schedule credibility. A schedule that cannot demonstrate this discipline does not pass basic credibility review.
What Good Looks Like
Good data date discipline is not complicated. It requires three things:
Cadence. The data date should be advanced at every update cycle - weekly for active projects, at minimum bi-weekly. It should match the schedule submission date in the contract. AACE RP 29R-03 and most major contract frameworks (including the ConsensusDocs scheduling provisions and many AIA supplementary conditions) treat this alignment as a baseline expectation, not a best practice.
Consistency. Actual start and finish dates should be entered contemporaneously, not retroactively. A schedule updated three months after the fact, with statused activities entered all at once, is forensically weak even if the data date is technically present. The DCMA assessment specifically evaluates whether actual dates are logically consistent with the data date; a batch retroactive update will typically fail this check.
Integration. The data date should be tied to the project's formal reporting cycle - the same date that goes on the narrative, the lookahead, and the owner submission. When the schedule and the report share a data date, they corroborate each other. When they don't, neither can fully stand alone.
This Is a Business Risk Conversation, Not a Scheduling Lecture
The people who need to read this are not schedulers. Schedulers generally understand data date. They know it matters. The reason it gets skipped is not ignorance - it is pressure.
Project managers who don't understand the forensic value of a properly maintained schedule treat data date updates as overhead. Owners who receive schedules as contract deliverables never ask whether the data date was advanced. Executives who review project dashboards don't know that the "green" schedule they're looking at may be legally incoherent.
The risk is not carried by the scheduler who skipped the data date. It is carried by the company - in the form of a delay claim that cannot be supported, a dispute that cannot be won, a project that went sideways with no contemporaneous record to explain why.
Scheduling without a data date is not a technical shortcut. It is an undisclosed liability, distributed across every project it touches, collectible at the worst possible moment.
The Bottom Line
When you hand a schedule to an owner, a subcontractor, or a court, you are making a claim about reality. You are saying: this is what we knew, and this is when we knew it.
Without a maintained data date, you cannot make that claim. You have a document that looks like a schedule, distributes like a schedule, and gets filed like a schedule - but cannot answer the one question that matters in every dispute, audit, and forensic analysis:
As of when, is this true?
If you cannot answer that question, your schedule is not a project record. It is a very organized guess.
References
- AACE International, Recommended Practice 10S-90: Cost Engineering Terminology
- AACE International, Recommended Practice 29R-03: Forensic Schedule Analysis
- AACE International, Recommended Practice 52R-06: Time Impact Analysis - As Applied in Construction
- DCMA, 14-Point Schedule Assessment
- Society of Construction Law, Delay and Disruption Protocol, 2nd Edition
- U.S. Government Accountability Office, GAO Schedule Assessment Guide: Best Practices for Project Schedules
About the Author
Nitin Bhandari is Co-Founder and CEO of Planera, where he is leading the shift toward modern, collaborative construction scheduling. With a background in building and scaling B2B SaaS and mobile technology companies, Nitin brings deep expertise in product strategy, go-to-market execution, and innovation. A Caltech graduate and multi-time founder, he is passionate about transforming CPM scheduling into a more intuitive, team-driven experience for the construction industry.
