how-to
How to Approve Custom Mockups: 7-Step Guide for 2026
Table of Contents
- Step 1: Gather Design Specifications Before You Approve Custom Mockups
- Step 2: Review the Digital Proofing Setup and Layout
- Step 3: Run a Custom Apparel Design Approval Process
- Step 4: Use a Mockup Approval Email Template
- Step 5: Manage Client Feedback and Design Revisions
- Step 6: Common Mistakes in Custom Apparel Mockups
- Step 7: Get Written Approval and Move to Final Production
- Frequently Asked Questions
Last Updated: September 16, 2026
Step 1: Gather Design Specifications Before You Approve Custom Mockups
Before you approve custom mockups, lock down the specs that determine whether the final print matches your intent: logo size, placement, thread or ink colors, garment style, and file dimensions, all confirmed in writing. At Logo Concepts & Printing, more reprints trace to a vague spec sheet than to a bad design.
Here's what to collect before any proof gets made:
- Exact logo dimensions in inches or centimeters, measured against the garment
- Placement coordinates (chest center, left chest, full back, sleeve)
- Color values: Pantone numbers for screen printing, thread codes for embroidery
- Garment brand, style number, and fabric content
- Print method and any production constraints
Step 2: Review the Digital Proofing Setup and Layout
Digital proofing previews a design before production, catching layout errors, spacing problems, and color shifts while changes are still free. Review the proof on the same device your customers will use, at full size.
Run this checklist on every proof:
- Logo centered and level against the garment seams
- Minimum margin of two inches from collar and side seams
- Text legible at the actual finished size
- Color accuracy verified against a physical swatch, not just the screen
- File dimensions match the print area
Step 3: Run a Custom Apparel Design Approval Process
A custom apparel design approval process is a defined sequence of review, feedback, revision, and sign-off that moves a design from concept to print-ready files, preventing the expensive mistake of printing hundreds of garments with an error nobody caught. Build it once, then run every order through it.
The sequence looks like this:
- Internal review. Your team checks the mockup against the spec sheet.
- Stakeholder review. Decision-makers sign off on brand alignment.
- Revision round. Feedback is consolidated and returned to the designer.
- Final proof. A locked version is issued for approval.
- Written sign-off. Approval is documented before production.
Version Control Strategies for Design Iteration
Version control means naming and tracking every iteration so nobody approves the wrong file. Use a convention like client-logo_v3_2026-09-16, never overwrite a previous version, and keep one shared folder as the single source of truth. Note the current version in the approval email to eliminate the "which proof did we approve?" argument that stalls production.
Mobile-First Approval Workflows
Mobile-first approval means the proof is built to be reviewed and signed off on a phone, since many decision-makers approve from a device, not a desk. Send proofs as a single scrollable image or a link that renders cleanly on mobile, with the approve button visible without zooming. Test it on your own phone first; if logo detail disappears at mobile size, the approver cannot judge it fairly.
Step 4: Use a Mockup Approval Email Template
Copy this and fill in the fields:
Subject: Mockup for approval: [Project Name], Version [X], due [Date]
Hi [Name],
Attached is the mockup for [Project Name], version [X] (file:
client-project_vX_YYYY-MM-DD). Please review the logo placement, colors, and sizing against the specs we confirmed on [Date].Please reply by [Date/Time] with one of the following:
- Approved - proceed to production on version [X]
- Approved with changes - list changes below; a new proof will be issued
- Not approved - see comments
By replying "Approved," you confirm that version [X] is correct and authorized for production, and that you have the rights to the artwork submitted. Changes requested after approval may require a new proof and may affect the project timeline and cost. If we don't hear back by [Date], we'll follow up before moving forward.
Thanks, [Your Name]
Why the Version Number Belongs in the Subject Line
Most approval disputes are not about whether the client approved a design; they are about which design the client approved. Putting the version number in the subject line and file name makes every reply self-documenting: when a client says "that's not what I signed off on," search the inbox for v3 and produce the exact proof they saw.
What Counts as a Valid Approval
An approval is valid when it is (a) in writing, (b) tied to a specific version, and (c) unambiguous. "Looks good" in a hallway is none of those; a reply that says "Approved" to a versioned email is all three. If a client approves verbally, send a follow-up restating the version and ask them to confirm in writing before production starts.
Adapting the Template for Different Approval Types
Adjust the template body based on what is being approved:
- Simple edit (color swap, spelling fix): shorten the review list to the one changed element and note that everything else is unchanged from version [X-1].
- Complex custom design (new layout, multi-location print): expand the review list to cover placement, scale, color, and garment, and require the client to confirm each line.
- Re-approval after a revision: reference the prior version and list exactly what changed, so the client is not re-reviewing the whole design from scratch.
Step 5: Manage Client Feedback and Design Revisions
Client feedback should arrive in one consolidated round, not a slow trickle of emails. Ask reviewers to gather all comments and return them together by a stated deadline. Scattered feedback multiplies revision cycles, pushes your timeline, and makes version control nearly impossible because every email may reference a different proof.
Set the Revision Rules Before the First Proof
Most revision disputes trace back to rules that were never stated. Before the first mockup goes out, put these in writing:
- How many revision rounds are included. A common pattern is two rounds for simple edits and three for complex custom work.
- What counts as a revision versus a new design. Moving a logo half an inch is a revision. Changing the concept entirely is a new design and a new quote.
- What counts as a scope change. Adding a second logo location, a new garment style, or a new colorway is a scope change, not a revision.
- How late changes affect the timeline. A change after final proof resets the proofing clock and may push the delivery date.
Sort Every Piece of Feedback Into One of Four Buckets
When feedback comes in, sort it before you act. The bucket determines the action, the cost, and whether a new proof is required.
| Feedback Type | Example | Action | Version Impact |
|---|---|---|---|
| Objective fix | Logo off-center by half an inch | Correct and re-proof | New version (vX+1) |
| Subjective preference | "Make the blue warmer" | Confirm exact color before changing | New version if changed |
| Scope change | Add a second logo location | Re-quote and reset timeline | New design, new version line |
| Rejection | Design does not fit brand | Return to concept stage | Restart at v1 |
Consolidate Feedback Into a Single Annotated Proof
Do not forward a client's raw email to the designer. Consolidate every comment onto one annotated proof, numbered and tied to the version it applies to, giving the designer a single source of truth.
Version Control Is the Backbone of Revision Management
Every revision produces a new version, and every version needs a name. Use a convention such as client-project_vX_YYYY-MM-DD, never overwrite a prior version, and keep one shared folder as the single source of truth. Reference the version number feedback applies to, and state which version each new proof supersedes.
When to Stop Revising
Revision rounds are not unlimited, and treating them as unlimited is how projects lose money. When the included rounds are used up, the next revision is a new quote. Say this in the email that delivers the final included proof, not after the client asks for one more change. Framing it as a rule rather than a penalty keeps the relationship intact and the project on schedule.
Step 6: Common Mistakes in Custom Apparel Mockups
The most common mistakes in custom apparel mockups are approving from a screen without a physical reference, skipping written sign-off, and ignoring how the design scales down. Each leads to reprints, delays, or a product that never matched the vision.
Watch for these:
- Approving on a monitor alone. Colors shift between screen and fabric.
- No written approval. A verbal "looks good" is not a record.
- Ignoring small-size legibility. Fine detail vanishes on a left-chest print.
- Forgetting the garment color. A design that pops on white may disappear on navy.
- No rejection criteria. Without a clear standard, feedback becomes personal taste.
Step 7: Get Written Approval and Move to Final Production
Written approval is the documented confirmation that a specific version of a mockup is authorized for production. It protects both sides: the client gets what they signed off on, and the printer has a record of exactly what was ordered. Get it by email or signed form, referencing the exact version number.
Legal Implications of Approval
Approval carries legal weight. A signed or emailed approval typically forms a binding agreement that the design is correct and authorized, limiting the printer's liability for errors the client approved, and confirms the client has rights to the artwork submitted. Most print vendors, including Logo Concepts & Printing, require documented approval before production for exactly this reason.
Frequently Asked Questions
What should I look for when reviewing a custom apparel mockup?
Check color accuracy against your brand guide, confirm file dimensions and logo placement, and verify that all design elements appear correctly on the garment. Look for print-ready files and ensure the mockup template shows the actual product color. Review the layout on both front and back if applicable. If anything looks off, request a design revision before signing off. Catching errors at this stage prevents costly reprints and keeps your project timeline on track.
How do I provide feedback on a design mockup?
Use a mockup approval email template that lists each design element and asks for specific changes. Reference the version number and point to exact areas needing adjustment, such as logo size or thread color. Avoid vague comments like "make it pop." Instead, say "increase logo width by 1 inch" or "switch to PMS 186 red." This clarity speeds up the client feedback loop and reduces back-and-forth. Always confirm the approval status in writing before moving to production.
What happens if I approve a mockup with an error?
Once you provide written approval, the design goes to final production as-is. Most vendors, including Logo Concepts & Printing, will not be responsible for errors that were visible in the approved proof. Reprints may be at your expense. That is why the custom apparel design approval process includes a final checklist for color accuracy, file dimensions, and layout review. If you spot an issue after approval, contact your vendor immediately. If production has not started, they may be able to pause the order.
Can I request changes after approving a mockup?
Changes after approval depend on whether production has begun. If the order has not entered final production, many vendors can accommodate minor adjustments, though rush fees may apply. Once screens are burned or embroidery files are set, changes become costly or impossible. To avoid this, use version control strategies and request all revisions before signing off. If you need to make a change, contact your project manager right away and reference the approval status and design iteration number.