Set up your club and first season

Open Settings, then Club and Age calculation

Choose Age at 31 August, Year of birth (31 December), or Custom cutoff date.

For a custom cutoff, enter the day and month and select Save cutoff

This changes the cutoff used by eligibility calculations. It does not rewrite dates of birth or send messages.

Open Settings, then Club and the kits section

Enter a kit name such as Home or Away.

Choose its shirt pattern and colours, then Add kit

The designer stores the shirt, secondary shirt, shorts and sock colours. Adding a kit does not assign it to an event or notify families.

Open the kits section in Settings, then Club

Identify the exact saved kit before using Remove.

Remove the intended kit and check the list

The existing editor applies its database relationship rules. It does not create a replacement kit or send messages.

Open Your requests in club onboarding

Find the club and team you asked to add. Only your own waiting requests have the withdrawal control.

Choose Withdraw request and confirm

The request is marked withdrawn. This does not create a team, grant a club role or send a notification.

Open Teams and its pending join requests

With club owner or admin access, identify the requester and proposed team.

Choose Decline and optionally write a short note

The decision attempts an email, when available, and a messages-channel push to that one requester. Your note is included; delivery is best-effort.

Confirm the decline and check the pending list

The request leaves the pending list. No team or staff role is created.

Open Teams and select the exact team

Use its staff controls with club owner or admin access.

Assign an existing person and choose their role, or remove a current staff assignment

Assignment updates volunteer and team staff records. An established linked account receives the applicable team access; an unlinked person does not receive an invitation or a new account.

Check the team and role before saving

Removing staff ends their access for that team, while other-team and club-wide roles remain. These controls do not send an invitation.

Open the exact player profile from People

Use current club owner, admin or registrar access.

Choose Archive member

Check the profile carefully: archiving stops their billing as well as archiving the player. This is not a refund.

Review the effect before confirming

Use the existing financial records to review any separate payment or refund question.

Open the player profile and Squad & membership

Use club owner, admin or registrar access.

Choose Grant exception or Remove exception

The setting changes whether ordinary team age and gender eligibility applies to this player.

Check the exact player and intended setting before saving

Open the exact player profile and its squad membership controls

Choose the target squad and the intended change

A primary-squad move closes other squads in that season; adding another squad preserves current memberships, and removing a primary squad can make a remaining same-season squad primary.

Check the resulting membership before saving

These controls do not change billing or send messages. Other seasons are preserved.

Open the member profile and Session credits

This section is available only for clubs with classes enabled.

Choose the quantity, credit type, optional team and expiry

Add a private note if needed. A credit is a session unit, not a payment collected by this form.

Check the recipient and save the credits

Credits may be used for class bookings; saving them sends no message and collects no money.

Open the exact member profile and its notes controls

Only notes allowed by your current coaching, admin, finance and safeguarding visibility are shown.

Choose Add, edit the selected note, or delete it

For a new or edited note, enter the text and choose its visibility. Keep private text in the form, not chat or an announcement.

Review the exact member, note and visibility before saving

Saving or deleting a note sends no message.

Open Settings and check the club identity

Confirm the club name, crest and contact details before inviting families.

Open full-size screenshot

Create or activate the current season

Use the dates your registrations, teams and fees should belong to.

Invite staff with the smallest suitable role

Use registrar, treasurer, coach or safeguarding access instead of club admin wherever possible.

Open full-size screenshot

Connect Stripe if the club will collect money

Do this in Settings → Money. Shop and Accounts only appear in the menu once Stripe is connected. You can still record cash and bank transfers as paid without it.

Check your club’s Seasons page

With no active season, enter a name and dates under Create your first season, then choose Create season. With an active season, Start the next season and Roll over to new season copy existing teams, players and fee plans. For a new empty season instead, ask Support to help you create one.

Provide the empty-season details

Tell Support the intended club, season name, exact start and end dates, and whether to make it active or leave it inactive. Answer any questions for missing or ambiguous details. If a Set up a season form is offered, use its club choices and review the same details there.

Review and create the season

Check the club, name, dates and active-season choice. Making it active replaces the previous active season. This creates an empty season with a default registration form; it does not copy teams, players or fees or send messages. Use season rollover separately to copy an existing season.

Open Teams in your club

Use the create-team control in the Teams area.

Enter the team details

Enter the team name and choose the intended season. Set age group, gender, format, ages or player capacity if needed.

Create the team

Check the club, season and details, then submit the create-team form. This starts an empty team; adding players, assigning coaches and inviting parents are separate steps.

Open the current controls

Open club Settings and the joining/signup settings.

Review and save

Choose every signup switch and completion estimate, then save. Existing custom questions are retained by this guided action.

Check the effect

These settings affect future registrations and automation; saving does not collect a payment or send a message.

Open the current controls

Open club Settings and the field/permission controls.

Review and save

Review every staff permission, parent-editable field and role capability, then save the complete selection.

Check the effect

The saved permission matrix can grant or remove access; no notification is sent now.

Open the current controls

Open club Settings and registration field controls.

Review and save

Choose Visible and Required for each field, then save. Hidden fields cannot remain required.

Check the effect

Future signup forms change; existing registrations remain.

Open the current controls

Open club Settings and Notifications.

Review and save

Choose each notification switch and the email footer, then save.

Check the effect

Future delivery follows these preferences; saving sends nothing immediately.

Open the current controls

Open club Settings and facility booking settings.

Review and save

Choose whether new bookings are approved automatically, then save.

Check the effect

Existing bookings are not changed.

Open the current controls

Open club Settings and pitch-format choices.

Review and save

Select every allowed pitch format for each age band, then save the complete matrix.

Check the effect

Existing bookings remain unchanged.

Open the current controls

Open club Settings and Money pricing rules.

Review and save

Enter the crossover discount, family cap and cap period, then save.

Check the effect

Newly generated invoices use these rules; existing invoices are not rewritten and no charge is collected now.

Open the current controls

Open club Settings and App.

Review and save

Choose on/off for each setting to change and on/off/follow club for each selected squad team, then save.

Check the effect

Unselected settings remain; sport restrictions still apply. Choose each setting or team only once.

Open the current controls

Open club Settings and the Club tab.

Review and save

Enter the club name, contacts, website and colours. Choose whether to preserve or remove the existing logo, then save.

Check the effect

Public club details can change. This guided action does not upload a replacement logo or send a message.

Open the current controls

Open club kit settings and choose the named kit.

Review and save

Change its name, pattern and colours, then save. Leave optional values untouched if no change is needed.

Check the effect

Team assignments remain; invalid colours retain their stored values.

Open the current controls

Open Facilities settings.

Review and confirm

Enter the venue name, address, notes, map coordinates and zoom, then add the venue.

Check the effect

Native blank numeric values become zero; no bookable pitch, booking, invoice or message is created.

Open the current controls

Open Facilities settings and the named venue.

Review and confirm

Enter the surface name and optional type, then add it.

Check the effect

Blank type uses grass; this is a physical surface, not a bookable pitch or booking.

Open the current app controls

Open the club join requests and the named pending requester/team.

Review and confirm

Review the requested role before accepting. The native action creates a current-season team and signup link, grants access, and notifies that one requester by best-effort email and push; it does not reuse an existing team.

Open the current app controls

Open the selected cheer team placement controls and choose an existing club player.

Review and confirm

Choose offered, accepted, reserve or declined and an optional private note. Accepted placement takes a roster place after the native capacity check and makes applicable fee plans relevant; no immediate invoice, charge or message is sent.

Open the current app controls

Open People and select the members to archive.

Review and confirm

Confirm archiving: club-person and linked player rows are archived and active squad memberships deactivated. Accounts and history remain; billing is not cancelled and no message is sent.

Open the current app controls

Open People, select the members, choose Move and select the destination team.

Review and confirm

Confirm the move. Non-player rows are skipped and native capacity applies. A later failure can leave earlier changes saved; team fee-plan relevance may change, without creating invoices or charging now.

Open the current app controls

Open People, select the members, choose Add to team and select the destination.

Review and confirm

Confirm the additional membership, retaining existing teams. Non-player rows are skipped and capacity applies. A later failure can leave earlier changes saved; this does not generate invoices or charge now.

Open the current app controls

Open the team settings and its defaults controls.

Review and confirm

Set meeting minutes, training day/time, reminder hours and team chat, then save the full form. Blank optional values clear defaults; no event or immediate message is created.

Open the current app controls

As club owner, open the team-only dashboard and its full club menu control.

Review and confirm

Confirm the navigation change. Existing data stays in place; it does not buy a subscription or create teams, invitations or messages.

Open the current app controls

Open the club signup-link controls and select the current season team and optional fee plan.

Review and confirm

Set the title, public or invite-only visibility and maximum uses, then create. The link is active immediately without automatic expiry; no player registration, invoice or invitation message is created yet.

Open the current app controls

Open the club signup-link list and choose the named link.

Review and confirm

Activate, pause or archive it and confirm. Pausing or archiving stops new registrations through that link; existing registrations, invoices and family access remain.

Open the current app controls

Open the football club league-registration worklist and select the named active players within your team scope.

Review and confirm

Choose Not submitted, Submitted or Registered and confirm. Moving backwards resets tracking timestamps as appropriate; this changes local tracking only, not an FA submission, membership or message.

Open the current app controls

Open the league-registration worklist and choose the player history controls.

Review and confirm

Enter the private note and save. It is appended with your author and timestamp as an immutable history entry, not a profile replacement or message.

Open the current app controls

Open the league-registration worklist, select the player and choose a field that is currently missing.

Review and confirm

Enter the private value in its date or text control. Existing values are not overwritten. Existing guardian fields update the primary/earliest shared guardian. A missing guardian can be created only with your current verified account contact and name, granting full child access with fee visibility disabled; unrelated or unverified contacts and name-only proof refuse. Earlier native primary effects can remain after a later failure.

Open the current app controls

Open the league-registration worklist and choose a player with both files already on record.

Review and confirm

Confirm swapping the latest photo and identity-document kind labels. The files are not moved or deleted, but shared person surfaces and future ID-pack attachment selection change. No upload or email is performed.

Open the current app controls

As an authorised club administrator, open the league-registration worklist and select up to 200 active players.

Review and confirm

Confirm sending their private names, birth dates, FANs, teams and available latest ID attachments to your current signed-in account email only. Attachment limits can split delivery into multiple emails and partial delivery can precede failure. Optionally mark players submitted after successful sends; this is not a direct FA submission.

Open the guarded developer queue

As the real SUPER_ADMIN account, open Developer > Clubs > Matches (/admin/developer/clubs/matches) and inspect the pending named candidate.

Review and confirm

Confirm Accept only when the raw opponent name and suggested directory club are the same club. This teaches a permanent reviewed alias and relinks currently unlinked fixtures with that raw name; crests and future matching can change. Native multi-stage writes may partially persist, without merging tenants or granting accounts.

Open the guarded developer queue

As the real SUPER_ADMIN account, open Developer > Clubs > Matches (/admin/developer/clubs/matches) and inspect the pending named candidate.

Review and confirm

Choose Reject for different clubs. A persistent match block stops future automatic matching of the pair and resolves the queue candidate; existing linked fixtures are retained. Native multi-stage writes may partially persist; no tenant merge, message or payment.

Open the guarded developer queue

As the real SUPER_ADMIN account, open Developer > Clubs > Claims (/admin/developer/clubs/claims) and review the unreviewed named link.

Review and confirm

Confirm the directory-to-Playlee-club association only when correct. The link becomes verified and an audit is recorded, allowing later joins to use it. Neither club is merged or renamed and no account role is granted; update and audit are separate native stages.

Open the guarded developer queue

As the real SUPER_ADMIN account, open Developer > Clubs > Claims (/admin/developer/clubs/claims) and select the incorrect named association.

Review and confirm

Enter the private reason and confirm Unlink. The directory club becomes claimable again, while the Playlee club retains its name, teams, people and payments. Only the association is deleted; native deletion and audit are separate stages, without granting access or sending messages.

Use Volunteers to add the intended person

Enter first and last name, optional email/phone, descriptive volunteer role and current team. In this bounded flow, Send app invite stays off. Native verified-account identity rules still apply and may refuse unrelated-person capture; never guess identities.

Review the saved-person and role effects

The native writer may reuse/create a person bound to the verified current account, associate them with the club and add a pending volunteer plus selected descriptive role/team staffing. It does not grant app permissions, create guardian links, collect payment or send email/SMS/push. Review a separate saved-contact invitation if access is needed. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Use the volunteer profile Send invite control

Select the existing volunteer, actual permitted access role and required team. Review the exact current saved email/SMS destination privately. Elevated club roles require owner/admin permission; do not type another person's guessed identity.

Review access and delivery before confirming

An already linked account can gain the role and Clubs access immediately and have suspension cleared. Otherwise a never-expiring pending invitation requires native verified acceptance; earlier pending invitations for the same role/team and matching destination are revoked. Other roles remain. Best-effort text/email can fail after earlier effects have saved. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Use Registrations and Send invite

Choose the current club/active season and enter the parent's intended email explicitly. This sends one never-expiring registration link; it does not replace prior pending email invitations.

Confirm the exact email and partial effects

Review the exact destination and season privately before sending. It creates a pending invitation only, not an account, child, guardian link, completed registration or payment. Saved invitations/audit can precede failed delivery; check the original operation before repeating. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Use the native parent SMS invitation controls

Enter the guardian name/phone explicitly, optional player names and a current team within your native scope. The native writer normalizes the phone and may reuse its historical phone/child match; typed names or that match are not verified authority or a new guardian claim.

Review the current text invitation effects

Confirm the exact normalized destination privately. Earlier pending registration links for that phone are revoked and a never-expiring personal link can reserve a team place. One best-effort SMS is attempted; no email, account, new guardian link, completed registration or payment is created. Earlier effects may survive a later failure. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Use the native season renewal invitation controls

Choose an existing previous source season and the current active target season. Review the actual eligible child/primary-guardian recipient list privately; current target-season players and pending target invitations are excluded.

Confirm the complete recipient batch

The native batch is bounded below 200 candidates. One eligible player can produce one email, so a guardian with multiple children may receive multiple emails. No account/guardian grant, completed registration or payment is created. Delivery can be partial; inspect the original result before repeating. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Use Documents and Publish a document

Enter the current title/kind, existing HTTP/HTTPS link and optional summary; explicitly choose acknowledgement/blocking flags and an optional published document to replace. This bounded flow does not upload, fetch or verify the linked contents.

Review current version and family requirements

A new document starts at version 1; replacement publishes the next version and retires the previous published version. Previous acceptances remain historical and the new version can require fresh family acknowledgement. No email/SMS/push or payment occurs. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Open the current family document through its native link or viewer

Choose a published document available to your current account's family club, and read its exact current title/version and content before explicitly confirming acknowledgement. This flow never downloads/signs the document on your behalf.

Confirm exactly what is recorded

The native action records acceptance of this current version for all its account-associated person records and retains identical existing acceptance. It is not a new guardian claim, identity check or child-specific consent; no email/SMS/push or payment occurs. Native changes, delivery and later audit can be separate; reconcile the original operation and current app record before repeating an uncertain result.

Open the current app control

Open the club onboarding registration requirements step as a current owner or administrator.

Review and confirm

Choose explicitly whether player photo, identity document, guardian date of birth and home address are required. Saving makes these four controls visible and preserves other registration settings. These are future collection requirements, not identity verification, uploaded evidence or consent; no invitation, message or payment is created. The review is rechecked before invocation; native changes, communications and audit remain separate and can partly succeed. Check the current app record before another request.

Open the current app control

Open the lightweight team setup/share flow and choose the named current club team and Age group.

Review and confirm

Review the current age label and playing format. The native England Future Fit mapping sets the corresponding format; blank clears both. This does not change minimum or maximum ages, eligibility rules, players, memberships or fixtures. No message or payment occurs. The review is rechecked before invocation; native changes, communications and audit remain separate and can partly succeed. Check the current app record before another request.

Open the current app control

Open Registrations and its pending invitations, then choose Revoke on the named parent/team link.

Review and confirm

Review the current pending link and exact destination in the private confirmation. Revocation stops that link while revoked; native invitations otherwise do not expire. Accepted accounts, family links, children and registrations remain, and earlier messages are not undone. If acceptance wins the native pending-only update race, it is not overwritten. No new message or payment is sent. The review is rechecked before invocation; native changes, communications and audit remain separate and can partly succeed. Check the current app record before another request.

Open the current app control

Open the named volunteer profile and choose Re-send app link for an existing linked, unsuspended account. Suspended recipients use the separate Restore app access control instead.

Review and confirm

Review the current role/team and exact saved SMS and email destinations in your private confirmation. Re-sending creates no account, invitation token, role, team membership or family grant. SMS is best effort, and email or later audit can fail after another channel completes; delivery is not guaranteed and no payment occurs. The review is rechecked before invocation; native changes, communications and audit remain separate and can partly succeed. Check the current app record before another request.

Use the owner committee invitation step

Enter one intended phone and choose club admin, treasurer or safeguarding officer. Review the exact normalized SMS destination privately; this bounded flow does not batch extra destinations or send email.

Confirm pending invitation and access effects

It saves a native never-expiring pending staff invitation and attempts best-effort SMS. Verified acceptance can grant the chosen role and Clubs access; native replacement/rate limits still apply. Earlier invitation/audit effects may survive failed delivery. No child access or payment is created. Native later reads, primary changes, audit and revalidation are separate phases; reconcile the original operation and current app record before repeating an uncertain result.

Use the native own-team setup step

Choose an existing active team and coach/manager role for your current signed-in account. The native shared writer uses current verified account ownership, not another guessed person.

Review membership and access effects

The writer can reuse/create your own person, associate the club and establish staff/volunteer membership, role and Clubs access. Ambiguous identity/contact conflicts can refuse. No guardian relation, invitation, delivery or payment is created. Native later reads, primary changes, audit and revalidation are separate phases; reconcile the original operation and current app record before repeating an uncertain result.

Use the owner money setup step

Explicitly choose skip fees or enter the signup/monthly GBP amounts and payment count. The bounded flow keeps Connect Stripe off; provider setup and editing existing plans remain in the app.

Review which settings actually change

Skipping fees records not collecting through Playlee and retains existing plans/offline controls. Otherwise an existing active plan keeps its amounts unchanged, or native execution creates the shown Membership plan and enables offline payment requests. No assignment, invoice, charge, provider handoff or message occurs here. Native later reads, primary changes, audit and revalidation are separate phases; reconcile the original operation and current app record before repeating an uncertain result.

Find the native control

Open Facilities, then Pitch editor. Choose a saved venue and surface.

Enter and review the intended change

Enter a name, the native pitch format, training/match uses and goal mode. Select existing surface areas, or leave the area selection empty to create a new named area.

Check the effects and result

This bounded flow uses the native centred default rectangle, format dimensions and saved venue coordinates. Edit map geometry in the app. Zone, resource and link writes can be separate; no booking, money or message is created.

Find the native control

Open Facilities, then Pitch editor, and select the saved venue and named pitch.

Enter and review the intended change

Review archiving this resource and clearing its parent and child pitch links. Existing records and booking history remain.

Check the effects and result

The native action refuses upcoming requested or approved bookings. This does not cancel bookings or send messages.

Open the member profile

In the staff area of the Playlee app, open the permitted member profile and its coaching notes. Current team scope applies; admin, finance, safeguarding and other authors' notes are not eligible for this guided change.

Add a coaching note

Choose Add note and enter private staff text. The guided form also accepts new private text only; never put it in chat.

Check the saved notes

Use the native save or delete control, or Do it after the guided review. Coaching notes are private staff records, not family messages. The note write and audit are separate, so a later failure can leave a change saved. No email, SMS, push or payment occurs; inspect the original member before repeating an uncertain request.

Open the member profile

In the staff area of the Playlee app, open the permitted member profile and its coaching notes. Current team scope applies; admin, finance, safeguarding and other authors' notes are not eligible for this guided change.

Edit your own note

Choose Edit on a coaching note you authored. In the guided form, choose the member and your note by creation date, then enter replacement text. Stored bodies are not shown or prefilled.

Check the saved notes

Use the native save or delete control, or Do it after the guided review. Coaching notes are private staff records, not family messages. The note write and audit are separate, so a later failure can leave a change saved. No email, SMS, push or payment occurs; inspect the original member before repeating an uncertain request.

Open the member profile

In the staff area of the Playlee app, open the permitted member profile and its coaching notes. Current team scope applies; admin, finance, safeguarding and other authors' notes are not eligible for this guided change.

Delete your own note

Choose Delete on a coaching note you authored. The guided form identifies your selected note by member and creation date. Deletion is permanent and has no undo.

Check the saved notes

Use the native save or delete control, or Do it after the guided review. Coaching notes are private staff records, not family messages. The note write and audit are separate, so a later failure can leave a change saved. No email, SMS, push or payment occurs; inspect the original member before repeating an uncertain request.

Open the team settings

As a club owner or administrator, open the team settings in the Playlee app and find its logo. Choose Remove for a currently saved team emblem.

Review removing the emblem

The guided action clears only the team's saved logo reference. Other team settings remain unchanged. Displays fall back to the club emblem or initials; the uploaded blob is retained and no new image is uploaded.

Check the team

Choose Do it after reviewing the selected team, then open the team result link. The database change and audit are separate, so an uncertain result needs checking before another attempt. No message, payment or refund is made.

Open the venue in Pitch editor

Open Facilities, Pitch editor and the saved venue. Choose a saved pitch and edit its name, type, Format, allowed training or match uses, and Goals. Layout geometry, coordinates, colours, zones and venue changes remain in the native editor.

Review the complete retained venue

The guided lane retains every saved pitch geometry and other settings, submits the complete venue matrix and lets the native writer recalculate all parent links. Review any parent changes and booking-conflict consequences. Incomplete legacy overlays require the native editor.

Save and inspect the layout

Use Save pitch layout in the native editor, or Do it after the guided review. Existing bookings and linked events are not cancelled. Per-pitch saves and the final audit are separate, so failure can leave a partly updated venue. Open the result link and inspect the original layout before retrying. No map lookup, upload, message or payment is requested.

Open the club wizard

As the club owner, open the native club onboarding wizard and Your season. The native control is Confirm season; it uses the displayed standard season. The generic form also accepts explicit calendar dates supported by the native mobile action.

Choose and review the intended season

Choose your named club and enter the season name and calendar start/end dates. The end must be after the start. If an active season already exists, this action retains it without changing its name or dates. It does not roll a season forward or copy players, teams or fees.

Confirm and check Settings

Choose Do it only after review. Without an existing active season the native action saves the active season and then records its audit separately; an audit failure may leave the season saved. No email, SMS or push is sent. Check the selected club Settings after completion or an uncertain result.

Open Your teams

As the club owner with Clubs access, open Your teams in the native club onboarding wizard. Use the age-band steppers and Create teams. The generic form supports one named age band and a count of 1 to 6 per request; use the app to configure several bands together.

Review derived names and the season

Choose the named club, age band and count. Native names combine the club and age band; multiple teams use native colour suffixes. Football age-band formats or the neutral non-football team format apply. The native selected season may fall back to an inactive season. Names already active anywhere in the club are skipped; archived names do not count as a skip.

Confirm and inspect Teams

Choose Do it after review. Each team is saved and audited separately, so a failure can leave earlier teams saved. Signup links are generated after the response on a best-effort basis and may be unavailable; they can make registration shareable. No players, staff assignments, fees, logo uploads, email, SMS or push are requested. Check Teams and the reported creation count before retrying an uncertain result.

Find the native control

Open club Settings and the season rollover control as an owner or admin. The native reader selects the active season, or its inactive fallback when none is active.

Enter and review the full intended change

Enter the new season name and calendar start/end dates. Review deactivating all existing seasons and creating the new active season and default registration form.

Check effects and the current result

The native action copies source teams including archived teams, active/inactive/trial player rows using shared people and mapped primary-team memberships, and nondeleted fee plans including archived plans plus their components, unassigned. New records use database defaults; source statuses and settings not explicitly copied are not promised preserved. Copied fee plans default to visible in registration, including plans previously hidden. Shared medical information stays linked; old withdrawn players become lapsed only under the current sport policy. Existing season/history remains. No new guardian/account, fee assignment, invoice, payment or notification is created. Separate phases can leave a partially completed rollover.

Open the current app control

Open Facilities and its recurring booking control. Choose a current named pitch or resource, optional team and club kit, training or home match, and explicit Europe/London minute times.

Review and confirm

Review recurrence weekdays, interval and ending calendar date, meet-time lead, goals and clash policy. Native conflicts can block the series or skip dates, and matching existing bookings may be reused, so the eventual new-record count can be lower than the reviewed occurrence count. Visible new events may trigger one events-channel push to the current family accounts; no email, SMS, fee or invoice is made. This bounded lane has no custom exceptions or away matches; those remain in the native app. Native reads, writes, audit and any delivery remain separate and can partly succeed; check the current app record before another request.

Open the current app control

Open Facilities and select the named linked booking to edit. Choose its replacement resource, optional team, title, explicit Europe/London minute times and notes.

Review and confirm

Only this occurrence changes, not the whole recurring series. Its linked schedule event also changes, preserving event kind and shifting its meet time with the start; current parent visibility remains unchanged. Native clash and goal-allocation checks can refuse. No payment or family notification is sent. Native reads, writes, audit and any delivery remain separate and can partly succeed; check the current app record before another request.

Open the current app control

Open Facilities and select the named requested or approved pitch booking. The native picker shows recent/upcoming bookings from seven days ago onward.

Review and confirm

Review whether to release only this occurrence or ALL active bookings in its recurring series. Series removal can include older occurrences outside the displayed window; the review is not a complete historical series count. Bookings become cancelled but linked schedule events remain, so visible events may still appear to families and event cancellation is separate. No fee, refund, email, SMS or push occurs. Native reads, writes, audit and any delivery remain separate and can partly succeed; check the current app record before another request.

Open Import Centre

Open the club Imports screen and find the staged batch card. Owners, administrators, registrars and treasurers with current Clubs access can use Cancel. The native list shows only the latest 12 batches; this guided picker has the same window and does not search older history.

Review what cancellation means

Review the source, creation date, status and current row counts, then choose Cancel. Completed, completed-with-errors and already-cancelled batches are unavailable. Staged files and rows remain, and all people, teams, payments and other records already applied are preserved: cancellation is not an undo.

Check the current batch afterward

While the status remains cancelled, the batch card disables further importing. An import already running does not recheck cancellation and may continue applying rows; its final count refresh can replace the cancelled status. The status write and later audit are separate, so an audit error may leave cancellation saved. No new import, payment, refund, email, SMS or push is requested.

Use the current app controls

Open Teams, Eligibility rulesets, then Add a ruleset. Enter its name/version, authority and source, age basis and bounds, level and squad limits, and optional notes, then save.

Review what happens

This creates a separate version. It is attached to no team and changes no current roster, fee or message. Review the exact reference date and limits rather than assuming a sport rule.

Check the original outcome

Only explicit approval invokes the native action. Current reviewed witnesses are rechecked, but later reads, writes, audits and delivery may remain separate. If the result is uncertain, reconcile the original request rather than creating another operation.

Use the current app controls

Open Teams, Eligibility rulesets. On the named current version, choose Archive and confirm.

Review what happens

Existing team links and history remain, but eligibility checks stop applying the archived rule. Review its current attached-team count. No player removal, payment or message runs.

Check the original outcome

Only explicit approval invokes the native action. Current reviewed witnesses are rechecked, but later reads, writes, audits and delivery may remain separate. If the result is uncertain, reconcile the original request rather than creating another operation.

Use the existing app controls

Open Facilities, Settings, then the physical setup controls. Choose the named surface, enter the zone name and display order, then Add zone.

Review what changes

This creates a physical zone only, not a bookable pitch or booking.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

In Facilities, Settings, Goalpost inventory by venue, choose the venue and enter the goal size, number of pairs and compatible pitch formats. Save the inventory.

Review what changes

This replaces and reactivates the same-size inventory. No compatible formats selected means all pitch formats; it does not alter existing bookings.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Settings, Goalpost inventory by venue. Select the venue and save whether shared-goal tracking is enabled.

Review what changes

Future native bookings use the tracking policy. Saved inventory and existing bookings remain.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

In Facilities, Settings, Venue booking policy, choose the venue and save Block unless explicitly available on or off.

Review what changes

Explicit-window mode blocks future requests outside configured windows. Existing bookings are not cancelled.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Settings, Goalpost inventory by venue. Choose unallocated goal pairs and the destination venue, then assign them.

Review what changes

Matching goal-size venue inventory is merged and the unallocated source consumed. Compatible formats combine; either all-formats inventory keeps all formats.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Settings, physical setup, Add bookable pitch. Choose its surface, type, physical zones, permitted uses, goal mode and optional parent. Enter its name, display format and rectangular overlay, then Add pitch.

Review what changes

No allowed uses selected means training and match; blank display format uses the resource type. Resource creation and zone links are separate writes, so failure can leave partial setup. This does not create a booking.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Settings, Recommended quick setup. Enter the venue and main surface names, location details and map zoom, then Create pitch template.

Review what changes

This creates the venue, grass surface, two half-pitch zones and 11v11, 7v7 and 5v5 resources and links. Blank numeric values become 0, with no inferred location. Native multi-stage setup can remain partly saved if a later step fails. Support does not run location search.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Availability. Choose the venue and pitch, start and end clocks, start date, repeat-until date, weekly or monthly recurrence and interval. Choose weekdays for a weekly pattern, then Add availability window.

Review what changes

Native facility clocks and calendar recurrence remain unchanged. Support adds no exception dates; add those in the app. This opens booking windows rather than creating bookings or events.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Availability. Choose the venue, find the named pitch window with its date and clock range, then Remove window.

Review what changes

Future booking checks stop using that active window. Existing bookings are not cancelled.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.

Use the existing app controls

Open Facilities, Maintenance and blackouts. Choose the venue, optionally a pitch, enter the reason and start/end date and time, then add the blackout.

Review what changes

A chosen pitch takes precedence over the whole venue. This blocks future bookings without cancelling existing ones. Support uses the native Facilities calendar zone, Europe/London (currently one shared zone), for human time controls.

Check the saved state

Use the current authorised named selection. Native writes and later audit steps may be separate, so a later failure can leave a saved primary change. No automatic booking, provider lookup or message is added by Support.