From 2d41e1610195171619f0e39be0f9d4f68f06cba8 Mon Sep 17 00:00:00 2001
From: "Piers Sinclair [SSW]"
 <79821522+pierssinclairssw@users.noreply.github.com>
Date: Mon, 12 Feb 2024 09:13:17 +1100
Subject: [PATCH] Update rules/tofu/rule.md

---
 rules/tofu/rule.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rules/tofu/rule.md b/rules/tofu/rule.md
index 043872574be..52581cbff3a 100644
--- a/rules/tofu/rule.md
+++ b/rules/tofu/rule.md
@@ -36,7 +36,7 @@ There are 2 main aspects to TOFU:
 2. **Communicate Proactively**: Don't wait for someone to ask for an update. Regularly communicate your progress, especially if you encounter any roadblocks or delays.
 3. **Set Clear Deadlines**: Establish realistic deadlines for your tasks and communicate these with your team and stakeholders. If a deadline needs to be adjusted, communicate this change as early as possible.
 4. **Use Tools to Your Advantage**: Understand the best ways for [following up effectively](/follow-up-effectively) and leverage Scrum tools (e.g., Azure DevOps, GitHub, Trello) to track tasks, deadlines, and progress.
-5. **Close the Loop**: Once a task is completed, ensure all relevant parties are informed and that any necessary documentation is updated. Closing the loop is a critical part of the follow-up process, as it signifies that no further action is required. The way to do this for a task you received via email is to [send a Done email](https://ssw.com.au/rules/reply-done-and-delete-the-email/).
+5. **Close the Loop**: Once a task is completed, ensure all relevant parties are informed and that any necessary documentation is updated. Closing the loop is a critical part of the follow-up process, as it signifies that no further action is required. The way to do this for a task you received via email is to [send a Done email](/reply-done-and-delete-the-email/). For tasks (e.g. a PBI) outside an email it is usually to [add a comment](/rules/close-pbis-with-context/).
 
 ### Common Pitfalls to Avoid