Esc

↑↓ move↵ openIndex · Pagefind

Schedule constraints: explain the date before changing the logic

Review imposed dates, understand negative float and document constraints without confusing a calculation result with responsibility for delay.

Charley Forey2 min readSchedulingSchedule forensics
On this page
  1. Separate three questions
  2. Understand negative float with a simple example
  3. Build a constraint register
  4. Resolve the underlying condition

A constraint records a date condition outside the dependency network. It might represent access, a contractual milestone or a management target. The same date can produce different results depending on the constraint type, so a review must capture both.

The GAO Schedule Assessment Guide, Appendix V, discusses constraint effects. Consult your scheduling application’s definitions as well: labels and behavior need to be understood in the tool actually used.

  1. 01PreserveOriginal file + issue date
  2. 02CorroborateDaily records + notices
  3. 03ExplainCause + affected work
  4. 04ReviewAssumptions + decisions
A schedule result becomes useful when someone can trace it back to a dated record and a documented assumption.

Separate three questions

Question What answers it
Why is this date present? Contract, access agreement, owner instruction or planning assumption
What does it do to the network? Constraint type, calculation settings and a controlled recalculation
Is it appropriate here? Project requirements and the responsible reviewer’s decision

Do not jump from the second question to the third. Finding a constrained activity at zero float does not establish that someone manipulated the schedule. It identifies an activity whose date logic needs an explanation.

Understand negative float with a simple example

Suppose a fictional path needs twelve working days from the status point, while a finish requirement allows ten. With a common calendar and a finish limit influencing the backward pass, the two-day mismatch can appear as negative float.

That calculation identifies a conflict between the modeled remaining work and the required date. It does not say why the work needs twelve days, who caused the conflict or whether an extension is due. Those questions require records and contract analysis.

Deleting the finish requirement may remove negative float while leaving the twelve-day forecast unchanged. The display looks cleaner; the project has not recovered any time. Preserve the distinction between improving the plan and changing what the report measures.

Build a constraint register

For each constraint retain the activity ID, type, date, source, reason, owner, approval status and last review date. Mark temporary planning assumptions so they receive attention when better information arrives.

Review a copy with the constraint altered or removed when that helps understand its effect. Compare early dates, late dates, float and the completion path. Label the run as a sensitivity test and retain the original result. Do not quietly replace a submitted schedule with the experimental version.

Resolve the underlying condition

An access constraint may need a revised handover agreement. A contractual deadline may require a credible recovery plan. An unexplained historical pin may need clarification from the scheduler. Each leads to a different action, which is why a constraint count alone is insufficient.

Follow the schedule audit checklist to turn findings into review comments, or study recovery planning. All guides are collected in the Schedule Forensics library.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file