Skip to content
Living professional glossary

Construction scheduling terms, explained for practice.

143 original, plain-language definitions spanning CPM, Primavera P6, schedule quality, updating, delay, risk, earned value, and contract time.

Glossary index

Find the term, then follow it into practice.

Delay & disruption

Acceleration

Measures taken to complete earlier than the current forecast or to recover delay, often through added resources, overtime, resequencing, or changed methods.

In practiceRecord direction, cost, productivity effects, achieved days, and remaining risk.
Primavera P6

Activity code

A controlled classification field used to group, filter, report, and exchange activities.

In practiceGovern code dictionaries and ownership; inconsistent codes make portfolio reporting unreliable.
Primavera P6

Activity ID

The unique identifier for an activity within a P6 project.

In practiceUse a stable, sortable coding convention; names may change as scope is clarified, but IDs should remain traceable.
Delay & disruption

As-planned versus as-built analysis

A comparison of the planned sequence and timing with what actually occurred.

In practiceBuild the as-built chronology from reliable records and analyze causation rather than treating every variance as responsibility.
Primavera P6

Check Schedule report

P6’s configurable report for logic, lag, constraint, float, duration, progress, baseline, and relationship warning signs.

In practiceTreat thresholds as screening criteria and investigate every exception; a passing count is not proof of a credible plan.
Delay & disruption

Collapsed as-built analysis

A method that removes selected delay events from an as-built model to estimate what completion might have been without them.

In practiceExplain the as-built logic and removal assumptions because the reconstructed counterfactual is highly judgment-dependent.
Delay & disruption

Concurrent delay

Two or more delay events affecting completion during the same period under the concurrency rule applicable to the contract or jurisdiction.

In practiceDo not label events concurrent merely because their dates overlap; analyze responsibility and actual critical-path effect.
Delay & disruption

Constructive acceleration

A claimed acceleration arising when excusable delay relief is denied or not timely granted and the original completion obligation remains enforced.

In practiceThe elements and remedy are contract- and jurisdiction-specific; obtain legal advice for consequential decisions.
Delay & disruption

Contemporaneous records

Documents and data created at or near the time work and decisions occurred.

In practicePreserve native schedules, reports, daily logs, correspondence, photos, approvals, and change records with dates and provenance.
Risk & recovery

Correlation

The tendency of uncertain durations or risks to move together rather than independently.

In practiceModel shared drivers such as weather, labor, or common suppliers to avoid artificially narrow forecasts.
CPM mechanics

Critical path method CPM

A network calculation that derives schedule dates and float from activity durations, calendars, relationships, constraints, and status.

In practiceTreat the calculated finish as the output of a model whose inputs still require professional review.
Risk & recovery

Criticality index

The percentage of simulation iterations in which an activity appears on the modeled critical path.

In practiceCombine it with sensitivity and path review; an activity can influence completion without being critical in every run.
Delay & disruption

Disruption

Loss of productivity or efficiency caused by interference, change, congestion, resequencing, or other impacts, whether or not completion is delayed.

In practiceAnalyze productivity and causation separately from critical delay.
Primavera P6

Duration percent complete

A time-based P6 percentage derived from original and remaining duration.

In practiceIt measures consumed planned duration, not necessarily installed physical work.
Primavera P6

Duration type

A P6 setting that controls how duration, units, and resource units per time respond when one value changes.

In practiceSet duration types deliberately before loading resources or updating progress; different types recalculate differently.
CPM mechanics

Early finish EF

The earliest calculated date on which an activity can finish under the current network.

In practiceCompare early finish with the baseline, contractual milestones, and operational commitments rather than reading it alone.
CPM mechanics

Early start ES

The earliest calculated date on which the remaining work of an activity can begin under the current network.

In practiceEarly start is calculated, not a contractual promise; it changes when logic, calendars, status, or constraints change.
Primavera P6

Enterprise project structure EPS

P6’s hierarchy for organizing projects, programs, portfolios, security, and summarized reporting.

In practicePlace projects under the correct EPS node before applying codes, security, and reporting standards.
Delay & disruption

Excusable delay

A delay for which the contract may provide additional time because the event is outside the contractor’s responsibility.

In practiceApply the contract’s risk allocation, notice, causation, and criticality requirements to the project facts.
Delay & disruption

Extension of time EOT

A formal increase to contractual time granted under the contract’s change or delay provisions.

In practiceTie the requested days to notice, entitlement, a supported schedule effect, and the specific milestone being changed.
Primavera P6

Filter

A P6 rule that limits the records displayed without deleting or changing the underlying schedule.

In practiceAlways disclose active filters in reviews and exports; a filtered layout can make material work disappear.
Primavera P6

Finish milestone

A P6 zero-duration activity type representing completion of an event or phase.

In practiceGive it predecessor logic and align contractual milestones with the governing documents.
CPM mechanics

Finish-to-finish relationship FF

A logic tie in which the successor finish is driven by the predecessor finish, subject to any lag.

In practiceConfirm the start of the successor is also logically supported; a finish tie alone can leave a dangling start.
CPM mechanics

Finish-to-start relationship FS

A logic tie in which the successor cannot start until the predecessor finishes, subject to any lag.

In practiceUse this relationship when the handoff is genuinely finish-to-start rather than merely because it is the default.
Delay & disruption

Forensic schedule analysis FSA

The technical investigation of schedule evidence to evaluate delay, sequencing, causation, and time-related responsibility.

In practicePreserve method transparency, data provenance, sensitivity checks, and the distinction between technical findings and legal conclusions.
CPM mechanics

Forward pass

The CPM calculation that moves from the beginning of the network to determine early start and early finish dates.

In practiceIf an early date looks wrong, trace the driving predecessor logic, calendar, constraint, and remaining duration.
Delay & disruption

Fragnet

A small network of activities and relationships representing added, changed, or delayed work for insertion into a schedule.

In practiceBuild it from the actual scope and handoffs; preserve the before-and-after files and calculation logs.
Primavera P6

Group and sort

P6 layout settings that organize rows into bands and define their display order.

In practiceUse WBS, phase, area, responsibility, or status grouping to answer a specific review question.
Delay & disruption

Impacted as-planned analysis

A modeled method that inserts delay events into the as-planned schedule to estimate prospective effect.

In practiceRecognize that it may not capture actual progress, changed logic, mitigation, or later project conditions.
CPM mechanics

Late start LS

The latest calculated date an activity may start without violating the completion condition used in the backward pass.

In practiceLate dates can be distorted by constraints or the selected float calculation, so inspect the scheduling options.
Primavera P6

Layout

A saved P6 view combining columns, grouping, sorting, filters, bars, timescale, and lower-pane details.

In practiceMaintain named working, review, and print layouts so different users reach the same evidence quickly.
Primavera P6

Level of effort activity LOE

A support activity whose dates are derived from relationships to other work rather than an independent duration-driven path.

In practiceKeep LOE work off the controlling path and do not use it to hide discrete deliverables.
CPM mechanics

Milestone

A zero-duration event used to mark a contractual, management, or technical point in the plan.

In practiceUse milestones for real events such as notice to proceed, beneficial occupancy, or approval—not as substitutes for missing work.
Risk & recovery

Monte Carlo simulation

Repeated sampling from defined uncertainty ranges and risk events to estimate a distribution of schedule outcomes.

In practiceDocument distributions, correlations, iterations, risk mapping, and sensitivity to assumptions.
CPM mechanics

Near-critical path

A path with little remaining float or a meaningful probability of becoming controlling.

In practiceMonitor path movement and convergence because tomorrow’s critical path often sits just outside today’s threshold.
CPM mechanics

Negative float

A calculated shortfall showing that the network cannot meet a constraint or required completion condition as modeled.

In practiceTrace the constraint and the driving path; do not “repair” negative float by weakening logic.
Primavera P6

P6 XML file

A schema-based Oracle exchange format used for projects and related P6 data.

In practiceConfirm what objects and global data the chosen exchange includes before treating XML and XER as interchangeable.
Risk & recovery

P50 date

The completion date met or improved in approximately half of modeled simulation outcomes.

In practiceUse it as a probability statement under the model assumptions, not a guaranteed or automatically appropriate commitment.
Risk & recovery

P80 date

The completion date met or improved in approximately 80 percent of modeled simulation outcomes.

In practiceConfirm whether organizational policy, risk tolerance, and funding align with that confidence level.
Primavera P6

Percent complete type

A P6 setting that determines whether duration, physical, or units progress drives the activity percent complete field.

In practiceChoose the type that matches the progress-measurement method and do not mix them without explaining the consequence.
Primavera P6

Physical percent complete

A user-entered or step-weighted P6 measure of completed physical scope.

In practiceSupport it with quantities, weighted steps, or another objective rule; it does not automatically reforecast remaining duration.
Primavera P6

Primary baseline

The comparison baseline assigned in P6 for primary bar, date, and variance display.

In practiceCreating a baseline is not enough—assign the intended project and comparison baselines and verify the displayed fields.
Primavera P6

Project ID

The unique identifier P6 uses for a project record.

In practiceApply a governed naming convention and avoid renaming IDs casually because exchanges and integrations may depend on them.
Risk & recovery

Recovery schedule

A revised execution plan showing specific actions intended to regain lost time or protect a required completion.

In practiceTie recovered days to named changes in crews, shifts, sequence, access, procurement, or method and measure whether they occur.
Primavera P6

Reflection

A what-if copy linked to a source project that can be reviewed and selectively merged back.

In practiceUse reflections for controlled scenario testing and preview every merge; never treat the reflection as an approved schedule by default.
CPM mechanics

Remaining duration RD

The estimated working time still required to complete an in-progress or not-started activity.

In practiceReforecast it from field conditions each update; percent complete alone does not establish remaining time.
Primavera P6

Resource dependent activity

A P6 activity type whose resources can be scheduled using their individual calendars.

In practiceUse only when resource calendars genuinely control the work; otherwise results can be difficult to explain.
Risk & recovery

Risk register

A controlled list of identified threats and opportunities with owners, causes, effects, probability, impact, and responses.

In practiceConnect material schedule risks to activities or milestones and update them as conditions change.
Risk & recovery

Schedule contingency

Time intentionally provided to absorb identified or residual uncertainty under a defined control rule.

In practiceMake contingency visible, assigned, and governed rather than hiding it inside durations or lags.
Primavera P6

Schedule log

The P6 scheduling report that records calculation settings, statistics, warnings, and results.

In practiceSave the log with each formal schedule submission so the calculation can be reproduced and challenged.
Risk & recovery

Schedule risk analysis SRA

A quantitative assessment that models uncertainty and risk events to produce a distribution of possible completion outcomes.

In practiceValidate the deterministic network first; simulation cannot repair missing scope or broken logic.
Primavera P6

Secondary baseline

An additional P6 comparison baseline available alongside the primary baseline.

In practiceUse secondary and tertiary baselines for controlled comparisons, not to obscure which baseline governs.
Primavera P6

Start milestone

A P6 zero-duration activity type representing the beginning of an event or phase.

In practiceGive it successor logic and a defensible driver unless it is the authorized project start.
CPM mechanics

Start-to-start relationship SS

A logic tie in which the successor start is driven by the predecessor start, subject to any lag.

In practicePair overlapping work with finish logic where needed so the successor cannot remain open after its driver finishes.
Primavera P6

Task dependent activity

A P6 activity type scheduled with the activity calendar rather than each assigned resource calendar.

In practiceUse it for most construction tasks when the activity work pattern controls the dates.
Delay & disruption

Time-slice windows analysis

A period-by-period method that examines contemporaneous schedule updates and changing critical paths.

In practiceChoose windows based on meaningful project changes and validate each update before relying on it.
CPM mechanics

Total float TF

The calculated time an activity may move before it affects the relevant project or milestone completion condition.

In practiceReview the float distribution and its movement between updates, not only activities at zero float.
Primavera P6

Units percent complete

A P6 percentage based on actual units compared with at-completion units.

In practiceUse it only when resource units are complete, current, and aligned with the progress-measurement basis.
Primavera P6

User-defined field UDF

A configurable P6 field for organization-specific text, dates, numbers, indicators, or classifications.

In practiceDocument data type, allowed values, owner, and intended reports before rolling a UDF across projects.
Primavera P6

WBS summary activity

A P6 activity type that summarizes dates from activities within the same WBS branch.

In practiceDo not rely on relationships to a WBS Summary activity; Oracle notes that those relationships are ignored during scheduling.
CPM mechanics

Work breakdown structure WBS

A hierarchical decomposition of project scope used to organize responsibility, deliverables, and schedule detail.

In practiceA WBS should follow the way the project will be managed and reconciled to scope, cost, and reporting structures.
Primavera P6

XER file XER

Oracle’s proprietary text exchange format for P6 project and enterprise data.

In practiceRecord source, export version, timestamp, checksum, import options, and post-import validation; an XER is not a simple spreadsheet.