Hours remain authoritative for float and duration. Working-day values require a resolved activity calendar; otherwise the day value is withheld.
Dates & as-ofActuals vs forecast
Also: actual, forecast, remaining work, to-go
Actuals are what the schedule records as done or started before the Project Date; forecast is everything planned after it.
Why it matters Actuals are evidence; forecast is a model. A review that mixes them without saying which is which hides where the risk lives.
Finance lens Actuals to date versus estimate to complete. Only the first is audited; the second is management's opinion.
How to read it Use explicit actual-start, actual-finish, and status fields to identify actuals. A planned date before the Project Date is not automatically an actual; it may be stale or invalid. Forecasts move; changed actuals require review.
Ask “Which of these dates are actuals and which are forecasts -- and have any actuals changed since the last update?”
Used on ReviewDates & as-ofBaseline
Also: target schedule, plan of record, approved schedule, older schedule
A governed reference schedule used for comparison. It is a promise only when its approval or contract authority is recorded.
Why it matters Slippage only means something against a fixed reference. If the baseline quietly changes, every comparison flatters the update.
Finance lens The approved budget. You measure variance against the budget, not against last month's forecast.
How to read it Ask when it was approved and whether it has been re-baselined. A re-baseline resets the variance clock and should be a deliberate decision.
Ask “Is this the contract baseline or a working target, and when was it last re-baselined?”
Used on ReviewDates & as-ofContracted substantial completion
Also: substantial completion, contract completion, SC date
The completion date the contract promises, entered by the owner; the schedule's forecast finish is measured against it.
Why it matters It is the line that separates on-time from late in the contract's terms, which is where damages and revenue start.
Finance lens The covenant the project is measured against; the maturity date.
How to read it The owner light compares the schedule's latest finish to this date. A forecast finish after it is a contractual problem, not just a scheduling one.
Ask “Is the contract date in the settings the current one after all executed change orders?”
Used on SettingsDates & as-ofCorrection
Also: older-date reupload, re-issue, corrected release
A later upload whose schedule Data Date is the same as or older than a previously received release.
Why it matters Receipt order records knowledge time while Data Date records schedule-valid time; collapsing them rewrites history.
Finance lens A restated prior-period submission received later.
How to read it Keep the newest receipt for a Data Date in derivative views, label it as a correction, and preserve every immutable receipt in custody.
Ask “What was corrected, and should the earlier receipt remain the comparison witness for any prior decision?”
Used on ImportsDates & as-ofData date
Also: project date, status date
The scheduler's name for the Project Date: the schedule-valid as-of date that splits recorded history from forecast.
Why it matters Same date, different word. When someone says data date, status date, or Project Date, they mean the one as-of.
Finance lens As-of date; balance-sheet date.
How to read it See Project Date.
Ask “Which field in the file carries it, and does it agree with the update's cover note?”
Used on ReviewDates & as-ofDate gate
Also: accept project date, date confirmation
The step where each file's Project Date is confirmed before any analysis relies on it.
Why it matters It stops a stale file from being compared with a current one and makes the as-of explicit in the record.
Finance lens Agreeing the period before reading the statements; tying out the balance date.
How to read it Accepted means confirmed. Needs review means a date is missing, disputed, or falls outside the work. Explicit unknown is an accepted unknown, shown with reduced confidence.
Ask “Why does this file's Project Date need review, and what would resolve it?”
Used on ReviewDates & as-ofLook-ahead
Also: lookahead, three-week look-ahead, six-week look-ahead
The window of work coming due in the next few weeks -- what to confirm before it starts.
Why it matters Most slippage is visible two to four weeks out as a missing precursor: a permit, a delivery, a crew, a crane.
Finance lens A cash-flow forecast for the next few weeks: what is coming due and whether it is funded.
How to read it Read it as a list of commitments. Each item should have an owner and a precondition that is either met or named as at risk.
Ask “For each item due in the next two weeks, what has to be true the day before it starts, and is it true today?”
Used on ReviewDates & as-ofMilestone
Also: key date, contract date, TT_Mile, TT_FinMile
A zero-duration marker for a commitment, like turnover, permit-in-hand, or substantial completion.
Why it matters Milestones are where time becomes money: payment triggers, liquidated damages, occupancy, revenue start.
Finance lens A covenant date or a payment trigger in the contract.
How to read it Compare the forecast milestone date with the contract date and with the baseline date. Watch the trend across updates more than any single value.
Ask “Which milestones moved since the last update, by how much, and what drove each one?”
Used on MilestonesDates & as-ofProject date
Also: data date, status date, as-of date, last recalc date, PROJECT.last_recalc_date, PROJECT.data_date
The date the schedule was last statused -- its own "as of". Everything before it is recorded history; everything after it is forecast.
Why it matters Every number in a review is true only as of this date. Two schedules can be compared only when you know both dates, and a stale date makes good progress look late or late progress look fine.
Finance lens The period-end close. A P&L is 'for the period ended'; a schedule is 'as of the Project Date'. Nobody reads statements without the date.
How to read it It should match the reporting cycle (every two weeks or monthly). Missing, older than the last update, or later than every activity in the file are stop signs.
Ask “What is the Project Date of this update, and was the schedule recalculated on it before it was exported?”
Used on ReviewDates & as-ofReceived date
Also: received_at, upload date, intake date
When this platform received the file. A platform clock, never the schedule's clock.
Why it matters It orders the project's version history and proves custody, but it says nothing about the schedule's progress. Confusing it with the Project Date is the most common as-of error.
Finance lens The posting date versus the transaction date. The books care about both, for different reasons.
How to read it Use it to answer 'when did we get this'. Use the Project Date to answer 'what was true when'.
Ask “Was this update received late relative to its Project Date, and why?”
Used on ImportsDates & as-ofSnapshot
Also: version, schedule file, XER, export
One schedule file exactly as it was received: a point-in-time copy that is never edited afterwards.
Why it matters A review is a comparison of snapshots. Because each one is sealed with a fingerprint, a finding can always be traced back to the exact bytes that produced it.
Finance lens A closed period's ledger. You do not post into a closed period; you open a new one.
How to read it Each snapshot shows its Project Date (the schedule's clock) and its received date (the platform's clock). Only the first one orders the project's story.
Ask “Is this the same export the scheduler sent, unmodified, and what is its Project Date?”
Used on ReviewDates & as-ofUpdate
Also: newer schedule, current schedule, progress update, status update
The current statused schedule -- the newer of the two files in a review.
Why it matters It carries the latest actuals and the latest forecast; the review is the difference between it and the baseline or the prior update.
Finance lens The latest period's actuals and revised forecast.
How to read it Its Project Date should be the most recent one on the project. An update with the same Project Date as the last one is a re-issue, not progress.
Ask “What changed between this update and the last one besides progress -- any logic, durations, or constraints?”
Used on ReviewTime & cushionFloat
Also: total float, slack, schedule cushion, TF, total_float_hr_cnt
Schedule cushion: how many working hours a task can slip before it delays something that matters.
Why it matters Float is the project's time contingency. When it is gone, every further slip lands on the finish date and on the contract.
Finance lens Contingency, or a cash buffer. Spending it is not a problem by itself; spending it without knowing is.
How to read it Positive is room. Zero is driving the finish. Negative means a commitment is already missed on paper. Hours, not days, unless the calendar is known.
Ask “How much float does this chain have left, and how much did it have at the last update?”
Used on ReviewTime & cushionFloat loss
Also: float consumption, float burn, float movement
Cushion that was consumed between the two schedules -- the update got tighter here.
Why it matters Float loss is slippage before it reaches the finish date. It is the earliest warning a schedule gives.
Finance lens Contingency drawdown in the period.
How to read it Look at where it concentrates (one area, one chain) and whether it is one event or a trend. Total hours lost matter less than how close the chain is to zero.
Ask “What consumed the float in this area, and is it a one-time event or a trend?”
Used on ReviewTime & cushionFloat reserve
Also: reserve hours, schedule barometer
Observed total-float hours carried by the declared incomplete activity population.
Why it matters It shows the modeled time cushion present in the selected population without claiming where the cushion can be spent.
Finance lens A stated contingency balance whose restrictions still matter.
How to read it Read the population, calendars, and Data Date. The latest two comparable reserves can produce a historical tendency, not a zero-date forecast.
Ask “Which activities and calendars make up this reserve, and is the population comparable to the prior release?”
Used on ReportsTime & cushionFloat velocity
Also: float-loss velocity, velocity, dFloat/dt
Observed float change divided by the elapsed schedule-valid Data Date interval, normally reported in hours per calendar week.
Why it matters It separates a large change over a long period from the same change over a short period without assuming that the rate will continue.
Finance lens A historical burn rate with no automatic runway forecast.
How to read it Two distinct comparable Data Dates give one velocity reading. Acceleration needs three and jerk needs four; irregular intervals are normalized separately and invalid intervals are withheld.
Ask “What release pair, elapsed interval, and identity basis support this velocity reading?”
Used on Change & MotionTime & cushionFree float
Also: FF, free_float_hr_cnt
How much a task can slip before it delays the very next task, as opposed to the project finish.
Why it matters It tells a crew how late it can be without making another crew wait -- the practical cushion at the handoff.
Finance lens The headroom before you start borrowing from someone else's budget line.
How to read it Free float is always less than or equal to total float. Zero free float means any slip is immediately someone else's problem.
Ask “Where is free float zero at a handoff between two subcontractors?”
Used on ReviewTime & cushionNear-critical
Also: near critical, low float
A task or chain with very little float left -- the next in line to start driving the finish.
Why it matters Critical paths change. Near-critical chains are where next month's critical path comes from.
Finance lens A covenant with a thin margin: compliant today, one bad month from a breach.
How to read it The product uses a near-critical threshold in hours (project settings). Watch the count of near-critical tasks across updates.
Ask “How many chains are within the near-critical threshold, and which one is most likely to take over?”
Used on ReviewTime & cushionNegative float
Also: negative total float, behind the constraint
The modeled network cannot meet a constrained or required date with its current logic, durations, calendars, and status.
Why it matters It means the plan as modeled cannot meet a constrained date. Either the date moves, the plan changes, or the schedule is misstating something.
Finance lens An overdraft against a modeled limit. First verify that the limit represents the governing obligation.
How to read it Read the constraint or required-finish basis before calling it a missed commitment. Negative float caused by a typed-in constraint still needs review, but it does not establish cause or responsibility.
Ask “Which constraint is creating the negative float, and what is the recovery plan?”
Used on ReviewTime & cushionOut-of-sequence progress
Also: out of sequence, OOS
Work that started before the task it depends on finished -- reality overrode the logic.
Why it matters It is often legitimate, but each case means the links no longer describe how the job is really being built, so the forecast may be wrong.
Finance lens A transaction posted out of period. Usually explainable, always worth a look.
How to read it A few are normal on a live project. A growing count means the logic needs maintenance before the forecast can be trusted.
Ask “Are these out-of-sequence starts deliberate, and has the logic been updated to match how the work is actually proceeding?”
Used on Schedule HealthTime & cushionPercent complete
Also: % complete, physical percent complete, phys_complete_pct, cmplt_pct_type, progress
The share of a task reported done. Physical percent is a judgment of the work; duration percent is just time elapsed.
Why it matters It is self-reported. Claimed progress that runs ahead of evidence (hours, quantities, remaining duration) is how surprises are built.
Finance lens Percent-complete revenue recognition. Treat it like an unaudited management estimate until evidence supports it.
How to read it Check which kind of percent the schedule uses. Compare it with remaining duration and with effort evidence; the talk-now gap flags the mismatch.
Ask “What evidence supports this percent complete, and which tasks are claimed further along than their hours show?”
Used on Performance & EVMTime & cushionRecovery schedule
Also: recovery plan, acceleration, re-sequence
A revised plan that shows how the project gets back to the promised dates after a slip.
Why it matters A recovery schedule that only compresses durations is a wish. One that changes logic, crews, or scope is a plan.
Finance lens A turnaround plan: it should name the levers, not just the target.
How to read it Compare it against the baseline, not the prior update, and look at what changed: durations shortened, links removed, constraints added.
Ask “What specifically changed in this recovery schedule to buy back the time, and what does it cost?”
Used on ReviewTime & cushionRemaining duration
Also: RD, remain_drtn_hr_cnt, remaining work
The work left on a task, in working hours, from the Project Date to its forecast finish.
Why it matters Remaining duration is the forecast. When it does not shrink between updates, the task is not progressing no matter what the percent complete says.
Finance lens Estimate to complete, in time.
How to read it Each update should reduce it by roughly the time elapsed. A task whose remaining duration stays flat across updates is stalled.
Ask “Why did remaining duration not fall on these tasks since the last update?”
Used on ReviewTime & cushionSchedule burden
Also: burden integral, activity-days, hour-days
Accumulated exposure estimated by integrating an observed schedule condition over elapsed schedule-valid time.
Why it matters A short severe episode and a smaller persistent condition can have the same current reading but different accumulated histories.
Finance lens Area under an exposure curve, with the sampling interval disclosed.
How to read it The trapezoid estimate and rule bracket describe observed history between samples. Sparse samples cannot reveal what happened inside each interval.
Ask “How many samples and what spacing support this accumulated burden?”
Used on ReportsTime & cushionSchedule-loss concentration
Also: concentration, H*, normalised Herfindahl, Ck
The distribution shape of observed loss across a complete declared subject population.
Why it matters It distinguishes a head-heavy distribution from a long tail without naming a cause or prescribing a recovery.
Finance lens Customer or portfolio concentration measured against the size of the population.
How to read it Always show subject count and the flat k/n comparison beside cumulative shares. Fewer than five subjects is too small to classify shape.
Ask “Is the ranked list complete, and how many subjects carry four fifths of the observed loss?”
Used on ReportsTime & cushionTotal float
Also: float, TF
The full cushion on a task before it pushes the project finish.
Why it matters Total float is the number that tells you whether a task can absorb a delay or will pass it straight to the finish.
Finance lens Total available contingency on that line.
How to read it Compare it with the task's remaining duration: a task with 40 hours of float and 400 hours of work left has very little real room.
Ask “Which tasks lost the most total float since the last update?”
Used on ReviewLogic & structureActivity code
Also: task code, task_code, activity ID, Activity ID
The ID of a task in the schedule (for example A1040). Stable across updates, unlike the name.
Why it matters IDs are how the product follows one task through many updates and how you ask a scheduler an unambiguous question.
Finance lens The account number, as opposed to the account description.
How to read it Prefixes usually encode area or trade, which is how a subcontractor's scope is selected. Renamed or renumbered tasks break the trail; lineage tracking tries to follow them.
Ask “Were any activity IDs renumbered since the last update, and why?”
Used on ReviewLogic & structureCalendar
Also: work calendar, clndr_id, hours per day
The working days and hours a task follows. It is why hours and days are not interchangeable.
Why it matters A 40-hour float is a week on an 8-hour calendar and under two days on a 24-hour one. Durations reported in days without the calendar can be wrong by a factor of three.
Finance lens The fiscal calendar and working-day conventions behind every accrual.
How to read it The product reports hours and converts to days only when the task's calendar is resolved. Unresolved calendars are named, not guessed.
Ask “Which calendar does this task use, and are crews actually working those hours?”
Used on Schedule HealthLogic & structureConstraint
Also: date constraint, cstr_type, must finish on, start no earlier than, finish no later than
A date typed onto a task that overrides the schedule's own logic.
Why it matters A constraint can make a late schedule look on time by pinning a date the logic would otherwise push. It is the main way float gets misstated.
Finance lens A plug number. The total looks right because someone typed it, not because the model produced it.
How to read it Count them and read their types. Soft constraints (no earlier than) are common; hard ones (must finish on) are where negative float hides.
Ask “Which constraints are contractual, and which are there to make a date look right?”
Used on Schedule HealthLogic & structureCritical path
Also: critical chain, critical activities, zero float path
The chain of work that sets the finish date: a day lost here is a day lost on the project.
Why it matters Delays anywhere else are absorbed by float. Delays here are not. It is where management attention pays off.
Finance lens The binding constraint -- the bottleneck in a throughput model. Improving anything else does not move the result.
How to read it There are two definitions: tasks with zero or negative float, and the longest chain of links to the finish. When they disagree, a constraint is usually the reason.
Ask “Which tasks are on the critical path by float and which by the driving chain, and why do they differ?”
Used on ReviewLogic & structureCrucial task
Also: linchpin task, linchpin, driver
The tightest task on the driving chain -- the first place to ask questions.
Why it matters One task usually governs the finish at any moment. Knowing which one turns a status meeting into a decision.
Finance lens The largest single exposure on the balance sheet.
How to read it It changes as work progresses. Watch for the same task staying crucial across updates without its remaining duration falling.
Ask “What has to happen this week for the crucial task to stay on plan?”
Used on ReviewLogic & structureDriving path
Also: longest path, driving chain, longest_path_flag
The chain of tasks actually pushing the finish date, computed from the links and independent of typed constraints.
Why it matters It is the critical path you can trust when constraints have distorted float. It shows what the schedule would do left to its own logic.
Finance lens The model's own answer before any plug numbers.
How to read it A task on the driving path that still shows float means a constraint is masking criticality somewhere.
Ask “Does the driving path agree with the float-based critical path, and where does it diverge?”
Used on ReviewLogic & structureHandoff
Also: hand-off, interface, scope boundary
Work crossing between two scopes: one crew finishes so another can start.
Why it matters Handoffs are where delays change owners. Most disputes are about a handoff that was late, not about the work itself.
Finance lens An intercompany transaction: both sides have to record it the same way.
How to read it The subcontractor view lists handoffs in (what others owe you) and out (what you owe others). Zero free float at a handoff is the pressure point.
Ask “Which handoffs into this scope are late, and which ones out of it are at risk?”
Used on ReviewLogic & structureHard constraint
Also: mandatory finish, mandatory start, must finish on
A typed date the schedule cannot move -- it can hide real slippage.
Why it matters With a hard constraint, a delay shows up as negative float instead of a moved date -- easy to miss if nobody reads float.
Finance lens A locked cell in the model that silently breaks the formula chain.
How to read it Every hard constraint should map to a real contractual or physical date. Negative float behind one is the tell.
Ask “Is this date really immovable, and what happens to the finish if the constraint is removed?”
Used on Schedule HealthLogic & structureLag
Also: lag_hr_cnt, delay between tasks
A built-in wait between two tasks (finish one, wait N days, start the next).
Why it matters Lags are invisible duration. A week of lag delays the finish exactly like a week of work, but no crew is assigned to it and nobody reports progress on it.
Finance lens A payment term: net-30 between two events. Fine when it is real, a problem when it is padding.
How to read it Lags should stand for something physical (curing, inspection). Large or unexplained lags on the critical path are a standard schedule-quality finding.
Ask “What does this lag represent, and could it be a task with an owner instead?”
Used on Schedule HealthLogic & structureLead
Also: negative lag, overlap
A negative wait: the next task is allowed to start before its predecessor finishes.
Why it matters Leads compress the schedule on paper. They are legitimate when the overlap is real, and a way to hide a late finish when it is not.
Finance lens Recognizing revenue early. Sometimes right, always worth checking.
How to read it Any lead on the critical path deserves a question. Leads are a schedule-quality check in their own right.
Ask “What part of the predecessor has to be done before this task can really start?”
Used on Schedule HealthLogic & structureLOE
Also: level of effort, hammock, summary task, TT_LOE, TT_Hammock
Level-of-effort and hammock tasks stretch across other work. They track presence, not progress.
Why it matters Counting them as progress inflates earned value and hides real slippage; they should never drive the finish.
Finance lens Overhead allocation. Real cost, but not a deliverable.
How to read it The duration ledger excludes them on purpose. A level-of-effort task on the critical path is a schedule-quality finding.
Ask “Are any level-of-effort tasks driving dates or counting toward progress?”
Used on Performance & EVMLogic & structureLogic
Also: schedule logic, network, ties, dependencies
The predecessor/successor links that say what must happen before what.
Why it matters Logic is what lets a schedule forecast. Without it, a delay cannot ripple, so the finish date never moves -- which looks fine and is not.
Finance lens The formulas in the model. Hard-coded cells do not update when the inputs change.
How to read it Tasks with no predecessor or successor (missing logic) and links with large lags are the places where the model is weakest.
Ask “How many tasks are missing logic, and which critical ones rely on typed dates instead of links?”
Used on Schedule HealthLogic & structureMissing logic
Also: open-ended activity, open end, dangling activity, no predecessor, no successor
A task with no predecessor or no successor -- the schedule cannot see what it depends on or what depends on it.
Why it matters A task with missing logic cannot be delayed by anything and cannot delay anything, so its dates never move. The forecast is blind there.
Finance lens An unreconciled item: it sits on the books but nothing ties to it.
How to read it Only the first and last tasks should be open-ended. The DCMA check counts the rest; a few percent is a warning, more is a rebuild.
Ask “Why are these tasks missing links, and what would really delay them?”
Used on Schedule HealthLogic & structurePredecessor
Also: successor, pred, succ, upstream, downstream
The task that must happen first; its successor is the one that waits for it.
Why it matters Predecessors are where a crew's delay comes from; successors are who it lands on. Most blame conversations are really predecessor questions.
Finance lens Upstream and downstream line items.
How to read it Follow the predecessor chain back from a late task to find the first thing that moved.
Ask “What is the first predecessor in this chain that slipped, and who owns it?”
Used on ReviewLogic & structureRelationship
Also: link, tie, FS, SS, FF, SF
One link between two tasks. Finish-to-start is the normal kind; start-to-start and finish-to-finish overlap the work.
Why it matters The type decides how a delay on one task reaches the next. Heavy use of overlapping types can hide sequencing problems.
Finance lens The dependency between two line items in a model.
How to read it Finish-to-start should dominate. A start-to-finish link is rare and worth a question.
Ask “Why is this pair linked start-to-start, and what really has to be finished before the second starts?”
Used on Schedule HealthLogic & structureTask chain
Also: chain, path, sequence
A sequence of linked tasks; float lost usually concentrates along one chain.
Why it matters Problems travel along chains, not across the whole schedule. Finding the chain finds the story.
Finance lens A value chain: cost or delay accumulates along it.
How to read it Follow the chain from where float was lost back to the first task that moved.
Ask “Where does this chain begin, and who owns the first task that slipped?”
Used on ReviewLogic & structureWBS
Also: work breakdown structure, PROJWBS, WBS branch, area, package
The work breakdown structure: the schedule's tree of areas, packages, and systems.
Why it matters It is how the product locates a problem -- which area absorbed the float -- and how a scope is selected for a subcontractor's view.
Finance lens The chart of accounts for work. Rolling up a branch is rolling up a cost center.
How to read it Selecting a branch selects everything beneath it. A WBS that does not match how the job is actually bought and built makes rollups misleading.
Ask “Does the WBS match the contract packages, so that an area's float loss maps to a responsible party?”
Used on ReportsCost & earned valueAC
Also: actual cost, ACWP, act_reg_cost, actual cost of work performed
Actual Cost: money spent to date.
Why it matters Without AC, there is no cost performance, no CPI, and no forecast of the final cost.
Finance lens Actual expenditure to date, as booked.
How to read it AC in the schedule is only as current as the cost load. A flat AC while work proceeds usually means the cost data was not updated.
Ask “Is actual cost loaded to the same Project Date as the progress, or is it lagging?”
Used on Performance & EVMCost & earned valueBAC
Also: budget at completion, total budget, target_cost
Budget At Completion: the total budgeted cost of the work.
Why it matters Every earned-value ratio is a fraction of BAC. If BAC is wrong or changes, the ratios move without any work happening.
Finance lens The approved budget for the full scope.
How to read it BAC should only change with approved scope changes. Watch for it drifting between updates.
Ask “Did BAC change since the last update, and which change order explains it?”
Used on Performance & EVMCost & earned valueBEI
Also: baseline execution index
Baseline Execution Index: of the work the baseline said would be done by now, the share actually done.
Why it matters It measures whether the team finishes what it planned to finish, which is the habit that keeps a schedule honest.
Finance lens Plan attainment.
How to read it 1.0 is on plan. Below about 0.95 is a standard DCMA concern. Tasks finished that were not planned do not make up for planned ones that were not.
Ask “Which planned finishes were missed this period, and were they replaced with other work?”
Used on Schedule HealthCost & earned valueCPI
Also: cost performance index, EV / AC
Cost Performance Index: earned vs spent (1.0 is on budget; below 1.0 is over).
Why it matters CPI is history and the most stable predictor of final cost. Past a third complete, it rarely recovers much.
Finance lens Gross-margin efficiency on the work done so far.
How to read it 0.9 means every dollar spent earned 90 cents of budget. The final cost is roughly BAC divided by CPI; the product shows that as a band, not a point.
Ask “What would have to change for CPI to recover, and has it ever recovered on this project?”
Used on Performance & EVMCost & earned valueCPLI
Also: critical path length index
Critical Path Length Index: how much room the critical path has (1.0 has none to spare).
Why it matters It compresses the whole critical-path float story into one ratio for trend reading.
Finance lens Interest coverage: how much cushion before the obligation bites.
How to read it (Critical path length + total float) divided by critical path length. Below 1.0 means negative float on the path.
Ask “Is CPLI trending down across updates?”
Used on Schedule HealthCost & earned valueCV
Also: cost variance, EV - AC
Cost Variance: earned minus spent -- negative means over cost.
Why it matters It is the overrun so far, measured against the value of the work done rather than the calendar.
Finance lens Favorable or unfavorable cost variance, exactly as in cost accounting.
How to read it Negative is over. A negative CV that grows every update is a trend, not noise.
Ask “Which work packages carry the cost variance, and is it rate, quantity, or rework?”
Used on Performance & EVMCost & earned valueDirected earned value
Also: directed EV, scoped EV, EV scope
Earned value focused on part of the project -- a trade, a package, a WBS branch, or a named task list. A per-view lens, never the project baseline.
Why it matters A project-wide SPI hides a trade that is far behind. Directing the view to one scope shows whose work is earning and whose is not.
Finance lens A cost-center or segment P&L cut from the same general ledger.
How to read it Always check the scope line: how many tasks, which prefixes or discipline. A narrow scope with few tasks gives noisy ratios.
Ask “How does this subcontractor's directed SPI compare with the project's?”
Used on Performance & EVMCost & earned valueDuration ledger
Also: hours ledger, duration-weighted
The default directed ledger: every planned hour counts the same, rollups are sums, and presence-only tasks are excluded.
Why it matters When a schedule carries no cost, hours are the only honest weight. The ledger says so instead of inventing money.
Finance lens Units-of-production accounting when no cost basis exists.
How to read it Ratios from a duration ledger are pace measures, not cost measures. Do not read its SPI as a budget statement.
Ask “Is this earned value in hours or in money, and which basis does the contract use?”
Used on Performance & EVMCost & earned valueEAC
Also: estimate at completion, forecast at completion, EAC band
Estimate At Completion: the forecast final cost. The product shows it as a band because the standard formulas disagree by design.
Why it matters It is the number the owner actually cares about: what will this cost in the end.
Finance lens The full-year forecast. Different assumptions give different forecasts; the band shows the spread.
How to read it The low edge assumes the rest goes to plan; the high edge assumes the rest goes like the past. A low-confidence schedule withholds the band rather than publish a guess.
Ask “Which edge of the EAC band does the team believe, and why?”
Used on Performance & EVMCost & earned valueEarned schedule
Also: ES, AT, actual time, SPI(t), SV(t), dSV/dt
Earned value measured in time: by when should the work done so far have been done? The gap to the Project Date is the schedule variance in weeks.
Why it matters It answers the question SV and SPI cannot: how much planned time the earned work represents and how far that sits from elapsed time.
Finance lens Converting a budget variance into a time variance -- like restating a shortfall as months of runway.
How to read it SV(t) states the time gap and SPI(t) the time efficiency. Derivatives describe observed movement and amplify sampling noise. A finish estimate is a separate, evidence-gated model and never a commitment.
Ask “How many weeks ahead or behind is the work, and what evidence would be required before estimating a finish?”
Used on Performance & EVMCost & earned valueETC
Also: estimate to complete, cost to go
Estimate To Complete: the forecast cost of the remaining work.
Why it matters It is the money still at risk. EAC minus actual cost.
Finance lens Remaining commitment; cost to go.
How to read it Compare ETC with remaining budget (BAC minus EV). If ETC is larger, the project is forecasting an overrun.
Ask “How does the estimate to complete compare with the budget left?”
Used on Performance & EVMCost & earned valueEV
Also: earned value, BCWP, budgeted cost of work performed
Earned Value: budget earned by the progress actually reported.
Why it matters EV is the only number that measures accomplishment rather than time or money spent.
Finance lens Revenue recognized on a percent-complete basis. It inherits every weakness of the percent complete behind it.
How to read it EV rises with reported progress. If percent complete is optimistic, EV is optimistic, and every ratio built on it is too.
Ask “What evidence backs the progress that produced this earned value?”
Used on Performance & EVMCost & earned valueProgress index
Also: progress ratio
Self-reported progress vs where the baseline said you would be (1.0 is on plan).
Why it matters It is the simplest pace check available even without cost loading.
Finance lens Actual versus budget on the progress line, as a ratio.
How to read it Below 1.0 is behind. Because it rests on reported percent complete, pair it with remaining duration.
Ask “Does remaining duration agree with this progress index?”
Used on Performance & EVMCost & earned valuePV
Also: planned value, BCWS, budgeted cost of work scheduled
Planned Value: what the plan said would be earned by the Project Date.
Why it matters PV is the yardstick. Earned value only means something against what was planned by now.
Finance lens Budget to date -- the year-to-date budget line.
How to read it The product time-phases PV linearly across each task's planned dates unless the schedule carries its own curve. Lumpy work can make PV look smoother than reality.
Ask “How was the budget spread over time, and is that how the work was really planned to flow?”
Used on Performance & EVMCost & earned valueSPI
Also: schedule performance index, EV / PV
Schedule Performance Index: earned vs planned (1.0 is on plan; below 1.0 is behind).
Why it matters It is the quickest read on pace -- and the most misread, because it drifts back to 1.0 as a late project finishes.
Finance lens An efficiency ratio: accomplishment per unit of plan. Like any ratio, read the trend and the denominator.
How to read it 0.9 means the work is earning 90 cents of every planned dollar. It cannot tell you weeks behind, and near the end it flatters. Pair it with earned schedule.
Ask “Is SPI below 1.0 because of the critical path or because of float-rich work that does not matter yet?”
Used on Performance & EVMCost & earned valueSV
Also: schedule variance, EV - PV
Schedule Variance: earned minus planned -- negative means behind plan.
Why it matters It says how far behind the plan the work is, in budget units, as of the Project Date.
Finance lens Budget variance on the progress line: actual accomplishment versus budgeted accomplishment.
How to read it Negative is behind. Because it is measured in money, not time, it cannot say how many weeks behind; earned schedule does that.
Ask “How many weeks of work does this schedule variance represent?”
Used on Performance & EVMCost & earned valueTCPI
Also: to-complete performance index
To-Complete Performance Index: the cost efficiency the remaining work would need to finish on budget.
Why it matters It tells you whether finishing on budget is plausible. A TCPI far above the CPI achieved so far is a plan that needs a miracle.
Finance lens The margin the rest of the year would have to earn to hit the annual target.
How to read it Compare TCPI with CPI. If TCPI is 1.15 and CPI has been 0.9, the budget will not hold.
Ask “Has this project ever run at the efficiency TCPI requires?”
Used on Performance & EVMCost & earned valueVAC
Also: variance at completion, BAC - EAC
Variance At Completion: budget minus forecast final cost -- negative means a forecast overrun.
Why it matters It is the forecast overrun or underrun in one number.
Finance lens Projected variance to budget at year end.
How to read it Negative is an overrun. Because EAC is a band, VAC is a range too.
Ask “What is the forecast overrun at the high edge of the band, and is it funded?”
Used on Performance & EVMCost & earned valueWin sheet
Also: saved scope, scope sheet
A named, saved Directed EV scope -- usually one client or package -- that the server resolves the same way every run.
Why it matters It makes repeated runs comparable and auditable: the same scope, by name, every period.
Finance lens A saved report definition with a fixed segment mapping.
How to read it If a win sheet carries the subcontract's value, the commercial seat shows revenue and margin at completion per EAC scenario.
Ask “Is the win sheet's scope still the contract's scope after change orders?”
Used on Performance & EVMSchedule qualityDCMA
Also: DCMA 14-point, 14-point assessment, schedule health checks
A 14-point schedule-quality screening from the US Defense Contract Management Agency -- structure checks, not a verdict.
Why it matters A schedule that fails the structure checks can produce any date it likes. The checks tell you whether the numbers deserve trust.
Finance lens Internal-controls testing before you rely on the reported totals.
How to read it Each check has a target from project settings and reports observed vs target. Failures are findings to investigate, not a grade for the scheduler.
Ask “Which checks fail, and which of those failures sit on the critical path?”
Used on Schedule HealthSchedule qualityNot evaluated
Also: evidence-gated, withheld, unable to evaluate, needs input
A check or metric that could not run, with the reason named. It is not a pass and not a fail.
Why it matters Silence would be misread as health. Naming the missing evidence keeps the absence of a verdict from becoming a verdict.
Finance lens An auditor's disclaimer of opinion: 'unable to express an opinion' is not a clean opinion.
How to read it Read the reason. Usually it is missing data (no cost loaded, no calendar, no baseline) that can be supplied.
Ask “What would have to be provided for this check to run?”
Used on Schedule HealthSchedule qualitySchedule health
Also: schedule quality, health check
The product's one-file read of whether a schedule is built well enough for its numbers to be trusted.
Why it matters Trust comes before analysis. A review built on a broken schedule is precise about the wrong thing.
Finance lens The audit opinion on the books before you use them for decisions.
How to read it Date Gate first, then the checks grouped by theme. Failed and warning checks lead in the exceptions view.
Ask “Would you rely on this schedule's dates given these findings?”
Used on Schedule HealthSchedule qualitySchedule weather
Also: weather report, schedule weather station, signal ladder
A set of evidence-gated schedule instruments using Advisory, Watch, Warning, and Withheld to describe current readings and their witnesses.
Why it matters It separates a condition, its precursors, an observed mechanism, and an unreadable instrument without creating a risk score.
Finance lens A control dashboard whose exceptions name the test and evidence rather than a synthetic score.
How to read it A Watch names what would promote it to Warning; Withheld names the missing witness. The report is a nowcast, not a finish forecast.
Ask “Which witness produced this signal, and what would change its evidence state?”
Used on ReportsSchedule qualitySchedule weather radar
Also: weather radar, schedule radar
A relationship view that places existing schedule-instrument readings by consequence and time to effect without calculating a new score.
Why it matters It aligns several bounded readings on one decision surface while preserving each reading's own evidence state.
Finance lens A dashboard layout, not a new accounting measure.
How to read it Trails show observed rank movement. No forward track is drawn because future movement is not known.
Ask “Which underlying instrument and release pair support this cell?”
Used on ReportsSchedule qualityTalk-now gap
Also: progress gap, claimed vs evidenced
Claimed progress running ahead of effort evidence by more than the project threshold -- the incentive is to say it before the gap opens.
Why it matters It catches optimism early, while it is a conversation rather than a surprise.
Finance lens Revenue recognized ahead of cost incurred -- the first thing an auditor tests.
How to read it A task is flagged when its percent complete exceeds what its hours or quantities support by the configured margin.
Ask “Which tasks are claimed ahead of their evidence, and what is the real status?”
Used on Performance & EVMSchedule qualityWindows analysis
Also: time impact analysis, TIA, delay analysis, windows
A delay analysis that splits the project into windows bounded by consecutive Project Dates and attributes what changed inside each one.
Why it matters It is how delay is allocated defensibly: period by period, from the schedules that existed at the time.
Finance lens Period-by-period variance analysis, each period closed on its own statements.
How to read it The product composes the windows and the evidence; the analysis argument is the consultant's. Window boundaries are the schedules' own Project Dates.
Ask “In which window did the critical delay occur, and what changed in the schedule during it?”
Used on ForensicsSchedule qualityWithheld claim
Also: WITHHELD, insufficient evidence, claim withheld
A conclusion the available evidence is not allowed to support, accompanied by the exact missing prerequisite.
Why it matters It prevents an unknown from becoming a zero, pass, forecast, or invented conclusion.
Finance lens A scoped disclaimer rather than an unqualified opinion.
How to read it Supply the named witness or leave the claim unanswered. A withheld state is not adverse or favorable evidence.
Ask “What exact evidence would permit this claim to be evaluated?”
Used on All schedule viewsProcess & evidenceChain of custody
Also: custody, custody sheet, provenance, evidence trail
Who uploaded what, when, with fingerprints -- the record that a finding traces back to exact, unmodified files.
Why it matters In a dispute, the question is never only what the schedule says; it is which schedule, received when, from whom, unaltered.
Finance lens The audit trail behind a journal entry.
How to read it Every file carries a SHA-256 fingerprint, a received time, and an uploader identity. The custody sheet can be re-verified later against the account's seal.
Ask “Can this review be tied to the exact files the scheduler sent, and can that be proven later?”
Used on ForensicsProcess & evidenceClaims pack
Also: claims package, evidence pack, dispute pack
The day-one handoff for a dispute: custody sheets, deltas between sealed reviews, the windows, and verification receipts in one sealed archive.
Why it matters It lets a consultant or counsel start from evidence rather than from a request for evidence.
Finance lens The audit binder.
How to read it Metadata and findings only; raw schedule files stay with the project. Every item in it is sealed and re-verifiable.
Ask “Is the claims pack complete for the windows in dispute?”
Used on ForensicsProcess & evidenceDecision memory
Also: accepted answer, challenged answer, superseded answer
Append-only dispositions and notes attached to a discussion answer without rewriting the answer or its schedule evidence.
Why it matters A later decision can disagree with an earlier reading while preserving what was known at the time.
Finance lens A subsequent-event note that does not reopen the closed-period ledger.
How to read it Accepted, challenged, and superseded describe governed human disposition; they do not change the source schedule facts.
Ask “What later review or evidence changed the team's disposition?”
Used on HomeProcess & evidenceDeterministic answer
Also: bounded answer, evidence-backed answer
A bounded answer produced from declared fields, calculations, and evidence gates so the same immutable inputs produce the same reading.
Why it matters The reader can inspect the calculation and know exactly why a conclusion was answered or withheld.
Finance lens A formula-driven report with traceable source cells and controls.
How to read it Check the cited review, fields, formula, units, and authority ceiling; unsupported questions are withheld.
Ask “Can this answer be reproduced from the cited evidence receipt?”
Used on HomeProcess & evidenceFingerprint
Also: sha256, SHA-256, hash, content hash, sha
A SHA-256 hash of a file's bytes: a short code that changes if even one character of the file changes.
Why it matters It proves a file is the same one received earlier, and it catches the same file uploaded twice under different names.
Finance lens A check digit on the whole document.
How to read it Two files with the same fingerprint are byte-identical. The product refuses duplicates and links identical files across reviews.
Ask “Does the fingerprint of this file match the one in the custody record?”
Used on ImportsProcess & evidenceOwner light
Also: project light, RAG, traffic light
The red, amber, or green on a project, always with its reasons listed beside it.
Why it matters A light without a reason is a mood. The reasons are what you take into the meeting.
Finance lens A covenant dashboard: status plus the test that produced it.
How to read it Red comes from named facts: at-risk precursors, a forecast finish past the contract date, negative float. Click through to each one.
Ask “Which single reason would turn this light green, and who owns it?”
Used on ReportsProcess & evidencePrecursor checklist
Also: precursors, preconditions, readiness
The things that have to be true before an upcoming task can start -- permits, deliveries, access, crews -- tracked by the crews themselves.
Why it matters Most slips are a precursor that was not ready. Tracking them is how a look-ahead becomes an early warning.
Finance lens Conditions precedent.
How to read it At-risk items feed the owner light and the weekly digest. An item at risk for two weeks running is a delay being scheduled.
Ask “Which precursors are at risk this week, and who is clearing them?”
Used on ReviewProcess & evidenceProvisional identity
Also: same-code match, candidate identity, identity witness
A cross-release activity match based on stable task code or another declared heuristic, pending a governed identity mapping.
Why it matters Movement calculations require the same subject on both sides; a re-key, split, or merge can otherwise masquerade as change.
Finance lens A proposed account match awaiting reconciliation.
How to read it Provisional comparisons may support discussion, but verified-series language is reserved for governed mappings.
Ask “Were any activities re-keyed, split, merged, or moved between WBS branches?”
Used on Baseline CompareProcess & evidenceSchedule evidence graph
Also: evidence graph, schedule graph
A provenance-safe map connecting immutable reviews, schedule observations, calendars, milestones, procurement snapshots, discussions, and decision events.
Why it matters It lets a reader follow a claim back to the release, fields, and bounded calculation that support it.
Finance lens The audit trail and supporting-ledger links behind a reported figure.
How to read it A relationship proves only what its type and identity basis say. Matching activity codes are provisional until a governed mapping verifies identity.
Ask “Which review, relationship, and identity basis support this reading?”
Used on HomeProcess & evidenceSealed
Also: seal, sealed manifest, receipt, evidence pack
A record whose contents are hashed so that any later change is detectable; the product seals manifests, receipts, and custody sheets.
Why it matters It turns 'we did not change it' from a promise into a check anyone can run.
Finance lens A signed, dated statement -- tamper-evident.
How to read it Verification answers altered-or-not by name. A seal that does not verify is an integrity incident, not a formatting issue.
Ask “Has every sealed record in this claims pack been verified, and when?”
Used on ForensicsProcess & evidenceVersion role
Also: declared role, baseline role, committed version
The declared role of a schedule file on the project -- baseline, current update, what-if -- committed at upload so it cannot be quietly swapped later.
Why it matters It records what each file was meant to be, which is the first question in any later dispute about which schedule governed.
Finance lens Labeling a statement as the approved budget versus a forecast revision.
How to read it Declared roles are immutable: a superseding file is uploaded, never edited in place. Positional roles (older/newer) are the fallback when nothing was declared.
Ask “Which file was declared as the baseline for this period, and by whom?”
Used on ImportsProcess & evidenceWeekly commitment
Also: commitments, weekly work plan, PPC
What a crew commits to finishing this week, and whether each item ended done, still open, or blocked.
Why it matters Commitment reliability predicts schedule reliability. Crews that finish what they commit to keep the forecast honest.
Finance lens Forecast accuracy tracking.
How to read it The rollup shows committed, done, and blocked. Blocked items name their reason; that reason is usually a precursor.
Ask “What blocked this week's commitments, and is it the same thing as last week?”
Used on ReviewIdentity / FK · join keyTASK.task_id
Native TASK primary key used to join schedule tables.
- Canonical
sourceTaskId- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Imports, Forensics
Identity / FK · join keyTASK.proj_id
Native project foreign key for the activity.
- Canonical
sourceProjectId- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Imports, Forensics
Identity / FK · join keyTASK.wbs_id
Foreign key to the activity's WBS branch.
- Canonical
sourceWbsId- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Reports, Forensics
Calendar · criticalTASK.clndr_id
Activity calendar identity. Working-day conversion is withheld unless this calendar can be resolved.
- Canonical
calendarId- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Identity / FK · criticalTASK.task_code
Human-facing activity identifier within the schedule.
- Canonical
taskCode- Unit
- source value
- Aliases
- activity_id
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on All schedule views
Identity / FK · contextualTASK.task_name
Human-facing activity description.
- Canonical
taskName- Unit
- source value
- Aliases
- activity_name
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on All schedule views
Dates · criticalTASK.act_start_date
Recorded actual start; blank means no actual start was supplied.
- Canonical
actualStartDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Review, Forensics
Dates · criticalTASK.act_end_date
Recorded actual finish; blank means no actual finish was supplied.
- Canonical
actualFinishDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Review, Forensics
Dates · criticalTASK.early_start_date
P6 forward-pass early start when exported.
- Canonical
earlyStartDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Critical Path What-If, Forensics
Dates · criticalTASK.early_end_date
P6 forward-pass early finish when exported.
- Canonical
earlyFinishDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Critical Path What-If, Forensics
Dates · criticalTASK.late_start_date
P6 backward-pass latest allowable start when exported.
- Canonical
lateStartDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Dates · criticalTASK.late_end_date
P6 backward-pass latest allowable finish when exported.
- Canonical
lateFinishDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Dates · importantTASK.expect_end_date
Scheduler-entered expected finish. Its presence is a review signal, not evidence of intent or manipulation.
- Canonical
expectedFinishDate- Unit
- source value
- Aliases
- expected_finish
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Forensics
Dates · importantTASK.restart_date
Remaining-work start supplied for an in-progress activity.
- Canonical
remainingStartDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Forensics
Dates · importantTASK.reend_date
Remaining-work finish supplied for an in-progress activity.
- Canonical
remainingFinishDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Forensics
Dates · importantTASK.suspend_date
Recorded date on which work was suspended.
- Canonical
suspendDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Forensics
Dates · importantTASK.resume_date
Recorded date on which suspended work resumed.
- Canonical
resumeDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Forensics
Baseline · criticalTASK.target_start_date
Planned or target start carried by TASK.
- Canonical
targetStartDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Milestones, Reports
Baseline · criticalTASK.target_end_date
Planned or target finish carried by TASK.
- Canonical
targetFinishDate- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Milestones, Reports
Float + critical path · criticalTASK.total_float_hr_cnt
Total float in hours. Working days require the activity calendar; zero or negative float is a path signal, not a causal conclusion.
- Canonical
totalFloatHours- Unit
- hours
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Reports
Float + critical path · criticalTASK.free_float_hr_cnt
Free float in hours before the earliest successor is delayed.
- Canonical
freeFloatHours- Unit
- hours
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Reports
Float + critical path · criticalTASK.driving_path_flag
P6 source flag for driving-path membership; it remains separate from independently observed total float.
- Canonical
drivingPathFlag- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Critical Path What-If, Forensics
Float + critical path · criticalTASK.cstr_type
Primary P6 constraint type.
- Canonical
constraintType- Unit
- source value
- Aliases
- constraint_type
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Float + critical path · criticalTASK.cstr_date
Date associated with the primary constraint.
- Canonical
constraintDate- Unit
- source value
- Aliases
- constraint_date
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Float + critical path · importantTASK.cstr_type2
Secondary P6 constraint type when exported.
- Canonical
constraintType2- Unit
- source value
- Aliases
- constraint_type2
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Float + critical path · importantTASK.cstr_date2
Date associated with the secondary constraint.
- Canonical
constraintDate2- Unit
- source value
- Aliases
- constraint_date2
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Forensics
Duration · criticalTASK.target_drtn_hr_cnt
Planned duration in hours. Working-day display requires a resolved activity calendar.
- Canonical
targetDurationHours- Unit
- hours
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Performance & EVM
Duration · criticalTASK.remain_drtn_hr_cnt
Remaining duration in hours; blank is unknown and never zero-filled.
- Canonical
remainingDurationHours- Unit
- hours
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Critical Path What-If
Duration · importantTASK.act_work_qty
Actual work quantity as exported; its unit remains source-declared unless independently resolved.
- Canonical
actualWorkQuantity- Unit
- hours or source quantity
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Performance & EVM, Forensics
Duration · importantTASK.target_work_qty
Planned work quantity as exported; not assumed to be calendar duration.
- Canonical
targetWorkQuantity- Unit
- hours or source quantity
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Performance & EVM, Forensics
Duration · importantTASK.remain_work_qty
Remaining work quantity as exported; blank remains unknown.
- Canonical
remainingWorkQuantity- Unit
- hours or source quantity
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Performance & EVM, Forensics
Duration · importantTASK.duration_type
P6 duration-type basis controlling how duration, units, and resources interact.
- Canonical
durationType- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Forensics
Status + progress · criticalTASK.status_code
P6 activity status such as not started, active, or complete.
- Canonical
statusCode- Unit
- source value
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Review, Performance & EVM
Status + progress · importantTASK.phys_complete_pct
Physical percent complete supplied by the schedule.
- Canonical
physicalPercentComplete- Unit
- percent
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Performance & EVM, Forensics
Status + progress · criticalTASK.cmplt_pct_type
Native P6 percent-complete basis (physical, duration, or units).
- Canonical
percentCompleteType- Unit
- source value
- Aliases
- complete_pct_type
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Performance & EVM, Forensics
Status + progress · importantTASK.act_pct_complete
Current percent value exported for the active completion basis.
- Canonical
activePercentComplete- Unit
- percent
- Aliases
- none
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Performance & EVM, Forensics
Task type · criticalTASK.task_type
P6 task type. LOE and WBS summary activities are excluded from critical-path populations.
- Canonical
taskType- Unit
- source value
- Aliases
- task_type_code
- Interpretation limit
- This source field is evidence to interpret with its review context; it does not establish cause, responsibility, intent, or entitlement.
Used on Schedule Health, Critical Path What-If, Forensics
