Will Urgent start a request when Active is full?

No. Priority changes ordering and attention, but it does not create another Active lane or bypass workspace capacity.

Does Urgent guarantee an earlier delivery date?

No. Priority signals relative attention inside the workspace. Scope, available Active capacity, required decisions, and response time still affect delivery.

What should I do when the target date changes?

Update the date and add the launch or dependency context to the brief or request discussion. A date is more useful when the team understands what happens if it moves.

Priority, target dates, and capacity

Choose a priority

Priority helps the team compare work inside the same workspace. Use Urgent for a real time-sensitive risk, High for important work that should move ahead of normal requests, and Low for work that can wait without consequence.

Set a target date

A target date gives the team a planning signal. Add the event behind the date to the brief, especially when a launch, campaign, legal review, or dependency makes the date fixed.

Respect Active capacity

Priority does not bypass the Active limit. Finish or move existing Active work, answer a request in Needs Input, or add capacity from Billing before starting more parallel work.

Priority is relative

Use priority to compare requests in the same workspace. Urgent should be reserved for work with a real consequence and a stated date. Changing a label does not guarantee delivery or move a request into Active automatically.

A target date needs context

Add the launch, event, review, or handoff reason to the brief when the date is fixed. The target date is easier to plan around when the team also knows who must approve, what source material is still missing, and what can be reduced if time becomes tight.