Best Practices

This guide compiles best practices from successful Moqup users to help you optimize your design review workflow.

Project Organization

Naming Conventions

Use consistent, descriptive names:

Good:
- [Client] - [Project] - [Year]
- Acme Corp - Website Redesign - 2025
- TechStart - Mobile App - Q1 2025

Avoid:
- Project 1
- New Design
- Final v2 FINAL

File Naming

Clear file names save time:

Good:
- homepage-hero-v3.png
- mobile-nav-dark-mode.jpg
- checkout-step-2-with-promo.pdf

Avoid:
- IMG_4532.jpg
- Screen Shot 2025-01-10.png
- design copy.psd

Stage Structure

Keep stages meaningful:

Simple (3-4 stages):
1. Concepts
2. Review
3. Approved

Comprehensive (5-6 stages):
1. Research
2. Initial Concepts
3. Internal Review
4. Client Review
5. Revisions
6. Approved

Feedback Quality

Writing Effective Annotations

• Be specific about location
• Explain the problem AND suggest solution
• Provide examples or references
• Use clear, professional language

• Leave vague comments ("looks wrong")
• Write essays - be concise
• Mix multiple issues in one annotation
• Use jargon clients won't understand

Example Good Feedback

Location: Hero section, main headline
Issue: Font size appears too small on mobile preview
Suggestion: Increase to 32px for better readability
Reference: Similar to the subhead size on our "About" page

Example Poor Feedback

"Doesn't look right"
"Make it pop more"
"Can you try something else?"

Version Control

When to Create New Versions

Create a new version when:

• Implementing client feedback
• Making significant changes
• Presenting new direction
• After internal review

Don't create versions for:

• Minor tweaks
• Test variations
• Incomplete work

Version Notes

Always add context:

Version 3:
- Increased headline font size per client feedback
- Updated CTA button color to brand orange
- Added mobile responsive adjustments
- Removed secondary navigation (see annotation #12)

Comparing Versions

Use comparison view to:

• Show clients what changed
• Verify feedback was addressed
• Document iteration history
• Create before/after presentations

Team Collaboration

Effective Communication

1. Use @mentions: Direct notification to responsible party
2. Stay in context: Discuss in annotations, not email
3. Resolve promptly: Close threads when addressed
4. Be constructive: Focus on solutions

Handoff Best Practices

When passing work to teammates:

• Document current status in project notes
• List pending items
• Tag incoming team member
• Brief them on client preferences

Avoiding Conflicts

• One lead per project
• Clear stage ownership
• Defined approval chain
• Communication norms

Client Management

Setting Expectations

At project start:

• Number of concepts
• Revision rounds included
• Timeline for each phase
• How to provide feedback
• Approval meaning and implications

Professional Presentation

Before client review:

1. Internal QA complete
2. Files properly organized
3. Descriptions added
4. Test client view
5. Prepare talking points

Handling Difficult Feedback

When clients are unclear:

• Ask clarifying questions
• Request examples
• Offer quick call
• Document everything

Workflow Optimization

Keyboard Shortcuts

Press Cmd+/ (Mac) or Ctrl+/ (Windows) to see all shortcuts.

Batch Operations

Save time with bulk actions:

• Select multiple files
• Move stages together
• Download as ZIP
• Archive completed work

Templates

Create templates for:

• Common project types
• Standard stage structures
• Quick reply messages
• Client communication

Notification Management

Optimal Settings

Balance staying informed vs. distraction:

Focused Work Time

Use "Do Not Disturb":

• During deep work
• Outside work hours
• During client calls
• When on vacation

Security Best Practices

Access Control

1. Minimum necessary: Don't over-permission
2. Regular audits: Review who has access
3. Revoke promptly: Remove access when projects end
4. Password protection: For sensitive work

Protecting Work

1. Enable watermarking for clients
2. Restrict downloads if needed
3. Set link expiration
4. Monitor activity logs

Performance Tips

For Large Projects

• Archive completed stages
• Keep active file count reasonable
• Use optimized image formats
• Regular cleanup

For Teams

• Stagger file uploads
• Use batch operations
• Cache when possible
• Monitor usage

Common Mistakes

To Avoid

1. No internal review: Always review before client
2. Too many options: Limit concept count
3. Vague feedback: Be specific
4. Scope creep: Document additions
5. Poor naming: Use conventions
6. Skipping descriptions: Add context
7. Ignoring notifications: Stay responsive
8. No version notes: Document changes

Checklist: Before Client Review

- [ ] All files properly named
- [ ] Descriptions added
- [ ] Stages organized correctly
- [ ] Internal review complete
- [ ] Branding configured
- [ ] Client permissions set
- [ ] Access tested
- [ ] Introduction prepared

Checklist: Project Completion

- [ ] All files approved
- [ ] Final versions exported
- [ ] Client notified
- [ ] Project archived
- [ ] Access revoked if needed
- [ ] Files backed up
- [ ] Lessons learned documented

Next Steps

1. Advanced Tips - Power user features
2. Workflows - Automation
3. Integrations - Connect tools