What Is an XER File?
An XER file is the native export format of Oracle's Primavera P6 project management software. It contains all the schedule data for one or more projects in a structured, tab-delimited text format. XER files are the standard method for exchanging schedule data between P6 databases, sharing schedules with project stakeholders, and archiving schedule versions for future reference.
Despite being a text file that can technically be opened in any text editor, XER files contain complex relational data that requires specialized tools to interpret meaningfully. The file format stores projects, activities, relationships, resources, calendars, WBS structures, and dozens of other data tables in a specific format that mirrors the P6 database structure.
For construction professionals, XER files are ubiquitous. Contractors submit schedule updates as XER files, owners archive baseline schedules as XER files, and claims analysts review historical schedules from XER exports. Understanding the XER format is essential for anyone working with construction schedules, even if they never directly edit the raw file data.
XER File Structure
An XER file is organized into sections, each representing a database table from Primavera P6. The file begins with a header line identifying the export format version, followed by a series of table definitions and their data rows.
File Header
The first line of every XER file starts with "ERMHDR" followed by tab-separated metadata including the export date, P6 version, database name, and user who performed the export. This header provides context about when and how the file was created.
Table Definitions
Each data table in the XER file begins with a "%T" line that names the table, followed by a "%F" line that lists the field (column) names. Data rows follow, each beginning with "%R" and containing tab-separated values corresponding to the field definitions. The table ends when the next "%T" line begins a new table or the file ends with "%E" (end marker).
Key Data Tables
PROJECT (PROJWBS): Contains project-level information including project name, planned start and finish dates, and project status. The PROJWBS table defines the Work Breakdown Structure hierarchy.
TASK: The core table containing all activity data — activity IDs, names, durations, dates (early start, early finish, late start, late finish, actual start, actual finish), percent complete, activity type, and status. This is typically the largest table in the file.
TASKPRED: Defines the logical relationships between activities — predecessor ID, successor ID, relationship type (FS, SS, FF, SF), and lag values. This table encodes the entire logic network that drives CPM calculations.
CALENDAR: Defines work calendars including working days, holidays, and work hours. Activities reference calendars to determine which days count toward their duration calculations.
RSRC and TASKRSRC: Resource definitions and resource assignments to activities. These tables contain resource names, rates, and the quantity of resources assigned to each activity.
ACTVCODE and TASKACTV: Activity code definitions and their assignments to activities. Activity codes provide categorization and filtering capabilities beyond the WBS structure.
Common XER File Issues
Working with XER files frequently involves troubleshooting common issues that can affect data integrity and import success:
Version compatibility: XER files exported from newer versions of P6 may not import cleanly into older versions. The file format evolves with each P6 release, adding new tables and fields. Always verify version compatibility before importing.
Character encoding: XER files use specific character encoding that can be corrupted if the file is opened and saved in a text editor with different encoding settings. Special characters in activity names or notes are particularly vulnerable to encoding issues.
Missing calendars: If an XER file references calendars that do not exist in the target database, imports will fail or produce incorrect date calculations. Always export calendars with your schedule data.
Circular relationships: While P6 prevents circular logic during data entry, corrupted XER files can sometimes contain circular relationships that cause import failures or calculation errors.
Large file sizes: XER files for complex projects with thousands of activities, extensive resource assignments, and multiple baselines can become very large. This can cause performance issues with some tools and may require splitting into smaller exports.
Read XER Files Without Expensive Software
Float Master reads and analyzes XER files instantly in your browser. No expensive software license needed, no installation, no waiting. Upload and analyze in seconds.
View Pricing →Reading XER Files Without Expensive Software
One of the biggest challenges in construction scheduling is that XER files are created in Primavera P6, but not everyone who needs to review schedules has access to enterprise scheduling software. These licenses are expensive, the software requires training to use effectively, and it must be installed on specific machines. This creates a bottleneck where schedule review depends on a small number of people with software access.
Float Master's XER File Reader solves this problem by reading XER files directly in the browser without requiring any expensive software license or installation. Simply upload your XER file and instantly access all schedule data including activities, relationships, float values, and critical path information.
This accessibility transforms how construction teams work with schedules. Project managers can review schedule updates independently. Owners can verify contractor submissions without relying on third-party schedulers. Field teams can check activity sequences and dates without waiting for someone to generate a report from P6.
Beyond basic reading, modern XER analysis tools provide capabilities that go beyond what P6 itself offers for schedule review. Float path analysis, driving logic visualization, and automated DCMA assessments provide insights that would require significant manual effort in P6.
XER vs. Other Schedule Formats
XER vs. XML (P6 XML): P6 also exports to XML format, which is more verbose but more widely supported by third-party tools. XML files are larger than XER files but contain the same data. Some organizations prefer XML for its broader compatibility, while others prefer XER for its smaller file size and direct database mapping.
XER vs. MPP (Microsoft Project): Microsoft Project uses the proprietary MPP format. While P6 can import and export MPP files, data fidelity is not perfect — some P6-specific features (like multiple calendars per project, activity codes, and resource curves) may not translate cleanly. For construction projects using P6, XER remains the preferred exchange format.
XER vs. CSV: While schedule data can be exported to CSV for basic review, CSV files lose the relational structure that makes XER files valuable. Relationships, calendars, and WBS hierarchies cannot be meaningfully represented in flat CSV format.
Best Practices for XER File Management
Naming conventions: Use consistent naming that includes the project name, update number or date, and any relevant identifiers. Example: "ProjectAlpha_Update12_2025-02-15.xer". This makes it easy to identify and organize schedule archives.
Version control: Maintain an archive of all XER exports, particularly baseline schedules and monthly updates. These archives are essential for baseline comparisons, delay analysis, and historical reference.
Export settings: When exporting XER files, include all relevant data — calendars, resources, activity codes, and WBS structures. Partial exports missing critical data tables will produce incomplete analyses when imported or read by other tools.
Validation after export: Always verify that an exported XER file can be successfully re-imported or read by your analysis tools. Corrupted exports are not uncommon, and catching them immediately is far better than discovering the issue weeks later when the data is needed.
Key Takeaways
The XER file format is the backbone of schedule data exchange in the construction industry. Understanding its structure, common issues, and management best practices is essential for anyone working with Primavera P6 schedules. While the format is proprietary to Oracle, modern tools like Float Master have made XER file analysis accessible to everyone on the project team, removing the expensive software barrier that historically limited schedule review to a select few.
Whether you are a scheduler creating XER exports, a project manager reviewing submissions, or a claims analyst examining historical schedules, a solid understanding of the XER format helps you work more effectively with construction schedule data.