Skip to main content

Schedule Dependencies

Skip to main content
How can we help you today?

Our Knowledge Base contains the answers to more than 500 previously asked questions.

Create a Ticket Schedule a Training

Schedule Dependencies


Overview
Understanding how tasks connect in a schedule is essential for keeping projects organized and on time. In Contractor Foreman, you can define dependencies, predecessors, and lead/lag times to control the sequence and timing of your project’s activities.


What Are Schedule Dependencies?

A dependency defines the relationship between two tasks — how the start or finish of one affects the other.
For example, you can’t begin painting until drywall installation is complete. Dependencies ensure your project flows logically and efficiently.


Types of Dependencies

There are four main types of task dependencies in Contractor Foreman. Each defines a different relationship between two activities.

  1. Finish-to-Start (FS) – Most common type

    • Task B starts only after Task A finishes.

    • Example: You can’t pour concrete (Task B) until formwork is complete (Task A)

  2. Start-to-Start (SS)

    • Both tasks can start around the same time, but Task B can’t start until Task A has started.

    • Example: Excavation (Task A) and foundation preparation (Task B) may start together.

  3. Finish-to-Finish (FF)

    • Task B can’t finish until Task A finishes.

    • Example: Electrical and plumbing inspections often complete at roughly the same time.

  4. Start-to-Finish (SF) – Least common type

    • Task B can’t finish until Task A starts.

    • Example: Temporary power must remain active until permanent power installation begins.


What Are Predecessors?

A predecessor is the task that must occur before another one.
When you assign a predecessor in Contractor Foreman, the system automatically links both activities according to the chosen dependency type.

Example:
If “Drywall” lists “Framing” as its predecessor (Finish-to-Start), the drywall task will begin only after framing is completed.
(Insert Screenshot: Task dependency setup with predecessor)


Lead and Lag Time

Dependencies can be adjusted using lead or lag time to fine-tune your schedule:

  • Lead Time → Allows tasks to overlap.

    • Example: Start painting 2 days before drywall is fully done (lead = –2 days)

  • Lag Time → Adds a delay between tasks.

    • Example: Wait 3 days after concrete curing before starting framing (lag = +3 days)


Why It Matters

Using dependencies correctly helps you:

  • Identify your project’s critical path.

  • Avoid overlapping tasks or scheduling conflicts.

  • Adjust quickly when delays occur.

  • Improve team coordination by clearly showing task relationships.

Even non-technical team members can easily understand your schedule when dependencies are properly defined.


Summary

Term Meaning Example
Dependency Relationship between two tasks “Drywall” depends on “Framing”
Predecessor Task that occurs before another “Framing” precedes “Drywall”
Lead Time Overlap allowed Start painting 2 days early
Lag Time Delay between tasks Wait 3 days after curing before framing

 

 

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.