Skip to main content

Best Practices for Template Descriptions

Adding clear, purposeful descriptions to your Project Templates helps your team quickly identify the right option for each project and avoid confusion. This article outlines best practices for writing effective template descriptions and managing in-progress work.

Add Clear Use Cases​

Each Project Template should include a short description that explains:

  • What the template is for: Define its intended use, such as “For evaluating grant applications” or “Used in all public construction procurements.”
  • When to use it: Specify any conditions or scenarios that apply—for example, “Use when the project involves multi-step vendor evaluation.”
  • Who should use it: If applicable, indicate the target audience or department. Well-written descriptions reduce ambiguity, save time when selecting templates, and ensure projects follow the correct structure from the start.

Indicate Work-in-Progress Templates​

To avoid confusion and prevent unintended use of incomplete templates, mark any template that is still under development clearly.

Consider the following practices:

  • Add “WIP” to the title: For example, Evaluation Flow – WIP.
  • Include a note in the description: Clarify that the template is not ready for use—e.g., “This template is still under construction and should not be used for live projects.”
  • Unpublish WIP templates: Keep them unpublished until fully tested, so they are not available during project creation.

Using “WIP” in both the title and description makes it easier for team members to identify templates in progress and avoid using them prematurely.

See Also​

To complement your knowledge of this process, check the following pages: