Ask → verify → simulate → decide
Evidence-first officiating practice with deterministic court-position checks and a digital scorer event stream. No official accreditation is claimed.
Move a player. See the overlap decision instantly.
Deterministic training model for standard FIVB receiving-team positional relationships at service contact.
P6
Training approximation: the real rule is judged from players’ feet in contact with the floor at service contact. Use VolleyCore evidence for the exact current rule text and competition context.
Digital scoresheet decision training
Guided match-event scenarios with instant correction.
| DIGITAL SCORESHEET | Team A | Team B |
|---|---|---|
| Points | 0 | 0 |
| Timeouts recorded in scenario | 0 | 0 |
| Regular substitutions recorded | 0 | 0 |
Event 1 / 4
Set 1 starts. Team A serves and wins the rally.
Training tool only. It does not issue official scorer certification; competition-specific procedures require the applicable regulations and official training materials.
Original call → review → first fault → final call
Deterministic training surface backed by the same officiating engine used by VUEM. It never overwrites the original decision.
Gesture sequence is semantic evidence only:PROPOSED · score mutation locked.
First validated fault:fault-1 · Team A · 4200 ms ± 6 ms.
Reason:BALL TOUCHED · PROPOSED
Score:13–13 · Next server: B
Original decision remains in history assignal-training-rally. Final decision is appended, never overwritten.
Decision cases
Use VolleyCore to verify the applicable edition and source before treating an answer as official.
Net / center line
Contact occurs near the net during an active play. Identify the exact rule family before deciding.
Rotation / position
A receiving team appears out of rotational order at service contact. What must be checked first?
Libero
A replacement sequence creates doubt about libero legality. Identify the evidence and rule reference needed.
Sanctions
Separate misconduct sanctioning from delay sanctioning before choosing an outcome.
Challenge
A challenge request occurs under competition-specific technology rules. Check the competition regulation before applying a workflow.
Competition-specific technology rules, temporary rule tests and federation overlays must be checked before a scenario is used as an official interpretation.