Job Dependencies
Define the order your work needs to happen. Set prerequisite relationships between jobs so nothing starts before its predecessor is done -- with blocking enforcement, override tracking, and a visual dependency graph.
Four relationship types
Not every dependency works the same way. Choose the relationship type that matches how your jobs actually connect.
Finish to Start
Job B cannot start until Job A is finished. The most common pattern for sequential work.
Finish to Finish
Job B cannot finish until Job A is finished. Both can run in parallel but must complete together.
Start to Start
Job B cannot start until Job A has started. Useful for coordinated kickoffs.
Start to Finish
Job B cannot finish until Job A has started. The least common type, used for handoff timing.
Block work that should not start yet
When a dependency is set to blocking, the dependent job cannot advance its status until the prerequisite is met. Your team sees exactly why a job is held and what needs to happen first.
Blocking dependencies
Prevent a job from advancing its status until all prerequisites are met.
Non-blocking dependencies
Track relationships without preventing status changes. Useful for soft sequencing.
Status check endpoint
Query whether all prerequisites are met before moving a job forward.
Dependency Check
JOB-2026-00041
Foundation Inspection
JOB-2026-00042
Framing & Structural
JOB-2026-00043
Electrical Rough-In
Waiting on: Framing & Structural
Override Record
Dependency Override Applied
JOB-2026-00043 → JOB-2026-00042
Customer requested early start on electrical to meet inspection deadline. Framing is 90% complete and crew confirmed safe to proceed.
Override when needed, with a paper trail
Real job sites are not always predictable. When a blocking dependency needs to be bypassed, authorized users can override it -- but the system records who did it, when, and why.
Authorized overrides
Owners and dispatchers can bypass blocking dependencies when circumstances require it.
Reason tracking
Every override requires a written reason explaining why the dependency was bypassed.
Full audit trail
Who overrode, when, and why -- all recorded and visible in the audit log.
See the full dependency chain
See all job dependencies and which jobs are blocking downstream work.
Visual Graph
See all job relationships mapped out visually
Status at a Glance
Color-coded nodes show which jobs are done, active, or blocked
Dependency Status
Identify which jobs are holding up downstream work
Max Dependencies
Configurable per company to prevent overly complex chains
Dependency Graph
Site Preparation
JOB-2026-00041
Foundation Work
JOB-2026-00042
Framing & Structural
JOB-2026-00043
Electrical Rough-In
JOB-2026-00044
Plumbing Rough-In
JOB-2026-00045
Built for real job site coordination
Dependencies are a coordination tool, not an obstacle. Everything is designed to keep work flowing while preventing costly mistakes.
Prerequisite Validation
The system checks all dependencies before allowing a job to advance its status.
Configurable Limits
Set the maximum number of dependencies per job to keep complexity manageable.
Dependency Graph API
An endpoint returns structured graph data for visual rendering of job relationships.
Override with Audit
Bypass blocking dependencies when needed. The system records who, when, and why.
Works with Projects
Dependencies pair naturally with project management for coordinating multi-job scopes.
Role-Based Control
Only authorized roles can create, modify, or override job dependencies.
Works alongside your other tools
Job dependencies integrate with the rest of Pillar -- from scheduling and dispatch to project management and audit logs.
Included in the Enterprise plan
ProJob dependencies are part of the Enterprise plan alongside project management, contracts, audit logging, and API access. Start with a 14-day free trial to explore the full feature set.
See job dependencies in action
Walk through dependency setup, blocking enforcement, and the visual graph with your real job types. We will show you how it fits your workflow.