A school or club considering portable training lighting may arrange a product demonstration. If the resulting notes say only “looks good” or “seems convenient”, the buyer still has little basis for explaining a model choice or identifying what the supplier must clarify.
This article focuses on organising the demonstration itself: define the training arrangements you want to discuss, then record observations, preferences and unresolved questions separately. A demonstration can help a team formulate purchasing questions. One experience does not establish suitability for other venues or conditions.
Define the purchasing decision the demonstration should support
“Have a look at the lights” is not a sufficiently clear purpose. Explain what the team is deciding: whether to add a lighting option to an existing programme, or how the management process differs between candidate models. Without a defined decision, the session can become a product presentation that leaves coaches’ questions about lesson transitions unanswered.
Use the buyer guides to organise your selection questions, then browse the lighting collection to identify products to discuss. A category page is a starting point. Ask the supplier to confirm the functions and included components of each candidate model.
The demonstration request can identify:
- The lesson stages you want to support and the questions coaches want answered.
- The proposed venue and timetable, without presenting them as established evidence of suitability.
- Which models require comparison and which are being shown only to explain a process.
- Who will take notes, consolidate coaching feedback and make the purchasing decision.
For example, ask who would take responsibility for the equipment during a lesson change and what information they would need. Avoid starting with the unsupported conclusion that a particular light will make every transition seamless.
Establish how the demonstration unit relates to the candidate model
First establish whether the equipment being shown matches the proposed purchase. Ask the supplier to identify the demonstration model, its components and any separately selected options. Record differences at the start of the notes so that the demonstration unit’s behaviour is not automatically attributed to the candidate configuration.
Ask who will operate the equipment during the demonstration, which model-specific instructions future users should consult, and whether the functions shown are included in the proposed configuration. These questions establish what is being compared; they do not ask coaches to determine technical suitability themselves.
Assembly, anchoring, operation, inspection and maintenance must follow the exact manufacturer’s instructions for that model. An operator’s verbal habits do not replace those instructions. A step omitted from the demonstration must not be recorded as unnecessary.
Observe the lesson workflow instead of collecting broad impressions
Organise the discussion around preparation, the lesson itself, transitions and the final handover. This gives participants a shared frame for their comments. The purpose is to document administrative arrangements, not to create equipment operating rules.
For preparation, ask who collects the equipment, who checks that the relevant documents are available and who contacts the supplier about unanswered questions. During the lesson discussion, coaches can describe their teaching positions and planned activities, then identify which questions the demonstration addressed and which it did not. For transitions, discuss what the next responsible person needs to know. For the final handover, identify who completes the return record and follows up unresolved points.
If a coach describes the process as inconvenient, ask which step they mean, who would perform it and what information is missing. If someone prefers another model, ask which lesson requirement supports that preference. Personal preferences can remain in the notes, but keep them separate from observations that can be checked.
For related background questions, see the portable training lighting article. Its discussion does not replace candidate-specific documentation or establish what this demonstration has verified.
Separate observations, interpretations and open questions
A short record can use three fields to prevent opinions from becoming product facts during editing.
- Observed: Describe what was demonstrated, who demonstrated it and which model was involved. Mark anything not shown as “not demonstrated”.
- Team interpretation: Explain which lesson arrangement a coach thinks the observation could help, or why a decision remains difficult.
- Open question: State what the supplier needs to clarify and name the internal person following it up.
For example, “the supplier demonstrated a control operation” is an observation. “The coach would like to use that operation during handover” is a requirement. “Does the proposed configuration include that function?” is an open question. Combining them into “this product meets the handover requirement” would go beyond the evidence.
Record the date and setting as well. Experiences involving different venues or configurations can be retained separately, but do not rank them as better or worse without a basis. Explain the differences first, then decide whether another demonstration or a written answer would resolve the uncertainty.
Keep unresolved points visible when comparing candidates
A comparison sheet does not need a score for every model. For each requirement, use statuses such as “supporting information available”, “clarification needed” or “not covered”, alongside the source of the information. These describe the completeness of the evidence, not a technical pass or fail.
Start with whether the team’s central purchasing questions have been answered. A more comprehensive demonstration does not establish that a model is preferable in every respect. Equally, an omitted demonstration step does not establish that another model lacks a capability. Ask the same question of each candidate before deciding whether the answers support the same requirement.
If an important question remains unresolved, leave the purchasing decision pending and specify the information required. Do not fill the gap with demonstration photographs, presentation language or participants’ overall impressions.
Produce a one-page decision note afterwards
Retain the candidate models, lesson requirements discussed, questions answered, questions still open and the person responsible for each next step. Coaches can confirm that their requirements are represented accurately. The buyer can check that the proposed configuration matches the record. Technical use questions should continue to be referred to the manufacturer or supplier for accurate instructions.
Keep the conclusion within what the evidence supports. “This candidate can proceed to documentation review” is more precise than “demonstration passed; suitable for all lessons”. Further comparison, additional information or a change in requirements should follow from the questions still unanswered.
When preparing a product discussion, use the contact page to share the lesson context, candidate models and questions you want the demonstration to address. Specific questions help both parties define the discussion more clearly than a request for a demonstration alone.
Frequently Asked Questions
Can one demonstration replace model-specific documentation?
No. It shows only what was actually presented in that particular setting. Functions, configuration and use still require the relevant documentation. Technical matters such as assembly, anchoring and inspection must follow the exact manufacturer’s instructions for the model.
How should conflicting feedback from coaches be recorded?
Connect each comment to a particular lesson stage, then distinguish preferences, observations and unanswered questions. If coaches are discussing different requirements, retain both. A vote is not necessary to compress different needs into a single overall rating.
What if the supplier cannot arrange a demonstration?
Begin with written questions about the model, configuration and lesson workflow. Keep anything that cannot be observed marked as unverified. The team can then decide whether the available information supports the next purchasing discussion without inventing demonstration findings.
Should the demonstration record say that a product passed?
If the team uses that term, define the internal stage it describes, such as completion of the requirements discussion. A broad “pass” should not simultaneously imply suitability, technical inspection and purchase approval. Each needs its own clear basis and responsible person.