Dependencies: explaining the sequence that work requires

A dependency describes a relationship between pieces of work. A finish-to-start dependency means that one task needs to finish before another can start. It is useful when the sequence is a real constraint, such as inspection before handover, rather than merely a preferred order on a list.

Dependencies make the consequences of delay easier to discuss. If inspection is late, the handover date may be exposed even when the handover task itself is short. The dependency explains the connection between the two.

DNA's task relationships

DNA's task creation and editing forms support selecting prerequisite tasks. These forms send selected relationships as finish-to-start dependencies. The task and its dependency records are saved through separate requests.

That separation matters: successful task creation does not by itself prove that every selected dependency was saved. The reviewed creation flow can retain a created task even if a subsequent dependency request fails. A reliable plan therefore needs its saved relationships checked, particularly after an interrupted operation.

Choosing dependencies carefully

Northstar plans equipment preparation, installation, inspection and handover. Installation requires prepared equipment; handover requires accepted inspection. These are meaningful dependencies. Making every administrative task depend on every other task would add complexity without describing real constraints.

A circular plan is logically impossible: if A must wait for B and B must wait for A, neither has a valid starting condition. The planning responsibility is to resolve that contradiction, not to assume that a visual chart makes it workable.

Dependency is not resource availability

Two independent tasks can still compete for the same specialist. Conversely, two tasks with different assignees may have a genuine technical dependency. Sequencing and resource availability are different planning questions.

Do not assume that adding a dependency reserves a person, books equipment or automatically updates every affected date. Use the saved relationships to explain the intended sequence, then review dates, ownership and real constraints together.