Team Delegate

Communication windows during a championship are tightly regulated — players cannot freely use phones during play, and the delegate must keep updates timely and on the record. WhatsApp groups blend personal and official messages, leak when a player leaves the team and offer no audit.

A private team channel inside the platform respects the permitted-communication rules, archives every message for federation review and keeps tournament logistics separate from personal chat.

Each team gets a delegate-managed channel with role-based posting (delegate, captain, federation officer) and read access for all players and approved staff. Messages outside permitted windows queue for delivery in the next allowed slot; every message is timestamped, language-tagged and exportable.

The channel auto-archives at the end of the event and is retained per federation policy with controlled review access.

Dress code disputes — wrong shorts, missing sponsor patch, undeclared boule set, unapproved footwear — happen most often at the very start of a match, when correction is hardest and forfeit risk is highest. A pre-match checklist with photos signed off by the delegate and visible to the duty referee removes ambiguity and protects the team from late challenges by an opponent or the jury.

It also gives the federation a clear record if the rules change during a tournament or a complaint surfaces after the event.

The compliance module presents the federation's dress and equipment list per category, lets the delegate tick each item, attach photos, note exceptions and sign off. The signed-off pack is visible to the captain and to the duty referee from the match record, included in any subsequent dispute case, and forms part of the event archive retained for the federation review window.

When an incident occurs — a yellow card, a foul, a verbal exchange — the delegate's first job is to record exactly what happened, gather evidence and respond within the procedural windows defined by FIPJP and the host federation. Without a workflow this lives in notebooks and emails and falls apart at the appeal.

A structured workflow ensures every step (notification, response, hearing, appeal) is captured against the right rule reference and the right deadlines.

The discipline workflow models FIPJP and federation procedures as configurable templates — incident types, sanction options, response windows, appeal paths. Each case captures evidence, timestamps and signed responses; the workflow blocks invalid transitions and surfaces upcoming deadlines to the delegate.

Outcomes feed the player's discipline history and the federation archive automatically.