A solo decorated apparel shop survives its first hire when core recipes, QC pass/fail rules, and stage owners are written before day one, tasks are handed off in low-risk order, and each skill is trained until the hire can run it without calling the owner.

Key definition: first-hire SOP set

The short written packets (purpose, steps, materials, pass/fail, named owner, review date) that turn tribal solo-shop knowledge into work another person can execute. The documentation bar is practical: write it so they can run without calling you. Checklists confirm handoffs happened; SOPs explain how and what "good" looks like.

Ownership spine: Document recipes, hand off low-stakes work first, train one skill up the independence ladder, name QC and stage owners, spot-check results (not every motion)

Part of the DAX Learning Hub: practical guides for apparel decorating. Pair this first-hire guide with ticket and stage discipline in Job Tickets and Shop Floor Flow: From Order In to Packed Box. Pricing and quote judgment stay with the owner longer; see How to Price Custom Apparel Jobs for Profit when you are ready to hand off that later.

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

Find more business and pricing guides in the DAX Learning Hub. Related guides: Screen Printing vs DTF Pricing for Small Runs and How to Price Setup Fees, Rush Orders, and Minimums.

This guide is for solo shop owners (screen, embroidery, DTF, multi-method) who are about to hire, or just hired, their first employee. It covers what to document, handoff checklists, training order, and quality ownership. It is shop-ops protocol only: not HR legal advice, not wage or benefit rules, not a decoration technique tutorial, and not a pitch for any shop-management or training product. Paper, binder, shared folder, and software can all carry the same packets.

Why the First Hire Breaks Solo Shops That Skip Documentation

Tribal Knowledge Does Not Scale Past One Brain

Many solo shops underestimate how much lives only in the owner's head: how to pack a team order, which label goes where, what "good enough" means at QC, and which holds need a phone call. That works until the owner is out sick, on a sales trip, or buried in quotes. The hire cannot run what was never written.

Shadowing Alone Creates a Permanent Phone-a-Friend Habit

Watching the owner for a few days feels like training. Without a written recipe and a pass/fail definition, the hire learns to interrupt instead of decide. Shadowing is a stage on the ladder, not the whole curriculum.

What "Write It So They Can Run Without Calling You" Means

The documentation bar is not a corporate binder. It is a practical test: can the hire complete this task from the written packet, matching the ticket and the pass/fail rule, without a mid-task call? If the answer is no, the packet is incomplete, not the hire.

What to Document Before Day One

Core Recipes: Prep, Pack, Label, Restock, and Station Kickoff

Write the recipes you repeat constantly: blank prep, packing sequence, labeling, restock, cleaning, and station kickoff (follow the shop's written setup checklist for that method). Include the "you'll just feel it" judgment calls in plain language. Station kickoff means the shop's checklist, not a press-settings tutorial.

Job Ticket Language and Stage Status Words Everyone Shares

Reuse the same status words the floor already needs: Intake, Art review, Ready, Blanks pulled, In decorate, QC, Packed, Shipped/Picked up, Hold, Remake. Ticket field design lives in the job tickets guide; here the hire rule is simpler: only the ticket authorizes the run, and everyone uses the same words.

QC Pass/Fail Definitions Tied to the Ticket (Not "Looks Good")

Write pass/fail against the ticket: placement, count, color or proof match, defects, labeling. "Looks good to me" is not a standard two people can share. Attach a short example photo set if that helps your methods.

Exception Flags: Rush, Customer Blanks, Holds, and Who Escalates

Flag rush, customer-supplied blanks, art holds, blank shorts, and specialty risk. Name who the hire calls for each exception. Escalation without a name becomes another owner interrupt.

Safety, Startup, Shutdown, and End-of-Day Closeout

Document machine startup and shutdown for stations the hire will touch, PPE expectations, and end-of-day closeout (power, ink/thread staging, trash, locked doors). Keep it shop-specific and short.

Where Docs Live (Binder, Shared Folder, Wall Chart) Without Crowning Software

Pick one home for SOPs and handoff logs so the hire is not hunting three notebooks. Binder, wall chart, shared folder, or software can all work. Buy tools when volume or headcount outgrows the carrier, not as a prerequisite for documentation.

Handoff Checklists: Owner to Hire

Pre-Arrival Checklist (Access, Tools, Samples, First Jobs)

Before day one: keys or codes, apron/PPE, labeled tool stations, printed SOP packet, sample "good" and "fail" pieces if useful, and two or three low-risk jobs already ticketed for practice. Do not invent the first job under pressure at 9 a.m.

Day-One Walkthrough Checklist (Show Once, Then They Do)

Walk the floor once with the packet open. Then have the hire perform the same steps while you watch. Resist re-doing the work for them. Correct against the written standard, then step back.

Daily Open and Close Handoff Log (What Is Open, Held, or Waiting)

Even without true multi-shift work, a simple open/close log prevents verbal memory from being the system: open jobs, quality holds, stuck work, and next actions. Solo-to-two shops can finish this in a few minutes.

Job-Level Handoff: Next Owner, Due Date, and Open Questions

Every ticket that leaves your hands needs a next owner, due date, and any open question written on it. Ownerless racks are how jobs disappear when two people share the floor.

End-of-Week Review: What Still Requires the Owner

Once a week, list what still required a mid-task call. That list is your documentation and training backlog. Pace milestones by skill readiness; do not promise a fixed "fully independent by day N" as gospel.

Training Order That Protects Quality and Margin

Hand Off First: High Volume, Clear Right Answer, Cheap to Fix

Start with prep, packing, labeling, restocking, cleaning, and order assembly. These tasks run often, have a clear right answer, and are cheap to fix if wrong. They free owner hours without betting the brand on day one.

Hand Off Next With a Spot-Check: Routine Production Steps

Move to routine production steps that follow a written station checklist, with an owner spot-check at first-article or end of batch. Do not flood the hire with every station at once.

Keep for Now: Pricing, Upset Customers, Money, and Brand Voice

Keep pricing, custom quotes, rush fee judgment, upset customers, money handling, and brand voice with the owner until trust and context exist. Mentioning those as "keep for now" is enough; fee math lives in the pricing hubs.

One Skill at a Time and an Independence Ladder (Watch, Do With Watch, Solo, Teach)

Move each skill through four stages: watch / instructed, do while watched, solo with spot-check, then can teach. Declaring someone "trained" after one demo is a common failure mode. Use the ladder as a method; you do not need a branded skills-matrix product.

First Live Jobs: Low Risk Work Before Customer-Critical Runs

Queue internal samples, simple reorders, or low-stakes packs before championship-weekend rush work. Confidence compounds; a remake on day two teaches the wrong lesson about independence.

Quality Ownership When Two People Share the Floor

Name an Owner for Each Stage Gate (Pull, Decorate, QC, Pack)

"Whoever is free" is not ownership. Name who owns blanks pull, decorate kickoff, QC before pack, and pack/ship for each job. One accountable name per gate, plus a backup when possible.

First-Article or Setup Check Before Full Run

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

Who Stops the Line and Who Escalates a Hold

Give the hire permission and a written rule: when to stop, when to Hold, and who to call. Fear of stopping creates remakes; stopping without a rule creates owner spam.

Remake Rules Written Before the First Mistake

Write who can authorize a remake, how the cause is noted on the ticket, and how the customer is notified. Verbal "just reprint it" without a ticket update creates the next lost job. Documented gates may reduce rework when they are followed; do not promise a fixed remake-percent outcome.

How the Owner Spot-Checks Results Without Re-Doing the Work

Once a skill is unsupervised, spot-check results against the ticket and pass/fail definition. Re-doing every motion trains dependence and burns the hours you hired to free.

Simple SOPs That Grow From Solo to Team

One-Page SOP Template (Purpose, Steps, Materials, Pass/Fail, Owner)

Keep each SOP to one page when you can: purpose, scope, materials, numbered steps, pass/fail, named owner, and review date. Grow from that sheet, not from copying a large-plant binder.

Living Docs: Review Date, Version Note, and Who Updates

Name a doc owner, publish date, and next review date. Review when process or equipment changes, and on a regular cadence (many shops aim for roughly every six to twelve months). Outdated SOPs create false confidence.

Skills Coverage Board so One Person Is Not a Single Point of Failure

Track which skills the owner and hire can each run unsupervised. Coverage risk shows up when only one person can run a critical task. A simple board or sheet is enough; no branded matrix required.

What to Add When Headcount Goes Past One Employee

Add named stage owners across more people, a short onboarding to status words, and a backup for each critical skill. Keep the same ticket and SOP packets. Do not invent a second shadow system in someone's notebook.

Paperwork for hiring (tax forms, classification, wages, benefits) needs qualified local advice. This Learning Hub page does not publish legal mandates or wage bands.

Frequently Asked Questions About Hiring Your First Shop Employee (FAQ)

What should I document before hiring my first shop employee?

Write the repeatable recipes (prep, pack, label, restock, station kickoff), QC pass/fail tied to the ticket, exception and escalate rules, and open/close routines so the hire is not guessing from memory.

What tasks should a solo shop hand off first?

Start with high-volume, clear-answer, cheap-to-fix work (prep, packing, labeling, restocking, cleaning, assembly). Keep pricing, money, upset customers, and brand voice with the owner until trust and context exist.

How do you train a first hire without them calling you constantly?

Train one skill at a time up an independence ladder (watch, do while watched, solo with spot-check, then can teach), and set the documentation bar at "run without calling you."

Who owns quality when there are only two people in the shop?

Name an owner for each stage gate (especially QC before pack), define pass/fail against the job ticket, write stop-and-escalate rules, and have the owner spot-check results instead of re-doing every step.

Do I need shop software before I hire my first employee?

No. Paper, binder, shared folder, or software can carry the same SOPs and handoff checklists. Buy tools when volume or headcount outgrows the carrier, not as a prerequisite for documentation.

Practice patterns in this guide are illustrative shop-ops themes. Verify stage names, checklist depth, and training pace against your own floor. This is not legal, wage, or benefits advice.

Written recipes and named owners make the first hire additive instead of another interrupt loop. Browse more guides in the DAX Learning Hub, and check cities and dates on the DAX show schedule when you are ready to compare equipment, blanks, and consumables in person.