That raises an interesting point, Skye. Is Template Name worth preserving in a project form's calculated field, e.g. "Template Version"? I'm leaning towards yes, especially if your templates regularly evolve. Our instance is fairly young, so our templates are still very fluid.
Something like below, combined with a template taxonomy (e.g. "Ad Hoc Email Launch v5.4") would effectively stamp a project with the template used to open it, along with a version number. You could then filter using contains to display projects made with any version of the template, or equals to display those opened with a specific version. IF(ISBLANK(Template Version),Template.Name,Template Version)
Taking it a step further, with each template revision, you can open a project from the template into a "template archive" program in order to preserve each version of the template. This would allow you to roll back template changes; restore deleted templates; or use for reference. I think I've talked myself into doing this. Any suggestions or other template best practices out there to share?
William English Disney Destinations
If you like my content, please take a moment to view and vote on my Idea Requests: https://tinyurl.com/4rbpr7hf