Schedule version control keeps every issued program revision stored, dated and retrievable, so every stakeholder can identify the current version and any earlier version can be recalled and checked. ProjectPulse is a real-time construction schedule dashboard built by Project Scheduling that does this as part of the normal program update cycle.
What Is Schedule Version Control on a Construction Project?
Schedule version control means each program update is kept as issued, with its data date and issue date, not overwritten by the next one. It covers the native P6 file, the reports issued with it, and a record of how each update moved against the baseline.
In practice that means three things:
The current revision is clearly identified.
Earlier revisions are kept as issued. Every one can be retrieved with its reports, exactly as it went out.
Movement is measured, not inferred. Each update gets a baseline comparison, so shifts in dates, float and the critical path are visible.
Most projects manage the first point informally and lose the other two. Program files get renamed or saved over the last update, and the issued PDFs drift away from the native file that produced them.
Why Do Stakeholders End Up Working From Different Program Versions?
Programs are usually distributed as email attachments and shared-drive files, so every update puts another copy into circulation. Site teams work from last month’s lookahead, commercial teams claim against superseded dates, and nobody can say with confidence which revision is current.
The problem grows with the number of people relying on the program. A site supervisor sequencing the next fortnight, a commercial manager preparing a progress claim, a client representative checking your update and a board reviewing forecast completion all need the same data at the same revision. When the program travels by email, each of them is one missed attachment away from making decisions on superseded logic.
Chasing files and confirming revisions takes time. The bigger cost is trust: once stakeholders question which version is current, they stop relying on the program.
Why Does Program Revision History Matter in a Delay Dispute?
Delay and extension of time assessments rest on the contemporaneous record. If you can produce every update as it was issued, you can show when an activity became critical and what changed at each update. If revisions were overwritten, that evidence has to be rebuilt after the fact, and a rebuilt record is easier to challenge.
A complete program revision history shows:
when float began to erode
when an activity moved onto the critical path
which logic changes occurred around a delay event.
Those revisions are important inputs to forensic delay analysis, alongside progress records, correspondence and the contract. They form part of the contemporaneous record used to investigate and substantiate cause and effect in an extension of time claim. A baseline comparison shows that dates moved. It does not by itself show why they moved or who is responsible.
As an illustrative scenario: the 30-Jun-26 update shows commissioning moving onto the critical path. The 31-May-26 update and its issued reports are still available, so you can see what changed between the two updates and start tracing the reason while the people involved are still on site.
The same history is useful well before any dispute. Comparing each update with the baseline can help identify three kinds of problem early enough to act on:
float that is eroding steadily
coordination problems between trades
resourcing assumptions that no longer match site conditions.
What Is ProjectPulse?
ProjectPulse is a real-time construction schedule dashboard built by Project Scheduling. It shows live critical path status against the baseline, keeps every program revision as a complete contemporaneous record, and scales from a single project to an enterprise portfolio. It runs on live projects across construction, mining and resources, oil and gas, power and water, utilities and renewables, heavy industrial and infrastructure.
ProjectPulse always shows the current project schedule, and the dashboards and revision history refresh with every update. The program, its issued reports and the supporting documents sit in one secure location, accessible from desktop, tablet or mobile. The ProjectPulse product page covers the dashboard in detail.
How Does ProjectPulse Fit Into the P6 Update Cycle?
ProjectPulse works as a Primavera P6 dashboard for everyone who relies on the program but doesn’t work in P6. It slots seamlessly into the normal update cycle. Program development and updating in P6 don’t change, and each update appears in ProjectPulse as part of the standard process.
Each update is compared against the baseline. The dashboards show current critical path status, schedule health metrics and forecast completion against that baseline. When the baseline changes, later updates are measured against the new one. The previous baseline is kept, and earlier updates can still be viewed against it. That answers a common question in any dispute: which update was current on a given date, and which baseline it was measured against.
Because every update is captured as it is issued, the record builds in lockstep with progress on the project, not in hindsight. For how updates are built and quality-checked, see Primavera P6 scheduling.
Who Can See the Program, and How Much?
Access is set for each stakeholder group. Clients and other external stakeholders can have their own page and login, showing anything from full program detail down to milestones and forecast completion only.
Role-based views let you choose what each audience sees, so commercially sensitive detail can be kept within the project team while clients, financiers or board members get the view they need.
What Do the Three ProjectPulse Tiers Include?
ProjectPulse comes in three tiers matched to the scale of the project and the organisation.
Foundation: real-time dashboards, full revision history and secure stakeholder access.
ProjectPulsePro: adds Monte Carlo simulation, with P0, P50, P80 and P90 completion forecasts.
Enterprise: consolidated dashboards, cross-project reporting and access controls across the organisation, custom built to your organisation’s specification.
Probabilistic forecasting suits projects facing uncertainty over approvals, weather windows or resource availability, and supports risk-informed board reporting. A probabilistic forecast does not by itself establish entitlement to an extension of time. The method is covered in schedule risk analysis.
How Can You See ProjectPulse Working?
A live demonstration is available on request. It shows the construction schedule dashboard, the baseline comparison and the stakeholder view on an example program.
Frequently Asked Questions
Does ProjectPulse replace Primavera P6?
No. P6 remains the scheduling tool. ProjectPulse presents each P6 update against the baseline and keeps the record of every revision.
Does it add work for the scheduling team?
No. ProjectPulse fits seamlessly into the standard update process, so the scheduling team keeps working in P6 as normal.
Which projects is it suited to?
Projects where several stakeholders rely on the same program, across construction, mining and resources, oil and gas, power and water, utilities and renewables, heavy industrial and infrastructure.
Is the Monte Carlo analysis included in every tier?
No. Monte Carlo simulation and P0, P50, P80 and P90 forecasts are included in ProjectPulsePro only.
