Esc

↑↓ move↵ openIndex · Pagefind

Activity durations and logic: build a schedule the field can update

Choose useful activity detail, support durations with production assumptions and test whether dependency logic represents real construction handoffs.

Charley Forey2 min readSchedulingSchedule forensics
On this page
  1. Give the duration a basis
  2. Model the physical handoff
  3. Check both ends of the activity
  4. Keep contract limits and planning judgment separate

A schedule activity should describe work someone can plan, recognize and update. Too little detail hides problems. Excess detail creates a model nobody can maintain. Start with the decisions the project needs to make, then choose activities and logic that expose those decisions.

Give the duration a basis

For a fictional installation, 120 units at an expected 20 units per crew-day implies six crew-days of work. That is a planning assumption, not a promise. Confirm the quantity definition, crew composition, access, working hours and whether preparation or testing is included.

Input Question to record
Quantity What exactly is being counted?
Production rate What comparable work or crew input supports it?
Crew Is the assumed crew actually available?
Calendar Which days and hours are usable?
Scope boundary What must happen before work starts and before it is complete?

Avoid dividing duration automatically when adding workers. Limited space, shared equipment or inspection availability may prevent proportional gains.

Model the physical handoff

Finish-to-start logic is straightforward when one complete activity releases the next. Where trades overlap, define the handoff clearly. A start-to-start relationship can represent a real overlap, but check whether the predecessor’s finish is also connected where necessary.

Make an area release visible

Rough-in area A → inspect area A → release area A → close walls area A.

A separate sequence for area B can show overlap without relying on an unexplained negative lag.

This is an illustrative decomposition. Use the level of detail the team can maintain and the project requires; do not subdivide every activity simply to increase the count.

Check both ends of the activity

An activity may have a predecessor and successor yet still fail to transmit a meaningful finish delay. Inspect the relationship types, not just the link count. Ask what happens if the activity takes longer: does the correct downstream work move?

Run that sensitivity on a copy, then restore the original. A failed response may expose missing logic, a constraint or an intentional alternative path. Record the explanation rather than assuming every nonmoving milestone means an error.

Keep contract limits and planning judgment separate

If the project sets a maximum activity duration or restricts relationship types, record the exact provision, units and exceptions. Procurement, level-of-effort work and field installation may be treated differently. Do not substitute a customary number for the incorporated requirement.

The GAO Schedule Assessment Guide provides a broader reference for schedule development and review. Use field knowledge and project records to test the model’s specific production assumptions.

Continue with lags and leads, the audit checklist, or the Schedule Forensics resource 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