T-Shirt Order Form Template
Collect shirt style, size, color, and quantity from every member of the group with one link, not a spreadsheet full of wrong sizes.
Ordering shirts for the group? Fill this in once per person. It takes about a minute, and it saves whoever is running the order a week of chasing sizes.
The name we should match to your shirt when it arrives.
Group shirt orders die in spreadsheets. Someone starts a shared sheet, half the team edits the wrong row, two people never open it, and the print shop gets a size count that's off by three. You fix that by making each wearer answer for themselves: one link, one submission per person, and a response table that already is the size tally.
Every choice is structured. The name field reads "Name for this order" rather than "name" because shirts get handed out in a pile, and the name on the response is the name on the bag. Style, size, and color are separate structured choices instead of one free-text line, since "medium-ish, the blue one" is the answer that ruins print runs, and dropdowns close that door. Quantity allows up to 100 for the parent ordering three kids' shirts or the coach grabbing spares. The optional print-text field caps at 30 characters, because printers charge by personalization and long names break layouts. Email is required because there is always one follow-up question, and the organizer should not have to hunt for the asker. A per-size quantity grid stays out: matrix-style "2 × M, 1 × XL" inputs look efficient and then confuse the one person who needed this to be simple, so anyone who needs multiple sizes submits twice and the tally stays clean. Shipping addresses stay out too, since group orders distribute by hand and collecting addresses you won't use is friction plus liability.
Who runs the order. Team managers kitting out a season, event organizers printing volunteer shirts, startups doing a merch run for an offsite, family reunion planners, and student clubs where the treasurer is one very tired sophomore. Booster clubs and camp counselors reach for it whenever a headcount of shirts has to match a list of names.
Tune it, then settle up. Swap the style and color options to match what your printer stocks; fewer options means fewer regrets. Set a response deadline in Settings so the order can go to print, and switch on duplicate prevention (one submission per device) if double-entries start showing up. When the window closes, export the CSV and pivot on the size column, the table your print shop asks for. Focus mode is the default here because size-style-color plays like a quick quiz on a phone. The ending tells respondents the organizer will confirm the per-shirt price and collect when the order prints, the honest sequence for group buys. Unit price depends on the final count, so committing sizes first and settling second is the correct order of operations.
Frequently asked questions
How do I get the size counts for the print shop?
Export responses to CSV and total the size column. Because each person submits their own row, the export is already the tally sheet printers ask for.
Can I make sure each person only submits once?
Turn on duplicate prevention in Settings (per device or per IP). Someone ordering for family members can still note it, or you can leave prevention off for group buys.
How do we collect the money for the shirts?
The form doesn't take payment, and unit price usually depends on the final count anyway. Lock in sizes first, then the organizer collects via your usual method once the print total is known.
Can I set a hard deadline so the order ships on time?
Set a close date and time in Settings with a custom closed message. Late submitters see why the window shut and who to contact.