Reading a Primavera P6 XER Export Outside of P6

On many construction and EPC projects, the master schedule lives in Primavera P6 but the analysis, reporting and cross-project comparison work happens elsewhere. That work usually starts with a P6 XER export. This guide covers what an XER file actually contains, what it does and does not include, and what kinds of insights can reasonably be extracted from XER data without a live P6 connection.

What an XER file is

XER is Primavera P6's proprietary text export format. The schedule is written out as a set of structured tab-separated tables — activities, relationships, calendars, WBS, resources and so on — packaged into a single .xer file that another P6 instance or a third-party analysis tool can read.

Practically, that means an XER is a point-in-time snapshot. When the scheduler produces an export on a Friday cut-off, that XER represents the schedule exactly as it stood in P6 at that moment — not what it looks like after subsequent edits back inside Primavera. The next XER, produced the following Friday, is a separate snapshot.

What can be inside an XER

Depending on how the schedule was built and how the export was configured, an XER may contain:

• Activities and their planned, actual and remaining durations.
• Early and late start/finish dates and float values.
• Predecessor and successor relationships with lag values.
• Calendars (project, resource, activity where applicable).
• Milestones (start / finish).
• Activity status (Not Started / In Progress / Completed) and physical percent complete where used.
• Schedule logic and constraints.
• WBS, activity codes and coding assignments.
• Resource-related data where the scheduler included it in the export.

Not every XER contains every field. Some organizations strip out resources or costs before sharing; some do not populate coding structures consistently. Any downstream analysis has to work with what was actually written into the file, not with what the schedule could theoretically contain.

Why teams analyze XER data outside P6

• Project-controls reporting. Weekly / monthly cycles need schedule performance surfaced without every stakeholder opening P6.
• Schedule analytics. Cross-check driving paths, milestone movement and baseline drift alongside cost and productivity data.
• QA / review. Compare the current period's XER against the previous one to see what actually changed, not just what the summary says changed.
• Executive reporting. Boil the schedule down to what the executive team actually needs to hear.
• Cross-project analysis. Portfolio-level comparison where different projects each publish their own XER.
• Dashboarding. Milestones, critical-path movement and slippage rendered next to EVM and cost metrics.

What file-based analysis can surface

When two consecutive XERs are compared — or a single XER is compared against an approved baseline XER — the following are commonly surfaceable:

• Schedule performance at the activity and WBS level.
• Critical and driving paths as computed in the export.
• Late or moved milestones.
• Baseline changes between reporting cycles.
• Schedule slippage against baseline dates.
• Broader project-controls context when the schedule sits next to cost, EVM and productivity data.

What outside-of-P6 analysis does not mean

Analyzing an XER outside Primavera does not replace P6 as the scheduling system. The scheduler still authors and maintains the network inside Primavera. Nothing about reading the XER writes back to P6 or edits the schedule logic. File-based analysis is a downstream read, not a substitute for CPM authoring.

It is also worth being direct about the workflow: Controls Star analyzes P6 XER data using a file-based upload — not a live Primavera P6 connection and not automatic synchronization. Each cycle is analyzed against the XER the scheduler exported at that cut-off.