Run every decorated apparel order on one production-ready job ticket that carries specs, approved art, due date, and pack/ship notes through intake, blanks pull, decorate, QC, and ship, with named handoffs so jobs and remakes do not get lost between desks and racks.

Key definition: job ticket (production-ready work order)

The single packet (paper or digital) that authorizes the floor to run a job. It includes customer and due date, garment counts by size and color, decoration method and placement, the approved art version, special finish/pack/ship instructions, exception flags, and the next owner. Quote approval alone is not production readiness.

Stage spine: Intake, art approval, blanks pull, decorate, QC, pack/ship (or customer pickup).

Part of the DAX Learning Hub: practical guides for apparel decorating. Pair this flow guide with cost math in How to Price Custom Apparel Jobs for Profit and method choice in Screen Printing vs DTF Pricing for Small Runs.

Published by DAX (Decorated Apparel Expo) · Last updated: September 2026

Also see How to Get and Run Corporate and Team Apparel Orders and Preparing Artwork for T Shirt Printing: File Specs by Method.

Also see Apparel Decorating Shop Setup: Layout, Utilities and Equipment and Contract Screen Printing and Embroidery: How It Works.

Find more equipment and shop setup guides in the DAX Learning Hub. Related guides: Blank Inventory and Sizing and Which Decoration Method to Start With: A Budget Guide for New Shops.

This guide is for shop owners, production leads, CSRs, and floor staff who lose jobs between sales, art, racks, and shipping. It covers ticket contents, stage handoffs, remake reduction, batching judgment, and simple SOPs a solo shop can grow into. It is shop-ops protocol only: not a decoration technique tutorial, and not a pitch for any shop-management product. Paper, whiteboard, shared folder, and software can all carry the same packet.

The same ticket discipline works for screen printing, embroidery, DTF, and multi-method shops. Method changes what readiness looks like at the station (screens, sew-out, gang sheet). It does not change the need for one complete ticket and named stages.

What Shop Floor Flow Looks Like in a Decorated Apparel Shop

Shop floor flow is the path a confirmed order takes from intake to a packed box (or pickup shelf). The goal is not bureaucracy. The goal is that anyone who touches the job can answer: what is this, who owns it now, what must be true before the next stage starts, and when is it due.

Why Stages Beat Memory and Sticky Notes

Verbal changes, sticky notes, and "everyone knows that job" fail when volume rises, someone is out sick, or two rush orders land on the same day. Incomplete tickets are a common remake driver in shop-ops write-ups: missing art version, wrong blank pull, unclear placement, or a change that never hit the packet. Named stages force a gate. If the ticket is incomplete, the job does not enter the schedule as production-ready.

Method-Agnostic Stages That Still Fit Screen, Embroidery, and DTF

Use one core spine for every method:

1. Order intake and spec confirmation
2. Art approval and production-ready gate
3. Blanks pull and inventory match
4. Decorate (method station kickoff)
5. QC before pack
6. Pack, label, and ship (or customer pickup)

Add method readiness as station add-ons, not separate workflows: screen/film readiness for screen, digitizing or sew-out readiness for embroidery, gang-sheet or transfer readiness for DTF. Keep those notes on the same ticket.

Solo Shop vs Growing Team (Same Stages, Different Owners)

A solo shop still needs the stages. You are simply every owner. Write the ticket so tomorrow-you (or your first hire) can run it without a phone call. When headcount grows, keep the same stages and assign a next owner on each handoff. Do not wait for a named MIS to call the shop "real." Protocol first; carrier second.

Stage by Stage: From Order In to Packed Box

Order Intake and Spec Confirmation

Capture customer or PO, garment style, colors, size curve, decoration locations, method preference if any, in-hands or ship date, and packing notes. Confirm ambiguities before art starts: allowed substitutions, customer-supplied blanks, specialty finishes, and rush flags. Price and due-date economics live in the pricing guide; this stage only locks the operational facts the floor will need.

Art Approval and Production-Ready Gate

Separate "yes on price" from "ready to produce." Production readiness means the approved art version is attached, placements and sizes are clear, method by location is set, counts match the ticket, and the promised date was checked against capacity. Until that gate passes, the job stays in pre-production, not on the floor schedule.

Blanks Pull and Inventory Match

Pull against the ticket: style, color, size counts, and any allowed substitution. Mark shortfalls and holds on the ticket before decorate starts. Treat inventory practices (how you bin, label, and count blanks by size and color) as part of the pull discipline. Wrong blank color or size is a classic remake path; the fix is match-to-ticket, not hope.

Decorate (Method Station Kickoff)

Kick off only from the production-ready packet. Confirm method readiness for this station (screens, sew-out, transfers), then run a first-article or setup check against the approved proof before the full run. If method choice is still open on a quote, resolve it with cost structure first (screen vs DTF pricing), then lock the chosen method on the ticket so the floor is not guessing.

QC Before Pack

QC is a checkpoint on the same work order, not a vibe at the end of the day. Check placement, color or stitch match to the approved proof, count vs ticket, defects, and labeling. Hold or remake rules should be written so the packer is not inventing policy under pressure.

Pack, Label, and Ship (or Customer Pickup)

Final pack confirms sizes, quantities, and ship or pickup method against the ticket. Include any special packing notes (fold, bag, hang, separate by size). Close the loop: update status, archive the approved art and run notes, and leave a clear trail for reorders.

What Belongs on a Job Ticket (Work Order)

Treat the fields below as a checklist, not as a software feature list. If a field is blank and the floor would have to invent it, the job is not production-ready.

Customer, Due Date, and Priority Fields

Name the customer or PO, the in-hands or ship date, and priority (normal, rush, hold). Rush is a schedule flag here, not a pricing lesson. If capacity cannot absorb it, escalate before the floor starts.

Garment Specs, Counts by Size and Color

List style, colorways, and counts by size. Note allowed substitutions and customer-supplied blanks so pull and remake decisions are not improvisation.

Decoration Method, Location, Colors, and Placement Notes

Method by location (left chest screen, full-front DTF, left-chest embroidery, and so on), color or thread notes, and placement size. Keep measurement notes as ticket fields, not as a technique tutorial.

Approved Art Version and Proof Reference

Point to the final approved file or proof ID. Version drift (running v3 when the customer signed v4) is a remake factory. Archive that proof with the ticket for reorders.

Special Finishing, Packing, and Ship Instructions

Fold/bag/hang, poly notes, labels, split shipments, and pickup vs carrier. Packers should not have to ask sales for rules already known at intake.

Exception Flags and Next Owner

Flag rush, specialty process, customer blanks, art holds, and blank shorts. Name the next owner so the job cannot sit ownerless on a rack.

Handoffs That Prevent Lost Jobs and Remakes

Separate Quote Approval From Production Readiness

A signed quote means commercial yes. Production readiness means the packet is complete enough that the floor will not invent missing details. Shops that conflate the two schedule incomplete work and pay for it in remakes.

Pre-Production Review Checklist Before Scheduling

Before a job hits the board or rack schedule, run a short review:

• Approved art attached and versioned?
• Line items matched to methods and locations?
• Counts, sizes, and placements clear?
• Notes operational, or still ambiguous?
• Promised date realistic vs current capacity?

If any answer fails, hold the job in pre-production. Do not "start and figure it out."

First-Article or Setup Check at the Station

At decorate kickoff, compare the first piece (or setup proof) to the approved art on the ticket. Catch placement and color drift before the full count runs. Write any approved tweak on the ticket so the rest of the run and future reorders match reality.

How to Document What Actually Ran (For Reorders)

After the job, note what actually ran: placement tweaks, substitutions, setup notes, and any QC holds. Spec sheets plus archived approved art reduce reorder drift. The next order should not depend on someone's memory of last season's tweak.

Batching vs One-Off Jobs on the Floor

Batching and one-offs are capacity tools, not moral categories. Use judgment against your changeover cost and due dates. Do not publish a fixed "batch every N jobs" rule as gospel.

When to Batch by Method, Colorway, or Due Date

Many shops batch same-method or same-setup work to cut changeovers: same screen setup, same hoop family, same transfer press profile, or same due-date window. Batch when it protects throughput without burying a nearer due date.

When One-Off Jobs Should Jump the Queue (And How to Flag Them)

Rush, customer pickup today, and oddball specialty jobs should stay visible. Flag them on the ticket and on the board or rack so they do not vanish inside a batch. Jumping the queue is a deliberate capacity decision, not a favor that never gets written down.

Protecting Capacity Without Losing Visibility

Batching saves changeovers. Status language and a morning rack walk protect visibility. If a batched ticket cannot be found or owned, the efficiency gain is fake.

Simple SOPs a Solo Shop Can Grow Into

One-Page Stage Checklist (Start Here)

Start with one page: the six stages, the ticket field groups, and a yes/no production-ready gate. Use it on every job for two weeks. Fix the checklist where real jobs break it. Grow from that sheet, not from copying a large-plant binder.

Ticket Status Language Everyone Shares

Pick a short status set and use the same words everywhere (board, ticket, chat): for example Intake, Art review, Ready, Blanks pulled, In decorate, QC, Packed, Shipped/Picked up, Hold, Remake. Shared words beat private shorthand.

Morning Board or Rack Walk Ritual

Once a day, walk the board or racks: what is due today and tomorrow, what is on Hold, what lacks an owner, what is waiting on art or blanks. Solo shops can do this in five minutes. Teams should do it out loud so handoffs are public.

Escalating Remake and Hold Rules

Write who can authorize a remake, when a job goes on Hold, and how the customer is notified. Verbal "just reprint it" without a ticket update creates the next lost job. Treat remakes as ticketed work with a cause note.

What to Add When You Hire the First Floor Helper

Add named stage owners, a short onboarding to the status words, and a rule that only the ticket authorizes the run. Keep the same packet. Do not invent a second shadow system in someone's notebook.

Frequently Asked Questions About Job Tickets and Shop Floor Flow (FAQ)

What is a job ticket in a decorated apparel shop?

A job ticket is the production-ready work order that carries customer, garments, decoration specs, approved art, due date, and packing/ship notes so the floor does not invent missing details. Paper or digital is fine; completeness and ownership matter more than the carrier.

What stages does a job usually go through from order to packed box?

Most shops can run a method-agnostic spine: intake and spec confirm, art approval, blanks pull, decorate, QC, then pack/ship or pickup. Use a production-ready gate before scheduling. Screen, embroidery, and DTF add station readiness steps on top of that spine.

What should be on every job ticket before production starts?

Counts by size and color, garment style, method and location, colors, placement, approved art version, due date, pack/ship instructions, exception flags, and who owns the next step. If the floor would have to guess, it is not ready.

How do shops reduce lost jobs and remakes?

Separate quote yes from production-ready, require a short pre-production checklist, keep one ticket as the source of truth, stop verbal changes that never hit the ticket, and run QC against that same packet before pack. Protocol beats product pitches for this failure mode.

Should a small shop batch jobs or run them one at a time?

Batch same setup when it cuts changeovers and still respects due dates. Keep rush and oddballs clearly flagged so they do not vanish inside a batch. Grow from a one-page SOP and shared status words, not from copying a large-plant system you do not need yet.

Practice patterns in this guide are illustrative shop-ops themes; verify stage names, capacity language, and checklist depth against your own floor before you lock SOPs.

Clean tickets and named handoffs make pricing and method choices easier to execute, because the floor runs what the quote promised. Browse more guides in the DAX Learning Hub, and check 2027 cities and dates on the DAX show schedule when you are ready to compare equipment, blanks, and consumables in person.