How dependency scheduling works
A dependency makes one item wait for another. Teamhood keeps every waiting item at the earliest date its dependencies allow. So the item moves later when a predecessor grows or moves later, and earlier when a predecessor shrinks or moves earlier.
A Start you set becomes a pin: the item’s start no earlier than that date. Scheduling never starts the item, or anything below it, before its pin.
What a dependency asks of the dates
Section titled “What a dependency asks of the dates”Working days are Monday to Friday for the whole organization, except the organization’s holidays. Every day count in scheduling is in working days: lag, the days an item moves, and the free days before a limit.
A dependency joins a predecessor, the item that goes first, to a successor, the item that waits. The dependency sets the earliest date the successor may have. Scheduling always reads and writes the Start and Finish fields. A Gantt that maps other date fields draws its bars from those fields, and a drag there changes only them.
| Type | Date it limits | Earliest allowed date |
|---|---|---|
| Finish to Start | the successor’s start | the next working day after the predecessor’s finish |
| Start to Start | the successor’s start | the predecessor’s start |
| Finish to Finish | the successor’s finish | the predecessor’s finish |
| Start to Finish | the successor’s finish | the predecessor’s start |
Finish to Start is the default. Lag adds whole working days to the earliest allowed date, and weekends and holidays are skipped. A negative lag is a lead, and it moves the earliest allowed date earlier by that many working days.
Where scheduling places an item
Section titled “Where scheduling places an item”An item that waits on a dependency starts at the latest date its dependencies require. The dependency can be the item’s own, or one held by a parent above it. When the item’s pin is later than that date, the item starts at its pin instead.
- The item moves in both directions. A predecessor that grows or moves later pushes it, and a predecessor that shrinks or moves earlier pulls it.
- An item with several predecessors starts at the latest date any of them requires.
- Every moved item keeps its length in working days. An item moved across a weekend or a holiday covers more calendar days, because those days are not counted.
- A change travels down the whole chain, from successor to successor. It stops at an item that its pin still holds in place.
An item with no dependency is never moved by scheduling, as long as no parent above it has one either. Its dates are yours. The one exception is a pin: a pin on the item, or on a parent above it, is still its earliest start.
The pin
Section titled “The pin”The pin is not a field of its own. It belongs to the item’s Start, and Teamhood sets it to that Start whenever you set it:
- by dragging the whole bar on the Gantt;
- by dragging the start edge of the bar;
- by editing Start in the item details or in a date cell, for one item or for many at once;
- by giving an item a Start when you create it.
Dragging only the finish edge sets no pin. Editing only Finish or Duration (d) sets none either. A drag of the finish edge changes the item’s Duration (d).
A pinned item shows a pin next to its Start in the item details, and on the start of its Gantt bar. Hovering the pin shows its date, and the dependency that holds the item later than its pin, if there is one.
Clearing Start clears the pin. To drop the pin without clearing Start, press the pin next to Start in the item details. You can do that only if you can edit Start.
- A pin you clear lets an item with dependencies move to the earliest date they allow.
- An item with no dependencies stays where it is when you clear its pin.
When a pin and a dependency disagree
Section titled “When a pin and a dependency disagree”A pin is the earliest start an item may have. It is not a fixed date.
- While the dependencies require a date before the pin, the item stays at its pin. A predecessor that changes within that gap moves nothing.
- Once the dependencies require a date after the pin, the item is pushed. The dependency wins over the pin.
- On the Gantt, a pinned bar shows a pin mark at its start. Point at the mark, and the hint names the pin date. When a dependency holds the bar later than its pin, the hint also names the predecessor that holds it.
Dragging a successor in front of its predecessor does not create a lead. The bar lands on the limit of the dependency. The drag preview shows that date before you release.
Adding and removing a dependency
Section titled “Adding and removing a dependency”- A new dependency starts with lag 0. The successor moves to the limit of the dependency or to its pin, whichever is later.
- So an item you placed keeps its place, unless the new dependency requires a later date. An item you never placed has no pin, and it moves to the limit of the dependency.
- Removing a dependency releases the successor to whatever its other dependencies require. With no dependency left, the successor stays where it is.
- Changing the type or lag of a dependency moves the successor to what its dependencies now require, or to its pin when that is later.
Lag is only ever the number you typed. Placing an item never changes the lag of its dependencies.
Close a gap that a pin holds
Section titled “Close a gap that a pin holds”A successor that its pin holds later than its dependencies require keeps that gap until the pin is cleared. Re-apply link in the dependency editor clears the successor’s pin, so the successor moves to the earliest date its dependencies allow.
Re-apply link is offered only when clearing the pin would move the successor. It names the date the successor moves to.
What starts a reschedule
Section titled “What starts a reschedule”- Start or Finish changes, from any screen, for one item or for many at once.
- A pin is cleared.
- A dependency is added or removed, or its type or lag changes.
- Holidays change on the Holidays page and you choose to keep durations. See When the holidays change.
Two changes never reschedule:
- dates written by the public API, an import or a webhook. A public API update that changes Start still sets the pin, as your own edit does. So does a re-import that moves the Start of an existing item. Creating an item through the public API, an import or a webhook sets none;
- moving an item to a different parent.
When the holidays change
Section titled “When the holidays change”A holiday is not a working day, so adding, moving or deleting one changes how many working days an item’s dates span. An item is out of step when that number no longer matches its Duration (d). A milestone is never out of step.
When a holiday change on the Holidays page puts items out of step, Teamhood shows what saving it does before it saves. You choose one of two ways:
- Keep durations, move finishes. This is the default, and it is what Microsoft Project does. Each item keeps its Duration (d). Its Finish moves, and a Start that falls on a new holiday moves to the next working day. The items that wait on it move as dependencies require, including items whose lag now crosses a holiday. It is unavailable when it would have to move an item you may not edit, because the items after that one could not move around it.
- Keep dates, change durations. No date moves. Each item’s Duration (d) becomes the working days its dates now span.
Either way, a completed item keeps its dates, and the change and its items are one action, so one undo takes back both.
A holiday changed through the public API, MCP or an imported file moves no item. To someone who can edit holidays, the Holidays page then says how many items are out of step, and Review offers the same choice. The preview of a change counts only the items that change itself puts out of step. Items already out of step before it keep their dates and Duration for Review, unless an item they wait on moves.
How parents are scheduled
Section titled “How parents are scheduled”A parent is scheduled on its whole span, its own dates and the dates of every item below it.
- Changing a Start the parent already had pins the parent. Every dated item under it moves by the same number of working days, and the pin of each moved item moves with it.
- A pin on a parent is the earliest start of every item below it. A parent pinned later than one of its own children pushes that child onto the pin.
- An item inside a parent that has a dependency starts at the parent’s limit, unless its own pin or its own dependencies hold it later. Microsoft Project schedules the tasks inside a summary task the same way.
- A Finish to Finish or Start to Finish dependency on a parent pushes every dated item under it as one block. That dependency never pulls them earlier.
What is never moved automatically
Section titled “What is never moved automatically”- A predecessor, for its own links. Scheduling moves successors only. A predecessor still moves when you change the Start of a parent above it.
- An item with no dependency, of its own or on a parent above it, except up to its pin.
- An item with no dates anywhere below it. It neither limits nor moves, except in the case described under When empty dates are filled in. A parent with no dates of its own is scheduled on its children’s span.
When empty dates are filled in
Section titled “When empty dates are filled in”Scheduling fills in dates for one kind of item: a successor with a Duration (d) and no dates anywhere below it. When a change reaches such a successor and one of its predecessors has dates, scheduling places it at the latest date its dependencies require, or at its pin when that is later.
Its finish follows from the Duration (d), and its own successors are scheduled like any other. Filling in dates sets no pin.
Milestones
Section titled “Milestones”A milestone is an item with a Duration (d) of 0. It has one date, and scheduling treats it as the end of that day, as Microsoft Project does.
- A Finish to Start dependency into a milestone places it on the predecessor’s finish date, not on the next working day.
- A Finish to Start dependency out of a milestone starts the successor on the next working day.
- Start to Start, Finish to Finish and Start to Finish dependencies read the milestone’s date like any other date.
- Moving a milestone moves its start and finish together. A milestone on a weekend moves to the Monday after.
- A parent’s span includes its milestones, at their dates.
For example, Build finishes on Friday 6 March. A milestone Ready linked to Build by Finish to Start sits on Friday 6 March. A task Ship linked to Ready by Finish to Start starts on Monday 9 March.
Microsoft Project puts a milestone that no finish date drives at the start of its day. Teamhood keeps one date per day, so such a milestone shows one working day less float than in Microsoft Project.
Marking and unmarking a milestone
Section titled “Marking and unmarking a milestone”Marking an item as a milestone sets its Duration (d) to 0. Unmarking clears the Duration (d). The steps are in Gantt view.
A milestone has one date, so an unmarked item usually becomes a task of 1 working day. When that date is not a working day, Duration (d) stays empty.
Both are an edit of Duration (d), so each can move the item and the items that wait on it:
- Marking. A Finish to Start dependency into the item now limits it to the predecessor’s finish date, not the next working day. The item can move earlier, and the items after it move with it.
- Unmarking. The same dependency limits the item to the next working day after the predecessor’s finish. The item can move later, and the items after it move with it.
One Undo takes back the change and everything it moved.
Giving a milestone a child
Section titled “Giving a milestone a child”An item with children cannot be a milestone, because a parent is scheduled on its children’s span. Mark as milestone is not offered on a parent. Giving a milestone a child makes it a task.
- The parent picker shows Becomes a task when it gets a child under a milestone. The row stays selectable.
- When your role may not change that milestone’s Duration (d), the picker shows the row as unavailable, with the reason.
- Dragging an item under a milestone shows no hint. Undo turns the task back into a milestone.
Where a milestone shows
Section titled “Where a milestone shows”| Where | What you see |
|---|---|
| Item details, beside the type | The Milestone chip |
| Item details, fields | One Date row in place of Start and Finish |
| List, and the Gantt’s list | A diamond before the title |
| Board card and mind map node | A diamond before the title, and the date |
| Gantt chart | A diamond |
- Only an item whose type has the Start, Finish and Duration (d) fields shows as a milestone.
- When your role may not see Duration (d) on an item’s type, that item shows none of these.
- Duration (d) shows 0 everywhere, as a number you can edit.
- The Date row appears when both Start and Finish are shown. Editing it edits Start, and Finish follows.
- A card shows the date even when the card shows no date fields. The date replaces the card’s own Start, Finish and Duration (d) entries. A milestone with no Start, or whose Start your role may not see, shows the diamond and no date.
Find milestones
Section titled “Find milestones”The Is milestone filter set to Yes keeps the milestones, and No keeps every other item. A view offers it only when it has a type with the schedule fields whose Duration (d) your role may see. To add it, see Gantt view.
When your role may see Duration (d) on no type with the schedule fields, a saved Is milestone filter is not applied for you. Pointing at its chip says why.
A new item created in a view filtered to Is milestone Yes starts as a milestone, so it stays on screen.
Undo a reschedule
Section titled “Undo a reschedule”One Undo reverts the whole change: the dates you changed, and every item that scheduling moved earlier or later.
After you add, change or remove a dependency, a message such as 4 dependent items moved offers Undo when the change moved other items’ finish dates. When it moved a milestone, pushed an item past its parent’s Finish or put someone over capacity, the message is a warning with one line for each kind of impact, which counts the items or people when there are several. Adding or removing a link in item details, or in a table’s Predecessors or Successors cell, works differently. When the link would cause one of those warnings, it waits for you to Save or Cancel it, and shows no message once saved. Undo in the message works while the change is still your latest one.
Dates kept when strict scheduling arrived
Section titled “Dates kept when strict scheduling arrived”Before this way of scheduling, an item could sit later than its dependencies required. When it arrived, every such item was pinned at its current Start, so no date moved.
One case can still move later. When a parent pinned this way started after one of its own children, the next change that reaches that child pushes the child onto the parent’s pin.
What is refused
Section titled “What is refused”A new dependency is refused when it would:
- link an item to itself;
- link an item to anything above or below it in the hierarchy;
- repeat a dependency the two items already have;
- close a loop.
The refusal appears while you pick or drag, and again when the change is saved. On save, a loop is named in full, for example “Would create a loop: Build → Test → Deploy → Build”.
What red means
Section titled “What red means”A broken dependency is one whose successor sits earlier than the dependency allows. The dependency editor states how many working days too early. The two views draw a broken dependency differently:
- On the Gantt, a broken dependency is a dashed red arrow.
- On the mind map, a broken dependency is a red arrow. A dashed arrow there means a dependency of any type other than Finish to Start, so a broken dependency of such a type is red and dashed.
Scheduling never leaves the successors it moves too early. A broken dependency comes from a change that left the dependency behind. Examples are an import, a public API or webhook write, or a move to a new parent.
While the critical path is on, a solid red arrow on the Gantt is not broken. It is a dependency that drives the critical path. A broken dependency stays dashed.
Red on a bar is a different signal. It marks the part of a child’s bar that runs past its parent’s finish. While a baseline is selected, a red bar marks a finish that slipped against the baseline. While the critical path is on, a red line along the bottom edge of a bar marks a critical item, and a red bracket marks a critical parent.
Blocked on cards and in lists
Section titled “Blocked on cards and in lists”A board card and a list row show an amber blocked mark while an item they depend on is not completed. Hover it to see how many items it is waiting on. Once every item it depends on is completed, the mark goes, because nothing is held up.
An item you cannot see does not count: one that is archived or deleted, or one of a type your role cannot read. Nobody can finish it from here, so it holds nothing up, and its type in the item panel is not amber.
In the item panel, such an item reads Unknown item.
The Dependencies column of the list says the same in words: Blocked, Blocks 2 while it is open and two open items depend on it, or 3 linked once its links are settled.
In the item panel, Dependencies lists the links under Waiting on and Blocking. Each starts with its type, such as FS for Finish to Start. Under Waiting on, the type is amber while that item is still open, because it is what holds this one up. Click a linked item’s status circle to change its status, as you can for a sub-item.
The mind map draws the same dependencies
Section titled “The mind map draws the same dependencies”Every arrow on the mind map is the same dependency the Gantt draws, stored once. A dependency drawn on the mind map is Finish to Start with no lag, and it reschedules like any other.
Float and the critical path
Section titled “Float and the critical path”A plan is a top-level item and every item below it. Top-level means the item has no parent at all. A view that shows only part of a plan, such as the contents of one item, still measures float against the whole plan. The plan finishes on the latest finish inside it.
Total float is how many working days an item can finish later before a plan finishes later. That plan is the item’s own plan, or a plan that waits on it through a dependency. An item with no float left is critical, and the critical items together are the critical path.
- Float is counted in working days, so weekends and the organization’s holidays do not count.
- Float is measured on the Start and Finish fields, at the dates scheduling gives every item, pins included. Those are the dates the items have now, unless a date was written outside Teamhood’s scheduling, for example by the public API or an import.
- A Gantt that maps other date fields still takes float and the critical path from Start and Finish. Its bars can then disagree with its critical marks.
- A parent is critical when its own dates, or any item below it, are critical.
- A completed item is never critical: finished work cannot delay the plan any more. Its float is still shown, and it still holds back the items that wait on it. A parent whose only critical items are completed is not critical either.
- A dependency between two top-level items carries float across them, so a late item in one plan can make another plan finish later.
- Float cannot be worked out for an item without both a start and a finish date, unless an item below it has both. Nor can it for an item in a loop of dependencies, an item with such a loop below it, or an item that waits on one. The Total float cell of such an item shows a dash.
- Float is worked out in your browser whenever a Start or Finish date, a pin, a dependency, completion or an item’s parent changes. Nothing is stored, and turning the critical path on or off changes nothing for anyone else.
How the Gantt draws the critical path
Section titled “How the Gantt draws the critical path”Until float has been worked out for every item in the view, which can take a moment after the critical path is turned on or the view changes, nothing fades and no bar or arrow turns red. The key at the bottom appears straight away.
- Bars, brackets, dotted rails, baseline ghosts and arrows that are not critical are drawn faded. On a grouped view, a group’s bracket is never critical, so it fades too.
- The buttons at the left and right edges of the timeline, which scroll to a bar out of view, do not fade.
- A faded bar still moves, resizes and opens as usual. Point at a faded bar and it returns to its normal strength. Faded brackets, dotted rails and baseline ghosts stay faded.
- A critical item gets a red line along the bottom edge of its bar. A critical parent’s bracket turns red.
- A dependency between two critical items, with no gap between them, is drawn as a solid red arrow. It drives the critical path.
- A broken dependency stays a dashed red arrow. A broken dependency that drives the critical path stays at full strength. Every other dashed arrow fades.
- The key Critical path — open items with no float sits at the bottom of the timeline, centred. The key replaces the bracket that spans the whole view. That bracket comes back when the critical path is turned off.
What the Total float column shows
Section titled “What the Total float column shows”- A negative number means the plan already finishes later. Its hint starts with Over by.
- A dash means float cannot be worked out. The cell also shows a dash briefly while the column first loads.
- Sorted ascending, the least float comes first. Sorted descending, the most float comes first. Rows with a dash sort last in both directions.
- Export to Excel and Export to CSV write the plain number, and an empty cell where the screen shows a dash.
Worked example
Section titled “Worked example”Three items, each joined by Finish to Start. The dates are in March 2026. Build and Test have no pin, for example because scheduling filled in their dates from their Duration (d).
| Item | Dates | Waits for |
|---|---|---|
| Design | Monday 2 to Friday 6 March | nothing |
| Build | Monday 9 to Friday 13 March | Design, lag 0 |
| Test | Wednesday 18 to Thursday 19 March | Build, lag +2 |
Build starts on Monday 9 March, the next working day after Design finishes, because the weekend is skipped. Test starts 2 working days after Monday 16 March, the next working day after Build finishes.
- Drag the finish edge of Design 2 working days earlier, to Wednesday 4 March. A finish drag sets no pin, and the Duration (d) of Design becomes 3.
- Build moves 2 working days earlier, to Thursday 5 to Wednesday 11 March.
- Test moves 2 working days earlier, to Monday 16 to Tuesday 17 March.
- Drag the whole Build bar later, to Monday 9 to Friday 13 March. The pin of Build becomes Monday 9 March.
- Build now starts 2 working days after its limit, Thursday 5 March.
- Test is pushed to Wednesday 18 to Thursday 19 March.
- Drag the finish edge of Design to Thursday 5 March. The limit of Build becomes Friday 6 March. That is still before the pin, so Build and Test stay.
- Drag the finish edge of Design to Tuesday 10 March. The limit of Build becomes Wednesday 11 March, after the pin.
- Build is pushed to Wednesday 11 to Tuesday 17 March. Its pin mark names Design.
- Test is pushed to Friday 20 to Monday 23 March.
- Drag the finish edge of Design back to Thursday 5 March.
- Build moves back to its pin, Monday 9 to Friday 13 March, and no earlier.
- Test moves back to Wednesday 18 to Thursday 19 March.
- Drag the whole Build bar 3 working days earlier, to start on Wednesday 4 March, before Design finishes.
- The drag preview shows Build on Friday 6 March, the next working day after Design finishes. Build lands there, on Friday 6 to Thursday 12 March. Its pin mark names Design.
- Test moves to Tuesday 17 to Wednesday 18 March.
No lag changes in any step.
Behaviours that surprise people
Section titled “Behaviours that surprise people”- Every Start you set is a pin. The item then stops following a predecessor that shrinks or moves earlier, until you clear the pin or use Re-apply link.
- Removing a dependency can move the successor earlier, to what its other dependencies require.
- Your role may hide some items, or some of their dates, from you. Scheduling never moves an item earlier because of a change you make when it waits on an item you cannot see, sits inside one, or has its own Start or Finish hidden from you. It can still move later, and moving a parent still moves everything below it. Teamhood cannot tell when an item you can see has items below it that you cannot, so those hidden items are not counted in its dates.
- A completed item with dates moves like any other.