Tooladoo Free online tools for your files

Compare XER updates when you don't have Claim Digger (Beta)

Claim Digger is P6's built-in comparison and needs P6. This tool compares two XER exports in the browser and lists every change by category.

Opens: XER, ZIP
Saves: HTML, XLSX, CSV

Compare

Earlier update (or the only schedule)
Choose a file… or drop it here
.xer, .zip · up to 200 MB
    Replace file

    The previous update or the baseline, as exported from P6 (.xer, or a .zip of it). Upload only this file to get a schedule health check instead of a comparison.

    Later update (optional)
    Choose a file… or drop it here
    .xer, .zip · up to 200 MB
      Replace file

      The newer update of the same project (.xer, or a .zip of it). Activities are matched by Activity ID.

      Options
      More options

      Only needed when an XER holds several projects. Empty: the projects whose Activity IDs match each other are used.

      Which activities count as critical in the report.

      For showing durations and float in days. 0 uses the hours per day of each activity's calendar, as P6 does.

      Your files are deleted after processing.

      Claim Digger is the project comparison built into Primavera P6: it compares two projects in the P6 database and lists their differences. That needs a P6 installation with both projects imported. When all you have is the XER files the contractor sent, this page compares them directly.

      Comparing two XER files

      1. Upload the earlier XER first and the later one second. A ZIP holding both works too; the data dates decide which is which.
      2. The comparison runs on our server and the result page shows the summary, the findings and the activities that slipped most.
      3. Download the full report as HTML, as an Excel workbook with one sheet per change category, or as a CSV list with one row per change.

      What is compared

      • Activities by Activity ID: added, deleted, start and finish movements, original and remaining durations, actual dates, percent complete, status, name, type, WBS and calendar.
      • Relationships by predecessor, successor and type: added, deleted, type changes and lag changes, each marked when it only follows from an added or deleted activity.
      • Primary and secondary constraints.
      • Calendar definitions by calendar name: work week, hours per day and every holiday or exception date, including those inherited from a base calendar. A holiday added to a calendar changes dates without any activity showing an edit, so it gets its own section.
      • Total float, negative float, the critical activities and P6's longest-path flag.
      • The scheduling options stored with each project, such as retained logic or progress override, the float calculation and the critical definition.

      Things to keep in mind

      Matching is by Activity ID, so a renumbered schedule shows the old IDs as deleted and the new ones as added. When both files are exports of the same P6 project, an edited Activity ID is recognised from P6's internal id and listed separately.

      Activity codes, notebook topics and user-defined fields are not compared; resource assignments, units, costs and expenses are. The dates and float are the values stored in the files, as P6 calculated them; recalculate before exporting so they are current.

      More about what this tool reads and writes: P6 Schedule Update Comparison (XER).

      More with P6 Schedule Update Comparison (XER)