4D BIM scheduling in 2026: Synchro vs Navisworks Timeliner vs Bexel Manager honest review

The programme was already six weeks late when the client asked for an animation.

Not a Gantt chart. Not a milestone table. An animation — one that showed the tower going up floor by floor, with the superstructure steel rising ahead of the concrete cores, the curtain wall following two levels behind, the MEP rough-in tracking two levels below that. The client's development director had seen something similar at a conference and wanted it for a board presentation in three weeks.

That request arrived on a Tuesday morning into the inbox of the project's 4D BIM specialist, a structural-background coordinator named Marcus who had been managing Navisworks Timeliner for the past eight months on a 28-storey mixed-use tower in the inner suburbs. Marcus had a working 4D model. He had 340-odd schedule tasks linked to Revit geometry. He had a Timeliner simulation that ran end-to-end without errors. What he did not have was anything that looked like a polished client-facing animation — the Timeliner playback was a tool for the project team, not a boardroom presentation, and there was no straightforward path to make it into one.

The request also surfaced a second problem. The programme had been revised twice since the 4D model was first set up, and the task linkage had drifted significantly. New tasks had been added in Primavera P6, renamed tasks had broken the ID-based linkage to Revit elements, and the simulation was now showing structural elements appearing mid-animation in the wrong sequence because nobody had updated the 4D model after either programme revision. Marcus spent four hours that week just auditing the linkage against the current programme before he could start thinking about what the animation would look like.

That week — the audit, the link repair, the export attempts, the conversations about whether a different tool would have handled the programme revisions more gracefully — was the catalyst for the evaluation that forms the basis of this article. Over the following two months, the project team ran three platforms — Navisworks Timeliner, Synchro Pro, and Bexel Manager — against the same project model and programme. This is what they found.

The short version: each platform is genuinely good at something different, the right choice depends heavily on what you're going to do with the 4D model after it's built, and the friction you encounter on the way in (schedule import, object-to-task linking) predicts most of the ongoing maintenance burden. The long version follows.

What 4D BIM Actually Does — and Where It Breaks

The technical mechanism

4D BIM adds a time axis to a federated 3D model. At its simplest, it is a synchronisation engine: tasks from a construction programme are linked to geometric objects in a BIM model, and a simulation renders the model state at any point along the project timeline, showing which elements exist, which are under construction, and which have not yet started.

The value proposition is real. McKinsey Global Institute's 2017 analysis of global construction found construction productivity growing at roughly 1% per year globally against 2.8% for the total economy — and one of the consistent findings across productivity studies in construction is that schedule visualisation, particularly 4D BIM, reduces rework rates and improves on-site sequencing decisions. The BIM Forum's 2022 4D BIM Use Case paper documents specific applications: constructability reviews, site logistics planning, crane lift sequencing, phased occupancy planning, and regulatory submissions to authorities requiring construction staging visualisations.

The mechanism requires three inputs: a federated BIM model, a construction programme, and a linking definition. The linking definition is the mapping between programme tasks and model objects — it answers the question "which physical elements appear, are under construction, or disappear during each task?" That mapping can be done manually (task by task, object by object), rule-based (all objects in a model layer named "STR-Level-05" link to tasks tagged "L5"), or automatically (the tool infers linkage from shared attributes such as floor level, zone code, or workpackage parameter).

In practice, every platform starts with some degree of manual intervention for the initial setup, and then — critically — must maintain that linkage every time the programme changes. This is where most 4D BIM implementations quietly fall apart. The model-to-task link is brittle in ways that are not obvious when the tool is first demonstrated. Task IDs change during programme revisions. Object names change during design revisions. Tasks are added at a level of granularity finer than the model geometry can represent. Objects are grouped in the model in ways that do not correspond to the task breakdown in the programme. The result is an accumulating drift between the 4D model and the current programme — a drift that, if unmanaged, eventually makes the 4D model useless as a real-time coordination tool and keeps it alive only as a static animation from month three of the project.

Schedule import fidelity — where the round-trip fails

Every platform evaluated accepts Primavera P6 XER and Microsoft Project MPP as primary schedule formats. The import is rarely as clean as the vendor documentation implies.

Primavera P6 XER files carry rich schedule data: WBS hierarchy, task constraints (Start No Earlier Than, Finish No Later Than), resource assignments, activity codes, calendar definitions, and custom fields. What matters for 4D linkage is primarily the WBS hierarchy and the task identifiers — the unique Activity ID that provides a stable hook for the model-to-task link. The problem is that XER round-tripping through the 4D tool frequently loses or reorganises the WBS hierarchy, flattening multi-level WBS into a single task list or reinterpreting the hierarchy incorrectly. This means that a programme with 1,200 tasks organised into a six-level WBS may import as a flat list of 1,200 tasks in the 4D tool, which eliminates the ability to use WBS-level groupings for object linkage.

Microsoft Project exports to MPP or MSPDI (XML). The MSPDI format is generally more reliably imported than MPP because it is text-based and the field mappings are more transparent. The risk with MSP is predecessor logic — complex lag and lead relationships, summary task predecessors, and external task links do not always translate correctly, which can alter the critical path in the imported version relative to the live programme.

Object-to-task linking — the productivity bottleneck

The rule of thumb among experienced 4D specialists is that the initial model-to-task linkage takes one hour per 50–80 tasks for a first-time user, and 30–40 minutes per 50 tasks once the practitioner is proficient. On a 1,200-task programme linked to a 30-storey tower model, that initial linkage phase alone represents three to four working days of dedicated effort — before a single simulation frame has been rendered.

Every platform has mechanisms to reduce this through automation — rule-based matching, batch operations, shared parameter matching — but the practical speedup depends on how consistently the model and programme have been structured in advance. If the Revit model uses a consistent Level parameter and the P6 programme uses Activity Codes that map to levels, automated linkage can work. If the programme tasks are named inconsistently ("Level 5 Slab Pour" in one section, "Concrete pour L05" in another, "5th floor concrete" in a third), automated matching fails and the coordinator falls back to manual selection for every task.

The LOD mismatch problem is equally important. A programme task "L05 Structural Steel — East Bay" may correspond to fifty individual Revit structural framing elements in the model. Linking that task requires selecting all fifty elements as the task's geometry. If the model subsequently adds elements to that bay (additional bracing, connection plates, miscellaneous steel), those elements are not automatically linked to the task — the coordinator must re-open the linkage editor and add them manually. This is the vector through which the drift described in the lede scenario accumulates over time.

The Pattern — How Each Platform Approaches the Same Problem

The three platforms in this evaluation share a common architecture: federated model viewer, schedule import engine, linkage editor, and simulation renderer. The philosophical differences between them, however, are substantial and predictive of which workflows each platform serves well.

Navisworks Timeliner — embedded coordination tool

Navisworks Timeliner is not a standalone 4D product. It is a module within Navisworks Manage, Autodesk's federated model coordination platform. This is both its greatest advantage and its clearest limitation.

The advantage is integration. On any project already using Navisworks for clash detection and coordination review, Timeliner is available in the same application, working against the same NWD/NWF file, using the same selection sets and search sets that the coordination team has already built. Adding a 4D layer to an existing coordination workflow is a matter of opening the Timeliner dock and importing the programme — there is no separate application to license, install, or maintain, and no file format conversion between the coordination model and the 4D model.

The schedule import in Navisworks Timeliner accepts Primavera P6 XER, Microsoft Project MPP/MSPDI, and CSV. The CSV format is a manual fallback that requires a specific column structure (Task Name, Start, End, optional Task Type), and it loses all hierarchical structure — but it works when the project scheduler will not export XER or MPP and the coordinator needs to get something into the tool quickly. The Navisworks help documentation for Timeliner field mapping explains the schedule field map in detail — a step that is not optional and that many first-time users skip, producing incorrect task durations.

Object-to-task linking in Timeliner is manual by default. The workflow is: select the task in the Timeliner panel, switch to the 3D viewport, select the model objects that correspond to that task, and click "Attach Current Selection." This produces a reliable, auditable link — each task can be inspected to see which objects are attached — but it scales poorly beyond a few hundred tasks. Navisworks Timeliner also supports auto-attach via rules that match task name to object property (for example, matching tasks with "Level 5" in the name to objects where the Revit Level parameter equals "Level 5"), but the text-matching rules are primitive and sensitive to naming inconsistencies.

The simulation output in Timeliner uses a task-type system: Construct, Demolish, Temporary, or None. "Construct" means the element appears in the model at task start and remains visible after task end. "Demolish" means the element disappears at task end. "Temporary" means the element is visible only during the task duration (useful for formwork, falsework, and temporary structures). "None" means the object remains unchanged throughout.

Animation export from Timeliner is functional but limited. The tool exports to AVI or WMV (Windows-only) at a user-defined frame rate, and the quality depends on the Navisworks viewpoint and display settings at the time of export. There is no built-in rendering pipeline — what you see in the Navisworks viewport is what you get in the export. For internal team use and project meetings, this is often sufficient. For client-facing boardroom presentations requiring rendered quality — which was Marcus's actual requirement — it is typically not.

Synchro Pro — purpose-built 4D with resource modelling

Synchro Pro is Bentley Systems' dedicated 4D BIM platform. Unlike Timeliner, it is a standalone application with its own data model — federated models are imported into Synchro (via NWC, IFC, DWG, DGN, Revit native, or SketchUp), and the 4D model lives in Synchro's proprietary SPP file format.

The schedule import capability in Synchro Pro is the most capable of the three platforms evaluated. P6 XER, MSP, Asta Powerproject PP, and CSV are all supported. More significantly, Synchro maintains a live link to the source schedule: when the P6 programme is updated, a refresh in Synchro pulls the changes without requiring a full re-import, and the platform preserves the existing object-to-task linkage while updating only the date and logic changes. This live link is the feature that most directly addresses the drift problem described in the lede — provided that the schedule revisions do not change Activity IDs and do not fundamentally reorganise the WBS structure.

Resource modelling is a Synchro strength that neither Timeliner nor Bexel matches in comparable depth. Within Synchro, resources — labour, plant, materials — can be assigned to tasks with quantities, production rates, and calendars. The 4D simulation then visualises not just which elements are being built, but how many workers, how many cranes, and how much plant are on site at each point in the programme. For crane lift studies, site logistics visualisations, and labour histograms linked to schedule, this capability is substantially more advanced than Timeliner's task-type system.

Object-to-task linking in Synchro uses a combination of manual assignment and rule-based automation. The rule engine is more powerful than Timeliner's text matching — Synchro can match objects to tasks based on any object property via attribute conditions, and it supports group operations that apply a rule to a batch of tasks simultaneously. In practice, a well-prepared model (consistent Level parameters, zone codes, workpackage identifiers as shared parameters) can achieve 60–80% automated linkage coverage, with the remaining 20–40% requiring manual attention. Bentley's Synchro training documentation provides worked examples of the resource assignment and rule-based linking workflows.

The simulation renderer in Synchro produces significantly higher-quality output than Timeliner's viewport export. Synchro supports rendered animation export via integration with Bentley's Luxology-based rendering pipeline, and the output can be exported to MP4 at high resolution. For a boardroom presentation animation — which was the triggering requirement in this evaluation — Synchro was the only platform that produced output the client's development director considered presentation-ready without additional post-processing. The camera path can be keyframed, the task transition effects (element appearance, disappearance, temporary structures) are smoother, and the export pipeline handles large models more robustly than Timeliner's AVI export.

The trade-off is application complexity and licensing cost. Synchro Pro is a sophisticated engineering application with a significant learning curve. Bentley's enterprise licensing structure ties it to the Bentley SELECT or Virtuosity subscription model, and the per-seat cost is substantially higher than Navisworks (where Timeliner is included in the Manage licence). A 4D specialist comfortable in Navisworks who moves to Synchro should expect two to three weeks of focused training before they are productive on a live project.

Bexel Manager — integrated 4D/5D/6D, IFC-native

Bexel Manager is a Czech-developed platform (Bexel Consulting, s.r.o.) that takes a different architectural position than either Timeliner or Synchro. Rather than being primarily a 4D simulation tool with additional features bolted on, Bexel is an integrated project controls platform that combines 4D scheduling, 5D cost management, and 6D operations/sustainability analysis in a single environment.

The defining characteristic of Bexel is its native IFC handling. Where Navisworks and Synchro treat IFC as one import format among several, Bexel was designed around IFC as the primary exchange format. The IFC 4.3 schema includes schedule-related entities (IfcWorkSchedule, IfcTask, IfcRelSequence) that Bexel can read directly — meaning that a project using ISO 19650-compliant IFC workflows can, in principle, import both model and schedule from a single IFC file rather than maintaining a separate programme file. In practice, Revit's IFC export does not yet fully populate the work schedule entities, so a separate schedule import is still required for most projects — but the architecture anticipates an ISO 19650 workflow where the IFC container is the single source of truth for both geometry and schedule.

Bexel's 5D capability is the most integrated cost-quantity engine of the three platforms. Once model objects are linked to programme tasks, Bexel can apply unit costs to each task-element pair and generate time-phased cost curves: an S-curve showing planned expenditure over the programme duration, derived directly from the 4D model rather than from a separate quantity surveying exercise. This is the platform's strongest commercial case for project controls teams that currently manage schedule and cost in separate tools with manual reconciliation.

Object-to-task linking in Bexel uses a classification-based approach. Bexel recognises IFC object types and can automatically apply cost and schedule rules based on object classification — an IfcBeam element of a certain material specification can be automatically linked to a task type ("Structural Steel Installation") and a unit cost, without the coordinator manually selecting each element. This is powerful when the model has been classified consistently (using Uniclass 2015 or OmniClass codes in the IFC properties), and significantly less useful when it hasn't.

For federated model support — multiple discipline models aggregated into a single coordination model — Bexel handles IFC federation natively, and its viewer can navigate a federated model with comparable performance to Navisworks for models in the 1–3 GB range. Above that range, performance degrades more noticeably than Navisworks, which is optimised for large model navigation and uses a streaming geometry engine developed over two decades of Autodesk investment.

The animation export in Bexel is competent but less polished than Synchro's rendered output. Bexel produces MP4 simulation videos directly, but without the keyframe camera control and rendering quality of Synchro Pro. For internal review and owner communications, the output is adequate. For the specific boardroom animation scenario described in this article, it would require post-processing in a video editing application to match Synchro's output quality.

The Fix — Building and Maintaining a Reliable 4D Model

Platform selection by use case

The decision between platforms is not primarily a feature comparison. It is a use-case prioritisation: what is the 4D model actually for, who will maintain it, and over what project duration?

1. Step 1 — Identify the primary 4D deliverable

   Before selecting a platform, answer this question explicitly: what does the stakeholder actually need to see, and who is the primary audience?

   If the deliverable is an internal coordination tool — used by the project team to review sequencing, identify logistics conflicts, and sequence clash resolution — Navisworks Timeliner is the path of least resistance on an Autodesk-stack project. The coordination team is already in Navisworks. Adding Timeliner adds no training overhead, no additional licensing, and no file conversion step.

   If the deliverable is a client-facing animation for owner, developer, or authority presentations — something that needs to look like a production video rather than a software simulation — Synchro Pro is the appropriate tool. The rendered export quality is the justifying feature.

   If the deliverable is an integrated project controls model combining schedule and cost — a 4D/5D platform that drives time-phased cost reporting, earned value analysis, and S-curves — Bexel Manager's integrated cost engine is the relevant feature, and the additional complexity is justified by eliminating the manual schedule-to-cost reconciliation that otherwise happens in Excel.

2. Step 2 — Audit programme structure before any linking work

   Regardless of platform choice, the programme must be audited for 4D compatibility before import. This is a one-to-two-day task on a typical tower project programme.

   The audit checks four things:

   Activity ID stability: Are Activity IDs unique, permanent, and consistent across revisions? Programmes where the scheduler routinely deletes and recreates tasks (rather than retaining IDs and updating dates) will break ID-based object linkage on every revision.

   Task granularity vs. model granularity: Is the programme at a level of detail that the model can support? A programme with a single task "Level 5 Structural Steel" can be linked to all Level 5 structural elements as a group. A programme with thirty tasks covering individual steel connections at Level 5 requires the model to have those connections as separately identifiable objects — which LOD 300 models typically do not.

   Consistent naming conventions: Do task names follow a pattern that can be used for rule-based matching? "STR-L05-East-Steel-01" is matchable. "Misc steel works fifth floor area east sector 1a" is not.

   WBS hierarchy: Does the WBS structure align with the model's zone and level organisation? Misalignment between WBS and model structure is the most common source of manual linking overhead.

3. Step 3 — Establish the linkage convention and document it in the BEP

   The linkage convention defines how model objects are linked to programme tasks. This convention must be documented in the BIM Execution Plan (BEP) before the first linkage session, not reverse-engineered after.

   A workable convention for a tower project:

   • Primary structural elements: linked at task level by floor and structural system. Tasks at the WBS level "Structural — Level N — Concrete Pour" link to all concrete elements at Level N by category and level parameter.
   • MEP systems: linked at task level by system type and zone. Tasks "MEP — Mechanical — L05 — Zone A" link to all mechanical elements in Zone A at Level 5 by system name parameter.
   • Facade: linked at task level by bay or elevation. Tasks "Facade — Grid B-C — Level 04-06" link to curtain wall panels in that grid range by marking family instance parameters.
   • Temporary works: linked with task type "Temporary" — appears at task start, disappears at task end. Formwork, falsework, tower cranes, hoarding.

   Record the convention in the BEP, version-control it, and circulate it to every discipline model author. A convention that only the 4D specialist knows will not survive a personnel change.

4. Step 4 — Run the initial linkage in structured passes

   The initial linkage session should be structured as a series of passes, not a single marathon effort:

   Pass 1 — Automated linkage: Apply rule-based matching across all tasks where naming conventions allow it. In Synchro and Bexel, this can cover 60–80% of tasks on a well-prepared model. In Navisworks Timeliner, the text-matching rules will cover less ground, but the principle still applies.

   Pass 2 — Level-by-level manual audit: For each floor level, open the linked tasks and verify that the correct objects are attached. This catches both missed elements (objects that should be linked but aren't) and spurious links (objects attached to the wrong task because the name-matching rule was too broad).

   Pass 3 — Temporary works and logistics: These are almost always manual — formwork families, crane families, hoarding, temporary roads. Link them task by task with "Temporary" task type.

   Pass 4 — Simulation playback audit: Run the simulation from start to finish and watch for sequencing anomalies: elements appearing before their predecessor tasks complete, elements disappearing mid-task, structural elements appearing in the wrong sequence relative to the programme logic. Fix each anomaly at its source (wrong task type, wrong task link, wrong task dates).

5. Step 5 — Establish the programme revision protocol

   Define in advance how the 4D model will be updated when the programme changes. This protocol should specify:

   • Who is responsible for the 4D model update (typically the 4D specialist, not the project scheduler).
   • What triggers a 4D update (programme revision that changes any task dates or Activity IDs, not just minor tweaks).
   • How quickly the 4D model must be updated after a programme revision (typically within one coordination cycle — one week on most large projects).
   • What happens to existing object-task links when a task is deleted and replaced (in Navisworks Timeliner, links are lost; in Synchro, links are preserved if Activity IDs are retained).

   Document this protocol in the BEP. Enforce it through the project's information management workflow.

The specific Navisworks Timeliner maintenance workflow

Because Navisworks Timeliner does not maintain a live schedule link, the programme revision workflow requires more care than Synchro's refresh mechanism.

When the programme is revised, the correct workflow is:

1. Export the updated programme from P6 or MSP in the same format used for the original import (XER for P6, MSPDI for MSP).
2. In Timeliner, use "Rebuild Task Hierarchy" → "Delete All Tasks and Rebuild" (not "Add or update tasks without deleting") if Activity IDs have changed. If only dates have changed and IDs are stable, use "Add or update tasks without deleting" to preserve existing linkage.
3. After the rebuild, run a linkage audit: use Timeliner's "Check for missing Tasks" function to identify objects that were linked to tasks that no longer exist.
4. Re-link any objects whose tasks were deleted or renamed.
5. Run the simulation playback audit from Step 4 of the workflow above.

The "Add or update tasks without deleting" path is substantially faster but requires that Activity IDs be stable across revisions. If the project scheduler has a habit of deleting and recreating tasks instead of updating dates on existing tasks — which is common in organisations where P6 is used informally — this path will accumulate orphaned links over time, and the 4D model will diverge from the programme in ways that are not immediately visible.

Synchro Pro — live link and resource modelling workflow

The Synchro live P6 link substantially reduces the maintenance burden for programme revisions, but it introduces its own discipline requirements. The link is configured by pointing Synchro at the P6 database (via P6 API connection, not file export) and mapping the Synchro project to the P6 project. From that point, Synchro can pull schedule updates via "Refresh Schedule" — a process that takes two to five minutes depending on project scale.

The risk in the live link is that it follows changes instantly, including changes you do not want the 4D model to reflect. If the scheduler is actively revising the programme in P6 and the 4D specialist refreshes at the wrong moment, the 4D model picks up a partially revised programme with inconsistent task logic. Standard practice is to agree a "locked" revision window with the scheduler — typically once per week, following the scheduler's programme lock — and only refresh the Synchro link after the P6 revision is finalised and issued.

Resource modelling in Synchro adds a layer of value that is particularly useful for client-facing presentations that need to show more than element appearance and disappearance. A tower project crane configuration — with the tower crane's radius, maximum lift capacity, and working hours linked to the tasks it serves — can be animated to show which crane is active during which task, the lift radii at each phase, and the hand-off between cranes as the building rises. This level of detail is beyond Timeliner and Bexel without significant additional modelling effort.

Bexel Manager — 5D integration and IFC classification workflow

Bexel's integrated 5D capability is the most operationally complex of the three workflows, but also the most valuable for owner-side project controls teams who need live cost reporting integrated with schedule.

The workflow adds a classification layer to the standard 4D linkage: once objects are linked to tasks, Bexel applies unit cost rates from a rate library. The rate library can be built from first principles (material + labour + plant unit costs per element type), imported from an estimating tool, or mapped from a BOQ (Bill of Quantities). The output is a time-phased cost model: the platform can show, at any point in the programme, how much cost has been incurred to date, what the planned expenditure profile looks like, and what the earned value is against the schedule.

For the IFC-native workflow to deliver its potential, model authors must use consistent IFC classification. This means applying Uniclass 2015 codes (or equivalent) to all model objects during authoring — a requirement that, in practice, is enforced through Revit's IFC export mapping or through a post-processing step that applies classification based on Revit category and type. Without consistent classification, Bexel's automated cost assignment falls back to manual rule configuration, and the efficiency advantage over Synchro's manual approach narrows significantly.

Anti-patterns

Linking at the wrong level of granularity

The most common mistake in 4D BIM setup is building the linkage at a finer level of granularity than the programme actually supports — or, conversely, at a coarser level than the visual simulation requires.

❌ Anti-pattern: Linking individual Revit structural connections (base plates, splice plates, gussets) to separate programme tasks, when the programme has a single task "L05 Steel Installation" that covers all structural steel at Level 5.

Why it fails: The programme task "L05 Steel Installation" has one set of dates. Linking individual connections to it adds no schedule information — all those objects will appear and disappear on the same dates. The visual simulation is no more informative than if the entire floor's steel were linked as a group, but the maintenance burden is fifty times higher.

Do instead: Link all structural steel elements at Level 5 to the single task "L05 Steel Installation" as a group. If finer sequencing is required (east bay before west bay), add that granularity to the programme first, then link.

❌ Anti-pattern: Running a single task "Structural Frame" that covers all structural elements for the entire building.

Why it fails: The simulation shows all structural elements appearing at task start and the building is fully framed at task end. There is no progressive construction sequence visible — which eliminates the primary value of 4D visualisation.

Do instead: Break structural tasks by floor level at minimum, and by zone or bay where the programme supports it. The simulation must show elements appearing in the correct construction sequence to be useful.

Using the 4D model as a planning tool instead of a communication tool

❌ Anti-pattern: Treating the 4D model as the primary source of schedule truth — making programme changes in the 4D tool rather than in the master programme and relying on the 4D model as the record of the current sequence.

Why it fails: The 4D model is a representation of the programme linked to model geometry. If the programme changes outside the 4D tool (as it always does — the scheduler owns the programme), the 4D model becomes stale. If the 4D coordinator starts making schedule changes inside the tool, two versions of the programme exist simultaneously, and nobody knows which is current.

Do instead: Maintain a clear ownership separation. The project scheduler owns the programme in P6 or MSP. The 4D specialist owns the 4D model representation of that programme. Changes flow one way: from the programme into the 4D model, not the reverse.

Skipping the playback audit after every programme revision

❌ Anti-pattern: Updating the programme link in the 4D tool after a revision and distributing the updated simulation without running a full playback audit.

Why it fails: Programme revisions frequently produce sequencing anomalies in the 4D model that are not visible from the task list — elements appearing before their predecessors, elements disappearing mid-construction-activity because a task type was set incorrectly, temporary structures remaining visible after their task ends. These anomalies are immediately obvious in the simulation playback but invisible in the task list.

Do instead: After every programme revision update, run the simulation from start to finish in real time (or at 2x speed), watching specifically for elements appearing and disappearing at unexpected times. Fix every anomaly at its source before distributing the updated simulation.

Client-facing animation directly from Timeliner without post-processing

❌ Anti-pattern: Exporting the Timeliner AVI and sending it directly to a client expecting a polished animation.

Why it fails: The Timeliner viewport export captures the Navisworks display exactly as it appears in the software — construction line colours, element outlines, and the default Navisworks background. It does not produce the rendered quality that clients typically expect from a construction animation they are going to show at a board meeting. The output looks like software output, not a presentation-quality video.

Do instead: Either use Synchro Pro for presentations requiring rendered quality, or post-process the Timeliner export in a video editing tool (DaVinci Resolve, Adobe Premiere) to add backgrounds, branding, title cards, and colour grading. Alternatively, use Autodesk's 3ds Max or Navisworks Presenter for a rendered output path from the same model.

Treating Bexel's 5D output as a substitute for a QS sign-off

❌ Anti-pattern: Using the Bexel time-phased cost output as the cost basis for formal project reporting without independent quantity surveyor verification.

Why it fails: The Bexel cost model is only as accurate as the rate library and the quantity take-off derived from the model. Model quantities at LOD 300 are indicative, not fabrication-accurate. A structural concrete element modelled at LOD 300 may have a volume within 5–10% of the fabrication quantity — but that 5–10% error, multiplied across a $150M tower project, is $7.5–15M of cost uncertainty in the S-curve. This is not the tool's fault; it is a LOD limitation.

Do instead: Use Bexel's time-phased cost output as a programme-side cross-check and early warning indicator, not as a substitute for QS-certified cost reporting. Any formal project cost report should be certified by the quantity surveyor against the current contract documents, not derived from the 4D model.

Case Studies — Three Projects, Three Platform Choices

Case study 1: 28-storey mixed-use tower, Synchro Pro for client animation

This is the project that opened the article. The project team was running Navisworks Manage for coordination and had an existing Timeliner model at the time of the client animation request. The animation requirement — a rendered video showing the progressive construction of the tower floor by floor — could not be met by Timeliner's export quality without significant post-processing effort.

The team elected to import the model and programme into Synchro Pro for the animation deliverable only — not to replace Timeliner for ongoing coordination use. The Revit models (architectural, structural, MEP) were exported to NWC from Navisworks and imported into Synchro. The P6 programme was imported via XER. The initial linkage took approximately 18 hours of specialist time over three days — comparable to the Timeliner linkage that already existed, but built from scratch in Synchro's interface.

The camera path was keyframed to rise with the building — starting at ground level with demolition and excavation, rising floor by floor with the structural frame, then tracking the curtain wall and MEP fit-out. The rendered output was MP4 at 1920×1080, 30 frames per second, approximately 8 minutes long for a 28-month programme at 10 seconds per month. The client's development director used it in the board presentation and rated it positively.

The lesson: for a one-off animation deliverable, the cost of establishing a Synchro model in parallel with an existing Timeliner workflow is approximately 3–4 days of specialist time. For a project team that anticipates multiple client animation deliverables, moving the primary 4D workflow into Synchro from the start — rather than running parallel tools — would save that overhead per deliverable.

On this project, the total cost of the 4D animation deliverable — specialist time plus Synchro Pro trial licence — was approximately 25 days of coordinator time across the evaluation, setup, and production phase. That figure is an observation from this project team, not a general benchmark.

Case study 2: Infrastructure linear project — cut/fill visualisation

A road and rail corridor project in a mountainous terrain context used Bexel Manager as the primary 4D platform, chosen specifically for its IFC-native handling of a geotechnical model and its integrated volume calculation capability.

The geotechnical model (cut/fill volumes, soil classification layers, temporary drainage structures) was authored in Civil 3D and exported to IFC. The structural model (bridges, retaining walls, culverts) was authored in Tekla Structures, also exported to IFC. Bexel's IFC federation handled both without conversion to a proprietary format — a significant advantage over Navisworks, which would have required NWC export from both tools.

The 4D simulation was used to validate the cut/fill sequence: that excavation volumes were balanced month by month against the fill requirements at downstream locations, and that temporary stockpile areas were available when needed. Bexel's quantity engine calculated cut and fill volumes directly from the model geometry at each programme step, and the team used this to validate the earthworks balance across the programme rather than relying on a separate spreadsheet exercise.

The limitation encountered was Bexel's performance with the geotechnical model — the terrain model contained approximately 2.8 million triangulated faces, and navigation in Bexel became sluggish at this scale. The team addressed this by working with a simplified terrain representation for 4D review and reserving the full-resolution model for specific cut/fill section analysis. This is a platform limitation that Bexel's development team acknowledges and is working on; Bexel Consulting's release notes document ongoing performance improvements in each version.

Case study 3: MEP-heavy fit-out, Navisworks Timeliner for coordination

A high-bay data centre fit-out project — 18,000 m² of floor area, complex MEP, phased occupancy — used Navisworks Timeliner exclusively for 4D coordination. The project team had no client animation requirement; the 4D model was an internal coordination tool used to sequence MEP installation and verify that phased occupancy milestones were achievable given the MEP installation sequence.

Timeliner was the correct choice here. The coordination team was already in Navisworks for clash detection, and the clash-to-4D linkage — knowing which clashes had to be resolved before a given MEP installation task started — was genuinely valuable. The team built a convention where Tier 1 clash BCF topics were tagged with the earliest programme task that would be blocked if the clash was unresolved, and the 4D simulation was used to calculate the resolution deadline.

The programme had 620 tasks linked to the MEP and structural models. The initial linkage took four days of specialist time. The programme was revised five times over the 14-month fit-out period; each revision required an average of six hours of linkage audit and re-linking. The total 4D specialist time on this project was estimated at 32 working days over the 14-month duration — a significant investment, but one the project team considered justified given the three phased occupancy milestones, each of which required demonstrating to the client that the MEP installation sequence would not delay the tenant handover dates.

Limits and Caveats

LOD is a hard ceiling for 4D value

The quality of a 4D model is bounded by the level of development of the underlying 3D model. A programme task "L05 Steel — East Bay Connections" cannot be linked to individual connection plates if those connection plates are not modelled as discrete objects. At LOD 300 — the practical minimum for coordination on most commercial projects — individual connections, hangers, anchors, and miscellaneous steel are typically not modelled as separate elements. The 4D model can therefore visualise the installation of primary structural steel at floor level, but not the granular installation sequence within a floor that the steel erector actually follows. This is not a platform limitation — it applies equally to Timeliner, Synchro, and Bexel.

The programme must be maintained for the 4D model to have value

All three platforms are only as current as the programme they are linked to. On projects where the programme is maintained inconsistently — where the P6 schedule is updated monthly but communicated weekly via email-distributed spreadsheets — the 4D model will always lag behind the current project state. This is a process problem, not a technology problem. A project that cannot maintain a current programme cannot maintain a current 4D model.

Automated linkage is not a substitute for expert judgement

Rule-based linkage (matching task names to model object properties) can substantially reduce the manual effort of the initial linkage phase. It does not eliminate the need for a 4D specialist who understands the construction sequence. An automated rule that matches all objects containing "Level 5" to tasks containing "Level 5" will correctly link most level-5 structural and MEP elements — but it will also link foundation elements that were modelled with an incorrect level parameter, temporary works families that happen to contain "Level 5" in their family name, and annotation elements exported from Revit with level data in their properties. Every automated linkage must be audited by a person who understands both the model structure and the programme logic.

The 4D specialist role requires both BIM and scheduling competence

This is the most under-appreciated constraint in 4D BIM delivery. The 4D model is at the intersection of the BIM model and the construction programme — it requires fluency in both. A BIM coordinator who does not understand programme logic (predecessor relationships, float, resource loading, critical path) will produce a 4D model that looks correct but contains schedule interpretation errors. A project planner who does not understand model structure (families, levels, shared parameters, category hierarchies) will design a programme structure that cannot be linked to the model efficiently. The ideal 4D specialist has substantial experience in both disciplines. These people are rare, and project teams should plan accordingly.

Synchro Pro's live P6 link requires P6 Professional, not P6 Team Member

The live P6 database connection in Synchro Pro requires a P6 Professional licence on the scheduler's end — not P6 Team Member or EPPM read-only access. Projects where P6 is managed by a specialist scheduler with Team Member access will not be able to use the live link and must fall back to XER file exchange. Verify this before committing to the live-link workflow.

Sources and Further Reading

• Autodesk Navisworks TimeLiner Documentation (Navisworks 2025) — Official Autodesk help covering schedule field mapping, task types, and simulation settings in TimeLiner. Essential reference before any linkage session.

• Bentley Synchro Pro — Product Overview and Training Wiki — Bentley's community documentation covering resource modelling, rule-based linking, and the P6 live link workflow. The resource assignment examples are particularly useful for crane and labour studies.

• Bexel Consulting — Bexel Manager Platform — Developer documentation and release notes for Bexel Manager, including IFC classification workflows and the integrated 4D/5D cost engine architecture.

• buildingSMART International — IFC 4.3 Standard — The normative IFC schema including IfcWorkSchedule, IfcTask, and IfcRelSequence entities relevant to schedule-linked IFC workflows. Required reading for teams considering IFC-native 4D with Bexel.

• BIM Forum — 4D BIM Use Case Paper (2022) — Industry guidance document covering constructability reviews, site logistics, crane sequencing, and phased occupancy applications of 4D BIM. Peer-reviewed by BIM Forum member organisations.

• BIM Forum — Level of Development (LOD) Specification (2023) — The definitive reference for what can and cannot be represented in a model at each LOD. Essential for understanding the geometric ceiling on 4D linkage granularity.

• McKinsey Global Institute — Reinventing Construction Through a Productivity Revolution (2017) — The underlying productivity data referenced in the article. Section on digital tools and 4D BIM specifically addresses schedule visualisation adoption rates and productivity correlations.

• NBS — Uniclass 2015 Classification System — The classification framework used for IFC object classification in Bexel Manager's automated cost assignment. Required for BIM teams implementing Bexel in a Uniclass-aligned information environment.

• AECbytes — 4D Construction Simulation Software Review (Laiserin, 2019) — Independent analysis of 4D BIM platforms from an AEC technology research perspective. Covers the competitive landscape including Vico Office, Synchro, and Navisworks.

• NIBS National BIM Standard — Construction Sequencing Application (NBIMS-US V4) — The US national standard's guidance on 4D BIM applications including the BIM Execution Plan requirements for construction sequencing use cases.

• Primavera P6 EPPM — Schedule Import/Export Technical Reference — Oracle's technical documentation covering XER file format structure and field definitions. Essential for understanding what data is available when importing to a 4D platform and what is lost in the round-trip.

• Vico Office R7 — Flowline Planning and 4D Workflow Documentation (Trimble) — Reference documentation for Vico Office, included here as a comparable platform to Synchro for location-based management workflows on linear and repetitive structure projects.