structuraline

Reference

What the words mean

The vocabulary a schedule report uses, in plain terms. Every one of these also explains itself where it appears.

Activity ID match

How much of this file's activity ID list is shared with the schedule it is compared with. Low means they may be different projects.

Approved extension

A change to the contract completion date that the owner has approved. A request on its own does not move the date.

Asserted

One party says so and the other has not agreed. Recorded as their position, nothing more.

Baseline

The schedule your contract runs against. Later updates are measured from it.

Blocking

A requirement stated in absolute terms that this file does not meet. Expect it to be raised on review.

Compared against

The schedule this one was measured from. You choose it; the previous submission is only the default.

Contract completion

The date the contract requires, including approved extensions. Only an approved document moves it.

Critical path

The chain of activities that decides the finish date. Anything that slips on it moves the finish.

Data date

The moment the schedule was statused. Everything before it is history; everything after is forecast.

Disputed

The parties disagree. Recorded as both positions; it moves no date.

Float

How long an activity can slip before it delays the work that follows. Zero or less means it is driving the finish date.

Forecast completion

When this schedule says the work will finish. It is the contractor's own forecast, not a contract date.

Needs your judgment

The specification leaves this to a person -- approval, reasonableness, or something a schedule file cannot show.

Negative float

The schedule cannot meet a date it is measured against. The number is how many working days short it is.

New

Present in this schedule and not in the one it was compared against.

Not verifiable

The file does not carry what the check needs, so we report what is missing instead of guessing.

Original contract completion

The completion date the contract started with, before any approved extension.

Pending

Submitted and awaiting a decision. It changes no contract date until it is approved.

Progress update

A schedule statused to a new data date, showing where the work actually is.

Recovery schedule

A re-planned schedule submitted to show how lost time will be made up.

Resolved

Present in the earlier schedule and gone from this one.

Specification edition

The published edition of the owner's specification we checked against. Your contract's own edition governs.

Still open

Present in both schedules. It has not been dealt with since the last submission.

Time impact analysis

An update carrying a fragnet, used to show the schedule effect of one delay or change.

--:--:-- LOCAL
SCHEDULE COMPLIANCE · 7 OWNERS
0 × 0  X000 Y000