We have a new project template with new tasks, and updated protocol for managing assignments. I'd like the process update to be a clean-break, by deleting all existing tasks and dropping in new project templates. The team shows up next Monday morning and their task lists, task names, and descriptions are fully refreshed. I place a big premium on clean breaks accompanying process change. I want to avoid old style tasks lingering for weeks, or even months. Many of our projects are designed to last for 4-6 months. I think my solution will be to mark these tasks Dead, unassign all team members, and create a default Tasks Filter for all team members upon their login so that the Dead tasks are hidden. The benefit of Updates continuing to be tied to Dead tasks is that the information is not lost The drawback of having Updates continue to exist is that they are tied to Dead tasks, which means everyone needs to be trained/policed to no re-open comment threads on Dead tasks. Nick Scarpello Audacity Health, LLC