Skip to main content
Level 1
Nov 4, 2026 5:53 PM UTC
Question

Managing capacity for a request-heavy team without Fusion

We’re implementing a team in Workfront that receives a high volume of requests, but they also need to be able to manage team capacity.

We’re trying to figure out how others have approached this without Fusion.

At the request level, we can assign multiple people and add planned hours, but it seems limiting when a request requires multiple resources with different levels of effort. We don’t get the same level of planning that we would with individual project tasks.

For teams with a similar setup, do you keep the work at the request level, or do you convert accepted requests into projects/tasks so you can better manage assignments, planned hours, and capacity?

We’d ideally like to keep intake simple while still giving the team enough structure to accurately manage workload and capacity.

Fusion is not available for this implementation, so I’m especially interested in native Workfront approaches.

1 reply

HeatherRo13
Adobe Champion
Adobe Champion
Nov 4, 2026 11:06 PM UTC

Hi!
So in order to get any capacity planning per resource, requests will need to be converted to a task or a project. It doesn’t have to be complicated and you can use a hybrid method workflow like this:
 

  1. Intake: One request queue (organized with topic groups + queue topic) with team-based routing rules and simple request forms.
  2. Triage: A designated person reviews incoming requests on a dashboard and decides path based on the complexity and level of effort you define:
    • Small / single-owner / to-do-style:  Keep as the request assign, track status. No conversion needed.
    • Needs multiple resources with different effort, scheduling, or a timeline: Convert the issue to a task on a standing catchall project, or convert to a project (from a template) if it's a larger multi-step deliverable.
  3. Allocate: Once there is a task, you can use advanced assignments to parse out the hours for multiple users on a task, or break out the tasks if a larger effort.

Tips: Set clear conversion guidelines (e.g., anything needing >1 role, or >X planned hours, or a scheduled due date) so triage is consistent and you're not converting trivial items. Keep project templates simple since over-granular templates make capacity views harder to manage.

Translate