A marketing team determines that in the future, their projects must be reviewed by the Project Sponsor before the project is closed. What is the best practice to ensure that each project is properly reviewed and approved?

Using a project template is the best practice for standardizing processes for future projects. By adding the required approval process to the marketing team's project template, you ensure that every new project created from that template automatically inherits the correct approval workflow. This method enforces consistency, eliminates the need for manual setup on each project, and significantly reduces the risk of human error, thereby guaranteeing that the Project Sponsor's review occurs before project closure.

A. A global approval process is available system-wide but does not automatically attach to specific projects. It would still require a manual step or a template to be applied consistently.
B. Creating a single-use approval process on each individual project is inefficient, time-consuming, and highly susceptible to being forgotten, making it the opposite of a reliable best practice.

1. Adobe Workfront Documentation, "Create a project template." This document states, "A project template is a predefined set of tasks and settings that you can use over and over to create projects." It emphasizes that templates are the primary tool for standardizing project creation and ensuring consistent processes are applied.

2. Adobe Workfront Documentation, "Attach an approval process to a Workfront object." In the section "Attach an approval process to a template," the documentation explicitly states: "When you attach an approval process to a template, any object created from that template automatically has the approval process attached." This directly supports the chosen answer as the correct implementation method.

3. Adobe Workfront Documentation, "Create an approval process for a work item." This source distinguishes between single-use and reusable approval processes. It clarifies that single-use approvals are for unique, ad-hoc situations, whereas reusable processes, which can be attached to templates, are intended for standardized, repeatable workflows, making option B an incorrect approach for a recurring requirement.