Canonical page: https://tellenze.com/guides/manage-dependencies Manage dependencies # Show what is waiting. Make the next action clear. Connect work that needs another result first. Explain the blocker, agree who will take the next step and keep the handoff evidence where the people involved can read it. [Follow the dependency steps](#link-dependency)[Read relation Help](https://tellenze.com/help/work-items#connect-and-complete-work) Synthetic example · a dependency between two Projects BILL-12 · Billing Project ### Agree the receipt fields. Confirm the fields and save the accepted format where both contributors can read it. blocks → PORT-18 · Customer portal Project ### Build the receipt download. This work needs the agreed format before its receipt content can be finished. Each item keeps its Project and workflow. The relation shows the dependency; Blocked records the waiting item’s current state. Choose the connection that fits ## A dependency, a part or a shared outcome? Start by saying how the items are connected. A relation, parent and milestone answer different questions. A prerequisite is work that supplies a result another item needs. Use that direction when adding a dependency. Relation ### Work needs other work. Use blocks when an item supplies a result another item needs. Relations can connect accessible work across Projects and Teams without moving either item to a new owner. Parent and subtasks ### Work is part of an outcome. Use Parent task for smaller pieces of one larger item. A parent and its subtasks belong to the same Project or Team. A parent link does not express a dependency’s direction. Milestone ### Work supports a shared goal. Where enabled, a milestone connects existing work toward an outcome across Projects and Teams. Each linked item keeps its own owner, workflow and access rules. [Read milestone Help](https://tellenze.com/help/milestones#define-a-shared-outcome) The supported relations ## Choose a label that explains the link. Related work → Add relation offers these four choices. The label describes the connection. It does not replace a decision about scope, stage, review or the next action. Relationship choices · use the meaning that fits the work Relationship | Purpose | How to use it | relates to | Keep useful context connected. | Use it when two items inform each other without saying that one must finish first. | blocks | Name the result another item needs. | Open the prerequisite and link the waiting item. The waiting item shows the reverse label, is blocked by. | duplicates | Identify repeated work. | Connect an item to the work it duplicates. Agree which item to continue; the relation does not merge or complete either item. | contributes to Business Case | Connect delivery to the reason for doing it. | Choose an active, accessible Business Case. The link records a contribution; it does not prove that the expected benefit happened. | Add a dependency in the right direction ## Start with the result needed by the next item. In the example, BILL-12 provides the receipt format needed by PORT-18. Open BILL-12 and add a blocks relation to PORT-18. Read the saved link from both ends to check the direction. You need permission to edit both items. Relation search follows your current access and excludes archived work and work in archived Projects or Teams. [Read Related work controls](https://tellenze.com/help/work-items#connect-and-complete-work) - 01 ### Open the prerequisite. Choose the item whose result is needed first. Open Related work and choose Add relation. - 02 ### Choose Relationship → blocks. Read the direction as “this item blocks the item I will select.” Use relates to if there is no dependency. - 03 ### Find the waiting item. In Related task, search by identifier or title. Type at least two characters for workspace results. Check the title and owner before selecting a match. - 04 ### Choose Add relation and inspect it. The prerequisite shows blocks. The waiting item shows is blocked by. Each item stays in its current Project or Team. Describe the current blocker ## A link explains the connection. A reason explains the wait. A blocks relation records a connection between items. Mark the waiting work Blocked separately when it cannot continue. Edit the Blocked field, select Mark as blocked, add a Blocked reason and choose Apply. Explain what is missing, who will take the next action and what will allow work to continue. Add a useful update in Conversation when that plan changes. Choose a workflow stage that matches the real state. A relation does not automatically change stages, set Blocked or clear it when the prerequisite completes. Synthetic example · a specific reason on the waiting item PORT-18 · Blocked reason ### Waiting for the accepted receipt format. MissingBILL-12 needs to confirm which payment fields belong in the PDF. Next actionThe Billing contributor will review the draft with the portal contributor and save the accepted format. Resume whenThe format is agreed, linked from both items and readable by both contributors. What can moveThe contributors agree whether error-message work can continue independently. Record that scope choice in Definition. Coordinate with current access ## Give people evidence they can actually open. A relation does not grant access to its target, its Project or Team, a document or a provider source. Check the handoff from the contributor’s account before relying on a link. The contributor ### Check the input. Open the linked prerequisite and its agreed output. If you cannot read it, ask the source owner for appropriate access or an allowed summary in a place you can use. The coordinator ### Keep the next action visible. Agree who provides the missing result and who checks it. Record a meaningful update beside the work. Do not copy private source material into a broader Conversation just to make a handoff visible. The creator or administrator ### Resolve the access route. Check the Project’s visibility, direct grants and owning Team membership. For provider material, check that source’s permissions separately. Removing one grant can leave another valid route. [Read access boundaries](https://tellenze.com/trust) When Required Context applies to agent changes, check its current pinned reading and receipt too. Reading a linked dependency does not replace Required Context. Use [Required Context Help](https://tellenze.com/help/required-context) to resolve unavailable or outdated reading. Close the handoff with a check ## Deliver the input. Confirm work can continue. Check the prerequisite’s acceptance criteria and link its result before completing it through its own workflow. Then ask the waiting contributor to confirm that the input is usable. Once the blocker is resolved, clear the waiting item’s Blocked state and choose its appropriate stage. Update the Definition if the agreed scope changed. Keep useful relations; remove a relation when it no longer describes the work. A shared milestone can help the team follow the overall outcome. Moving it through The Loop does not move linked tasks. Completing all linked work does not automatically complete the milestone. [Read milestone completion rules](https://tellenze.com/help/milestones#complete-and-maintain-the-milestone) Handoff completion checks ## Ready for the next action. - The dependency points the right way.The prerequisite blocks the work that needs its result. - The missing result is clear.The blocker names what must change and the agreed next action. - The contributor can use the evidence.Check the saved output and its access with the receiving person. - The waiting item reflects reality.Clear Blocked only after the issue is resolved, then update its stage and relevant scope. A few useful details ## Keep connections and decisions clear. Does adding blocks automatically block the other item? The relation records the dependency. The waiting item’s Blocked state and reason are separate edits. Stages and Blocked do not change automatically when you add this relation or complete the prerequisite. Can I connect work from different Projects or Teams? Relations can connect active work you have permission to edit across accessible owners. Each item keeps its own owner and workflow. Parent and subtask links stay within the same Project or Team. Why can I not find the related item? Use at least two characters and check the identifier or title. Search follows your current access and excludes archived work and work in archived Projects or Teams. Check the item’s availability and access with the relevant owner; a copied URL does not grant access. Does a duplicates relation merge the work? It records the duplicate relationship. Decide which item to continue, save the reason and update each item through its own workflow. Adding the relation does not merge or complete either item. Will everyone see the same linked work in a milestone? Milestone access does not grant access to linked work. Readers can see different lists. Inaccessible private work can contribute to overall milestone progress without exposing its details. Check the evidence you are authorized to read. Keep the work moving together ## A useful connection. A usable handoff. Review dependencies when scope or priorities change. Keep the current facts beside the work so the next person knows what to do. [Keep each Definition clear](https://tellenze.com/guides/define-clear-work) Keep your next step clear ## Find the guide for your next step. [Browse all guides](https://tellenze.com/guides) COME TAKE A LOOK ## A little less busy. A lot more together. Curious? Join the waitlist and see how we welcome your team. Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace. [Join waitlist](https://tellenze.com/waitlist)Start with your email. No payment needed to join.