Quick Summary
Approving completed work is the final step in the request process. Learn how to properly review work, what to check before approving, and how to ensure you're completely satisfied.
What You'll Learn
- How to approve requests
- Final review checklist
- When to approve vs request revisions
- Downloading final files
- What happens after approval
The Approval Process
When Work is Delivered
When your request is completed, you'll receive:
- Email notification
- Dashboard notification
- Request status changes to "Delivered" or "Awaiting Review"
- Link to view the work
- Any notes from your PM or team member
Your Next Step
You have two options:
- Approve: If work meets all requirements
- Request Revision: If changes are needed
Important: Take time to review thoroughly before approving!
Final Review Checklist
Before Approving, Check:
✅ Requirements Met
- Does it match your original request?
- Are all requested features included?
- Is the scope complete?
- Nothing missing?
✅ Functionality Works
- Test all buttons and links
- Submit forms to verify they work
- Try all interactive elements
- Check navigation
- Test user flows
✅ Visual Quality
- Design matches your vision
- Colors are correct
- Fonts and typography look good
- Images display properly
- Layout is clean and professional
✅ Responsive Design
- Test on desktop (large screen)
- Test on tablet (medium screen)
- Test on mobile (small screen)
- Everything displays correctly on all sizes
- No layout breaking or overlapping
✅ Browser Compatibility
- Test in Chrome
- Test in Safari
- Test in Firefox
- Test in Edge (if relevant)
- Works consistently across browsers
✅ Content Accuracy
- Text is correct (no typos)
- Links go to right destinations
- Images are correct ones
- Contact information is accurate
- All content is as specified
✅ Performance
- Pages load quickly
- No slow loading elements
- Images optimized
- Smooth user experience
How to Approve a Request
Method 1: Approve Button
- Go to your dashboard
- Open the completed request
- Review the work thoroughly
- Click "Approve" or "Mark as Complete" button
- Optionally add feedback comment
- Confirm approval
Method 2: Via Comment
- Open the request
- Add a comment: "Looks perfect! Approved."
- Your PM will mark it as approved
What Happens After Approval
- Request status changes to "Completed"
- Request moves to your completed list
- Files remain available for download
- Next request in queue starts automatically
- Team member receives positive feedback
Requesting Final Tweaks
Sometimes work is 95% perfect but needs small adjustments.
Minor Tweaks
For very small changes:
- "Looks great! Just one small thing: can you change the button color from blue to green?"
- "Perfect! Can you increase the logo size by 10%?"
- "Almost there! Just fix the typo in the headline."
Process:
- Add comment with the small change
- Team makes quick adjustment
- Delivered again
- You approve
Significant Changes
For multiple or larger changes:
- Click "Request Revision"
- List all changes needed
- Be specific about each one
- Submit revision request
Process:
- Request goes back to "In Progress"
- Team makes all changes
- Delivered again for review
- You review and approve (or request more revisions)
When to Approve vs Request Revision
Approve When:
- ✅ All requirements are met
- ✅ Functionality works perfectly
- ✅ Design matches your vision
- ✅ Responsive on all devices
- ✅ No bugs or issues
- ✅ Quality meets your standards
- ✅ You're satisfied with the result
Request Revision When:
- ❌ Something doesn't match requirements
- ❌ Functionality isn't working
- ❌ Design needs adjustments
- ❌ Mobile view has issues
- ❌ Content errors or typos
- ❌ Quality doesn't meet standards
- ❌ You're not satisfied
Don't Approve If:
- You haven't tested thoroughly
- You haven't checked mobile view
- You know changes are needed
- You're unsure about something
- You haven't reviewed completely
Why? It's easier to request revisions before approving than to reopen after approval.
Downloading Final Files
What Files You'll Receive
Depending on request type:
Website Development:
- HTML, CSS, JavaScript files
- Images and assets
- Theme or plugin files
- Documentation if applicable
Design Work:
- Figma link (view-only or editable)
- Exported PNG/JPG files
- SVG files for logos
- Source files (PSD, AI) if requested
WordPress/Webflow/Shopify:
- Usually implemented directly on your site
- Backup files if requested
- Custom code snippets
- Documentation
How to Download
- Go to completed request
- Find "Files" or "Attachments" section
- Click file name or download icon
- File downloads to your computer
For Multiple Files:
- Select all files
- Click "Download All" or "Download as ZIP"
- Extract ZIP file on your computer
File Storage
- Files stored indefinitely while account active
- Available for download anytime
- Stored for 90 days after cancellation
- Download important files before canceling
After Approval
What Happens Next
- Request marked as completed
- Moves to completed requests list
- Next request in queue starts automatically
- You can still access files
- Request remains in your history
Can You Reopen After Approval?
Within 7 Days:
- Yes, you can request additional changes
- Message your PM: "Need to reopen Request #123"
- Explain what needs changing
- Request reopened and changes made
After 7 Days:
- Better to submit a new request
- Reference the original request
- Explain what needs updating
- Treated as new work
Approval Best Practices
1. Review Promptly
- Review within 24-48 hours of delivery
- Don't let requests sit for weeks
- Faster review = faster next request
- Keeps workflow moving
2. Test Thoroughly
- Don't just glance at it
- Actually test functionality
- Check on real devices
- Try different browsers
- Verify everything works
3. Be Decisive
- Either approve or request revisions
- Don't leave requests in limbo
- Make a clear decision
- Communicate your decision
4. Provide Feedback
- Let team know what you liked
- Acknowledge good work
- Helps team understand your preferences
- Builds better working relationship
5. Download Important Files
- Download files you'll need
- Don't rely solely on platform storage
- Keep backups of critical work
- Especially before canceling subscription
Common Approval Scenarios
Scenario 1: Perfect Work
Situation: Work is exactly what you wanted
Action: Approve immediately with positive feedback
Example: "Perfect! Exactly what I needed. Great work!"
Scenario 2: Minor Tweaks Needed
Situation: 95% perfect, just 1-2 small changes
Action: Comment with specific tweaks
Example: "Looks great! Just change button color to #00AA00 and we're good."
Scenario 3: Multiple Changes Needed
Situation: Several things need adjustment
Action: Request formal revision with detailed list
Example: Click "Request Revision" and list all changes
Scenario 4: Doesn't Match Requirements
Situation: Work doesn't match what you requested
Action: Request revision, reference original requirements
Example: "This doesn't match the original request. Please see the requirements in my initial description."
Scenario 5: Unsure About Something
Situation: You're not sure if something is correct
Action: Ask your PM before approving
Example: "Is this the best way to implement this feature? Want to confirm before approving."
Common Questions
Q: How long do I have to approve?
A: No strict deadline, but we recommend within 48 hours to keep workflow moving.
Q: Can I approve without testing?
A: You can, but we strongly recommend testing first to avoid issues later.
Q: What if I approve by mistake?
A: Contact your PM immediately. Within 24 hours, we can usually reopen for changes.
Q: Do I have to approve if I'm not satisfied?
A: No! Request revisions until you're completely satisfied. Unlimited revisions included.
Q: Can I partially approve?
A: No, it's all or nothing. Request revisions for any parts that need changes.
Q: What if I never approve?
A: Request stays in "Awaiting Review" status. Your next request won't start until you approve or request revision.
Need More Help?
Contact your project manager or email support@thrivepix.com