Quick Summary

Requests are the core of how Thrivepix works. Each request is a specific task or deliverable you need completed. Learn what requests are, how they differ from projects, and how to use them effectively.

What You'll Learn

• What is a request
• Difference between projects and requests
• Request workflow and lifecycle
• Request statuses
• Request priority levels

What is a Request?

A request is a specific task, deliverable, or piece of work you need completed. It's the fundamental unit of work in Thrivepix.

Examples of Requests:

• "Create a homepage for my website"
• "Fix the contact form bug on mobile"
• "Design a logo in Figma"
• "Add a new product page to Shopify store"
• "Update the footer across all pages"
• "Optimize website loading speed"

Each Request Should Be:

• Specific: One clear task or deliverable
• Actionable: Something we can complete
• Measurable: Clear when it's done
• Detailed: Enough information to start work

Project vs Request

Understanding the difference is key to using Thrivepix effectively.

Project = Label/Folder

• Organizational container
• Groups related requests
• Optional to use
• Example: "Client A Website"

Request = Specific Task

• Actual work to be done
• One deliverable
• Required to get work done
• Example: "Create homepage"

Visual Example

Project: Client A Website (the folder)

• Request 1: Create homepage
• Request 2: Build contact form
• Request 3: Add blog section
• Request 4: Fix mobile menu
• Request 5: Update footer

The project groups all Client A work together. Each request is a specific task.

Real-World Analogy

Think of it like email:

• Project = Email folder ("Work", "Personal", "Client A")
• Request = Individual email message

You can organize emails into folders, but the emails are the actual content.

Request Lifecycle

Every request goes through a lifecycle from creation to completion.

1. Creation

• You create and submit a request
• Provide title, description, files
• Assign to project (optional)
• Set priority

2. Queue

• Request enters your queue
• Waits for available slot
• Core: 1 at a time
• Pro: 2 at a time

3. Review

• Project manager reviews request
• May ask clarifying questions
• Assigns to developer/designer
• Estimates completion time

4. In Progress

• Developer/designer works on request
• May provide updates
• May ask questions
• Work is being completed

5. Under Review

• Work is completed
• PM reviews quality
• Tests functionality
• Prepares for delivery

6. Delivered

• Work delivered to you
• You review the work
• Test and verify
• Decide: Approve or Request Revision

7. Revision (if needed)

• You request changes
• Goes back to In Progress
• Changes made
• Delivered again
• Repeat until satisfied

8. Completed

• You approve the work
• Request marked complete
• Files available for download
• Next request in queue starts

Request Statuses

Requests have different statuses throughout their lifecycle.

Pending

• Meaning: In queue, waiting to start
• What's Happening: Other requests being worked on first
• Your Action: None needed, just wait
• Duration: Depends on queue position

In Progress

• Meaning: Actively being worked on
• What's Happening: Developer/designer is working
• Your Action: Answer any questions promptly
• Duration: 24-72 hours average

Under Review

• Meaning: Work completed, PM reviewing
• What's Happening: Quality check before delivery
• Your Action: None, almost ready
• Duration: Few hours

Revision Requested

• Meaning: You requested changes
• What's Happening: Changes being made
• Your Action: Wait for revised version
• Duration: 24-48 hours average

Completed

• Meaning: Approved and finished
• What's Happening: Nothing, it's done
• Your Action: Download files if needed
• Duration: Permanent

On Hold

• Meaning: Paused, waiting for something
• What's Happening: Waiting for your input/files
• Your Action: Provide what's needed
• Duration: Until you respond

Cancelled

• Meaning: Request cancelled
• What's Happening: No longer needed
• Your Action: None
• Duration: Permanent

Request Priority Levels

You can set priority to indicate importance.

High Priority

• Use For: Urgent, time-sensitive work
• Examples: Site is broken, client deadline tomorrow
• Effect: Moved to front of your queue
• Note: Still follows plan limits (1 or 2 at a time)

Normal Priority

• Use For: Standard requests
• Examples: Regular updates, new features
• Effect: Processed in order submitted
• Note: Default priority

Low Priority

• Use For: Nice-to-have, non-urgent
• Examples: Future improvements, ideas
• Effect: Processed after higher priorities
• Note: Good for backlog items

Priority Tips

• Don't mark everything as high priority
• Reserve high for truly urgent matters
• Normal priority works great for most requests
• Use low for ideas and future work
• You can change priority anytime

Request Best Practices

One Request = One Deliverable

✅ Good:

• "Create homepage with hero section, features, and CTA"
• "Fix contact form validation on mobile"
• "Design logo with 3 variations"

❌ Poor:

• "Build entire website" (too broad, break into multiple requests)
• "Fix everything" (not specific)
• "Make it better" (not actionable)

Provide Complete Information

Include in every request:

• Clear title
• Detailed description
• Reference links or examples
• All necessary files
• Specific requirements
• Any constraints or limitations

Break Large Projects Into Requests

Instead of: "Build e-commerce store"

Break into:

1. Request: Setup Shopify store structure
2. Request: Design homepage
3. Request: Create product page template
4. Request: Build collection pages
5. Request: Setup checkout customization
6. Request: Add payment gateway

Request Limits

No Limit on Submissions

• Submit unlimited requests
• They queue up
• We work through them based on your plan

Active Request Limits

• Core Plan: 1 request active at a time
• Pro Plan: 2 requests active at a time

Queue Management

• Reorder queue anytime
• Change priorities
• Cancel requests if needed
• Pause requests temporarily

Common Questions

Q: How many requests can I submit?
A: Unlimited! Submit as many as you need.

Q: Can I submit multiple requests at once?
A: Yes! They'll queue up and be worked on based on your plan.

Q: What if I need to change a request after submitting?
A: Add a comment with the changes or message your PM.

Q: Can I cancel a request?
A: Yes, anytime before it's completed.

Q: What happens if I don't provide enough information?
A: Your PM will ask clarifying questions before work begins.

Q: Can I combine multiple tasks into one request?
A: Yes, if they're closely related. But separate requests often work better.

Q: How do I know when my request is done?
A: You'll receive a notification and can review the work in your dashboard.

Need More Help?

Contact your project manager or email support@thrivepix.com