When evaluating software, follow one example through those perspectives. Do not assume the handoff is complete because the coach and athlete screens look related.
Understand the states before comparing tools
The following labels describe concepts for evaluation; individual products may use different names.
Scroll the table horizontally on smaller screens.
| Concept | What it describes | What it does not establish by itself |
|---|---|---|
| Planned work | The intended session, order, prescription and instructions | That a particular athlete has received it |
| Assigned work | Work associated with an intended athlete or group and relevant schedule/context | That the athlete opened or carried it out |
| In-progress work | A session with activity or entries that are not yet fully completed | That all entries have been saved or the entire session finished |
| Recorded work | Values or notes the system has persisted under its own rules | That the workout is complete or reviewed |
| Completed work | The product's explicit completion state | The quality of execution, adaptation or improvement |
| Coach review | The coach examines the returned information and relevant context | An automatic decision or proof of a beneficial outcome |
These distinctions help expose an incomplete demonstration. A total such as “one of nine sets recorded” and a current empty set can both be true. A training goal and a separate test result can also coexist without establishing measured progress toward that goal.
1. Express the coach's intent
Begin with a fictional session. Identify its exercise sequence, prescribed work and coaching instruction. Ask the demonstrator to explain how the prescription is represented: which values are required, which are optional, and what text the athlete will see.
A coaching cue should be evaluated as communication, not as a decorative note in a screenshot. Can a reader locate it beside the relevant work? Is the instruction associated with the correct exercise or set? Avoid making exercise or medical recommendations during a software demonstration; use content appropriate to the authorized test.
2. Confirm the intended assignment
Show the actual recipient and context. Is the view a reusable program, a published version, a dated assignment or an individual session? Those are not interchangeable concepts.
Ask what happens when a coach edits the source program after work has been assigned. Does the product preserve earlier context, create a new version, update future work, or do something else? The correct answer depends on the system and the program's needs; the point is to make the behavior explicit.
3. Inspect the athlete's next step
Open the athlete-facing experience for the same fictional example. Confirm the relevant assignment, exercise order and instruction. Check its real usability at a phone size, rather than relying only on a desktop screenshot inside a mock device.
Ask the athlete or representative user to locate today's schedule, an unfinished session and a longer-term objective. These should not be confused. A rest day does not necessarily mean that an older unfinished session has disappeared; what matters is whether that distinction is understandable.
4. Test incomplete and changed work
A polished happy path is only one part of the evaluation. Ask the vendor to demonstrate an unfinished set, an empty performed-value field, and leaving or returning to the session where that behavior is supported.
Record what is actually persisted and when. Ask how invalid values, network interruption, repeated taps or conflicting changes are handled, but do not conclude the behavior from a button label or a diagram. Use only an authorized disposable test environment for any action that changes records.
This article is a checklist for a demonstration, not permission to alter retained data in a real program.
5. Complete the work and inspect the coach's view
When the demonstration environment permits it, perform the explicit completion action, then return to the coach's corresponding assignment or review view. Check that the record can be identified, the state is clear, and prescribed versus performed information is understandable.
If that step cannot be run, mark the return-to-review behavior as not demonstrated. Do not turn it into a verified workflow simply because two screenshots contain the same exercise name.
The useful question is not just “does data sync?” Ask exactly which record changed, what the coach can see, how old the information is, and which decision or conversation it supports.
6. Keep development evidence separate from aspiration
A baseline, target, qualitative note and recent result play different roles. Ask what connects a result to a particular objective and whether the values are comparable. Do not infer improvement from a lower target, an upward chart or an unrelated recent test.
Software can present context for a coaching conversation without proving that a session caused a performance change. Claims about athlete outcomes need their own evidence and appropriate expertise; they are not established by this workflow checklist.
A practical review worksheet
For each step, record the exact task, role, product version, observed screen/state, saved result if tested, limitation and follow-up question. Use “Observed,” “Partial,” “Not demonstrated” and “Not applicable” rather than a blanket pass for the whole platform.
End with a short summary: what the coach can prepare, what the athlete can understand, what is returned for review, and which conditions still require verification. That summary is more useful than a list of attractive screens.
SPP's current previews
SPP's Coach and Player development previews show related training prescriptions and coaching instructions. Their fictional examples can help explain the intended relationship between the experiences. They do not independently establish a newly executed save, workout completion or completed return-to-Coach test.
Explore Coach and Player to examine the current public direction. The Software Evaluation Guide provides a broader checklist for organizational fit.
Contact SPP with the workflow you would like to evaluate. Use a general description of the task and roles, not identifiable athlete or medical records. Public availability and commercial launch timing remain unannounced.
