Plan/Percent Complete

Percent Complete Analysis

Upload a P6 XER file to compare physical percent complete against duration consumption, and find activities where progress reporting has drifted from what the schedule actually shows.

Upload Programme
Programme (.xer)
Click or drop file
A single P6 export — not a before/after pair
Physical % Complete FROM phys_complete_pct, PLANNER-ENTERED
Overall Physical % Complete (duration-weighted)
—%
Distribution
Schedule Quality Flags FROM THE FILE'S OWN FIELDS, NOT COMPUTED

Each flag below compares phys_complete_pct against another field the file already carries. None of these are calculated — they're straight consistency checks on data already in the XER.

Started, 0% Reported
—
100%, Not Closed
—
Progress, No Actual Start
—
Activities In Scope
—
Started but 0% reported (0)
ActivityStatusActual Start
100% reported but not marked complete (0)
ActivityStatusActual Finish
Progress reported with no actual start date (0)
ActivityStatusPhys % Complete
Duration % Complete FROM target_drtn_hr_cnt / remain_drtn_hr_cnt

Formula: (target_drtn_hr_cnt − remain_drtn_hr_cnt) / target_drtn_hr_cnt. Always computable when the file carries remain_drtn_hr_cnt — not every export does.

Units % Complete FROM TASKRSRC act_reg_qty / target_qty

Requires resource loading — the XER's TASKRSRC table with quantity fields populated. Read locally by this page; lib/xer-parser.js doesn't parse TASKRSRC at all today.

Cost % Complete FROM TASKRSRC act_reg_cost / target_cost

Requires cost loading — the XER's TASKRSRC table with cost fields populated (this page does not read the separate PROJCOST summary table). Read locally, same as units.

Divergence: Duration % vs Physical %

Delta = duration % − physical %. Positive: duration is burning down faster than reported progress (often the activity is being extended). Negative: reported progress is ahead of duration consumption (less common, worth a look). No score or grade — just the numbers, ranked by how far apart they are.