Skip to content

First-run setup

Activation creates the plugin's tables and two public pages, Join us (/join-us/) and My account (/account/), then takes you to Club Management → Setup. Setup walks you through the club's name, its squads and its members, and then lists the remaining tasks (email, a season, payments) with a Done / To do badge each. You can come back to it at any time.

This page covers the same ground in the order that works best, and explains why. The order is not arbitrary. Email has to work before you send a season's approval links; squads have to exist before an import can put anyone in one; the season has to exist before you can register anybody for it. Doing these in a different order mostly means doing them twice.

Allow an hour for the whole run, plus however long the club takes to decide its fees.


1. Decide who gets in

Club Management → Settings → Club Admins

Any WordPress administrator is already a club admin. Add anyone else who needs the full plugin — they must have a WordPress account first; this screen grants access to an existing account, it does not create one.

Squad secretaries are not added here. They are set per squad, in step 4.

Who can see what · Club Admins

2. Make email work

Club Management → Email Settings → Sending

This is the step most worth getting right first, because almost everything the plugin does ends in an email.

  1. Check how mail leaves the site. Club Management sends through WordPress's own mail, so it uses whatever the site already has. For HTTPS sending that survives a host blocking SMTP, activate the Club Mailer plugin and choose Elastic Email under Settings → Club Mailer → Site-wide sending; the Sending tab then says Sending through Elastic Email and links there.
  2. Set From Email to an address your provider will genuinely send as, and From Name to the club's name. Nothing sends until From Email is set.
  3. Turn on Logging only mode while you are still setting up. Every email is recorded but redirected to one test address, so a misconfigured season cannot mail three hundred parents.
  4. Save, then use Send test email. Save first — the test uses the stored settings, not what is on screen.

If you chose Elastic Email, paste the delivery feedback webhook URL shown on Club Mailer's settings screen into Elastic Email under Settings → Notifications, and enable all six notification types (Bounce/Error, Complaints, Unsubscribed, Sent, Opened, Clicked). Bounces then show up in the email log and as an Undelivered warning against the season registration rows they affect — which is how you find the parent whose address is wrong before you conclude they are ignoring you.

Turn logging-only mode off before the real send

It is the single easiest thing to forget. The Email Log will happily show a full season's worth of approval emails as sent-but-logged while no parent has received one.

Sending · Email Log

3. Read the emails and switch them on

Club Management → Email Settings → Emails

Twenty emails go out on their own — waiting-list notifications, sign-in links, photography permission, the season approval request, the season confirmation, payment reminders, the Direct Debit mandate email, the club's own alerts and six payment updates for parents. They ship with sensible wording that is not your club's wording.

Every email starts off, and nothing is sent until you switch it on. Open each one, read it in the club's voice, edit it, and switch it on with Send this email. The Emails tab lists them in tables with who each goes to and whether it is on, with a switch on each row to turn it on or off straight from the list, and counts how many are still off; each email's page has the placeholders it accepts beside the form.

Switch on at least the ones the site cannot work without: the account sign-in link (parents cannot sign in otherwise), the season registration request, and the Direct Debit mandate email for the environment you use. Two of them also need an address before they can send: the no suitable squad alert and the registration paid alert.

Email Settings

4. Create the season and the squads

Club Management → Seasons, then Club Management → Squads

Create the season first and set it active — an active season is what the registration form, the payments screens and most of the reporting assume.

Then create a squad per date-of-birth cohort. For each one set:

  • the date-of-birth range it covers, which is what matches waiting-list sign-ups to a squad and decides which members the plugin suggests for it (an import never places anyone by date of birth);
  • the squad type (Mixed or Girls);
  • the squad secretary email — the WordPress account with that address gains access to that squad and nothing else.

If a squad's fees differ from the club default, you can leave that until step 7.

Creating a season · The active season · Date-of-birth ranges · Squad secretary

5. Get the members in

Members → Import Members

Several ways in, and most clubs use more than one eventually:

  • Import the club's own spreadsheet — the bulk route. On Members → Import Members, select Download Template, fill in one row per member with up to two parents or carers and the member's squad, and upload it. Squads come from the Squad column only, never from a date of birth; a row with a blank or unknown squad imports the member without one. Uploading the same sheet again updates members rather than adding them twice.
  • Import the FA Club Player Report — needs English FA. Export the report from Whole Game System and upload it on English FA → Import Players. Members are matched on FA Number, so a re-import updates rather than duplicates. This import does not put anyone in a squad.
  • The waiting list — a public sign-up converts into a member in one click.
  • By hand — Members → Add Member, for the child who turns up mid-season. Squad secretaries can do this for their own squads.

After an import, look at two screens before going further. Club Management → Actions lists every member who still needs a squad ("Put … in a squad"), and Members → Find Duplicates lists likely duplicate records. Merging two records is easy now and unpleasant after they have separate payment histories.

Importing members · When the import can't be sure · Find Duplicates · Merging

6. Check the guardians

Members → Guardians

An import creates guardians from the parent and carer details it was given. Two things are worth a pass now:

  • Email addresses, because they are what every approval and payment link travels down.
  • The payment contact, where a child has more than one guardian — it decides who gets a Direct Debit setup link the club sends. A guardian who sets the payment up themselves from the registration page pays as themselves, whoever is flagged.

Guardians · The payment contact

7. Set up payments (optional)

Payments → Settings, then Payments → Products

Skip this whole step if the club takes money some other way — you can still record offline payments against a member.

  1. Connect GoCardless and confirm the connection from the settings screen. Start in sandbox.
  2. Give GoCardless the webhook URL the settings page shows. Without it the plugin never hears that a payment cleared, and every member sits at Awaiting bank forever.
  3. Create the products: the registration fee, and anything else the club charges for. A product carries its own registration amount and instalment plan.
  4. For a monthly sub, set the product's Pricing to A monthly sub, counted from each member’s registration date — give it the monthly amount, the collection day and the date the subs run to, and each member's number of payments is worked out from when the club took them on. Missed months decides what happens when a parent sets the Direct Debit up after the first collection day has gone.
  5. To charge each member their season cost (the season's registration fee plus their subs, set on the season's Season cost card), set the Registration product's Pricing to Each member’s season cost. The fee is taken up front and the subs monthly, pro rata for late joiners. Months already gone by when the parent sets up are added to the up-front payment, and parents can choose to pay the whole cost at once on the registration page. The collection day and last collection date are always read from the season, so a change there applies to everyone set up afterwards.
  6. Where one squad pays something different, add a squad override rather than a second product.

Move to live credentials only once a sandbox run has been through a full setup and confirmation.

Products · One squad paying something different · Configuration

8. Build the public pages

Two pages already exist, because the plugin created them on activation:

Page What it is for
Join us (/join-us/) Public sign-up; lands on the waiting list
My account (/account/) Where parents sign in, with an emailed link or a passkey, to see their children and their registration and payment status

You can write whatever you like on either page; the plugin adds its form underneath.

The season registration page is the one to set up yourself. Choose one of these:

  • Let the plugin create it. Switch on Season and squad pages on Club Management → Settings. Each season then gets a page of its own at /season/…, with the registration form added automatically. There is no shortcode to place.
  • Use a page of your own. Create a page containing [cpm_registration_form], then choose it as the season's Registration page on Club Management → Seasons → the season.

Optionally, add a page containing [cpm_registration_request] for parents who have lost their link. The registration page already falls back to that form when someone arrives without a valid link.

Visit each page signed out, which is how a parent will see them.

Public pages · Shortcode reference

9. Send the season's approval emails

Club Management → Seasons → the season

Now the order pays off. Each parent gets one private link covering all of their children, and the season page tracks who has confirmed, declined or not answered.

Before the real send: turn logging-only mode off (step 2), and send yourself one first if the plugin's own test send has not already convinced you.

Getting parents to confirm · The five statuses

10. Then it is a weekly rhythm

Once a season is running, the recurring work is small and lives on three screens:

  • Waiting list — convert new sign-ups, and check nothing has sat pending for a fortnight.
  • Payments → Not Set Up — who has not set up, and chasing the setup links nobody used.
  • Email Log — anything that bounced, which is usually a typo in an address.

Who has not set up · Chasing up setup links nobody used · Working through the list


Setup checklist

  • Club admins added
  • From Email and From Name set; Club Mailer set up if sending through Elastic Email
  • Test email received
  • Delivery feedback webhook configured (Elastic Email only)
  • Automatic emails read and reworded
  • Season created and set active
  • Squads created with date-of-birth ranges, types and squad secretaries
  • Members imported; members without a squad placed, and duplicates cleared
  • Guardian emails and payment contacts checked
  • GoCardless connected and webhook delivering (if using payments)
  • Payment products and any squad overrides created
  • Season registration page set up, and every public page viewed signed out
  • Logging-only mode turned off
  • Season approval emails sent

Once the club is running, the User guide covers every screen in detail, and squad secretaries have a shorter guide of their own.