Best Practices for Updating and Versioning Project Templates in Workfront | Community
Skip to main content
Level 3
April 13, 2026
Question

Best Practices for Updating and Versioning Project Templates in Workfront

  • April 13, 2026
  • 3 replies
  • 43 views

Hi everyone! I’m currently working on cleaning up and standardizing our project templates and I’d love to hear how others are managing this.

When updates are needed to a template, do you typically:

  • Update the active template directly, or
  • Create a new version (copy), make updates, and deactivate/archive the old one?

I’m leaning toward a versioning approach for better governance, but I’m curious how others are handling:

  • Template version control
  • Naming conventions
  • Preventing users from selecting outdated templates

Would love to hear what’s working well for your teams or any lessons learned. Thanks in advance!

3 replies

Lyndsy-Denk
Community Advisor
Community Advisor
April 20, 2026

For us, it often takes ages and a day for final agreement on a template. Then, as an admin, I have to audit their work to make sure the template complies with our governance and reporting needs. As a result, I have a dedicated program where folks can play. They start a new project (brand new or from an existing template) and curate to their heart’s desire. When they’re ready, they tag me in to do my admin review and I convert it to a new template.

 

We go with a net new template because often our changes are significant enough that it’s hard to capture all the nuances and apply them as an update. However, if someone just needs something little (ex. a new task or change in assignment), they submit a ticket to me and I update the existing template. New templates do mean you have to track somewhere all filters based on specific templates. We don’t often use that function, though. Instead I filter on custom fields. In fact, that’s something you could do: Add a custom field on your templates that categorizes it for filtering purposes.

ninoskuflic
Level 4
April 22, 2026

Out of curiosity, why are you not using a Sandbox environment where users can play with new templates, etc. instead of a dedicated program in production? Sorry, maybe that is the case but I misunderstood. 😀

If this solved your issue, please mark it as solved so others can find the solution faster.
KierstenKollins
Community Advisor
Community Advisor
April 21, 2026

I have done both, but primarily have deactivated the old template and created a new one for version control. Typically, this was due to revamping forms and we wanted to retain the original forms on the templates for past projects.

 

When deactivating old templates, we would put Zold_ or Z_ in front of the template name. In the description area, you can also add a note on when the template was deactivated.

 

Another note, users can favorite templates and one thing we noticed was that when a user does this and the template is deactivated, it does not remove from their favorites. So a good reminder to users is to unfavorite old templates and favorite new templates.

 

ninoskuflic
Level 4
April 22, 2026

I would deffinetly copy a template to a new one and then do my changes, deactivate the old one and use a version control in template description. 😊 I would also recommend to do a cleanup of very old templates here and there unless you need them for auditing purposes or similar.

If this solved your issue, please mark it as solved so others can find the solution faster.