Quick Summary

Clear, detailed request descriptions lead to faster turnaround and better results. Learn how to write effective requests that give your team everything they need to deliver exactly what you want.

What You'll Learn

• Writing clear and specific titles
• Creating detailed descriptions
• Including examples and references
• Providing access credentials securely
• Complete request checklist
• Good vs bad examples

Why Request Quality Matters

Benefits of Good Requests

• Faster Turnaround: Team starts immediately without clarification delays
• Better Results: Team understands exactly what you want
• Fewer Revisions: Get it right the first time
• Less Back-and-Forth: All information provided upfront
• Higher Satisfaction: Results match your expectations

Cost of Poor Requests

• Delays waiting for clarification
• Multiple revision rounds
• Mismatched expectations
• Frustration for both sides
• Wasted time and effort

Writing Clear Request Titles

Title Best Practices

Be Specific:

• Good: "Add Contact Form to About Page"
• Bad: "Update Website"

Include Key Details:

• Good: "Fix Mobile Menu Bug on iPhone"
• Bad: "Menu Not Working"

Use Action Words:

• Good: "Create Product Landing Page"
• Bad: "Landing Page"

Mention Platform/Page:

• Good: "Redesign Shopify Homepage Hero Section"
• Bad: "Redesign Homepage"

Title Examples by Request Type

New Development:

• "Build Custom WordPress Plugin for Lead Capture"
• "Create Webflow Blog Template with CMS"
• "Develop Shopify Product Configurator"

Updates/Changes:

• "Update Header Navigation Menu Structure"
• "Change Homepage Hero Background Image"
• "Modify Contact Form Fields"

Bug Fixes:

• "Fix Checkout Button Not Working on Mobile"
• "Resolve Image Loading Issue on Product Pages"
• "Debug Contact Form Submission Error"

Design Work:

• "Design 3 Email Newsletter Templates in Figma"
• "Create Brand Style Guide Document"
• "Design Mobile App Landing Page Mockup"

Creating Detailed Descriptions

Description Structure

1. Overview (What):

• What needs to be done
• Which page/section/feature
• Brief context

2. Requirements (How):

• Specific requirements
• Technical details
• Design preferences
• Functionality needed

3. References (Examples):

• Example websites
• Screenshots
• Mockups or wireframes
• Brand guidelines

4. Access (Credentials):

• Login URLs
• Usernames and passwords
• API keys if needed
• FTP/hosting access

5. Success Criteria (Done When):

• What defines completion
• Expected outcome
• Testing requirements

Description Template

Overview:
I need [what] on [where] for [purpose].

Requirements:
- Requirement 1
- Requirement 2
- Requirement 3

Design/Functionality:
- Design detail 1
- Functionality detail 1
- Technical requirement 1

References:
- Example site: [URL]
- Attached: [file names]
- Inspiration: [description]

Access:
- Website: [URL]
- Username: [username]
- Password: [password]
- Admin URL: [URL]

Success Criteria:
This request is complete when [specific outcome].

Including Examples and References

Types of References

Example Websites:

• Sites with similar features
• Design inspiration
• Functionality examples
• Include specific URLs and what to notice

Screenshots:

• Current state (before)
• Desired state (after)
• Specific elements to reference
• Annotate with arrows and notes

Design Files:

• Figma/Adobe XD links
• PSD or AI files
• Wireframes
• Mockups

Brand Assets:

• Logo files
• Brand guidelines
• Color palettes
• Font specifications

Content:

• Text copy
• Images to use
• Videos or media
• Data or spreadsheets

How to Provide References

For Websites:

• Include full URL
• Specify what to look at
• Example: "See the hero section animation on https://example.com - I want something similar"

For Screenshots:

• Use annotation tools to highlight
• Add text notes explaining
• Number multiple screenshots
• Name files descriptively

For Design Files:

• Share Figma/XD links (preferred)
• Upload PSD/AI files
• Include fonts if custom
• Export assets if needed

Providing Access Credentials Securely

What Access to Provide

Website Access:

• Admin/dashboard URL
• Username
• Password
• Two-factor authentication codes (if applicable)

Hosting Access (if needed):

• cPanel/hosting panel URL
• FTP credentials
• Database access (if needed)

Third-Party Services:

• Email service (Mailchimp, etc.)
• Analytics (Google Analytics)
• Payment gateway
• API keys

How to Share Credentials Securely

In Request Description:

• Use the secure credentials field (if available)
• Credentials are encrypted
• Only visible to assigned team

Via Password Manager:

• Share via 1Password, LastPass, etc.
• Create temporary share link
• Set expiration date

Create Temporary Access:

• Create temporary admin user
• Delete after project completion
• Limit permissions if possible

Security Best Practices

• Never email passwords: Use secure request fields
• Use strong passwords: For temporary accounts
• Limit permissions: Only what's needed
• Change after completion: Update passwords when done
• Enable 2FA: If platform supports it

Complete Request Checklist

Before Submitting

✅ Clear Title: Specific and descriptive

✅ Detailed Description: What, how, why explained

✅ Requirements Listed: All requirements specified

✅ References Attached: Examples, screenshots, files

✅ Access Provided: All necessary credentials

✅ Success Criteria: Clear definition of done

✅ Priority Set: If you have multiple requests

✅ Deadline Noted: If time-sensitive

✅ Brand Assets: Logo, colors, fonts if needed

✅ Content Ready: Text, images, media included

Optional But Helpful

✅ Technical Constraints: Browser support, performance needs

✅ User Stories: "As a user, I want to..."

✅ Edge Cases: Special scenarios to consider

✅ Mobile Requirements: Mobile-specific needs

✅ SEO Requirements: Meta tags, keywords, etc.

Good vs Bad Examples

Example 1: Homepage Update

❌ Bad Request:

Title: Update Homepage

Description: Need to update the homepage. Make it look better.

✅ Good Request:

Title: Redesign Homepage Hero Section with New Branding

Description:

Overview:
I need to update our homepage hero section to match our new brand identity. The current hero feels outdated and doesn't reflect our new positioning.

Requirements:
- Replace hero background with attached image (hero-bg.jpg)
- Update headline to: "Transform Your Business with AI-Powered Solutions"
- Update subheadline to: "Join 10,000+ companies using our platform"
- Change CTA button from "Learn More" to "Start Free Trial"
- Update color scheme to new brand colors (see attached brand-guide.pdf)

Design Preferences:
- Modern, clean design
- Large, bold headline (similar to https://stripe.com)
- Prominent CTA button in brand blue (#3B82F6)
- Mobile-responsive (test on iPhone and Android)

References:
- Inspiration: https://stripe.com (love the hero layout)
- Attached: hero-bg.jpg, brand-guide.pdf, logo-new.svg

Access:
- Website: https://mysite.com/wp-admin
- Username: admin@mysite.com
- Password: [provided securely]

Success Criteria:
Complete when hero section matches new branding, all text updated, and displays correctly on desktop and mobile.

Example 2: Bug Fix

❌ Bad Request:

Title: Form Not Working

Description: The contact form isn't working. Please fix.

✅ Good Request:

Title: Fix Contact Form Submission Error on Mobile Devices

Description:

Overview:
Our contact form on the /contact page is not submitting on mobile devices (iPhone and Android). Desktop works fine.

Issue Details:
- When users tap "Submit" on mobile, nothing happens
- No error message displayed
- Form works perfectly on desktop browsers
- Started happening after last update on Jan 10
- Tested on iPhone 12 (Safari) and Samsung Galaxy (Chrome)

Steps to Reproduce:
1. Visit https://mysite.com/contact on mobile
2. Fill out all form fields
3. Tap "Submit" button
4. Nothing happens - form doesn't submit

Expected Behavior:
Form should submit and show success message: "Thank you! We'll be in touch soon."

Screenshots:
- Attached: mobile-form-issue.jpg (shows the form on mobile)
- Attached: console-error.jpg (browser console error)

Access:
- Website: https://mysite.com/wp-admin
- Username: admin@mysite.com
- Password: [provided securely]

Success Criteria:
Form submits successfully on mobile devices and displays success message.

Example 3: New Feature

❌ Bad Request:

Title: Add Search

Description: We need a search feature.

✅ Good Request:

Title: Add Product Search with Filters to Shopify Store

Description:

Overview:
I need to add a product search feature with filtering capabilities to our Shopify store. Customers should be able to search products and filter by category, price, and color.

Requirements:
- Search bar in header (visible on all pages)
- Search results page showing matching products
- Filters: Category, Price Range, Color, Size
- Sort options: Relevance, Price (Low to High), Price (High to Low), Newest
- Display 12 products per page with pagination
- Mobile-responsive design

Functionality:
- Real-time search suggestions as user types
- Search should include product title, description, and tags
- Filters should update results without page reload
- Show result count (e.g., "24 products found")
- "Clear all filters" button

Design Preferences:
- Clean, modern design matching our store theme
- Filters on left sidebar (desktop) or collapsible menu (mobile)
- Product grid layout (3 columns desktop, 2 mobile)
- Reference: https://gymshark.com (similar search/filter layout)

References:
- Inspiration: https://gymshark.com/collections/all
- Attached: search-mockup.png (rough design idea)

Access:
- Shopify Store: https://mystore.myshopify.com/admin
- Email: admin@mystore.com
- Password: [provided securely]

Success Criteria:
Search feature works on all devices, filters update results correctly, and design matches store theme.

Common Request Writing Mistakes

Mistake 1: Too Vague

• ❌ "Make the site better"
• ✅ "Improve homepage load time from 5s to under 2s"

Mistake 2: Missing Context

• ❌ "Change the button color"
• ✅ "Change CTA button color from green to brand blue (#3B82F6) to match new branding"

Mistake 3: No Examples

• ❌ "Add a slider"
• ✅ "Add image slider like https://example.com/slider - see attached screenshot"

Mistake 4: Assuming Knowledge

• ❌ "Update the usual section"
• ✅ "Update the testimonials section on the homepage (below hero)"

Mistake 5: Multiple Requests in One

• ❌ "Update homepage, fix contact form, add blog, redesign footer"
• ✅ Create separate requests for each task

Tips for Different Request Types

Design Requests

• Include brand guidelines or existing designs
• Specify dimensions and formats needed
• Provide color codes (hex values)
• List font preferences
• Show design inspiration examples

Development Requests

• Specify platform/technology
• Include technical requirements
• Mention browser/device support needed
• Provide API documentation if integrating
• Note performance requirements

Bug Fix Requests

• Describe the issue clearly
• Provide steps to reproduce
• Include screenshots or screen recordings
• Note when issue started
• Specify affected browsers/devices

Content Updates

• Provide exact text to use
• Include images with proper names
• Specify where content goes
• Note any formatting requirements
• Provide links if needed

Using AI to Improve Requests

AI Writing Assistants

Use ChatGPT or similar to:

• Expand brief notes into detailed descriptions
• Organize scattered thoughts
• Generate requirement checklists
• Improve clarity and structure

Example Prompt:

"I need to update my website homepage. Help me write a detailed request description including: new hero section with modern design, updated copy, new CTA button, and mobile responsive. Format it with clear sections for overview, requirements, and success criteria."

Common Questions

Q: How long should my request description be?
A: As long as needed to be clear. Usually 200-500 words with all details. Better too much info than too little.

Q: Can I edit my request after submitting?
A: Yes, you can edit requests or add comments with additional information anytime.

Q: What if I don't have all the information yet?
A: Submit what you have and add details via comments. Or wait until you have complete information.

Q: Should I include technical details if I'm not technical?
A: Describe what you want to achieve. Your team will handle technical implementation.

Q: Can I attach multiple files?
A: Yes, attach as many files as needed (up to 25MB each).

Q: What if I'm not sure how to describe what I want?
A: Use examples! Show similar websites or features and say "I want something like this."

Q: How detailed should I be about design?
A: Provide preferences but trust your designer's expertise. Say what you like/dislike and provide examples.

Q: Should I create one request for multiple related changes?
A: If they're closely related (e.g., updating one page), yes. If separate features, create separate requests.

Need More Help?

Contact support@thrivepix.com or message your project manager