A "session" is a single bout of training composed of one or more workouts. You might generally think of it as a one or two hour training block where the athlete begins a session with a warm-up, practices some aspect of training, then ends with a cool-down.

The concept of sessions is used on the calendar and in programs. The format is slightly different in the two locations, but the attributes are essentially the same.


The form below shows the standard attributes of a session in the sessions database. When managing a session on the calendar, there are a few more attributes related to the session's timing (date, start time, end time, etc.)


The session name is pretty self-explanatory. You generally want to give it a succinct, but descriptive name that informs people what the session is about. For sessions in the database (explained below), you'll want to give it a unique name that makes it easy to distinguish from other sessions in the database.

The name appears in various contexts, including in the calendar, in the program interface, and in the mobile app where athletes will be following the session.


The session type determines which exercise attribute is used when sorting athletes on the whiteboard. For example, if you want athletes to be sorted by the amount of weight they can lift, then the type would be "Weight." If you want athletes to be sorted by their speed, then the type would be "Speed." (See the Calendar guide for info on the whiteboard.)


Assigning a session to a facility enables FYTT to automatically group athletes into stations within the facility. If you have tablets setup at each station, the tablets will automatically be populated with the appropriate athletes' workouts for the session when you start a session from the whiteboard. (See the Facilities guide for info.)


The description attribute allows you to provide more long-form information about the session. So if you have additional instructions or notes that people need to know about, use this attribute to communicate that info.

Session attributes on the mobile app:


The session's workouts are where you define the actual work do be done in the session. When building a session, you can either create a new workout from scratch, or you can quickly add a workout that you've previously created in your workout database (see the Workouts guide for more info).

As a best practice, try to keep individual workouts small and concise. This generally leads to a better user experience for both coaches and athletes, because it's easier to manage and consume information in small chunks. For example, if your session calls for 3 sets of 5 @ 65% for bench press, back squat, and hang clean, then separate out those three exercises into their own workouts.


You can create a database of session "templates" that can be inserted into any program or session on the calendar. The Sessions database can be found in the main menu. Once you've created sessions in the database, you can quickly insert them into a program or onto the calendar.

You can create sessions at the institution level, which are accessible to all teams at the institution. If a team. has its own "private database," you can also create sessions at the team level, which are only accessible to that team (see the Institutions guide for more info).


To insert a session into a program, simply click on the day you want to modify, then use the search form to search for and select the desired session from the database.

Note that the search form also allows you to search and add individual workouts from the database. Sessions in the search results are distinguished by the session icon next to the session's name.


Once you've added a blank session to the calendar, you can insert a session from the database (see the Calendar guide to learn about adding blank sessions). To do this, click on the "New Workout" button in the "Session Workouts" section. From the dropdown, select the "From session" option. This brings up a search field where you can search and select sessions from your database.

Note: Inserting a session in both cases illustrated above overwrites any session attributes that might be present on the existing session (name, description, facility, etc.).

Did this answer your question?