Back to Resources
    Working With Your Designer

    How to Review Design Proofs: Approvals, Feedback & Sign-Off

    March 2025·9 min read

    You've hired a designer, submitted your files, and now the first proof has arrived. What happens next determines whether the project moves forward efficiently or spirals into endless revisions. Here's how to review design proofs like a pro, even if you've never done it before.

    What Is a Design Proof?

    A design proof is a visual draft of your website or logo presented for your review. It's not the final product. It's a checkpoint where you evaluate direction, layout, typography, and overall feel before the designer refines or builds it out.

    Proofs can come in several forms:

    • Static mockups: High-fidelity images showing how pages will look (usually presented as PDFs or image files).
    • Interactive prototypes: Clickable previews that simulate navigation and user flow.
    • Logo concepts: Multiple directions presented side by side for comparison.
    • Style tiles: Mood boards showing color, typography, and visual direction before full mockups.

    What to Look for in a Proof

    Focus your review on the big picture first, then move to details. Here's a framework:

    1. Overall Direction

    Does the design feel right for your brand? Consider tone, mood, and professionalism. Don't evaluate individual elements in isolation. Ask yourself: "If a potential customer saw this, would they trust my business?"

    2. Layout & Hierarchy

    Is the most important information prominent? Do your eyes flow naturally from headline to content to call-to-action? Check that key messages aren't buried below the fold or competing with decorative elements.

    3. Typography & Readability

    Are headings clear and body text easy to read? Font choices should match your brand personality. A law firm shouldn't use playful handwriting fonts, and a children's brand shouldn't feel corporate.

    4. Color & Imagery

    Do the colors align with your brand guidelines? Are photos high quality and relevant? Placeholder images are normal in early proofs, so focus on the design framework, not temporary content.

    5. Functionality (for websites)

    Can you see where buttons lead? Is the navigation intuitive? For interactive prototypes, click through the experience and note anywhere you feel lost or confused.

    How to Give Effective Feedback

    The quality of your feedback directly impacts the quality of the next revision. Here's how to communicate clearly:

    Be Specific, Not Vague

    • Instead of: "I don't like it."
    • Try: "The headline font feels too casual for our corporate audience. Can we try something more structured?"
    • Instead of: "Make it pop."
    • Try: "The call-to-action button blends into the background. Can we increase the contrast or make it larger?"

    Separate Personal Preference from Business Need

    Your favorite color might be green, but if your brand is blue, the design should be blue. Evaluate proofs through your customer's eyes, not your personal taste. Ask: "Will this resonate with my target audience?"

    Consolidate Feedback

    Gather input from all stakeholders before responding. Multiple rounds of conflicting feedback from different people is the fastest way to derail a project. Designate one person as the final decision-maker.

    Use Visual Annotations

    If possible, mark up the proof directly. Circle areas you want changed, draw arrows to show where elements should move, or use tools like Markup Hero or even a simple screenshot with annotations. Visual feedback is clearer than written descriptions alone.

    The Approval Process

    Most design projects follow a structured approval flow:

    1. Initial proof: Designer presents 1 to 3 directions based on the brief.
    2. Direction selection: You choose one direction to refine (or request a new exploration if none fit).
    3. Revision rounds: Designer refines based on your feedback. Most projects include 2 to 3 revision rounds.
    4. Final approval: You sign off on the completed design, confirming it's ready for development or delivery.

    What "Approved" Means

    When you approve a proof, you're confirming that the design direction, layout, and visual elements are correct. Changes after approval, especially structural ones, may incur additional costs or timeline extensions. Review thoroughly before signing off.

    Common Review Mistakes

    • Reviewing on your phone: Always review proofs on a desktop/laptop first. Mobile screens distort proportions and colors.
    • Asking for too many changes at once: Prioritize the most impactful changes. Trying to fix everything simultaneously creates confusion.
    • Ignoring the brief: If the design matches what was agreed in the discovery phase, trust the process. Changing direction mid-project is costly.
    • Comparing to competitors: Your brand should stand out, not look like everyone else. Reference competitors for context, not as templates.
    • Delayed responses: Sitting on a proof for weeks stalls the entire project. Aim to provide feedback within 2 to 3 business days.

    When Multiple Stakeholders Are Involved

    If partners, executives, or team members need to weigh in, establish a clear process upfront:

    • Set a deadline for feedback collection (e.g., "All feedback due by Friday").
    • Use a shared document or comment thread, not separate email chains.
    • One person compiles and submits the consolidated feedback to the designer.
    • Resolve internal disagreements before sending feedback. Don't make the designer mediate.

    Pro Tip: The 24-Hour Rule

    When you first see a proof, your gut reaction might be strong, positive or negative. Give yourself 24 hours before responding. Fresh eyes often catch things you missed initially, and first impressions can shift once you sit with a design longer.