SoftwarePublished

Approval workflows that stop the reprints

Most reprints trace back to something nobody formally approved. Building an approval step that is fast enough to survive a busy week.

  • 12 min read
  • 1,045 words
Approval workflows that stop the reprints — quality check at a print shop
Software12 min readA1printsoft EditorialPhoto: TECNIC Bioprocess Solutions / Unsplash
On this page7 sections

The short answer

  • An approval is a record, not a conversation
  • Approve artwork, sizes, garment, placement and price together
  • One named person on the customer side, agreed in advance
  • Slow approvals cause more damage than missing ones — make it one click
  • Nothing enters production without the approval attached

Work backwards from any reprint and you usually arrive at the same place: something went to press that nobody had formally agreed. Not carelessness — a verbal yes, an email that mentioned one detail but not another, or an approval from somebody who turned out not to have the authority.

An approval workflow exists to convert those into a single unambiguous record. It costs a few minutes per order and removes the most expensive category of mistake there is.

What approval is for

It does three things

  • Forces the customer to look properly before production
  • Creates a dated record of what was agreed
  • Gives the shop a clear signal to start

The second is what protects you commercially. When a customer says the logo is the wrong shade of blue, the answer is either an argument or an approved proof showing the colour reference they signed off — and only one of those ends the conversation.

An approval is not a courtesy. It is the document that decides who pays when something is wrong.

What needs approving

Everything that could be wrong, on one page. A proof covering artwork alone leaves five other things unagreed.

ItemWhy it matters
Artwork, at print sizeThe obvious one
Spelling of every wordThe commonest reprint cause
Print dimensions and placement"Bigger than I expected" is a dispute
Ink or thread colours, referencedScreens do not match fabric
Garment style and colourSubstitutions must be visible
Size breakdown and quantityCannot be fixed after printing
Price and delivery dateRemoves the later surprise

Names and numbers deserve their own approval when a job carries them. A list of forty names approved as a list is far safer than forty names buried inside a proof image nobody read line by line — and the collection method matters as much as the approval, as personalised orders shows.

Who approves

Agree the name at quoting, before there is anything to approve. The failure mode is a proof approved by an enthusiastic committee member whose decision the treasurer later disowns.

Establish early

  • Who has authority to approve, by name
  • Whether anyone else must see it first
  • How long their internal process takes
  • A backup when that person is away
  • Where a purchase order number is required

The internal process question saves whole weeks. A school that needs governor sign-off has a timeline you must plan around, and discovering it after sending the proof is how a deadline is lost to nobody's fault in particular.

Making it fast

The practical enemy of approval is not resistance, it is delay. A proof sitting unapproved for four days has consumed the slack in the schedule.

What speeds it up

  • One link, one button — no printing, signing or scanning
  • Works on a phone, because that is where it will be opened
  • Everything on one screen, nothing in an attachment
  • An automatic reminder after 24 and 48 hours
  • A stated deadline tied to the delivery date
  • A rejection path that captures what is wrong

The rejection path matters as much as the approval. "Not quite right" restarts a conversation; a structured comment against the item that is wrong lets the art desk act immediately.

Automatic reminders remove the chasing entirely, and they land better than a person asking twice. Where proofs are issued from the system holding the order, the reminder, the deadline and the record all happen without anyone scheduling them.

Recording it

Keep with the job

  • The exact proof that was approved, as a file
  • Who approved it, by name and email
  • Date and time
  • The version number — proofs get revised
  • Any comments made during approval
  • Anything the customer explicitly waived

Version numbering is what prevents the worst kind of confusion, where a job is produced from version two while version three was the one approved. Number every proof, and make the number visible on the image itself — the discipline is the same as tracking which version was approved.

Internal checks

Customer approval covers what the customer can see. It does not cover whether the job is producible, and that check belongs to you.

Before release to production

  • Artwork resolution adequate at final size
  • Colour count matches what was quoted
  • Blanks confirmed available in every size
  • Method suits the garment — check blends for migration
  • The schedule can actually hit the date
  • Deposit received where terms require it

Doing this before the customer sees the proof is better still. A proof issued for something you cannot produce wastes the approval cycle and costs the days you needed.

When it is skipped

It will be skipped, usually for a rush job or a long-standing customer. The right response is a defined exception rather than a pretence that it never happens.

If you are proceeding without one

  • Get something in writing, even a one-line email
  • Note on the job that approval was waived and by whom
  • State that reprints in this case are chargeable
  • Never skip approval on names, numbers or spelling
  • Never skip it on a first order with a new customer

Those last two are where skipping actually costs money. A repeat run of a design you have printed before carries little risk; a new customer's personalised order carries most of the risk in the shop, and the five minutes saved is never worth it.

Set a deadline that moves the delivery date rather than absorbing the delay. "Approve by Thursday for delivery on the 14th, otherwise the date moves" is factual rather than aggressive, and it puts the consequence where it belongs — with the person holding the approval up.

Review skipped approvals monthly alongside the reprints. If the same customer or the same job type keeps bypassing the process, that is a pattern to fix rather than a series of individual decisions — the same logic as treating spoilage as data. The rest of the software archive assumes nothing reaches a press without a recorded approval.

Filed underSoftware
Share
Written byA1printsoft Editorial
175 articles

The print production desk at A1Printsoft. Writes the practical side of running a decorating shop: what things cost, how long they take and what to charge, checked against published trade figures.

Keep reading

More on software

All Software articles

Set up in an afternoon. From what you already do.

Free for 14 days · no card · pick what you make and we preload the methods, products and price tables.