Adobe Workfront PM Professional key terms

A central project that receives incoming work requests so they can be triaged, approved, and converted into real work. It hosts queue topics, routing rules, and request forms.

A subtopic inside a request queue that groups similar requests and decides which custom form and default settings apply when a requester submits through it.

An automated rule that sends incoming requests to a specific queue, topic, team, or person when the request matches criteria such as values in its custom form.

A set of custom fields attached to a queue topic that captures the details needed to evaluate a request before it is approved or turned into a project.

A project-level summary of costs, benefits, risks, and strategic alignment, combined with a scorecard, used to justify and prioritize investment before or during initiation.

A weighted questionnaire used inside the business case to produce a comparable alignment score across projects, helping leaders rank requests and prioritize objectively.

The action that turns an approved request into a project, carrying over its form data, documents, and details so planning starts without re-entering information.

A reusable blueprint holding tasks, assignments, durations, custom forms, and settings that standardizes how similar projects are created and saves setup time.

A task or marker that flags a significant checkpoint or deliverable in a project, usually with zero duration, used to track key dates in reports.

A task whose dates constrain another task through a dependency, so when its schedule shifts the linked successor task moves automatically.

The four ways tasks link: finish-to-start, start-to-start, finish-to-finish, and start-to-finish, each defining which dates of two tasks are tied together.

Extra wait time inserted into a dependency that pushes the successor later than the relationship alone would, such as two days after a task finishes; negative lag is lead time.

The longest chain of dependent tasks in a project; its total duration sets the earliest possible completion date, and any delay on it delays the project.

The working time between a task's planned start and planned completion, shown in days or hours. Together with planned hours it drives how the scheduler places work.

The estimated effort in hours a task or assignment should take. It feeds resource planning and is compared with actual hours to measure effort variance.

A task setting deciding whether duration, planned hours, or assignments stay fixed when another of these changes, which affects recalculation and resource load.

A project setting that anchors scheduling on the start date, pushing tasks forward, or on the completion date, pulling tasks backward to meet the deadline.

A date rule such as As Soon As Possible or Must Finish On that tells the scheduler how to place a task relative to its dependencies and project dates.

A measure of how much of a task or project is done, updated manually or calculated from hours, which feeds status, condition, and reporting.

Time logged by people working on a task or project. Comparing it with planned hours shows effort variance and supports billing and performance reporting.

A health indicator shown alongside status, such as on target, at risk, or in trouble, that communicates how work is progressing without changing its workflow step.

A status value configured for an object type to mirror an organization's own workflow, used in approvals, reporting, and board columns instead of default statuses.

A work item attached to a project or task that captures problems, risks, or follow-ups, handled through its own queue and assignments without disturbing the main plan.

A planning tool that compares role-based or user-based planned hours across projects with available hours over time, revealing over-allocation and open capacity.

A tool that displays assigned and planned work per person or role across a date range, letting managers rebalance by reassigning, adjusting hours, or changing dates.

A defined position or skill such as Designer or Developer, linked to users and used to match work against availability and cost rates during resource planning.

The share of a person's working time committed to a project, task, or role, usually shown as a percentage or FTE, used to compute capacity and spot overallocation.

A report editing mode where columns, filters, groupings, and views are written as code rather than built visually, unlocking advanced fields and calculations.

A placeholder in a filter or assignment that resolves at run time, such as $$USER.ID for the viewing user, so one report or rule serves many people.

A page collecting several reports and calendars into a single view, usually shared through layout templates so stakeholders see key metrics without opening each report.

A custom field whose value comes from a formula using other fields, dates, or functions, providing derived metrics for reports and forms without manual entry.

A card-based view where statuses become columns and cards move between them, giving teams a visual flow of work instead of a task list.

A fixed-length timebox in which an agile team completes selected stories; iterations are planned from the backlog and tracked with points, hours, and completion.

A prioritized list of stories or requests not yet scheduled into an iteration, from which teams pull work as capacity allows.

A review cycle on a file version where reviewers add markup comments and record a decision, with stages and deadlines tracked so feedback is documented and auditable.

A configuration controlling what users see, including main menu, tabs, fields, and defaults, assigned to users, groups, or job roles to simplify daily navigation.

A permission set defining what a user can view, edit, or delete for object types; combined with sharing rights it determines a person's final abilities.

An organizational unit that can own users, templates, forms, and statuses, allowing administrators to delegate management and separate configuration by department.