Spond roster to team uniform sizing: complete 2026 workflow

Instead of repeatedly copying names and chasing sizes in messages, turn your Spond roster into a controlled uniform-sizing sheet, collect garment-specific confirmations, and release an approved order file. This Spond roster to uniform sizing workflow gives Australian team managers a practical manual hand-off for their 2026 uniform order without assuming an automatic connection between Spond and a supplier.

Why this matters

A team list identifies people. It does not establish which garment each player needs, whether a size matches the selected cut, or whether a parent has approved the printed name. Treating membership as order approval skips those decisions.

FE Custom is an online sports customisation store serving Australia. Use this workflow to prepare your team’s uniform requirements, then confirm the current garment information and ordering requirements directly before submitting anything.

A roster entry is not a confirmed uniform order. The useful connection is a traceable record linking each player to a garment, a selected size and an approval.

Before you start

• Arrange authorised access. You need access to the relevant Spond group’s player information, permission to use it for uniform administration, and a club-controlled spreadsheet. For juniors, identify the parent or guardian responsible for confirming the order.
• Obtain the sizing reference. Choose the intended garment and get its current size chart and measurement instructions. Ask the supplier to clarify anything missing before collecting sizes; do not assume an old chart still applies.
• Separate players from contacts. A guardian’s contact details are not the player’s identity. Keep the person receiving the request separate from the person wearing the uniform, particularly when siblings share a contact.

This guide uses a manual roster-to-sheet process. Its bold column labels are fields you create yourself, not claimed Spond buttons or settings; it does not depend on an export menu, API access or a supplier integration.

Roster register

Establish the order population

1. Open the relevant team roster in Spond using your authorised account. Identify the squad, season and players included in this uniform round rather than treating every group contact as a buyer.
2. Create a spreadsheet tab named Roster 2026. Add Player key, Player name, Team, Order required, Confirmation contact and Roster checked on.
3. Assign 1 internal player key per player. Use a club-controlled reference that does not change when a name is corrected; do not use a child’s birth date as the identifier.
4. Copy only the information needed for this order. Keep guardian details in the restricted roster register rather than repeating them throughout supplier-facing files.
5. Review the register against the Spond roster. Mark each player’s Order required field explicitly, including those who do not need new garments.

Expected result: every player in the ordering group has a distinct record, an identified confirmation contact and an explicit inclusion decision.

Do not use a jersey number as your player key. Numbers can change during allocation, and an unassigned number should not prevent you from collecting a size. Keep identity and printing instructions in separate fields.

Set access boundaries

Give editing access only to the people maintaining the order. Send players or guardians their own confirmation request instead of circulating a sheet containing everyone’s contact details and measurements.

Nominate an order owner and a backup. Record who resolves sizing questions and who can authorise the final submission so a reply to an assistant coach does not become an unrecorded change.

Garment sizing register

Build the fields before requesting replies

1. Create a second tab named Sizing 2026. Use 1 row per player per garment, linked to the roster through Player key.
2. Add Garment reference, Cut, Size chart reference, Chart checked on, Selected size, Quantity, Printed name, Printed number and Approval status.
3. Add measurement columns only for measurements requested by the selected garment’s chart. Include the unit in each heading, such as Chest circumference (cm) when circumference is actually required.
4. Set Approval status to a small, controlled list: Not requested, Awaiting reply, Needs clarification, Confirmed and Released. These are your spreadsheet values, not Spond settings.
5. Keep printed numbers as text where necessary so spreadsheet formatting does not remove an intended leading zero. Confirm the competition’s numbering requirements separately.

Expected result: every proposed garment has its own sizing decision, quantity, printing instructions and approval state.

Match the measurement to the chart

Use the measurement method named on the selected chart. A flat garment width and a body circumference are different measurements; entering either beneath a generic chest heading conceals that difference.

Ask the supplier whether a chart describes body measurements or finished garments if the wording is unclear. Do not add a homemade allowance, double a measurement without checking the method, or convert a familiar retail size into a supplier size by guesswork.

For basketball teams, use the full-squad basketball jersey sizing guide alongside the selected garment’s current chart. General advice supports the process; the relevant chart determines the size options you offer.

Compare the collection methods

Choose how families will return their decisions before sending the request. Both methods below feed the same sizing register; neither replaces garment-specific confirmation.

Collection method	Best for	Advantage	Limitation
Private message reply	Managers handling individual questions	Keeps clarification beside the player’s response	Requires manual transcription and checking
Club-controlled form	Teams collecting consistent fields	Uses the same questions for every respondent	Requires careful identity matching and access settings

Use a club-controlled form when consistent fields matter; use private replies when individual clarification matters more. In either case, retain the response as evidence rather than treating a typed spreadsheet entry as approval.

Confirmation and order release

Collect an explicit decision

1. Send each player or guardian the garment reference, current sizing instructions and the exact fields they need to confirm. State the response deadline with its Australian time zone.
2. Request a selected size for each garment. Collect jersey and shorts decisions separately rather than asking for a single team-kit size.
3. Ask the respondent to confirm the printed name, printed number and quantity where those details apply. Keep blank printing fields distinct from unanswered questions.
4. Record the response and its date in the restricted working file. Resolve unclear answers before changing Approval status to Confirmed.
5. Run 2 approval checks before release: the player or guardian confirms their details, then the nominated club approver checks the consolidated order.

Expected result: confirmed rows have an identifiable response behind them, while unanswered or ambiguous rows remain visibly unresolved.

A useful request states the garment, the chart reference and the decisions required. Ask the recipient to check spelling and size together, but do not make them infer the garment from a team nickname or an old order screenshot.

Prepare the supplier-facing file

Create a separate Order 2026 tab containing only approved order information. Include garment references, sizes, quantities and the required personalisation; exclude guardian contacts, raw body measurements and unrelated roster information unless specifically needed and authorised.

Summarise quantities by garment, cut and size. Reconcile that summary against the individual approved rows, then ask the supplier which submission format and details are required before sending the file.

Use a dated filename such as Team_uniform_order_2026_APPROVED with the actual approval date added. Keep the released version unchanged; record later requests in a change log instead of silently replacing its contents.

The release sequence is Roster check, Size selection, Player approval and Club approval. Keep each gate visible so a completed name list cannot be mistaken for a completed order.

When the Spond roster changes

Use a change-only workflow for late arrivals, withdrawals and corrected details. A roster update is a reason to review an order record, not permission to alter an already released order.

1. Compare the current Spond roster with Roster 2026 at the club’s chosen review points. Identify additions, departures and identity corrections using the internal player key.
2. Create a Change log entry with Player key, Requested change, Requested by, Requested on and Decision.
3. For a new player, collect garment-specific sizing and approval through the same process. Do not copy a sibling’s size or assign the squad’s most common size.
4. For an existing confirmed player, return affected garment rows to Needs clarification until the revised details are approved.
5. For a released order, ask the supplier whether the requested change can be accepted before promising it to the player.

Expected result: late changes remain separate from the approved file until their status is resolved.

Retain withdrawn players in the restricted working register with an explicit exclusion status. Deleting the record removes the explanation for why the roster and order population differ.

Reversible basketball jersey checks

Reversible basketball jerseys need a clear garment record. Record a reversible jersey as the garment being ordered, not as separate home and away garments merely because it has contrasting sides. Record quantity according to the actual order requirement.

Use the selected reversible jersey’s chart rather than carrying a size across from a different basketball singlet. Ask the supplier to clarify the cut and measurement method, and request garment-specific fit guidance if a player is between the chart’s options.

Keep colour-side and artwork instructions separate from sizing. Ask the supplier to confirm how names, numbers and team identification are represented on the proposed garment; do not assume the same personalisation appears on both sides.

For FE Custom reversible basketball jersey orders, confirm the current garment details before finalising the spreadsheet. This workflow organises the team’s decisions; it does not establish product specifications, sizing equivalence or a supplier’s ability to accept changes.

Troubleshooting

A guardian replies for more than one player

Match each response to the player key and garment before updating the register. Ask the guardian to identify the relevant child when the reply is ambiguous; a shared contact is not enough to determine whose size changed.

A player supplies only a familiar retail size

Return the selected garment’s chart and request confirmation against it. Leave the row at Needs clarification rather than converting the size yourself; an adult medium from another garment is not a verified selection for this order.

The measurements do not match the chart’s method

Check the column label and the instructions sent to the player. Ask for a corrected measurement using the specified method, retaining centimetres where the chart uses centimetres; do not compare flat width with circumference.

Two players request the same printed number

Check the relevant team and competition rules before deciding whether the duplication needs resolving. Keep the printed number separate from the player key, then obtain approval for any reassignment before releasing the affected rows.

A size changes after the approved file is sent

Log the request and contact the supplier with the released file reference. Keep the original approved file intact, and record the supplier’s response before telling the player the change is confirmed.

Customise your workflow

Keep FE Custom uniform ordering separate from roster administration: Spond identifies your team, while the approved garment register defines what you intend to order. That separation makes the working sheet reusable without assuming every future garment has the same chart or requirements.

For soccer, retain separate jersey and shorts rows. For tennis and pickleball groups, organise records by the actual squad and selected garment, not by an assumed club-wide fit.

At the end of the 2026 order round, archive the approved file under the club’s access and retention arrangements. Keep the blank template, but request fresh garment and size confirmations for the next round instead of carrying old approvals forward.

FAQ

One last thing

Audit the unresolved rows, not just the size totals. A quantity summary can reconcile perfectly while still containing an unapproved size or misspelt name. Before release, check every included garment row for confirmation evidence, then preserve the approved version.

Related guides

• How to choose reversible basketball jerseys for your club
• How to size custom soccer jerseys for a full squad
• How to proof and approve your custom jersey design