Skip to content

Art approval for custom apparel: a proof process that prevents remakes

By UniformsOS Team. Updated .

Most remakes start at approval, not in production. A misspelled name, a shade the coach pictured differently, a logo that looked fine on a phone and came out the size of a coaster. The factory made what it was sent. A proof is the contract for how the product looks: what the customer signs is what gets made. This is the process we would run on every order.

What a proof must show

On the proof Why it is there
Front, back and side views, drawn to scale Placement is judged against the whole garment
Height and width in inches for every logo, name and number A screen hides real size
Color callouts by name and code Two screens never show the same red
Decoration method for each element It changes the look, the cost and the minimum
Garment style, fabric and body color So the proof matches the quote
The size range, and anything that changes by size A chest logo that fits an adult large can swallow a youth small
Name and number font, with a sample name and number Fonts are the most common surprise
Version number and date So everyone is looking at the same file
Approval line: name, date, approved as shown So approval is a record and not a feeling

For an embroidered logo, see embroidery digitizing.

One approver, named at the quote

Decide who approves before the first proof goes out. On a team order it might be the coach, the athletic director or a parent who runs the booster club. It cannot be all three. Put one name on the quote. Other people can comment, and the approver collects the comments and sends one answer.

Revision rounds

  1. State the number of included rounds in the quote. Two is enough for most orders.
  2. Ask for all changes from a round in one message.
  3. Every change makes a new version with a new number and date.
  4. Mark the old version superseded. Never edit an approved file in place.
  5. Charge for rounds beyond the included number, and say so before you start one.

The roster is its own approval

Art approval covers the design. The roster covers names, numbers and sizes, and it fails in different ways.

  • Take the roster as a spreadsheet, not as photos or text messages.
  • Send back a typed list in the font that will be used, and have the approver sign that list.
  • Spelling belongs to the customer. Checking that every number is legal for the sport belongs to you.
  • Set a roster lock date. Late additions become a second, smaller order with its own date.

Color cannot be approved on a screen

A proof shows where color goes. It cannot show what the color will look like on fabric. Use one of these:

  • A physical color card from the factory, with the customer choosing by code.
  • A strike-off, which is a small printed or dyed sample of the actual color on the actual fabric, for a new color or a brand match.
  • A reference from a previous order, where the instruction is to match what was delivered last season.

Write the method on the proof. Color approved from the factory card is a different promise than color approved from a strike-off.

When changes stop

Approval starts the production clock. After approval, a change is a change order with a price and a new ship date, and the customer agrees to both in writing before anything moves. This is the rule that protects the date for everyone else in the queue.

How approvals go wrong

  • Approval arrives as a screenshot or a thumbs up, with no version named.
  • The proof was reviewed on a phone and nobody saw the small text.
  • Three people replied and two of them disagreed.
  • The proof showed the design on one size only.
  • The logo came in as a small image, was redrawn, and nobody compared it with the original.
  • The quote said screen print and the proof was drawn as sublimation.

The process, start to finish

  1. Collect the logo as a vector file, the colors, the roster deadline and the name of the approver.
  2. Send proof version 1 with every item in the table above.
  3. Collect one consolidated reply. Revise and send the next version.
  4. Get approval on a named version, with name and date.
  5. Approve color by card, strike-off or reference.
  6. Lock and approve the roster.
  7. Release to production with the approved version attached to the purchase order.
  8. Keep the approved proof and roster with the order. They settle every later question, and they are the starting point for the reorder.

See the tech pack checklist for what else goes to the factory with the approved proof.

Approvals in UniformsOS

In Designs each design request holds its proofs as numbered versions. The customer approves a version or asks for changes on a link, and the answer is saved with its note, its date and who gave it. A version that has been replaced is marked Superseded, and each request has a set number of revisions. The roster sits on the order line, one row per player with size, name and number.

FAQ

What is an art proof?
A drawing of the finished product that shows the design, placement, sizes, colors and decoration methods. The customer approves it before production.
How many revision rounds should a quote include?
Two rounds cover most team orders. State the number in the quote and price extra rounds.
Who should approve a team order?
One person named at the quote, usually the coach or the athletic director. Everyone else sends comments through that person.
Can a customer approve color from a screen?
No. A screen can confirm where a color goes. The shade is approved from a color card, a strike-off or a past order.
What if the customer finds a mistake after approval?
If the product matches the approved proof and roster, a fix is a new order or a paid change. If the product does not match what was approved, the remake is on the supplier.

Try UniformsOS free for 30 days

30-day free trial, every module on, no card needed.

All articles