Choose sports academy software by following a participant from enquiry and enrolment into the correct session and attendance record. Define who may view or change the relevant information, including family and staff access. Use the worksheet below to evaluate scheduling and handover while keeping safeguarding responsibilities with the academy’s actual policies and authorised people.
Which person and enrolment does the record describe?
Begin with the participant, the person making the booking and the academy colleague handling the enquiry. Keep their identities and relationships explicit. A household contact and a participant record may serve different purposes, so ask how the proposed system represents each in the actual workflow.
Omnify includes lead and client profiles in its described CRM capabilities. Documentation. Omnify describes booking several family members through one checkout. Documentation. Use those descriptions to prepare a family-booking demonstration with fictional records. Ask which person is enrolled in which activity and which contact receives the relevant information. Include a correction to the relationship so the evaluator can examine more than the initial successful booking.
Write the information needed for the academy’s actual enrolment process. Have the responsible organisation determine the relevant permission, welfare and information-handling requirements. The software brief should implement those decisions clearly rather than treating a general registration form as the academy’s complete safeguarding process.
How should the chosen session remain unambiguous?
Omnify describes multiple sessions or schedules within one camp listing. Documentation. spynPRO describes client session reservations. Documentation. Identify the activity, date, time, location and participant reference in the proposed booking. Ask the reviewer to trace the selected session from the public listing to the operational roster. Include similar session names so the evaluator must establish the actual reference.
spynPRO describes clients renewing subscriptions and viewing their details. Documentation. Review the distinction between a subscription or plan and the individual session being attended. Ask the provider to show the actual relationship in the selected configuration. Keep any rule about eligibility to reserve a session written explicitly in the working brief.
Prepare an exception for a rescheduled or cancelled session. Decide who updates the record, which people need to be informed and what the attendance team should see. Record the expected behaviour before testing so the resulting observation can be compared with an intentional operating rule.
An original enrolment-to-session worksheet
Use this practical checklist for a representative participant and family booking. Complete it with the actual academy roles and record references. It is an original evaluation aid for enrolment, attendance and access decisions.
| Handover boundary | Information to specify | Question for the proposed evaluation |
|---|---|---|
| Participant identity | Participant reference and current details | Is this the intended person? |
| Family relationship | Relevant contact and authorised relationship | Who should receive this information? |
| Enrolment | Activity, plan and accepted registration reference | What has actually been booked? |
| Session | Date, time, location and roster reference | Is the participant assigned to the correct session? |
| Attendance | Session-specific observation and responsible staff role | Who records and corrects the attendance entry? |
| Staff access | Tasks and information required by each role | Can staff reach only the intended records and actions? |
| Exception | Changed contact, cancelled session or disputed entry | Who decides the next action? |
| Handover | Record export and continuing operational owner | Can the next authorised person understand the information? |
Add a separate row for access to a sensitive note or document when relevant to the academy’s actual process. Ask which role needs that information and which role does not. Include permitted and denied examples in the controlled evaluation using fictional data.
Keep family access and staff access as separate questions. A person booking several participants should have an understandable view of the intended records, while staff responsibilities may differ between administration and session delivery. Request demonstrations of those boundaries rather than inferring them from a family-booking feature.
What should the attendance record establish?
Omnify describes attendance tracking for each session. Documentation. Connect the observation to the specific session and participant. Define who records it, who can correct it and how a later reviewer understands the correction. Keep a booking state distinguishable from the attendance observation the academy expects staff to make.
Omnify describes reports covering enrolment, revenue, attendance and membership churn. Documentation. Review the definitions behind the reporting view the academy intends to use. Ask whether the selected report concerns registrations, reservations, actual attendance or another measure. Record the date basis and filters before interpreting a summary as evidence of participation.
Use an ordinary session and a changed-session example in the proposed exercise. Have a session colleague locate the roster and record the intended observation using only the instructions and access provided. Retain any ambiguity as a requirement to resolve before acceptance.
How should access and information sharing be checked?
spynPRO describes a video library shared with clients and staff. Documentation. Identify which content or records each proposed sharing route makes available. Ask the evaluator to show the intended audience and a person outside it. Keep the academy’s actual communication and safeguarding policies with the responsible people when defining those checks.
spynPRO describes importing client and enquiry data from Excel. Documentation. spynPRO describes exporting data to an Excel file. Documentation. Prepare a migration and handover mapping rather than treating a successful file upload as the whole acceptance decision. Compare representative identities, relationships, session references and historical entries in the source and destination. Keep uncertain mappings provisional until an authorised owner resolves them.
Record the product and configuration used for the demonstration. The cited publisher pages describe selected features; the proposed access model and the academy’s operating process still need their own evidence. Retain the result of each controlled check with the relevant version.
Hypothetical example: two siblings, different sessions
Imagine a family booking contains two participants in different sessions. A later schedule change affects only one participant, while the operational team prepares the next roster. This hypothetical case tests the relationship between family contact, participant identity and session assignment.
Put both participant references and the relevant sessions on the worksheet. Apply the proposed change in the controlled test arrangement and ask a colleague to identify who attends which session. Review the contact information and update message for the affected booking.
Then ask a staff member with a different responsibility to perform their intended task. Check that they can locate the information needed and that unrelated records are handled according to the agreed boundary. Record the observed result and assign any unresolved access question to the responsible academy owner.
For wider document handling, see document management. Discuss the public enrolment journey through web development and get started with the academy roles, session examples and safeguarding access decisions you need the proposed workflow to support.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.