likebooster↗

Think outside the box.

Menu
Let’s talk
← All insights

Practical guide

A Branded Hoodie Size Run That Does Not Rely on Guesswork

Build a hoodie size run from the selected garment’s size chart and each wearer’s confirmed choice. Give people a consistent way to compare fit, separate confirmed quantities from unresolved requests, and agree any reserve stock explicitly. A generic ratio of small, medium and large cannot tell you what your particular team needs.

For a November or December order, the temptation is to collect familiar size labels quickly and move on. That shortcut leaves an important question unanswered: which hoodie are people choosing a size for?

Choose the model before collecting sizes

A useful size request identifies the garment. Confirm the model or custom specification, fit description, colour and available sizes before asking the team to respond. Include the chart supplied for that exact garment and the instructions for interpreting it.

If the item is still being developed, label the sizing exercise provisional. You can collect expressions of interest, but do not turn them into a final production breakdown until the relevant chart and fit are settled.

LikeBooster’s merchandise service includes made-to-order hoodie and sweatshirt categories for discussion. It is not a live stock catalogue. Materials, sizes, quantities and production arrangements follow the brief, so an unrelated retailer’s hoodie chart should not become the specification for your order.

Use this short setup record before opening the request:

FieldWhat to record
Garment referenceExact model, or custom specification and version
FitSupplier’s description and intended way of wearing it
ChartFile or link, revision/date and measurement units
Measurement basisBody measurements or finished garment measurements
OptionsConfirmed sizes, colours and style variants
Response deadlineDate for wearer choices, separate from the production date
CoordinatorPerson responsible for questions and final totals

Do not fill gaps with assumptions. If the chart does not explain how a dimension is measured, ask before distributing it.

Help wearers compare like with like

Explain what the chart measures. A body measurement and a finished garment measurement answer different questions. Likewise, a garment’s flat chest width is not the same number as a circumference. Mixing these up can make a careful-looking spreadsheet unreliable.

If the supplier provides finished garment measurements, invite people to compare with a hoodie they already like using the same measuring method. Ask them to follow the chart’s reference points rather than inventing their own. They can keep those measurements private and submit only their size choice.

If the chart uses body measurements, direct wearers to the supplied instructions. Avoid adding an arbitrary allowance or telling everyone to size up. The garment’s fit, layering preference and chart guidance should inform the decision.

Where feasible, discuss a sample or try-on arrangement. Confirm that the sample represents the intended model and fit. A different hoodie may help someone describe a preference, but it does not validate the final size. If samples are not available, say so and make the limitations of the comparison clear.

Collect the decision without building a body-data file

For a standard team order, the coordinator usually needs a way to match the item to its recipient, the chosen option and whether that choice is final. Weight, body photographs and personal explanations are not useful default fields.

Keep the collection narrow. Use a private form or individual response rather than a shared sheet where everyone can see colleagues’ selections. A recipient code can help with distribution, but it is not anonymous if the organiser can connect it to a person. Restrict access accordingly.

The Office of the Privacy Commissioner of Canada’s meaningful consent guidance stresses clarity about what information is collected, its purpose and who receives it. Apply that principle to the sizing request: explain the use, access and retention plan in plain language. This worksheet is an organising aid, not legal advice or a determination of which privacy law applies to your organisation.

For a bulk delivery, the production team may only need aggregate quantities by size and variant. Keep the recipient mapping with the organiser unless there is an agreed reason to share it. Individual shipping requires a separate discussion about addresses and who needs them.

Copy this sizing worksheet

Use one row per recipient and garment choice. Add another row if someone is receiving a different model. Keep names or the code-to-name list in a restricted version.

Recipient referenceGarment/versionColourSelected sizeQuantityStatus
\[Internal code\]\[Confirmed model\]\[Option\]\[Choice\]\[Number\]Pending / confirmed

Before using the form, provide these instructions:

  • Review the attached chart for this garment, including the units and measuring method.
  • Compare the fit privately or use the agreed try-on option.
  • Submit your selected size and colour by the response deadline.
  • Contact the coordinator privately if the available options do not meet your needs.
  • Confirm any change before the order is locked.

Keep the question about unavailable sizes open and neutral. People should not need to explain their bodies to the whole team. The coordinator can ask the producer about options and communicate the answer privately.

Turn responses into an order, not a forecast

Create a separate summary grouped by garment, colour and size. Count confirmed responses only in the confirmed column. List unanswered requests and unresolved options separately so they cannot disappear into the total.

Garment / colour / sizeConfirmed unitsAgreed reserve unitsFinal units
\[One exact combination\]\[Count\]\[Count\]\[Sum\]

For each combination, final units equal confirmed units plus the specifically approved reserve. Then check that the sum of all combinations matches the intended order total.

For example, if a team needs one hoodie for each of 24 people and only 21 have confirmed, the record contains 21 confirmed choices and three unresolved recipients. It does not justify assigning the remaining people a medium. These numbers illustrate the counting process; they are not a recommended distribution.

Follow up with the unresolved recipients or agree how their requests will be handled. If the deadline forces a decision, make the consequence explicit rather than silently inventing their sizes.

Decide what a reserve is for

Reserve stock can serve several purposes: late joiners, a planned event allocation or a possible replacement. Choose the purpose first and agree the budget and quantities. There is no universally correct percentage or size mix.

Do not describe a reserve as an exchange guarantee. Ask about the order’s actual replacement, return and reorder arrangements before relying on them. A later order may involve a new availability check, estimate and production plan.

Keep reserve units separate in the summary. That makes it possible to see whether the order covers known recipients or speculative demand. If the budget cannot cover a reserve, record that decision too.

Lock the size run with the rest of the brief

Have one responsible person approve the final version. Record the garment reference, chart version, totals by variant, unresolved issues and approval date. Archive earlier versions clearly so they cannot be mistaken for the production instruction.

If the model, cut or chart changes, ask affected wearers to reconfirm. A previous choice is not automatically transferable to the replacement garment. Likewise, establish a cutoff for changes and check the consequences of a late amendment before promising it can be accepted.

Send the aggregate breakdown alongside the artwork, placement and delivery requirements in your project brief. Keep the wearer-level worksheet only as long as your organisation’s stated distribution and retention needs require. The result is a size run based on documented choices, with uncertainty visible before production begins.