Dependencies

A dependency records that one task relies on another — that work has to happen in a certain order. Capturing dependencies is what turns a flat list of tasks into a realistic schedule, and it's what lets Bluprint warn you when the plan doesn't add up.

You manage dependencies from the Dependencies panel in the task editor.

The four dependency types

Every dependency has a type that describes exactly how the two tasks relate. Finish-to-start is by far the most common; the others cover work that overlaps in time.

Type	Rule	Everyday example
Finish-to-Start (default)	The blocked task can't start until the blocking task finishes.	You can't ice the cake until it's baked.
Start-to-Start	The blocked task can't start until the blocking task starts.	Translation can't start until writing starts.
Finish-to-Finish	The blocked task can't finish until the blocking task finishes.	Editing can't finish until writing finishes.
Start-to-Finish	The blocked task can't finish until the blocking task starts.	The night-shift guard can't clock off until the day-shift guard clocks on.

Internal vs external dependencies

Dependencies have a scope:

• Internal — both tasks live in the same project. This is the common case.
• External — the dependency crosses into another project or workspace. Bluprint keeps the names of the linked project and workspace alongside the dependency so the relationship stays clear even though the tasks live apart.

Hard vs soft enforcement

Each dependency also has an enforcement mode:

• Hard — a true blocker; the order must be respected.
• Soft — a preferred order or a nice-to-have sequence, not a hard rule.

This lets you distinguish "this genuinely cannot proceed" from "we'd rather do these in this order".

What dependencies power

Once tasks are linked, dependencies do real work across Bluprint:

• Gantt arrows — the timeline draws the links between tasks so the sequence is visible.
• Critical path — Bluprint can calculate the chain of dependent tasks that directly determines the project's end date.
• Notifications — people subscribed to a dependency are kept informed when the linked tasks change, so a slip upstream doesn't surprise the team downstream.

Next

• Statuses & priorities
• Views: the Gantt chart