Two coaches ask for portable soccer goals. A department lead forwards another request described as “equipment for the new term”. Before anyone approaches a supplier, the purchasing coordinator needs to answer a simple question: are these three separate needs, or three descriptions of the same purchase?
For a club or school collecting requests from several teams, consider the following administrative workflow. Its purpose is to make each purchasing decision traceable without requiring every coach to manage the whole order.
Give each request a clear identity
Consider keeping one shared request list with a reference for each submission. An email subject such as “new goals” gives the coordinator little basis for comparing it with another message.
Ask requesters to supply a short, consistent description:
- Requester and team or department.
- Intended sessions or programme.
- Venue where the equipment would be used.
- Number of individual goals requested, avoiding an unexplained “set”.
- Whether the request concerns replacement equipment, an additional allocation or a new programme.
- Whether anyone else has already submitted the same need.
- Date by which an internal decision would be useful, with the reason.
These are suggested administrative fields. They do not replace a product specification or establish which equipment is suitable. For the separate task of considering selection questions, see our soccer goal buying guide.
Compare the underlying need before combining requests
Similar wording is a reason to ask a question, not sufficient evidence to delete a request.
For example, two entries might both say “two portable goals for after-school football”. One could refer to a shared programme described by two staff members. Alternatively, the entries could concern separate sessions that need equipment at the same time.
As a suggested comparison, check the programme, venue, intended allocation and requester’s explanation. Then ask both requesters to confirm whether they are describing the same requirement.
Use a direct question: “Should request B be included within request A, or does B require a separate allocation?” Record the answer beside both references. Avoid interpreting silence as agreement to merge them.
If the answer remains unclear, keep both requests visible and mark their relationship as unresolved. The purchasing coordinator can then see that the combined quantity is still undecided.
Keep an original request when creating a combined one
When requesters confirm that their needs overlap, consider creating one lead request and linking the original entries to it. Preserve the original wording so each coach can see what happened to their submission.
A useful distinction is between combining the administration and reducing the requested quantity. Several requests can belong in one purchasing exercise while still representing separate equipment allocations.
For example, use notes such as:
- “Same requirement confirmed by both requesters; quantity counted once under request G-14.”
- “Separate requirements; included in one purchasing exercise, with both allocations retained.”
- “Possible overlap; clarification required before quantity approval.”
Avoid a bare “duplicate” label. It does not explain whether the need was included elsewhere or rejected.
Separate permission to enquire from permission to order
Choose status labels that describe an actual decision. A suggested sequence is received, clarification needed, ready for review, approved for supplier enquiry, approved to order and closed.
For each decision, record the responsible person, date and agreed scope. If your organisation uses different approval steps, follow those rather than adding a parallel process.
In particular, a coach asking for information should not appear to have authorised a purchase. Likewise, an enquiry covering several possible quantities should not be recorded as an approved order quantity.
Nominate one coordinator for the combined supplier enquiry. Other staff can contribute questions through that person, keeping the request references attached to the conversation.
Worked example: three messages, two needs
The following is an illustrative example, not a customer account.
A PE lead submits request G-14 for two goals for a lunchtime programme. An administrator submits G-15 after receiving the same programme brief. An after-school coach submits G-16 for two goals for a separate allocation.
The coordinator asks the three requesters to clarify the relationship. The PE lead and administrator confirm that G-14 and G-15 describe the same requirement. The after-school coach confirms that G-16 is additional.
The proposed review record would therefore contain two goals under G-14, a link from G-15 to G-14, and two goals under G-16. The combined request for consideration is four individual goals. That arithmetic records the requests; it does not establish that purchasing four is necessary or approved.
The decision-maker can now assess the two needs without counting the lunchtime request twice.
Close each request with a visible outcome
Before closing an entry, consider checking that:
- The requester has received the decision.
- Any combined request is identified by reference.
- The approved quantity and intended allocation are explicit.
- Deferred requests have a review trigger or date.
- Withdrawn requests are marked as withdrawn rather than silently removed.
- Any resulting order can be traced back to the relevant requests.
Once an order reaches the receiving stage, continue with the separate task of matching soccer goal deliveries to orders.
If your club or school is preparing an enquiry, you can browse the goals collection and use the B2B enquiry page to describe your consolidated requirements. Include which quantities are agreed internally and which remain under discussion.
Frequently Asked Questions
Should identical requests always be merged?
No. As a suggested practice, confirm the underlying need with the requesters first. Identical descriptions may represent separate allocations. Combining an enquiry does not necessarily mean reducing its quantity.
Can we manage this in a spreadsheet?
Yes. One suggested layout is a row per request, with columns for reference, requester, quantity, purpose, related request, status and decision note. Use a shared location your organisation already maintains.
What if a coach changes the requested quantity?
Record the revised quantity, date and reason, and return it to the appropriate internal decision stage. Keep the earlier decision visible so nobody mistakes approval of the original request for approval of the change.
Does approval of a request mean the goals are ready to use?
No. This workflow concerns purchasing administration. Technical inspection, assembly, anchoring and repairs must follow the exact manufacturer’s instructions for the equipment concerned.