A SYNCHRO 4D sequence is not the controlling project schedule
Bentley describes SYNCHRO 4D as linking schedule and model information to visualize construction sequences; project teams still need baseline, data-date, logic, update, approval, and work-authorization lineage.
Editorial figure by Contractor Systems Index. Source context: Bentley SYNCHRO.
The direct answer
A 4D sequence is a model-based representation of schedule information, not automatic proof of the controlling project schedule. Before using it for coordination, commercial review, or field direction, the team needs to identify the source schedule and version, contractual status, data date, model revision, linking rules, assumptions, approvals, and the exact scenario being displayed.
Bentley publicly describes SYNCHRO 4D as connecting schedules and 3D models so teams can plan, visualize, analyze, and communicate construction sequences and progress. Those are provider statements about product scope. They do not independently establish configuration, schedule quality, model completeness, field adoption, contractual effect, or outcomes on a particular project.
Freeze the source records
The 4D record should point to the project, contract or work package, approved baseline identifier, current schedule update, native schedule file and import time, data date, calendars, activity identifiers, logic and constraints, status method, responsible scheduler, model authoring sources, coordination model version, and object identifiers. A new import should create a new lineage record.
The platform can also support what-if analysis or internally created schedules. Those scenarios need unmistakable labels and owners so they are not confused with the accepted update. Deleted logic, remapped objects, summarized activities, temporary objects, and lagging model revisions can make a compelling animation diverge from both the schedule network and current field conditions.
Test links and status before acting
Activity-to-object mapping should expose included and excluded scope, one-to-many relationships, location and work-package logic, temporary works, procurement or design activities without model objects, and quality checks. A visually complete sequence may omit non-modelled activities that control access, approvals, material availability, testing, turnover, or commissioning.
Progress status needs a named source, cutoff time, measurement method, quantity or completion basis, reviewer, and exception process. A colored object is not field acceptance, installed quantity, earned value, payment entitlement, or safe readiness for successor work. Reconciliation should connect the model view to daily reports, quantities, inspections, schedule status, and approved corrections without treating any one record as sufficient.
Keep coordination and contract authority distinct
Teams can use a 4D view to test access, logistics, temporary conditions, interfaces, handoffs, and alternative sequences. Turning that insight into action still requires the contractually defined process for schedule acceptance, design coordination, request for information, change, work planning, permits, owner or designer direction, and superintendent or trade authorization.
Retain the scenario shown, meeting date, participants, observations, decisions, action owners, due dates, and subsequent schedule or model changes. Do not infer delay entitlement from visualized variance; entitlement depends on contract terms, notices, causation, contemporaneous records, schedule analysis, and authorized determination. The useful 4D control is traceability from visual insight to accountable project record.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Contractor Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.