Block dependencies

Link work blocks so one can't start until another finishes — creating the logical sequence that recast uses to calculate your schedule.

Dependencies define the order of work. You can't pave until grading is done. You can't backfill until the pipe is laid. Dependencies encode this logic so the scheduling system can calculate dates automatically and cascade changes correctly. When the grading block takes two extra days, every block that depends on it shifts accordingly.

Finish-to-start dependencies

Gradeworks uses finish-to-start dependencies: Block B can't start until Block A finishes. This is the most natural way to express construction sequencing — "do this, then do that." Every dependency creates a predecessor-successor relationship: A is B's predecessor, and B is A's successor.

Creating dependencies visually

On the project timeline, hover over the right edge of a block until a connector dot appears
Click and drag from the dot to the successor block
Release on the successor block — an arrow line connects them
The successor block's start date recalculates based on the predecessor's end date

You can also create dependencies in the block detail panel: open a block, scroll to Dependencies, and select predecessors from the dropdown. Both methods create the same link.

Dependency chains

Dependencies can form a sequence — if grading must finish before paving, and paving must finish before striping, then a delay in grading pushes everything back. The longest sequence of dependent blocks determines your project's finish date. Delays on that sequence delay the entire project. Blocks not on that sequence have some built-in flexibility — they can slip a few days without affecting the end date.

Pro tip

Don't create dependencies between every block. Only link blocks that have a true logical dependency — the second genuinely cannot start until the first finishes. Over-linking creates an artificially rigid schedule. Two blocks that happen to run sequentially don't need a dependency unless the order is required.

Removing dependencies

Click the arrow line connecting two blocks and press Delete, or open the block detail panel and remove the predecessor. Removing a dependency frees the successor block to be scheduled independently. Recast recalculates to reflect the removed constraint.

Circular dependencies

Gradeworks prevents circular dependencies (A depends on B, which depends on C, which depends on A). If you try to create one, the system rejects the link and shows a warning. If you see this error, re-examine your dependency chain — there's a logical mistake in the sequence.

Was this helpful?

Working with work blocks

Create, configure, and manage work blocks — the individual units of work that make up your project schedule.

Automatic rescheduling (recast)

How Gradeworks automatically recalculates your project schedule when changes happen — respecting dependencies, pinned dates, and the work week calendar.

The project timeline

Visualize and manage your entire project schedule on the timeline — create blocks, set dependencies, assign crews, and watch the schedule respond to changes in real time.

Parallel work blocks

Schedule overlapping work blocks to compress project timelines — when crews can work simultaneously without interfering with each other.