SOP: Member Invitations (Coordination)
Quick summary table
| Mode | Required information | Role | Delivery |
|---|---|---|---|
| Team member | Full name and email | Choose an available team role | Optional email dispatch; a queued email is not proof of delivery |
| Child guardian | Child full name and guardian email | The child is always a player | Optional in-app share link; no automatic email |
Phone and notes/additional guardian contact are optional. Pre-registration is not a current invitation mode.
Operational flow (4 steps)
- Open Team Management for the correct team.
- Select Add Member.
- Choose Team member or Child guardian and enter the required information.
- Choose an available team role for a Team member invitation. Child guardian invitations always use the player role.
- Choose whether to queue email for a Team member invitation, or whether to share the guardian link now or later.
Modes in detail
- Team member: The invited person reviews and accepts or rejects the invitation in the app.
- Child guardian: Share the link using the app's share sheet. The guardian signs in or creates their own account and accepts for the child.
Closing checklist
- Correct team confirmed
- Mode selected
- Role validated
- Required name and email entered
- Delivery choice checked: email dispatch for Team member; link sharing for Child guardian
Common errors
- Wrong team: verify header before Add Member
- Wrong role: validate with coach before sending
- Missing name or email: complete both required fields before submitting.
- Guardian invitation without guardian email: add the required email; sharing the link does not send an invitation email.
Operational examples
- Team member: New U17 player -> Add Member -> enter name and email -> choose player role -> choose whether to queue email.
- Child guardian: U11 player -> Add Member -> enter child's name and guardian email -> create the link -> share it from the app or save it for later.