Work a project's schedule

Anchors, the permit lattice, the task tracker and the critical dates for one project, on one page.

A project's schedule is one page with four sections, in the order the work happens. Anchors are the events and contracts every rule below refers to. Clocks are the permit lattice for this project. Tasks are the tracker view, grouped, with plan against actual. Critical dates are the deadlines that carry a consequence, banded by how soon they land.

A jump bar under the header moves between the four, because one long page only beats two tabs if a thumb can get around it.

Anchors and the cascade

An anchor is a real event: a contract signed, a plat recorded, an approval issued. Dates below it are not typed. They are stated as a rule against the anchor, for example thirty business days after recording.

Move the anchor and every date derived from it moves. Nothing is retyped and nobody has to be told. That is the most useful thing this page does, and it is why importing a plan as rules is worth more than importing it as values.

Reading a long task list

A couple of hundred rows is a schedule, not a list. The filter pills above the table cut it to what is late, what has no plan, what is still open, and what is done. Above a threshold the groups arrive folded, because a long imported schedule wants to be navigated rather than read.

The same pills sit on the critical dates register below, so both surfaces are worked the same way.