Priority (Beta)

The Priority tab shows the order your workforce picks up work across all requests in a project. Use it when one request matters more than the others, or when a request should wait behind what you upload next.

The Priority tab is in Project Management, on each project where priority is enabled. Users with the workspace role Admin, Project Manager, Annotation Manager or Developer can see it.

To change priority, you need the workspace role Admin or Project Manager, and access to every request in the project. If you can access only some of the requests, you see just those, numbered from 1 in each tier, and cannot change the order. See Roles & permissions.

By default, the workforce is always given the task closest to delivery. Priority lets you override that for specific requests by moving them into one of three tiers: Critical, Normal, or Low.

Each time someone in your workforce submits a task, the platform picks their next task from all requests in the project. Two things decide the order: the request's tier, and how close each task is to delivery.

Closest to delivery goes first. Within a tier, a task late in the workflow (for example a correction after Client QA) is picked before a task early in it (a new annotation). This is what shortens turnaround: nothing that is nearly finished waits behind new work.

Tiers override that for whole requests.

Completed requests stay in their tier, with the status Completed. Archived requests are not shown.

Nothing is applied until you save, so you can rearrange freely and discard if you change your mind.

Click Cancel to discard all changes. If you changed anything, you are asked to confirm first. The same happens if you leave the page while editing. Save changes stays disabled until you change the order.

If Critical already holds three requests, you cannot drop a fourth. Move one out first.

Each tier has its own search field. Search by request name or ID. Matches are highlighted in place, so you can drag them while searching.