Creator Economy

How to Prioritise Content Production When Every Client Says It’s Urgent

Learn how to prioritize content production using deadline impact, readiness, capacity, effort, dependencies, and explicit scheduling trade-offs.

Published:

Read Time:

5 min

Warm cinematic side-profile portrait of a young man with glowing circular backlight.

Written by:

Fawwaz

Trend Research and Copywriter

AN URGENT REQUEST NEEDS A CAPACITY DECISION

Content production planning becomes more difficult when several clients need work at once. Compare the consequences of delay, production readiness, dependencies, and capacity at the required stage. Then ask if this project moves ahead, which commitment changes?

AN URGENT REQUEST NEEDS A CAPACITY DECISION

Content production planning becomes more difficult when several clients need work at once. Compare the consequences of delay, production readiness, dependencies, and capacity at the required stage. Then ask if this project moves ahead, which commitment changes?

AN URGENT REQUEST NEEDS A CAPACITY DECISION

Content production planning becomes more difficult when several clients need work at once. Compare the consequences of delay, production readiness, dependencies, and capacity at the required stage. Then ask if this project moves ahead, which commitment changes?

Overview

  • Compare urgent requests using deadline consequences, business impact, and production readiness.

  • Check capacity at the stage where the work needs to happen.

  • Identify which commitments change when a new request moves ahead.

  • Turn agreed priorities into clear assignments, handoffs, and delivery plans.

This guide explains how to make that decision, communicate the trade-off, and keep the resulting production work coordinated.

Translate “Urgent” Into a Consequence

Ask what happens if the requested date moves.

Deadline context

What to establish

Fixed external commitment

Whether a launch, event, booked placement, or other commitment depends on delivery

Preferred delivery date

Whether the date supports a specific business need or can be negotiated

Last-minute request

Why the work arrived late and what accommodating it would displace

These categories can overlap. A late request may still support a fixed launch, so evaluate the consequence rather than dismissing it because it arrived late.

Record the practical impact: missed media setup, unavailable talent, a postponed review, reduced deliverables, or limited disruption. Use that information to compare requests.

Check Whether the Work Is Ready

Check whether the next task has the inputs and approvals it needs. A high-priority launch video may be blocked for editing while another task within that project can proceed.

Keep the project’s business priority visible, but allocate production time according to what can move forward. Assign an owner and next update time to each blocker.

Readiness Changes Priority in Practice

Readiness does not erase importance, but determines what the team can actually move forward. A useful readiness check is:

Production Stage

Ready When

Scripting

Brief, objective, claims, and deliverables are sufficiently defined

Shooting

Script or shot requirements, product, talent, and required assets are available

Editing

Footage, script, graphics, audio, and required product information are accessible

Review

The intended review version is available and reviewers know what they are checking

Delivery

Approval is recorded and destination requirements are confirmed

Keep blocked work visible, but separate it from the ready-to-start queue. Reassess the schedule when the missing input or approval arrives.

Prioritise the Bottleneck, Not Just the Project

Effective workload management requires checking demand and available capacity at each production stage. A team may have available scriptwriters but limited filming resources, overloaded editors, or delayed reviews. When multiple projects depend on the same constrained resource, that bottleneck determines how quickly work can progress. By comparing workload demands with available capacity at each stage, teams can identify production constraints, allocate resources more effectively, and avoid adding capacity where it will not resolve the actual bottleneck.

Map Capacity by Production Stage

Consider a hypothetical agency this week.

Stage

Available Capacity

Committed Work

Remaining Capacity

Scripting

24 hrs

14 hrs

10 hrs

Shooting

18 hrs

14 hrs

4 hrs

Editing

40 hrs

38 hrs

2 hrs

Review

12 hrs

7 hrs

5 hrs

Delivery/Admin

10 hrs

6 hrs

4 hrs

Overall team availability does not guarantee capacity at every production stage. Even when scripting and review teams have spare time, an urgent project requiring six editing hours can create scheduling conflicts if editors are already near full capacity. Effective production planning requires identifying where additional work will place demands on resources, rather than relying on broad assumptions about team bandwidth.

Use a Practical Project Prioritization Matrix

There is no universally validated scoring formula that determines which content project should go first. The following framework is an illustrative decision aid where you can use it to make priority conversations more consistent by evaluating five factors.

Factor

Question

Deadline consequence

What concretely happens if this date moves?

Business impact

What important campaign, client commitment, launch, or objective does this support?

Readiness

Can the next production stage actually start?

Effort

How much constrained production capacity will this consume?

Dependencies

Does other work depend on this being completed first?

Do not treat each dimension as mathematically equal. The table helps expose trade-offs, but it does not replace judgment.

Add One More Question: What Gets Displaced?

Every urgent project that moves ahead in the production queue should be evaluated against the work it displaces. This displacement test makes scheduling trade-offs visible by identifying which tasks move forward, which are delayed, and how those changes affect downstream deliverables. For example, prioritizing an emergency revision may push another video's editing schedule back and delay its delivery. If the resulting impact is unacceptable, teams must consider alternatives such as reducing scope, adding capacity, adjusting deadlines, splitting deliverables, or removing lower-priority tasks. Treating every request as equally urgent does not resolve production constraints.

Three Projects, One Editor

Consider three hypothetical client projects competing for the same editing capacity.


Project A: Launch Video

Project B: Monthly Social Batch

Project C: Emergency Client Revision

Deadline

Thursday 12 PM

Friday

Tuesday 5 PM (requested)

Consequence of delay

Product launch creative misses scheduled campaign start

Two organic posts move into the following week

Client wants revised creative before a Wednesday campaign review

Business impact

High

Medium

High

Readiness

Fully ready

Fully ready

Blocked until product team confirms a revised claim

Editing effort

8 hours

10 hours

3 hours once ready

Dependency

Media team needs final export before setup

Social calendar can absorb a small shift

Approval required before campaign review

At 9 AM Tuesday, every stakeholder could describe their project as urgent. But the order is not simply C → A → B, because Project C cannot start. 

The Initial Decision

At 9 AM Tuesday:

  • Start A because it is ready and supports a fixed launch.

  • Assign someone to resolve C’s product-claim approval.

  • Keep B in the agreed queue.

When C Becomes Ready

Suppose approval arrives at 1 PM. Before moving C ahead, the production lead checks whether its three editing hours can fit without making A’s launch commitment unachievable.

Assume the editor has seven working hours per day: 9 AM–12 PM and 1 PM–5 PM. One illustrative editing sequence is:

Day

Editing allocation

Tuesday

A: 9 AM–12 PM

C: 1–4 PM

A: 4–5 PM

Wednesday

A: 9 AM–12 PM and 1–2 PM

B: 2–5 PM

Thursday

B: 9 AM–12 PM and 1–5 PM

This accounts for A’s eight hours, C’s three hours, and B’s ten hours.

A’s edit finishes Wednesday afternoon and B’s finishes Thursday. Review, corrections, exports, and handoffs must also have reserved capacity before delivery is promised.

B starts later, but that does not automatically mean its Friday deadline is missed. The decision changes the editing sequence; its effect on final delivery must be checked separately.

Make Trade-Offs Explicit

When capacity is full, teams have four main levers.

Move Another Commitment

The new work enters and existing work moves. Tell the affected stakeholders.

Reduce Scope

Instead of four edits by tomorrow, the team may deliver two priority edits tomorrow and two later. The reduced scope should still make sense for the campaign.

Add Capacity

Increasing production capacity can help teams manage urgent workloads, but additional resources must address the actual bottleneck. Options include assigning another editor, hiring freelance support, expanding review coverage, or extending production hours when appropriate. The key is to allocate support where capacity is constrained, since adding resources to an unaffected production stage will not resolve the scheduling issue.

Change the Deadline

Sometimes this is the most rational decision. A requested date can change when the business consequence is limited and another commitment carries a higher cost of delay. The decision should be explicit rather than discovered after the deadline is missed.

Avoid Invisible Overtime as the Fifth Option

Accommodating urgent requests by consistently increasing individual workloads can temporarily keep production schedules on track while concealing underlying capacity shortages. Asana's resource-allocation guidance emphasizes reviewing team availability and priorities before assigning additional work, particularly across multiple projects where over-allocation can occur. When workload demands exceed available production hours, teams should document the capacity gap and adjust their plans accordingly, rather than relying on overtime to make unrealistic schedules appear achievable.

Assign a Priority Decision Owner

Project management across multiple projects requires clear authority over shared resources. Name a production lead, project manager, or other authorized person to resolve scheduling conflicts. Account managers should confirm capacity with that owner before promising accelerated delivery. For each priority change, record:

The request and reason.

The stage and person affected.

Which commitment changes.

The revised deadline or scope.

Who needs to be informed.

Review blockers and capacity on a cadence suited to the team. A daily check may be useful during busy periods, while broader commitments can be reviewed in weekly planning.

Reopen the schedule when a material condition changes, such as an approval arriving or a fixed deadline moving. Avoid changing it for every new message.

Present Clients With Feasible Choices

Confirm internal capacity before offering an accelerated date. Then explain the options within that client’s project. For example:

“Our agreed delivery is Friday. We have checked capacity and can offer the priority edit on Wednesday if final copy and product assets are approved by Tuesday at noon. The two secondary variations would remain scheduled for Friday.

If all three assets are needed by Wednesday, we would need to confirm additional capacity or a smaller scope before committing.

Please confirm which option supports the campaign.”

State what changes, what remains scheduled, and which conditions must be met.

Do Not Ask Clients to Prioritise an Internal Queue

Clients should communicate their business priorities, explain the consequences of delays, and make decisions about trade-offs within their own project scope. However, determining which client receives limited production resources should remain an internal responsibility. Effective cross-client prioritization requires production teams to gather sufficient information from each client, evaluate competing commitments, and allocate capacity based on business impact, project readiness, and available resources.

A Useful Metric: Emergency Work by Source

Record the source of each emergency request and summarize recurring causes. The counts below are hypothetical:

Source of Urgency

Number This Month

Client requested scope change

5

Internal approval delay

4

Assets arrived late

3

Fixed external event

2

Production estimate was too low

2

This is an operational diagnostic, not a performance benchmark. Over time, the pattern can reveal whether the team genuinely faces unpredictable demand or keeps manufacturing urgency through preventable delays. 

Another Useful Metric: Stage-Level Queue Pressure

Track ready-to-start work at each stage, then compare its estimated effort with the capacity available before the relevant deadlines.

Nine edits do not necessarily represent more workload than two scripts. Counts show queue size; estimated hours, task complexity, and available capacity help explain the pressure.

For example, 18 editing hours waiting against eight available hours tomorrow exposes a capacity gap. Apply the same check to shooting and review rather than relying on a total project count.

Where Mastershorts Fits After Priorities Are Agreed

A priority decision needs to reach the people doing the work. If the production lead changes the order but the editor, reviewer, and account manager follow different instructions, the revised plan remains difficult to execute.

Mastershorts is content production management software designed to help content teams and agencies coordinate production tasks, ownership, handoffs, review stages, and work status.

The team evaluates urgency, capacity, and trade-offs. Mastershorts supports the production coordination needed to put those decisions into practice.

Content Production Prioritisation FAQ

How do you prioritise multiple urgent projects?

Compare the consequence of missing each deadline, business impact, readiness, required effort, dependencies, and available capacity. Start ready work that carries meaningful consequences while actively resolving blockers on higher-impact projects. If a new project moves ahead of existing commitments, identify what will move back or what additional capacity is required.

How do you manage production when your team is at capacity?

When production demand exceeds available capacity, teams should first identify the specific stage creating the bottleneck. From there, they can evaluate practical trade-offs, such as rescheduling existing commitments, reducing project scope, adding relevant resources, or adjusting deadlines. Overtime should not be treated as additional capacity that can be assumed without consequence. If workloads consistently exceed available resources, the issue points to a broader capacity constraint that requires long-term planning rather than repeated short-term scheduling adjustments.

What is the difference between urgency and priority?

Urgency indicates how quickly a project needs attention, while priority determines how limited production resources should be allocated. An urgent project may remain blocked by missing approvals or assets, while a strategically important project may have greater scheduling flexibility. Effective prioritization requires evaluating urgency alongside business impact, project readiness, and available capacity to determine which work should move forward first.

Should the highest-value client always go first?

That is too simplistic. Commercial importance can be one factor, but teams should also consider contractual commitments, fixed external deadlines, readiness, dependencies, effort, and the consequences imposed on other projects. A clear internal policy helps prevent priority decisions from changing according to whoever asks most loudly.

Should teams use a scoring model for project prioritization?

They can use scoring to support consistent discussion. A numerical score should not be treated as objective truth unless the organization has validated that model for its own decisions. For content production, a simpler matrix covering deadline consequence, impact, readiness, effort, and dependencies may be sufficient. Human judgment is still required.

Every Priority Change Has a Cost

Before moving a request ahead, check its consequence, readiness, and demand on constrained capacity. Identify which commitments change, then communicate the revised plan to the people responsible.

The goal is to allocate available production capacity according to business priorities and commitments, rather than assuming every project can receive immediate attention without affecting other deliverables. Mastershorts helps content teams and agencies coordinate content production work across assignments, ownership, production stages, reviews, and handoffs after the team has decided what should move first.

Want to keep priority changes connected to the people, stages, and handoffs that need to execute them?

Want to keep priority changes connected to the people, stages, and handoffs that need to execute them?

This guide explains how to make that decision, communicate the trade-off, and keep the resulting production work coordinated.

Translate “Urgent” Into a Consequence

Ask what happens if the requested date moves.

Deadline context

What to establish

Fixed external commitment

Whether a launch, event, booked placement, or other commitment depends on delivery

Preferred delivery date

Whether the date supports a specific business need or can be negotiated

Last-minute request

Why the work arrived late and what accommodating it would displace

These categories can overlap. A late request may still support a fixed launch, so evaluate the consequence rather than dismissing it because it arrived late.

Record the practical impact: missed media setup, unavailable talent, a postponed review, reduced deliverables, or limited disruption. Use that information to compare requests.

Check Whether the Work Is Ready

Check whether the next task has the inputs and approvals it needs. A high-priority launch video may be blocked for editing while another task within that project can proceed.

Keep the project’s business priority visible, but allocate production time according to what can move forward. Assign an owner and next update time to each blocker.

Readiness Changes Priority in Practice

Readiness does not erase importance, but determines what the team can actually move forward. A useful readiness check is:

Production Stage

Ready When

Scripting

Brief, objective, claims, and deliverables are sufficiently defined

Shooting

Script or shot requirements, product, talent, and required assets are available

Editing

Footage, script, graphics, audio, and required product information are accessible

Review

The intended review version is available and reviewers know what they are checking

Delivery

Approval is recorded and destination requirements are confirmed

Keep blocked work visible, but separate it from the ready-to-start queue. Reassess the schedule when the missing input or approval arrives.

Prioritise the Bottleneck, Not Just the Project

Effective workload management requires checking demand and available capacity at each production stage. A team may have available scriptwriters but limited filming resources, overloaded editors, or delayed reviews. When multiple projects depend on the same constrained resource, that bottleneck determines how quickly work can progress. By comparing workload demands with available capacity at each stage, teams can identify production constraints, allocate resources more effectively, and avoid adding capacity where it will not resolve the actual bottleneck.

Map Capacity by Production Stage

Consider a hypothetical agency this week.

Stage

Available Capacity

Committed Work

Remaining Capacity

Scripting

24 hrs

14 hrs

10 hrs

Shooting

18 hrs

14 hrs

4 hrs

Editing

40 hrs

38 hrs

2 hrs

Review

12 hrs

7 hrs

5 hrs

Delivery/Admin

10 hrs

6 hrs

4 hrs

Overall team availability does not guarantee capacity at every production stage. Even when scripting and review teams have spare time, an urgent project requiring six editing hours can create scheduling conflicts if editors are already near full capacity. Effective production planning requires identifying where additional work will place demands on resources, rather than relying on broad assumptions about team bandwidth.

Use a Practical Project Prioritization Matrix

There is no universally validated scoring formula that determines which content project should go first. The following framework is an illustrative decision aid where you can use it to make priority conversations more consistent by evaluating five factors.

Factor

Question

Deadline consequence

What concretely happens if this date moves?

Business impact

What important campaign, client commitment, launch, or objective does this support?

Readiness

Can the next production stage actually start?

Effort

How much constrained production capacity will this consume?

Dependencies

Does other work depend on this being completed first?

Do not treat each dimension as mathematically equal. The table helps expose trade-offs, but it does not replace judgment.

Add One More Question: What Gets Displaced?

Every urgent project that moves ahead in the production queue should be evaluated against the work it displaces. This displacement test makes scheduling trade-offs visible by identifying which tasks move forward, which are delayed, and how those changes affect downstream deliverables. For example, prioritizing an emergency revision may push another video's editing schedule back and delay its delivery. If the resulting impact is unacceptable, teams must consider alternatives such as reducing scope, adding capacity, adjusting deadlines, splitting deliverables, or removing lower-priority tasks. Treating every request as equally urgent does not resolve production constraints.

Three Projects, One Editor

Consider three hypothetical client projects competing for the same editing capacity.


Project A: Launch Video

Project B: Monthly Social Batch

Project C: Emergency Client Revision

Deadline

Thursday 12 PM

Friday

Tuesday 5 PM (requested)

Consequence of delay

Product launch creative misses scheduled campaign start

Two organic posts move into the following week

Client wants revised creative before a Wednesday campaign review

Business impact

High

Medium

High

Readiness

Fully ready

Fully ready

Blocked until product team confirms a revised claim

Editing effort

8 hours

10 hours

3 hours once ready

Dependency

Media team needs final export before setup

Social calendar can absorb a small shift

Approval required before campaign review

At 9 AM Tuesday, every stakeholder could describe their project as urgent. But the order is not simply C → A → B, because Project C cannot start. 

The Initial Decision

At 9 AM Tuesday:

  • Start A because it is ready and supports a fixed launch.

  • Assign someone to resolve C’s product-claim approval.

  • Keep B in the agreed queue.

When C Becomes Ready

Suppose approval arrives at 1 PM. Before moving C ahead, the production lead checks whether its three editing hours can fit without making A’s launch commitment unachievable.

Assume the editor has seven working hours per day: 9 AM–12 PM and 1 PM–5 PM. One illustrative editing sequence is:

Day

Editing allocation

Tuesday

A: 9 AM–12 PM

C: 1–4 PM

A: 4–5 PM

Wednesday

A: 9 AM–12 PM and 1–2 PM

B: 2–5 PM

Thursday

B: 9 AM–12 PM and 1–5 PM

This accounts for A’s eight hours, C’s three hours, and B’s ten hours.

A’s edit finishes Wednesday afternoon and B’s finishes Thursday. Review, corrections, exports, and handoffs must also have reserved capacity before delivery is promised.

B starts later, but that does not automatically mean its Friday deadline is missed. The decision changes the editing sequence; its effect on final delivery must be checked separately.

Make Trade-Offs Explicit

When capacity is full, teams have four main levers.

Move Another Commitment

The new work enters and existing work moves. Tell the affected stakeholders.

Reduce Scope

Instead of four edits by tomorrow, the team may deliver two priority edits tomorrow and two later. The reduced scope should still make sense for the campaign.

Add Capacity

Increasing production capacity can help teams manage urgent workloads, but additional resources must address the actual bottleneck. Options include assigning another editor, hiring freelance support, expanding review coverage, or extending production hours when appropriate. The key is to allocate support where capacity is constrained, since adding resources to an unaffected production stage will not resolve the scheduling issue.

Change the Deadline

Sometimes this is the most rational decision. A requested date can change when the business consequence is limited and another commitment carries a higher cost of delay. The decision should be explicit rather than discovered after the deadline is missed.

Avoid Invisible Overtime as the Fifth Option

Accommodating urgent requests by consistently increasing individual workloads can temporarily keep production schedules on track while concealing underlying capacity shortages. Asana's resource-allocation guidance emphasizes reviewing team availability and priorities before assigning additional work, particularly across multiple projects where over-allocation can occur. When workload demands exceed available production hours, teams should document the capacity gap and adjust their plans accordingly, rather than relying on overtime to make unrealistic schedules appear achievable.

Assign a Priority Decision Owner

Project management across multiple projects requires clear authority over shared resources. Name a production lead, project manager, or other authorized person to resolve scheduling conflicts. Account managers should confirm capacity with that owner before promising accelerated delivery. For each priority change, record:

The request and reason.

The stage and person affected.

Which commitment changes.

The revised deadline or scope.

Who needs to be informed.

Review blockers and capacity on a cadence suited to the team. A daily check may be useful during busy periods, while broader commitments can be reviewed in weekly planning.

Reopen the schedule when a material condition changes, such as an approval arriving or a fixed deadline moving. Avoid changing it for every new message.

Present Clients With Feasible Choices

Confirm internal capacity before offering an accelerated date. Then explain the options within that client’s project. For example:

“Our agreed delivery is Friday. We have checked capacity and can offer the priority edit on Wednesday if final copy and product assets are approved by Tuesday at noon. The two secondary variations would remain scheduled for Friday.

If all three assets are needed by Wednesday, we would need to confirm additional capacity or a smaller scope before committing.

Please confirm which option supports the campaign.”

State what changes, what remains scheduled, and which conditions must be met.

Do Not Ask Clients to Prioritise an Internal Queue

Clients should communicate their business priorities, explain the consequences of delays, and make decisions about trade-offs within their own project scope. However, determining which client receives limited production resources should remain an internal responsibility. Effective cross-client prioritization requires production teams to gather sufficient information from each client, evaluate competing commitments, and allocate capacity based on business impact, project readiness, and available resources.

A Useful Metric: Emergency Work by Source

Record the source of each emergency request and summarize recurring causes. The counts below are hypothetical:

Source of Urgency

Number This Month

Client requested scope change

5

Internal approval delay

4

Assets arrived late

3

Fixed external event

2

Production estimate was too low

2

This is an operational diagnostic, not a performance benchmark. Over time, the pattern can reveal whether the team genuinely faces unpredictable demand or keeps manufacturing urgency through preventable delays. 

Another Useful Metric: Stage-Level Queue Pressure

Track ready-to-start work at each stage, then compare its estimated effort with the capacity available before the relevant deadlines.

Nine edits do not necessarily represent more workload than two scripts. Counts show queue size; estimated hours, task complexity, and available capacity help explain the pressure.

For example, 18 editing hours waiting against eight available hours tomorrow exposes a capacity gap. Apply the same check to shooting and review rather than relying on a total project count.

Where Mastershorts Fits After Priorities Are Agreed

A priority decision needs to reach the people doing the work. If the production lead changes the order but the editor, reviewer, and account manager follow different instructions, the revised plan remains difficult to execute.

Mastershorts is content production management software designed to help content teams and agencies coordinate production tasks, ownership, handoffs, review stages, and work status.

The team evaluates urgency, capacity, and trade-offs. Mastershorts supports the production coordination needed to put those decisions into practice.

Content Production Prioritisation FAQ

How do you prioritise multiple urgent projects?

Compare the consequence of missing each deadline, business impact, readiness, required effort, dependencies, and available capacity. Start ready work that carries meaningful consequences while actively resolving blockers on higher-impact projects. If a new project moves ahead of existing commitments, identify what will move back or what additional capacity is required.

How do you manage production when your team is at capacity?

When production demand exceeds available capacity, teams should first identify the specific stage creating the bottleneck. From there, they can evaluate practical trade-offs, such as rescheduling existing commitments, reducing project scope, adding relevant resources, or adjusting deadlines. Overtime should not be treated as additional capacity that can be assumed without consequence. If workloads consistently exceed available resources, the issue points to a broader capacity constraint that requires long-term planning rather than repeated short-term scheduling adjustments.

What is the difference between urgency and priority?

Urgency indicates how quickly a project needs attention, while priority determines how limited production resources should be allocated. An urgent project may remain blocked by missing approvals or assets, while a strategically important project may have greater scheduling flexibility. Effective prioritization requires evaluating urgency alongside business impact, project readiness, and available capacity to determine which work should move forward first.

Should the highest-value client always go first?

That is too simplistic. Commercial importance can be one factor, but teams should also consider contractual commitments, fixed external deadlines, readiness, dependencies, effort, and the consequences imposed on other projects. A clear internal policy helps prevent priority decisions from changing according to whoever asks most loudly.

Should teams use a scoring model for project prioritization?

They can use scoring to support consistent discussion. A numerical score should not be treated as objective truth unless the organization has validated that model for its own decisions. For content production, a simpler matrix covering deadline consequence, impact, readiness, effort, and dependencies may be sufficient. Human judgment is still required.

Every Priority Change Has a Cost

Before moving a request ahead, check its consequence, readiness, and demand on constrained capacity. Identify which commitments change, then communicate the revised plan to the people responsible.

The goal is to allocate available production capacity according to business priorities and commitments, rather than assuming every project can receive immediate attention without affecting other deliverables. Mastershorts helps content teams and agencies coordinate content production work across assignments, ownership, production stages, reviews, and handoffs after the team has decided what should move first.

Want to keep priority changes connected to the people, stages, and handoffs that need to execute them?