Your XER is not a schedule

A planner hands over the schedule. The file is called project.xer, it is a few megabytes, and it contains everything: every activity, every link, every calendar and baseline. The site manager double-clicks it. Nothing opens. The plan is complete and it is unreadable, and that gap is where most of a project's planning value quietly leaks away.

01What an XER actually is

An XER is not a document. It is a text dump of Primavera P6's database tables, one after another, tab-separated. Each table is announced by %T, its columns by %F, and every row by %R. Open it and you get twenty-odd tables of raw identifiers.

%T	PROJECT
%F	proj_id	proj_short_name	last_recalc_date	scd_end_date
%R	4783	EACOP-CFR	2026-05-23	2027-09-19

%T	TASK
%F	task_id	wbs_id	task_code	task_name	target_drtn_hr_cnt	total_float_hr_cnt
%R	316296	2051	E-CIV-1100	Pile caps, Row A	240	0

%T	TASKPRED
%F	task_pred_id	task_id	pred_task_id	pred_type	lag_hr_cnt
%R	90114	316296	316201	PR_FS	0

You can open that text in Excel. You will not get a schedule. A row in TASK is a duration and two id numbers; its real dates come from a calendar in another table, its sequence from links in a third, its critical path from re-running the network. Strip the relationships and the CPM logic and you have a spreadsheet of orphaned numbers. To turn it back into a plan you have to rebuild P6's object graph and recompute the dates. That is why PDF, Excel and Project cannot just read it, and why it normally takes P6 itself. The technical companion piece walks through the parse and the rebuild in detail.

02Why the format is good

The XER survives because it is honest and complete. It is lossless: activities, logic, calendars, resources, cost, activity codes, user fields and every baseline travel together, nothing rounded off for display. It is portable: one P6 installation exports it, another imports it and rebuilds the exact schedule. As an exchange format between schedulers it is the right tool. The trouble is that everyone else on the project is not a scheduler.

03The lock

To open an XER you need Primavera P6, a per-seat licence that costs thousands a year and takes training to drive. On a real project that means one planner holds the only key. The schedule that the whole team is meant to work to lives inside a file only one person can open, and the plan becomes whatever that person has time to export and email as a picture.

04One plan, many readers

Worse, a single view serves no one. The same schedule has to be read at three different altitudes on the same day.

So the planner rebuilds the plan by hand, over and over: a one-page summary for the partner, a package cut for the director, a printed lookahead for the site. Each is a manual filter, re-layout and export in a tool nobody else can check. It is hours a week, it is late by the time it lands, and it creates no new information. It is the same schedule, retyped for each audience. That work is real and necessary, and it is pure friction: the plan is only useful when it is close to hand for the person deciding, and getting it there is eating the planner's week.

05Hand the file to everyone

The fix is to break the lock, not to buy more seats. Drop the same .xer into a browser and read it directly: no Primavera, no licence, nothing uploaded to a server. Pick the altitude instead of rebuilding it. Roll the schedule up to Level 1 for the partner, cut it by discipline for the director, switch to a three-week lookahead for the site, and export any of them as a clean slide. The planner stops being a bottleneck and the team reads the plan without translation.

None of this replaces P6. The planner still builds and runs the schedule where the logic lives. It replaces the retyping: the part with no judgment in it, the part that only ever moved the same facts to a different reader. That is what XER Gantt is for. A plan is information, and information design is what makes it legible to the person who has to act on it.