Your workflow lives across three tabs: Queue, Delivered, and Completed. Here's how each one works.

Queue

The Queue is your active pipeline. Everything here is either being worked on or waiting in line. Your designer works from top to bottom, so order matters.

You can:

• Drag requests to reorder them
• Pause a request if you're waiting on assets or internal approvals
• Delete a request using the three-dot menu

One quirk to know: when a request returns from Delivered back to Queue (because you sent revisions), it jumps to the top by default. If it's not actually your highest priority, drag it back down.

Delivered

When your designer hands off a first draft or revision, the request moves to Delivered. Think of Delivered as "the ball is in your court."

Two things can happen next:

• You send revisions and the request bounces back to Queue
• You mark it Completed and it moves to the Completed tab

Completed

Completed means done. No revisions pending. No designer action needed. You can still reopen a Completed request by messaging on it, and it'll move back to Queue.

Pausing a request

Pause is useful when you're waiting on client sign-off, a stakeholder review, or missing source files. A paused request doesn't count against your designer's daily capacity and doesn't clog the queue. Resume it when you're ready.

A quick tip on prioritization

Rather than submitting ten requests in one burst and hoping your designer intuits the order, spend 30 seconds re-ordering the queue. Put time-sensitive work up top. Park exploratory stuff at the bottom. This is the single biggest lever you have on turnaround.