Quick Summary

Your request queue determines the order in which your requests are worked on. Learn how to manage your queue effectively to get the most important work done first.

What You'll Learn

• How the queue system works
• Core vs Pro queue differences
• Reordering request priorities
• Estimated turnaround times
• Queue management best practices

What is the Request Queue?

The request queue is a list of all your submitted requests waiting to be worked on. Think of it like a to-do list that we work through in order.

Queue Basics:

• Requests are processed in the order you set
• You can reorder priorities anytime
• Core plan: 1 request active at a time
• Pro plan: 2 requests active at a time
• Unlimited requests can be in queue

How the Queue Works

Core Plan Queue (1 at a time)

Example Timeline:

• Day 1: You submit 5 requests (A, B, C, D, E)
• Day 1: Request A starts immediately (Status: Active)
• Day 1: Requests B, C, D, E are queued (Status: Queued)
• Day 3: Request A completed → Request B starts automatically
• Day 5: Request B completed → Request C starts automatically
• Day 7: Request C completed → Request D starts automatically

Visual Representation:

Active:  [Request A] ← Being worked on
Queue:   [Request B] [Request C] [Request D] [Request E]
         ↑ Next      ↑ After B  ↑ After C  ↑ After D

Pro Plan Queue (2 at a time)

Example Timeline:

• Day 1: You submit 5 requests (A, B, C, D, E)
• Day 1: Requests A & B start simultaneously (Status: Active)
• Day 1: Requests C, D, E are queued (Status: Queued)
• Day 3: Request A completed → Request C starts (B still active)
• Day 4: Request B completed → Request D starts (C still active)
• Day 5: Request C completed → Request E starts (D still active)

Visual Representation:

Active:  [Request A] [Request B] ← Both being worked on
Queue:   [Request C] [Request D] [Request E]
         ↑ Next      ↑ After C  ↑ After D

Queue Status Indicators

Each request in your queue has a status:

• ⚪ Queued - Waiting to start, position in queue
• ???? Active - Currently being worked on
• ???? In Review - Completed, waiting for your review
• ???? Completed - Finished and approved by you
• ???? Revision Requested - Changes requested, back in queue
• ⚫ On Hold - Paused, won't start until resumed

Viewing Your Queue

From Dashboard:

• See "Request Queue" widget on homepage
• Shows next 5 requests in queue
• Quick view of queue position

From Requests Page:

• Click "Requests" in left sidebar
• Filter by "Queued" status
• See all queued requests
• Drag-and-drop to reorder

Queue Information Displayed:

• Request title
• Project name
• Queue position (#1, #2, #3, etc.)
• Estimated start date
• Priority level

Reordering Your Queue

You have full control over request order. Change priorities anytime!

Method 1: Drag and Drop

1. Go to Requests page
2. Filter by "Queued" status
3. Click and hold a request
4. Drag it to new position
5. Drop to set new order

Method 2: Priority Buttons

1. Find the request you want to prioritize
2. Click the "Move to Top" button
3. Request jumps to #1 in queue

Method 3: Edit Priority Level

1. Click on a request
2. Click "Edit" or "Change Priority"
3. Set priority: High, Normal, or Low
4. High priority requests move to top automatically

Queue Management Best Practices

1. Prioritize by Urgency

• Put urgent requests at the top
• Less urgent requests can wait
• Consider deadlines and dependencies

2. Group Related Requests

• Keep related requests together
• Complete one feature before starting another
• Easier to review and test

3. Balance Complexity

• Mix simple and complex requests
• Don't queue all complex requests first
• Helps maintain steady progress

4. Review Queue Regularly

• Check queue weekly
• Remove requests you no longer need
• Update priorities as needs change
• Add new requests as they come up

5. Communicate Changes

• If you reorder significantly, add a comment
• Let your PM know why priorities changed
• Helps team understand your needs

Estimated Turnaround Times

Average Turnaround per Request:

• Simple requests: 24 hours or less
• Medium requests: 24-48 hours
• Complex requests: 48-72 hours
• Very complex: 3-5 days

Calculating Total Queue Time:

Core Plan Example:

• 5 requests in queue
• Average 48 hours each
• Total time: 10 days (5 × 2 days)

Pro Plan Example:

• 5 requests in queue
• Average 48 hours each
• Working on 2 at a time
• Total time: 5 days (faster completion)

Queue Position Notifications

You'll receive notifications when:

• Request starts: "Your request is now active"
• Position changes: "Your request moved to #2 in queue"
• Estimated start: "Your request will start in ~2 days"
• Delays: "Request taking longer than expected"

Notification Settings:

• Email notifications (on/off)
• In-app notifications
• Daily queue summary
• Customize in Settings

Pausing Requests

Need to pause a request temporarily?

1. Find the request in your queue
2. Click "Put on Hold"
3. Request status changes to "On Hold"
4. Won't start until you resume it

When to Pause:

• Waiting for client approval
• Need to gather more information
• Priorities changed
• Project on hold

Resuming Paused Requests:

1. Find the paused request
2. Click "Resume"
3. Request returns to queue
4. Set new priority position

Canceling Queued Requests

No longer need a request?

1. Find the request in queue
2. Click "Cancel Request"
3. Confirm cancellation
4. Request is removed from queue

Note: You can only cancel requests that haven't started yet. For active requests, contact your PM.

Queue Optimization Tips

For Core Plan Users:

• Submit requests in batches
• Prioritize most important first
• Keep queue at 3-5 requests for steady flow
• Don't submit too many at once (hard to manage)

For Pro Plan Users:

• Keep 4-6 requests in queue
• Ensures both slots stay filled
• Balance different types of work
• One complex + one simple works well

For Agencies:

• Organize by client
• Use project names to identify client work
• Prioritize by client deadlines
• Communicate client urgency to PM

Common Queue Scenarios

Scenario 1: Urgent Request Comes In

Problem: You have 5 requests queued, but a client needs something urgent.

Solution:

1. Submit the urgent request
2. Immediately move it to #1 in queue
3. Add comment: "URGENT - Client deadline tomorrow"
4. Notify your PM via message

Scenario 2: Request Dependencies

Problem: Request B depends on Request A being completed first.

Solution:

1. Ensure Request A is before Request B in queue
2. Add note in Request B: "Depends on Request A"
3. PM will ensure proper order

Scenario 3: Too Many Requests

Problem: You submitted 20 requests and queue is overwhelming.

Solution:

1. Review all requests
2. Cancel any no longer needed
3. Pause low-priority requests
4. Keep top 5-10 active
5. Add others back later

Common Questions

Q: Can I change queue order while a request is active?
A: Yes, you can reorder queued requests anytime. Active requests continue until completion.

Q: What if I want to skip a request in queue?
A: Move it to the bottom of the queue or put it on hold.

Q: How do I know when my request will start?
A: Check the estimated start date shown in the queue. It updates automatically.

Q: Can I have different queues for different projects?
A: No, all requests share one queue. Use priority levels and reordering to manage.

Q: What happens if I upgrade from Core to Pro mid-queue?
A: The next request in queue starts immediately, so you'll have 2 active requests.

Need More Help?

Contact your project manager or email support@thrivepix.com