Esc

↑↓ move↵ openIndex · Pagefind
Construction lessons in a minute · 0:48

The Schedule Has a Wait. Does Anyone Own It?

Expose what an important waiting period represents without pretending the model change saves time.

An animated teaching example with AI narration. The illustrations explain the process; they are not a recording of the app.

Published · Illustrative examples · Watch on YouTube

Video transcript

Your schedule says, wait sixteen hours. Wait for what? A lag can show time without explaining the process behind it.

In this example, task A finishes, then a sixteen-working-hour review wait comes before task B. One calendar governs the whole chain.

Compare a named review activity with the same duration and zero-lag links. In this simple model, B starts at the same time.

The benefit is visibility: a place to name the owner and report the remaining wait. Do not count the original lag again.

Ask what each important lag represents before changing it. Explore the scheduling guides at os dot construction.

Your next step

See it on one project record.

Explore the written guide, then open the sample project to see how construction records connect.

Try it in the app
Open file