Schedule analysis,
reimagined.

The DCMA 14-point assessment is the industry standard for checking whether a construction schedule is reliable. It examines things like missing logic (activities with no predecessors or successors), excessive lag, negative float, and high-duration tasks.

PlanXER runs all 14 checks automatically the moment you upload your XER file. Each check gets a traffic-light score — green means pass, amber means review needed, red means there's a problem that could undermine your programme.

Every activity in Primavera P6 is assigned a calendar that determines which days are working days, which are holidays, and what the standard working hours are. When schedules go wrong, the calendar is often the hidden culprit — a public holiday that wasn't accounted for, or a 5-day calendar applied where a 6-day one was needed.

The Calendar Decoder extracts every calendar from your XER file and lays them out visually. You can see at a glance which holidays are set, which exception days exist, and how many working hours each calendar assumes per day.

In Primavera P6, the Work Breakdown Structure (WBS) organises your project into phases and packages. Activity codes, on the other hand, let you tag activities with labels like discipline, area, or responsibility — allowing flexible filtering and grouping.

This tool takes your existing WBS hierarchy and converts each level into a set of activity codes automatically. Instead of manually creating activity code structures and assigning them one by one, you get the entire mapping done in a single click.

Sometimes you just want to see the programme. No health checks, no forensic analysis — just open the XER, look at the bars, print it or share it with someone who doesn't have P6.

Gantt View loads your file and renders it as a clean, readable Gantt chart in the browser. Zoom in for detail, zoom out for the full project sweep, filter by WBS or activity code, and send it to PDF or Excel with one click. No P6 licence needed on the receiving end either — the output is universal.

The critical path tells you the longest sequence of dependent activities that determines your project end date. But in complex schedules with thousands of activities, finding the true driving path to a specific milestone isn't straightforward — especially when calendar differences and resource constraints come into play.

The Driving Path Finder traces backwards from any milestone you select and identifies every activity that is genuinely driving that date. It distinguishes between the longest path (based on total float) and the actual driving path (based on relationship logic and calendars).

Most schedules contain untapped opportunities that planners don't notice because they're buried under thousands of activities. These include excessive total float on non-critical paths, redundant constraints that prevent the schedule from calculating naturally, and activities that could be overlapped or fast-tracked.

This tool scans your entire schedule and flags these opportunities: which constraints could be removed without affecting the critical path, where float exists that nobody is using, and which activity sequences could be compressed to pull the end date forward.

Resource loading is one of the most underused parts of a P6 schedule. Most planners load resources but rarely visualise them properly. The result: hidden over-allocations, unrealistic manpower spikes, and EVM data that doesn't match reality.

Resource Dashboard reads the resource assignments inside your XER and presents them as a clean dashboard: histograms of manpower by month, peak demand by trade, allocation across activities, and resource curves overlaid on key milestones. Filters let you slice by resource type, WBS, or activity code.

Every monthly progress report needs a written narrative explaining the current state of the programme: what's on track, what's delayed, what the key milestones are, and what actions are needed. Writing this from scratch by reading through hundreds of activities takes hours.

The Programme Narrative tool uses AI to analyse your XER file and generate a professional executive summary automatically. It identifies the critical path, highlights milestones approaching or missed, summarises activity completion rates, and flags areas of concern — all written in clear, professional English ready for your report.

Earned value (EV) is the single most powerful method for measuring project progress objectively. But running EV manually across schedule updates is painful: extracting BCWS, BCWP, ACWP for every period, computing SPI and CPI, plotting curves, and then comparing it all against the previous update.

Resource Earned Value automates the full EV workflow across two or more XER files. It pulls budgeted cost of work scheduled (BCWS), budgeted cost of work performed (BCWP), and actual cost of work performed (ACWP) directly from your resource assignments, then computes Schedule Performance Index (SPI), Cost Performance Index (CPI), and variance trends across each update. Visualised as S-curves with current-period markers.

The critical path gets all the attention — but the activities most likely to become critical are the ones already sitting close to it. Activities with 1 to 15 days of total float can flip onto the critical path the moment something slips. Most planners only notice them after the slip has already happened.

Near Critical Path scans your schedule (or your full update history) and surfaces every activity sitting in the at-risk float band. You set the threshold — 5, 10, 15 days — and the tool returns a watch-list ranked by float, with each activity's path, predecessors, and trend across updates. Run it on one file for a snapshot, or on multiple files to see which activities are creeping toward critical over time.

The most common comparison task in planning: take last month's programme and this month's programme, and show me exactly what changed. Activities added, removed, dates shifted, durations modified, progress updated.

Compare 2 XER does exactly that with zero setup. Drop the two files in, and within seconds you get a clean table of every difference — ordered by impact, colour-coded by change type, and exportable to PDF or Excel for your monthly report.

Two-file comparison is great for month-to-month, but sometimes you need to see the trend across three snapshots — for example, baseline versus last month versus this month, or three consecutive weekly updates.

Compare 3 XER extends the comparison engine to three files, showing how each metric drifted across the three versions. You can spot activities that have been slipping consistently (a classic warning sign) versus those that only shifted once.

Project directors rarely want the full forensic comparison — they want one question answered: what's late, and what's ahead? Two lists, clear numbers, no noise.

Delays & Ahead filters your comparison down to exactly that. On the left: activities that slipped, sorted by number of days late. On the right: activities running ahead of schedule. Each item shows its baseline date, current date, and the delta in working days.

Every month, every planner stares at the same blank page: "How do I turn this comparison data into a progress report the project director will actually read?" Hours of writing, structuring, and rephrasing the same patterns of language.

Progress Report Generator does the writing for you. Upload your two XER files (last update + this update), and the AI produces a complete monthly report: executive summary, overall progress, milestone status, critical path changes, areas of concern, recommended actions, and a next-period outlook. Output is editable Word format so you can tweak wording before submission.

Relationships (predecessors and successors) are the logic backbone of any schedule. When someone changes a relationship — adding a new dependency, removing an existing one, or modifying the type from Finish-to-Start to Start-to-Start — it can fundamentally alter the critical path and project end date.

Relationship Changes compares the logic network between two schedule versions and lists every single change: new relationships added, existing ones removed, type changes (FS to SS, etc.), and lag modifications. Each change shows the affected activity IDs, the old relationship, and the new one.

The critical path is rarely the same path twice. Activities slip, durations change, logic gets rewired, and the chain that drives your end date shifts — sometimes subtly, sometimes dramatically. Critical Path Compare shows you exactly how.

Upload your schedule updates (2 files for a before/after, or many files for the full timeline) and the tool produces a side-by-side critical-path view: activities that were critical before but aren't now, activities that have become newly critical, and the chains that flip in and out across versions. You can isolate "always-critical" activities, "newly critical" ones, and the points where the path diverged.

Three of the most-watched signs of schedule manipulation, in one tool: activities that appeared, activities that disappeared, and original durations that changed.

Activities Audit compares your XER files and produces three lists. Added: activities that exist in the current file but didn't in the previous one. Deleted: activities that existed before and are now gone. OD changed: activities whose original duration shifted between updates — usually a strong signal that scope or assumptions have changed.

The fastest way to answer the question every project director asks first: "What dates moved between these schedule updates?"

Upload your XER files (2 or more) and Actual Dates Diff produces a single clean table showing every activity whose actual start or actual finish shifted across the updates — ordered by impact, with the previous date, the current date, and the variance in working days. No noise from durations, relationships, or constraints — just date movement.

The most common source of programme noise: activities that should have been progressed during a reporting period but weren't. They sit there with their original dates, polluting the critical path and skewing every downstream calculation.

Missed Updates scans your latest XER against the previous one and flags every activity whose actual start or finish should have been recorded but wasn't — based on planned dates that have passed without a corresponding update. Each flagged activity shows what was expected, what's missing, and how stale the data is.

Sometimes a table can't tell the story — you need to see how the programme moved across updates. Where did the foundation slip? When did the structure phase compress? How did the handover milestone drift over six months?

Gantt — Compare Multiple XERs renders every schedule update on a single visual Gantt timeline, with each version represented as a different colour band. Activities that moved show as offset bars; new activities appear as ghost bars; deleted ones fade out. Zoom in on any week, filter by WBS, and export the visual as a PDF for stakeholder briefings.

Relationship Changes (in Compare Progress) works on two files at a time. This tool extends the idea to your full revision history. Upload 5, 10, or 50 schedule updates and see every logic change across every version on a single timeline.

The output shows each relationship on its own row and each update as a column — a matrix where you can trace exactly when a predecessor was added, when it was removed, when a type changed, when a lag was modified. Filters let you isolate repeated flips, logic bursts, or specific activity chains.

The forensic workbench. Upload up to 50 XER files (each up to 200 MB) and run every analysis in one go — date deltas, relationships, calendars, constraints, missed dates, float erosion, longest path, EoT risk, EoT quantum. The complete claims-grade output, no separate tools, no separate runs.

17 analyses bundled together: Cover · Summary · Actual Starts · Actual Finishes · Duration Changes · Relationships · Lookup · Constraints · Missed Start · Missed Finish · Float Erosion · Calendars · Longest Path · Activity Matrix · EoT Start Risk · EoT Finish Risk · EoT Quantum.

When you manage multiple subcontractors or projects, you often need to review several XER files at once — running quality checks on each, comparing them against baselines, or generating summary reports across the portfolio. Doing this one file at a time is tedious and error-prone.

The Bulk XER Processor lets you upload multiple XER files in a single batch. It runs your chosen analysis (quality check, summary, or comparison) across all files simultaneously and produces a consolidated report showing results side by side.

Windows analysis is the SCL-recommended methodology for allocating delay responsibility. The schedule is broken into time windows (usually monthly), and for each window you identify what drove the critical path, who was responsible, and how many days of delay were caused.

The Window Culpability Sheet automates the bookkeeping behind this analysis. Upload your series of schedule updates, and the tool builds a period-by-period matrix showing who caused what delay in which window — with Employer, Contractor, and Concurrent delays tracked separately.

An Extension of Time claim is two things stacked together: the numbers (which dates moved, by how much, due to what) and the narrative (the written explanation that ties the numbers to delay events and contractual entitlement). Most tools give you the numbers. None give you the narrative.

EoT Delay Analysis Narrative does both. Upload your pre-delay and post-delay schedules, identify the delay events, and the AI produces a structured claim package: time impact analysis, critical-path-shift analysis, concurrent delay assessment, and a fully written narrative that references the data. Output is editable Word format so your claims consultant can refine the language before submission.

Most planning tools focus on a single schedule at a time. But real planning work happens across multiple projects at once — tracking which packages are healthy, where resources are stretched, and how the overall programme sits against its budget and earned value.

Master Planning is a multi-project dashboard. Load your XER files, and you get a consolidated Gantt view across all projects, workload distribution by team or discipline, manpower requirements by month, and an Earned vs Burned comparison showing where actual progress has outpaced or fallen behind what was planned.

Not every planning conversation starts in P6. Sometimes the schedule lives in an Excel sheet — handed over by a sub-contractor, prepared by a procurement lead, or built quickly to scope a tender. Turning that into a usable Gantt usually means rebuilding it inside P6 or MS Project.

Gantt from Excel takes your sheet (activity name, start, finish, % complete, optional WBS) and renders it as an interactive Gantt directly in the browser. Filter, group, print, or export to PDF without ever opening a desktop scheduling tool.

Cash flow drives every project conversation outside the planning room. Owners want to know when invoices will land, contractors want to know when they'll be paid, finance teams want to forecast working capital. The data is already in your schedule — but it sits in resource-loading tabs nobody reads.

Cash Flow reads the cost-loaded resources in your XER and produces a proper monthly and cumulative cash curve, broken down by WBS, trade, or activity code. Compare planned versus earned versus actual on a single chart, and export the underlying data to Excel.

Loading resources is one of those tasks that gets postponed until the schedule is too far along to do properly. The result: planners forecast manpower with rules of thumb, procurement lags, and HR finds out about peaks the month they hit.

Resource Calculation takes your activity quantities and unit-rate library and computes the resource demand for every period — by trade, by WBS, by activity code. Output is a clean histogram of monthly manpower requirement, the underlying activity allocation, and a peak-demand summary for procurement.

Site photos are taken every day on every project, but they almost never make it into a structured report. They sit in someone's phone, get forwarded on WhatsApp, and lose all context about when, where, and what they show.

Progress Photos Report Generator ingests a folder of photos (with their EXIF dates intact) and produces a captioned, dated, location-tagged report — ready to attach to monthly progress submissions or claim packages. Group by area, link to specific WBS elements, and export to a single PDF in seconds.

Most planners are running multiple programmes at once but don't have a single screen to track them. Health checks, EV status, slip trends, and notice obligations live in different tools, different files, and different mental models.

Planners Dashboard consolidates the core indicators across every programme assigned to you — DCMA score, current SPI/CPI, days slipped vs. last update, critical-path activity in flight, open notices, and upcoming milestones. Click any tile to drill into the underlying file.

Extension of Time work is full of moving deadlines: notices to issue, particulars to submit, contractor responses, engineer determinations. Miss a contractual time-bar and the strongest claim in the world becomes uncollectible.

EoT Dashboard is a tracker for every claim and notice on every contract you manage. It pulls notice periods from the contract clauses you register, counts down to each deadline, flags overdue items in red, and gives you a one-page status view across all live claims.