Creating and Managing a Training

Trainings are scheduled coaching sessions that players browse and register for through the PadelOS player app. As a club, you publish a training with a defined schedule, and players sign up and pay to secure their spot.

A training is the container. Inside it sit one or more sessions — the individual classes that actually take place. A training with a single session is a one-off class. A training with many sessions is a programme or course. How players pay for those sessions is something you control separately through the pricing options.

Creating a training happens in two distinct stages:

This two-stage approach means you're not locked into one date range or one recurring pattern. You build up your schedule piece by piece into a single collection of sessions, then review the whole thing before making it live.

Select which club this training belongs to.

Sport: Select the sport this training is for.

Club Page Visibility: Controls whether the training is publicly visible on the club page.

Name: The name of the training.

Description: A description of the training, shown to players. Supports rich text formatting.

Labels: An internal tagging system used for your club's own reporting — not shown to players.

Gender: Restrict the training to a specific gender if needed.

Set the overall Start Date and End Date for the training.

These dates serve two purposes: they show players when the training programme runs, and they're used for pricing and billing — particularly for the monthly and custom billing period options set in the next step.

They do not by themselves generate any sessions. Actual sessions are added separately in Stage 2.

These dates adjust automatically. Once you start adding sessions, PadelOS keeps the training's overall dates in sync with the actual schedule. The training's start date always reflects the first session in the list, and the end date always reflects the last session. So if you add sessions that fall outside the range you originally entered, the training's dates are updated automatically to cover them — you don't need to go back and correct them manually.

First, choose between Individual or Group registration.

Individual Players register and pay one at a time.

Group Players register in fixed-size groups rather than individually. You set how many groups can sign up, and how many people per group.

The example used throughout this section: a training called "Winter Improvers," running 1 January to 31 May, with 20 sessions — every Wednesday at 6 PM, roughly four sessions per month.

There are two price fields, and you can fill in one or both depending on what you want to offer:

You then decide whether players are allowed to buy individual sessions, or must commit to the full programme. That choice determines which payment options are available to them.

This applies when you allow players to purchase sessions one at a time rather than committing to the whole programme.

A player can buy any session that is still available and hasn't already started. They aren't required to take the full set, and they aren't restricted to a consecutive block — they can pick whichever sessions suit them.

Each session is charged at the Price Per Session you set. In our example, a player who wants to attend just four of the 20 Winter Improvers sessions pays €25 per session, so €100 in total.

This option suits drop-in style classes, or programmes where you want to give players flexibility rather than requiring a full commitment.

The player pays the full programme price in a single transaction at the point of registration.

In our example, a player registering for Winter Improvers pays €400 immediately, covering all 20 sessions from January through May. There is nothing further to collect — the programme is paid in full from day one.

This is the simplest option to administer, and works well for shorter programmes or where you'd rather secure the full commitment upfront.

Rather than paying everything at once, the player is charged once per month across the life of the programme. The number of monthly charges is determined by the training's overall start and end dates.

In our example, Winter Improvers runs from 1 January to 31 May — five calendar months. So the total price is spread across five monthly charges of €80.

The player is charged at the start of each month for that month's sessions:

If a player registers in December, ahead of the programme starting, their billing simply begins on 1 January and continues monthly from there.

Monthly billing works well for longer programmes where asking for the full amount upfront would be a barrier to signing up.

Custom billing gives you full control over how the cost is broken up. Instead of being tied to fixed monthly increments, you define your own billing windows and set a different price for each one.

This is useful when the programme isn't evenly weighted across its duration, or when you want to structure pricing around blocks rather than months.

Example — two blocks at different rates

Using Winter Improvers, you might split the programme into two billing periods:

The player is charged €160 at the start of January, then €240 at the start of March. Two charges in total, rather than five.

Example — month-by-month with varying prices

You can also define monthly windows but charge different amounts for each, which is useful when session frequency or content changes as the programme progresses — for instance, if the later months include more sessions or additional coaching.

The key difference from standard monthly billing is that you decide both the length of each period and its price, rather than the system dividing the total evenly across calendar months.

Open Registration: How many days before the start date registration opens to players.

Close Registration: How many days before the start date registration closes.

Both settings use the training's own start time as their reference point, not midnight. So if a training starts at 6 PM and Open Registration is set to 1 month before, registration opens at 6 PM one month prior. Likewise, if Close Registration is set to 3 days before, registration closes at 6 PM three days before.

Important: When registration closes, the system checks whether the Minimum Participants set in Step 5 has been met. If the minimum hasn't been reached, the training is automatically cancelled and any players who already registered and paid are automatically refunded.

Allow Player to Add Guests: When enabled, participants can register with guests according to your guest settings and pricing.

Show Participants on Coaching Public Page: When enabled, registered participants are displayed publicly on the training's page.

Add Users in Waiting List: When enabled, players can join a waiting list once the training reaches its maximum participant limit.

Show Waiting List on Coaching Public Page: When enabled, players on the waiting list are shown publicly on the training's page.

Internal Notes: Notes visible only to your club's admin team — not shown to players.

Gallery: Upload images to display alongside the training.

Attachments: Upload PDF documents related to the training (e.g. a class syllabus or waiver).

Save the training to move on to building its schedule. At this point the training exists but has no sessions and is not yet live.

With the training saved, you now add the sessions that make it up. Sessions are added in batches, and each batch can have its own combination of trainer, court, and dates.

When you add sessions, you specify:

PadelOS then generates the matching sessions and adds them to the training's session list.

You don't have to do this all at once. After adding one batch, you can go back and add another with a completely different combination.

Example: You might add a weekly Tuesday evening batch on Court 1 with one trainer, then add a second batch of Saturday morning sessions on Court 3 with a different trainer. Both batches sit inside the same training, forming one combined schedule.

This is the main advantage of the batch approach: a single training can hold sessions across different trainers, courts, days, and time patterns, rather than being restricted to one uniform recurring series.

As sessions are generated, PadelOS checks each one against trainer availability and court availability. Any session that clashes with either is flagged as a conflict.

When conflicts appear, you can either:

If you save with conflicts present, the training stays in Draft — it is not published or visible to players. Sessions without conflicts are saved normally; conflicted sessions are saved too, but flagged for your attention.

While in Draft, you can edit individual sessions one at a time. For example, if one session in a series needs to move from its usual 9–10 AM slot to 11 AM–12 PM on a particular day, you can change just that session without affecting the rest. You can also add or remove individual sessions from the schedule.

Once you're satisfied with the full session list and any conflicts have been resolved or accepted, publish the training to make it visible and bookable for players.

Once a training is published and players start joining, two tabs become available at the top of the training: a Players tab, showing all player activity for that training, and a Chat tab, which opens the group chat automatically created for everyone who's joined — accessible from there just like any other message thread.

For an explanation of when to use a single session, a multi-session package, or bulk creation, see the Trainings: Single Session vs. Multi-Session vs. Bulk Creation article.