Percent Complete Types

Last reviewed 9 September 20261,747 words8 min read

Duration, Physical, Units β€” three numbers called "percent complete" that measure three different things

🟩 In one line: Duration % is time elapsed, Units % is resource consumed, Physical % is work in place β€” only the last is progress, so it is the type on every production activity, with Units % allowed where the only loaded resource is the measured quantity itself.

πŸ‘€ Who this is for: J/M. Prerequisites: progress-measurement-and-rules-of-credit, quantity-tracking-and-physical-progress. Companion to p6-activity-types-explained and p6-duration-types-explained.

e / c
First, let's be honest about why this page exists

The column is labelled "Activity % Complete" and it shows one number. Which of three calculations produced that number is decided by a setting on the General tab that most people leave at the project default β€” and the project default, on a copied project, is often Duration. A schedule on Duration % can be "62% complete" with nothing installed, because the data date moved and P6 counted the days.

Three types, one table, and the rule. The argument about rules of credit is on its own page; this page is only the mechanics.

🟨 The standard β€” what "good" looks like
SourceWhat it asks for (paraphrased)Consequence
AACE RP 38R-06Progress measurement method recorded in the basis% type stated per activity type in the SBM
GAO Schedule Assessment Guide, BP 9Progress based on actual work performed, not elapsed timePhysical (or Units on measured quantity)
PMI Practice Standard for Scheduling, 2nd ed.Percent complete method selected to reflect actual accomplishmentSame
DCMA 14-Point, Metrics 9, 13, 14Status consistent with data date; CPLI, BEIBEI counts actual finishes β€” a Duration-% activity "finishes" by calendar
Client schedule specifications (typical Gulf)Usually mandate Physical % with quantity substantiationCheck; rarely permit Duration %
FIDIC 1999 Cl 8.3 / 2017 Cl 8.3; NEC Cl 32.1Programme reflects actual progressActual progress = work done, not time passed

🟒 Rule: Physical % on production work, entered from the quantity sheet or earned through steps; Units % only where the sole resource is the measured quantity; Duration % on nothing that is measured β€” and remaining duration is always set separately, never derived from the percent.

How it actually works

1. The three types

TypeFormulaWhat you typeWhat P6 changesMeasures
Duration(Original βˆ’ Remaining) Γ· Original Γ— 100Either the % or the Remaining Duration β€” they are locked togetherEditing one changes the otherTime elapsed
UnitsActual Units Γ· At Completion Units Γ— 100The % or the actual unitsEditing the % writes actual units; remaining units = At Completion βˆ’ actualResource consumed (hours or quantity)
PhysicalNone β€” user-entered, or from weighted stepsThe % (or tick steps)Nothing β€” remaining duration is independent and must be set by handWork in place, as assessed

2. Where each is set and read

ActionPath
Project defaultEnterprise β†’ Projects β†’ Details β†’ Defaults β†’ Percent Complete Type
Per activityActivity Details β†’ General β†’ % Complete Type
Steps drive Physical %Project Details β†’ Calculations β†’ "Activity percent complete based on activity steps" (ticked); Activity Details β†’ Steps, weights per rule of credit
Column showing the selected typeActivity % Complete (add the three specific columns β€” Duration %, Units %, Physical % β€” when diagnosing)
What earned value usesWBS β†’ Earned Value tab β†’ Technique for computing performance % complete (default from Admin β†’ Admin Preferences β†’ Earned Value)

"Performance % complete" is a fourth number: it is what EV multiplies against the budget. Set to "Activity percent complete" it follows the type above; set to 0/100 or 50/50 it applies the rule of credit regardless of what was typed. The SBM says which applies per WBS node.

3. Choosing per activity type

Activity% typeWhy
Measured trades β€” concrete, block, plaster, tiling, cable pulling, pipeworkPhysical from quantity sheet; or Units where the only resource is a non-labour quantity resource (mΒ², mΒ³, m)Both equal installed Γ· total; Units removes a typing step if the quantity resource is the sole assignment
Labour-loaded activities with hours as the resourcePhysicalUnits % would be hours spent β€” a crew that is slow earns more
Short activities under 0/100 or 50/50 rulesPhysical (or performance % via WBS EV setting)Rule of credit, not calendar
Multi-step activities (slab: rebar / formwork / pour)Physical via Steps, weights 40/30/30Each step earned on an inspection record
LOE β€” supervision, scaffold, hoistDurationIt genuinely is time-based; the only place Duration % belongs
MilestonesNone β€” 0 or 100β€”
Approvals, curing, review periodsDurationElapsed time is the work

4. The trap inside Duration %

Tools β†’ Update Progress ("progress spotlight") statuses everything in the window as if it went to plan: actual dates set, remaining durations reduced, and β€” on Duration-% activities β€” percent moved. It is the fastest way to produce a schedule that is exactly on time and completely untrue. Never used on a contractual update; every actual comes from records.

5. The two numbers that must be set separately

On Physical %, entering 60% does nothing to the remaining duration. That is the point: 60% installed at an achieved rate below plan means the remaining 40% takes longer than 40% of the original. The monthly update enters Physical % from the quantity sheet and remaining duration from remaining quantity Γ· achieved rate (forecasting-honestly). Two columns, two sources, every activity.

6. Changing type mid-project

Changing from Duration to Physical on a progressed activity leaves Physical % at 0 until typed, and BEI/EV on that activity jump in the transition month. Do it in a baseline draft, note it in the change table, and re-enter the percents from the quantity sheet in the same session.

πŸŸ₯ Where people go wrong
  1. Duration % left as the project default. The schedule progresses itself as the data date moves. The check is one column: group by % Complete Type and read the counts.
  1. Units % with labour hours as the resource. 1,200 hours spent of 1,920 shows 62% β€” but 400 mΒ² of 640 is laid, which is 62% only by coincidence. Slow crews earn more under Units % on labour.
  1. Physical % typed and remaining duration left alone. 70% installed, RD still original βˆ’ elapsed. The activity finishes on paper on the original date whatever the rate. Two entries, always.
  1. Update Progress on a contractual update. Every activity in the window hits plan. The narrative then explains a BEI of 1.00 against a site that visibly isn't.
  1. Percent as a substitute for steps. "Slab 75%" with no record of which steps. Steps with weights and an IR reference per step β€” the percent is then a result, not an opinion.
  1. Milestones with a percent. A milestone is 0 or 100. Anything between is a corrupt import or a Task pretending.
βš–οΈ When you're challenged

"Why is the activity 40% but you've only reduced the remaining duration by 6 days of 24?" Forty percent installed in 12 days means 27 mΒ² a day against the 32 planned. The remaining 384 mΒ² at 27 a day is 15 days, rounded up. The percent measures what's done; the remaining duration measures how fast β€” they're set separately because they say different things.

"Just use Update Progress, it's the end of the month and nothing's late." Update Progress statuses to plan; it doesn't look at the site. If nothing's late the quantity sheet will show that and the entries take the same hour. If something is late, Update Progress hides it and we find out next month.

"The sub's programme shows 71% on the risers. Yours shows 58%." Theirs is Units % on labour hours β€” 71% of the budgeted hours are spent. Ours is Physical from the joint walk sheet β€” 58% of the pipe is installed and IR'd. The reconciliation table shows both with the reason; payment is on ours.

πŸ“„ Related pages
✏️ Worked example

Level 5 blockwork, Dubai mid-rise, data date 1 October. Original 24 days, started 6 September, 640 mΒ² total, 384 mΒ² installed and IR'd, 1,240 mh booked of 1,920.

% typeValue shownWhere it came fromVerdict
Duration88%21 of 24 working days elapsedFiction
Units (labour hours)65%1,240 Γ· 1,920Hours, not walls
Units (quantity resource, mΒ²)60%384 Γ· 640Correct β€” equals Physical
Physical (from quantity sheet)60%384 Γ· 640, IR-1102Correct

Remaining duration entered separately: 256 mΒ² Γ· 18.3 mΒ²/day achieved (384 Γ· 21) = 14 days. Forecast finish moves 8 working days later than original. Notebook "Forecast Basis" written. Both the 60% and the 14 days go in the update; neither was derived from the other.

πŸ“– References
  • AACE International RP 38R-06, Documenting the Schedule Basis
  • GAO Schedule Assessment Guide (GAO-16-89G), Best Practice 9
  • PMI Practice Standard for Scheduling, 2nd ed.
  • DCMA 14-Point Schedule Assessment, Metrics 9, 13, 14
  • FIDIC Conditions of Contract for Construction, 1999 and 2017, Cl 8.3; NEC3/NEC4 ECC Cl 32.1 (check the edition in your contract)
  • Oracle Primavera P6 Professional User Guide β€” Percent Complete Types; Activity Steps; Earned Value settings; Update Progress (field labels as in P6 Professional v20; earlier versions differ)

From the field

Experience from working planners. Unreviewed β€” read it as experience, not guidance.

Add what you know about percent complete types. What worked, what the consultant pushed back on, what you would do differently next time. A paragraph is plenty.

Contributors get their name and one link on the site β€” your own templates, course or consultancy. We take nothing and hold nothing.

Add your experience