Skip to main content

Managing Design Requests

Written by Luis

Juggling multiple design requests gets overwhelming when you can't see where things stand. Dynamic design slots and priority queue management make it easy to track what's being worked on, what's up next, and what's finished, and they make the work itself better.

Our system is built to provide higher quality design, fewer revisions and smoother collaboration!

Before diving in, we recommend watching this short video tutorial about how active design slots work.

How a request moves

Every request follows the same path, and its status tag tells you exactly where it is at any moment.This is the common request journey:

  1. Scoping

  2. Queued

  3. If design slot available

  4. Scheduling

  5. Designing

  6. Ready for Review

  7. Completed d

A request is scoped when you submit it, waits in your queue until a slot opens, gets scheduled and designed, then comes back to you for approval. Feedback sends it to Revising and back around; approval closes it out. Tags like Resizing, Redesigning, Response Needed, Paused, and Archived cover the variations, all of them are defined in Understanding Status Tags.

Dynamic active design slots

Graphic and video requests share one cohesive queue, so your active slots work as a single pool. No separate lists, no separate queues, and total control over how your slots are used.

As soon as an active slot opens, the next request in your queue moves to Scheduling automatically and work begins. Design slots are released the moment a request is completed, paused, or archived and filled again straight from the top of your list, without anyone having to ask.

How your queue works

Scoping and In Queue requests sit together in the In Queue section of your Requests page, in a single list you control. Drag requests into whatever order you want, the order determines what gets worked on next.

Two rules to know

Queued requests move up automatically. When an active slot opens, the topmost Queued request moves to Scheduling on its own.

Scoping requests hold their place. A Scoping request does not move to Scheduling on its own, but if it sits above an Queued request, it reserves the open slot rather than letting the lower request take it.

Example:

Say two of your design slots are free.

Case 1: one request still being scoped, one ready to go

At the top of your queue is request 1 still in Scoping. Below it, request 2 Queued and ready. Request 2 starts right away in one slot. The second slot stays open and waits for request 1, so the moment scoping wraps up, it starts too.

Case 2: one being scoped, two ready to go

Same request 1 is in Scoping at the top, but this time two other requests (2 & 3) are waiting below it. Only request 2 starts. The second slot is still being held for request 1, so request 3 waits its turn.

Case 3: two being scoped, one ready to go

Now a request 1 and request 2 are both in Scoping at the top of your list, with request 3 Queued below them. Neither slot gets used yet, both are held for the two requests at the top, and request 3 waits.

If that's not the order you wanted

In case 3, if request 3 is what you actually need first, drag it to the top of your queue. It starts immediately in one of the open slots, and the requests still being scoped hold the other.

The rule behind all three: anything still in Scoping at the top of your list reserves a slot for itself. Your ready-to-go requests use whatever slots are left.

Ordering behavior

  • New requests are always added to the bottom of the list. Move them up if they are urgent.

  • A request that moves between Scoping and In Queue keeps its place in the list, it will not jump around on you.

  • A request returning to the queue from another status (for example, a reopened or resumed request) is placed at the bottom.

Improved priority management

Everything waiting on you lives in one list, in the Queued section of your Requests page. Drag and drop to reflect shifting priorities, whatever you put at the top is scheduled first, and reordering takes effect immediately.

That means you never have to ask for something to be bumped up. If a request suddenly matters more, move it. If one is stalled on your end, pause it and free the slot for something that can move. For the full set of ordering rules, see managing the design queue.

Tips for managing your queue

  • Order the queue deliberately. The top of your Queued list is what gets worked on next. Drag your highest priority there rather than waiting for it to come up.

  • Pause instead of waiting. If a request is stalled on your end, pause it. The slot frees up immediately and the next request can start.

  • Reply quickly to Response Needed. These requests hold an active slot while they wait on you, so a fast reply keeps your slots productive.

  • Review promptly. Ready for Review also holds a slot. Approving or commenting quickly returns that capacity to your queue.

🛎️ Looking for a hands-off experience? Let us handle the heavy lifting for you! Explore the Perks of Upgrading to Fully Manage, the perfect solution for a fully managed, hands-off design experience.


Need Help?

If you have any questions remember that support is just a click away. Use the chat feature to connect with a Customer Success Representative who can provide real-time assistance.

Did this answer your question?