Plan hackathon team shirts around a design the whole team wants to wear, confirmed garment sizes and a delivery window the supplier can actually meet. Keep the project reference readable, check the event's rules and approve a sample before committing to a larger order.
The shirt is optional team equipment. Do not make participation, a photo or belonging depend on wearing it.
Write a one-page team brief
Agree on the purpose first: finding each other at the venue, a team photo, or a souvenir of a project. Pick one primary job so the front does not become a list of sponsor marks, usernames and jokes.
Here is an illustrative brief for a fictional team building a route-planning demo: “One More Route”, one simple path graphic, one front placement, and no personal names. This is a sample concept, not a product listing or evidence from a real team test.
Ask every member whether they understand and want the reference. Include designers, researchers and first-time participants in that check. A project joke can be specific without implying only the person writing backend code belongs on the team.
Collect sizes without turning them into public team data
Choose the exact garment before asking for sizes. Share its measurement chart and state whether the dimensions describe the garment or the body. Let members compare it with a shirt they like.
Ask each person privately for their preferred listed size, color and whether they want a shirt. Keep the order list limited to the people who need it, and remove unnecessary personal details after the order is resolved. Do not print a member's name or photograph without checking their preference.
Approve the artwork and physical sample
Read the final print file at actual size. Check spelling, punctuation, color contrast and placement on the selected shirt color. A code-style joke should also be checked by someone who understands its reference.
Ask the supplier about its file requirements, proof process and sample options. A digital mockup helps with layout but does not establish the physical print's feel, exact color or fit. If a sample is available, inspect it before approving the team quantity.
- Text: the agreed phrase is complete and readable.
- Placement: the artwork fits the intended size range.
- Garment: the sample matches the ordered model and color.
- Order: sizes, quantity and delivery details have been checked.
- Permission: the team may use the included artwork and any event or sponsor marks.
Work backward from the event
Confirm production and delivery estimates with the supplier, including the destination and any approval deadlines. Ask what happens if a proof needs revision. Do not promise a team delivery date based only on a general shipping banner.
Keep a fallback: attend in personal clothing if the order cannot arrive in time. Matching shirts do not replace the venue's clothing requirements or the event's conduct rules.
For the rest of the clothing plan, read what to wear to a hackathon. For an original joke, use the programming shirt joke workflow.
You can browse current developer shirts for individual choices. This link does not promise a custom-print, bulk-discount or team-order service.
0 comments