Skip to content

Glossary

The heaviest load a player can lift once on an exercise. Personal and tracked over time, it’s the reference for prescribing strength in percentages: the same % gives a different actual weight for each player. Entered directly or estimated from a submaximal set (Epley/Brzycki). See Strength & 1RM.

The ratio of a player’s recent load to their habitual load: load over the last 7 days ÷ (load over the last 28 days ÷ 4). Around 1, the player is absorbing what they are used to; above the balance zone (0.8 to 1.3), overload risk. Always measured, never estimated. Feeds the readiness colour. See Readiness and Training load.

Three per-player season metrics: attendance (trainings / matches), program completion and check-in response rate (30d). Computed from data already collected, shown on the player profile, the dashboard and the weekly report. Excused absences (a reason or an injury) and cancelled events are excluded from the calculation. See Adherence.

The calculation applied to a metric over a question’s period: Total over the period, Average over the period, Latest known value, Minimum over the period, Maximum over the period or Per 90 minutes. It is chosen under How is this figure calculated? — a metric name does not carry its calculation. Only the calculations that make sense for the metric are offered (Per 90 minutes only on match and playing-time metrics, no Total on a rate or a ratio). See Reports.

AI-generated synthesis built from an opponent’s observations: a playing-style summary, strengths (to contain), weaknesses (to exploit), likely formation and a suggested plan. A proposal to review — the coach accepts, edits or dismisses it. See Scouting opponents.

The text the AI writes in a presentation, from the figures it contains alone. It carries this badge until you touch it up (it becomes Edited); To review flags a text written under another context or one that quotes figures not all the staff can read. See The presentation editor.

Player manually removed from the active squad (status Inactive): they drop out of call-ups, fines and the availability board, but all their history (check-ins, injuries, load) is preserved. Reversible via Reactivate. Not to be confused with Remove from team, which permanently erases all personal data (GDPR). See Manage the roster.

A made-to-measure page the assistant builds in the background when a canvas can’t draw the request: a free layout, linked views, picking a match or a player, pitch and goal crossed. It draws only the figures read in the conversation, copied and dated at build time, like a Snapshot widget: it doesn’t update on its own, but Regenerate, on a dashboard, rebuilds it with today’s data. Until you save it to a dashboard, no one else sees it. See Have a page built.

The time step of an Evolution: Per match, Per week or Per month. It must be at least as wide as the measurement — a daily metric such as fatigue cannot be shown Per match. See Reports.

The 12 columns by 9 rows of a presentation page. A block takes up a rectangle of cells, snaps to them when moved, and can never cover another one. See The presentation editor.

A presentation whose context is an opponent: its blocks (notes, boards, clips, squad, analysis, results) re-read the opponent’s scouting file at every display. See Opponent presentation.

What a question shows: subjects compared with each other, an evolution over time, or a distribution (each subject’s share of the total). It follows from the chosen Display — Lines or Stacked area for an evolution, Donut or 100% stacked bar for a distribution. See Reports.

A player training with the group for a defined period before the club decides to sign them. Badged Trial, called up and rated like an active player, but excluded from team statistics and limited to the agenda on the portal (up to the expected trial end date). Closed with Sign, Don’t sign (report required) or Extend. See Trial players.

Player × day grid view that summarises check-in responses for the current week. See Well-being check-in.

Attendance request sent to one or more players for an event. Response statuses are: present, absent, limited, uncertain, pending. See Call-ups (RSVP).

Protocol that lets you plug your own AI (Claude, ChatGPT…) into strivn. Enabled team by team in Settings › AI coach › External AI access. See Connect your AI.

An exercise metric is no longer typed in: every GPS import adds that session’s value to the exercise’s history, and the weighted average of that history becomes its value. What the staff types is only a seed, useful before the first session and kept under the measurement. The number stays calibrating until 3 sessions, then turns confirmed — the same vocabulary as the felt RPE. The “calibrated on 4 sessions” line opens and shows the sessions behind the number. See Exercise metrics.

What a session should produce in distance, sprints or accelerations, computed before the session from the key metrics of the exercises on the timeline. Always shown with its coverage rate, because a timeline holds blocks with no exercise. Indicative only — it feeds no load calculation. See Exercise metrics.

A plan block saved as a reusable model (Save as block template). Personal to the coach, it follows them from one team to another and drops back in from the plan’s library, under My block templates. See Live session.

A player’s card total brought back to 90 minutes of play, computed on their minutes in recorded matches only. The column stays ”—” until they reach 180 minutes — the Players tab’s floor — and the hover gives the reason. See Cards.

A plan structure where groups rotate through several stations, with a number of turns and a turn length. Live, the bell rings the rotations, the dial shows the current turn and the Who goes where table follows the groups from station to station. See Live session.

A conversation in team messaging: the Team channel (staff, players, parents of minors), the Staff channel, one channel per event (opened at the first call-up, archived after the event) or a private conversation.

Short well-being questionnaire filled in by the player each morning before the session: fatigue, sleep, stress, and depending on team configuration other indicators. Main input of the performance loop. See Well-being check-in and Do your check-in.

A strength-workout block where exercises chain in rounds: set 1 of each station, then set 2, with no rest between stations. Rest lands at the end of the round. See Strength & 1RM.

A video attached to an opponent’s scouting material: either a link (YouTube, Vimeo, Veo, Hudl…) or an uploaded file (up to 250 MB, mp4/mov). Reusable in a report like a note or a photo: YouTube and Vimeo play in the page, Veo/Hudl links open in the source platform. See Scouting reports.

What a presentation is about: a match, a period, a player, or a player over a period. Data blocks that follow the context are computed on it; a relative period is frozen into dates. See Presentations.

A page you compose yourself in Analytics › Dashboards — several views (KPIs, charts, tables, notes) — that replays on current data every time it is opened. It is created from a sentence, a role-based template or a saved question, and can be shared, pinned to the home page and sent every week. Not to be confused with the home dashboard, which ships with STRIVN, nor with tactical boards. See Dashboards.

The Period, Players and Position that every view of a dashboard looks at, all at once. Save as default filters makes them the lens everyone opens the dashboard under, and the one its sends and public link use. A view can keep its own period or its own players. See Dashboards.

The gap between a player’s external (GPS) load and internal (sRPE) load: when the external ÷ internal ratio drops well below its 28-day base, the player is doing less mechanical work for the same perceived effort — a sign of hidden fatigue. Shown in the GPS tab.

The shapes placed on a presentation page — rectangle, banner, line, arrow, pictogram —, in the club’s colours only, behind or in front of the content. Thirty elements at most per page. See The presentation editor.

A file (PDF, image or Office document) uploaded by staff and shared with the whole team or a selection of players, who read it in the portal’s Documents tab. Distinct from a file attached to a program. Staff track the first open per player (Seen / Not seen), with the Unreachable and Out of reach markers. See Documents.

A message strivn prepares from your data (match closed, coming week, test results) and that waits for your approval in strivn drafts before it goes out. It expires after 14 days. See Team messaging.

Space where the coach gathers training exercises: links (TikTok, X, Instagram, Facebook), photos, videos, tactical diagrams and text notes. Each exercise can be filed (private) or published (shared with the team), organised into folders and tags, then attached to a session on the calendar. See Exercise library.

The goal split into nine zones inside the frame (top, middle, bottom, each left, centre or right) and three outside (wide left, over the bar, wide right). It always reads seen by the shooter: their left is on the left. A goal or a shot is placed there live or in the goal review. See Pitch (Statistics).

Queue of exercise captures (links, photos, videos) not yet sorted. Nothing there is visible to the team until the coach files or publishes it. See Exercise library.

Total weekly load × monotony: combines volume and lack of load variation. High strain is a fatigue signal worth watching, especially combined with an ACWR outside the optimal zone. See Training load.

A link (/b/… for a dashboard, /q/… for a saved question) that shows the dashboard or the question read-only, on the day’s data, without a STRIVN account. It expires after 7 days, 30 days or never, is revoked in one click, excludes medical and wellness views by default, and can replace names with initials. The figures are computed with the access rights of the coach who shares it. See Sharing a dashboard.

An unguessable address that opens an exercise from the library with no account and no sign-in — meant for your staff or a colleague outside strivn. The link itself is the key: disabling it makes every copy already sent unreachable. The page shows the media, the description, the tags and the declared metrics; never the observed values, nor how many sessions used the exercise. See Exercise library.

A value describing what an exercise produces: distance, sprints, target RPE, players, area. Set by the staff on the exercise itself, anchored to a reference duration. Cumulative metrics (distance, sprints) scale with the block’s duration; intensive metrics (RPE, players, area) stay unchanged. See Exercise metrics.

The unit internal load is displayed in. By default the AU (arbitrary unit): a 90-minute session at RPE 7 weighs 630 AU. A staff can declare its own unit, defined as a fixed multiple of the AU (for example 1 CU = 108 AU), to bring load onto a scale close to RPE. Every load screen and every input then switches to it; the data stays stored in AU. Ratios (ACWR, monotony) keep their scale, strain follows the unit. See Training load.

A match’s presentation — overview, standout performances, player statistics, conclusion. Created on its own when the GPS import is validated, from the designated template (Automatic badge, shared with the staff), or on demand from the match page or the Match report example template. See Presentations.

How uniform a player’s training load was over a week: average daily load ÷ daily standard deviation. High monotony means very similar loads day to day (little relative rest), which raises injury risk at the same total load. Always measured, never estimated. See Training load.

Intermediate RSVP status: the player will be present but with a restriction (minor injury, reduced load). Different from present (full participation) and absent. See Call-ups (RSVP).

Overview of an opposing team: roster and players to watch, observations, tactical boards, photos and AI tactical analysis, aggregated from scouting sessions. The starting point for a game report. See Scouting opponents.

A dated block inside a season — pre-season, competition, break, taper… — with a weekly target and a template week. Cycles cannot overlap and must stay within the season dates. Every new planner week inherits its cycle (a copy, never a live link). See Season & cycles.

A tab of the Statistics page, between Goals and Players, that shows across the selected matches where placed actions happen on the pitch and where shots end up in the goal. The two views are crossed: a zone picked on the pitch keeps in the goal only the shots that left from there, and a zone picked in the goal keeps on the pitch only the actions that ended there. It reads the positions recorded during the live match and in the goal review, counts only reviewed goals, and states its coverage at the top (“34 actions placed out of 51 recorded”). The goal reads as the shooter sees it. See Pitch.

A document of 16:9 pages in the club’s colours — figures, tables, charts, photos, tactical boards, videos, texts and decor — computed on a context. Private when created, shared with the staff when you ask, projected full screen, exported as PDF or sent by public link. See Presentations.

A reusable layout — pages, blocks, settings, decor — saved by the staff (Team template) or provided by strivn (strivn example template: Individual review, Training week, Match report). It remembers the type of context it expects, never its value, nor the texts. See Presentation templates.

An option on a messaging message: each member confirms by tapping I’ve read it. The staff see Seen and Confirmed under the message, and can Nudge those who haven’t (once every 24 hours).

Each player’s readiness for the day, classed green / yellow / red. It always starts from a real check-in (a measured state); between check-ins, STRIVN doesn’t let it go stale — the model projects fatigue forward day by day from the last check-in, driven by training load (each session or match pushes it up, rest brings it down). Only fatigue is estimated — load and ACWR are always measured. An estimate carries a confidence (0–100%) that drops the older the last check-in gets, or when sessions ran without their load (RPE, duration) logged; below the threshold the player moves to “To re-check” (no hard colour, excluded from at-risk counts). With no usable check-in at all, the state is unknown. Shown on the player’s dashboard and the staff Readiness screen (measured states marked as such, estimates marked “Estimated · X%”).

A match carrying a finished live run or a match sheet — the only kind discipline is counted on. A match with neither shows ”—”, never 0, and drops out of the denominator of “cards per match”. The line “x matches recorded out of y” states that coverage above every average. See Cards.

The basic unit of scouting: a piece of analysis text (typed or dictated) with a tactical board, video clips and photos attached, linked to an opposing player and to tactical tags. See Scouting opponents.

Aggregated indicator (red / green) that synthesises a player’s well-being and load to draw staff attention. Red = risk, green = good state. See Dashboard & signals.

The duration an exercise’s key metrics are measured over. Required as soon as a metric is set: “1,200 m” means nothing without it, “1,200 m over 15 min” scales to any block length. See Exercise metrics.

All the players in a team, with their position, status (active / inactive) and contact details. Accessible from the Roster menu.

A 1–10 scale of the perceived intensity of a session. Entered by the coach in the session review, and by players in their post-session check-in or via a direct request after the session. Cross-referenced in session results. On the coach side, the team can enable decimal RPE (Settings → General) to enter two decimals (4.17) instead of a whole number; that precision is kept in the sRPE load calculation. The players’ RPE stays a whole number. See Session review.

The average of the RPE the players gave an exercise, block by block, across the collective sessions where it ran in the team — not to be confused with the target RPE the staff declares on the exercise page, nor with the RPE planned on a session block. Answers outside the exercise’s P10–P90 are excluded above 10 answers. The figure stays calibrating until 3 sessions with at least 2 answers each on median, then turns confirmed. Indicative: no load calculation reads it. Shown on the exercise page and on its card in the library.

A question from Explore a question kept under a name, listed under Saved questions (Automatic reports page). Opening it re-runs the question on current data — the numbers are never frozen. It can be added to a dashboard (as a copy) or shared through a public link. See Reports.

A dashboard’s weekly send, on the chosen day and time (team local time), to the designated staff members, by Email with PDF and/or Notification. Each recipient receives the dashboard computed with their own access rights. Never by WhatsApp. See Dashboards.

Game-specific document composed from an opponent’s dossier material (notes, tactical boards, photos), attached to one or more games and shared with players and staff. Stays a private draft until shared; on the player side it’s read-only and only visible to a recipient who’s called up to the game. See Scouting reports and View a scouting report.

A dated moment of observation (a live game, a video, some research) that all material collected on an opponent attaches to: rich notes, boards, clips, photos and match paper. See Scouting opponents.

The team’s reference period (name, start date, end date), set in the settings. “Season” views anchor to it. You close it to start a new one: the old season is archived read-only, nothing is deleted. It carries the periodization cycles. See Season & cycles.

The convention of every goal drawn in STRIVN: the goal as the shooter sees it, their left on the left, for your goals and for conceded goals alike. It applies in the live match console, in the goal review, in the In the goal block of the statistics and in the Pitch tab. To read your goalkeeper, mirror it: the shooter’s top left is your keeper’s top right. See Goal review and Pitch.

List page showing past sessions with their session review status and player response rates. Accessible from the Session results menu. See Session review.

Report filled in by the coach after a training session or match: perceived RPE, actual duration, session rating, free notes. Cross-referenced with player feedback — given at the next day’s check-in, or sooner if Ask for feedback after the session was enabled when creating the event. See Session review and Calendar & events.

Aggregated well-being indicators (fatigue, sleep, stress, pain, motivation) from player check-ins. Accessible from the Signals menu. See Well-being check-in.

Counter of consecutive check-ins by a player. Displayed in their personal dashboard to encourage consistency.

A block of two or three alternated exercises in a strength workout: the player does set 1 of each, then set 2, with no rest between exercises. The portal runner guides the alternation (“Superset A · 1/2”, “Straight into: …”). See Strength & 1RM and My strength session.

The execution speed of a strength set, written as four beats (e.g. 3010: 3 s lowering, 1 s lifting). The player receives it in plain words in their runner: “3 s lowering · 1 s lifting”. See My strength session.

A rule set on a dashboard view to colour its values: Alert, Watch or On target, with an optional label (five at most per view). The Preset reuses the usual values (for example the ACWR target zone from 0.8 to 1.3), and the Target zone shows as a band on a ranked bar chart. With no threshold, nothing is coloured. See Dashboards.

A dashboard view that only lists the players past a threshold (ACWR, fatigue), most urgent first. When nobody is past one, it shows “Nobody beyond the thresholds.”. See Dashboards.

A club’s internal document listing expected behaviours and their fines. STRIVN can import it (PDF, photo or spreadsheet) to build the fine catalog. See Fines.

Tab of the Session results page that aggregates the review history: average rating and intensity, weekly evolution, weekday profile, breakdown by type, player ranking and automatic insights. Filterable by period and type. See Session review.

Mobile application for players (iOS and Android). Gives access to call-ups, check-ins, the team schedule and notifications. See The STRIVN Player app.

Feature that sends a reminder only to pending players for a call-up, without notifying those who have already responded. See Call-ups (RSVP).

Cumulative session load (RPE × duration) per player over a rolling period. Accessible from the Team load menu.

A team’s audience type: Adults / seniors, Youth (teens) or Kids. Determines whether players have direct app access, whether parental consent is required, and whether certain features (fines, check-ins, GPS) are available. Chosen when the team is created, editable afterward by the head coach only. See Youth teams & parental consent.

Authorization given by a parent/guardian for a minor player, purpose by purpose (club participation, wellness/health, GPS/load, photo), via a personal WhatsApp link. An unchecked box counts as a refusal; the parent can withdraw it at any time via a new link. See Youth teams & parental consent.

Space where a parent/guardian, once consent is given, creates their own access (phone + password) to follow their child’s schedule and answer call-ups on their behalf. A parent with several children at the club picks the active child and switches from the profile button at the top right. See Parent portal.

The name a coach gives to a sum of zones from their GPS export — for example Aerobic = Zone 1 + Zone 2 + Zone 3. Bands are not a fixed list: each team defines its own in the settings. A band carries a target per measure (distance and time), and reads in both if its zones are mapped to both columns. See GPS — speed bands.

A tile on a dashboard: a question (metric, subject, period, order) and the way it is displayed, with its thresholds and its on-click behaviour. A dashboard holds at most 8 data views; notes and headings don’t count. See Dashboards.

A speed band as the GPS provider delivers it — numbered (Zone 1, Zone 2…), in distance and often in time too. A zone is mapped once to its export columns, then stays the brick that speed bands are made of. An unmapped zone appears nowhere. See GPS — speed bands.

Tying a player to a role on one specific goal: scorer, assist, trigger, but also “bad positioning” on a conceded goal. A goal accepts as many attributions as needed, and the role’s label is frozen at the moment it is saved — renaming the role later does not rewrite history. See Goal review.

The ordered sequence of roles behind a goal. It is entered pitch-side as soon as your vocabulary declares at least three credit roles, and it pre-fills the post-match review: you correct, you do not retype. The same player may hold two roles in it. See Live match.

An axis that qualifies a goal, with its own value list: finishing zone, action side, action type, scoring method, timing. The dimensions are yours — the match recap enumerates them without knowing any of them by name. See Goal review.

An action your team counts and attributes: shot on target, save, key pass. Every fact carries its grain (per player, for the collective, or both), its live availability, and its player visibility — a subjective fact like “decisive save” stays hidden from the portal. See Goal review.

A part of a session a GPS file can be attached to: a half for a match (a closed, sport-specific vocabulary), a plan block for a training session. Importing by sub-element rather than for the whole session does not change what is measured, but makes the session value be rebuilt from the sub-elements, metric by metric, using the aggregation mode set. A file covering the whole session always takes precedence. See GPS — speed bands.

The value you give to a dimension on one specific goal: “penalty area”, “counter-attack”, “header”. A goal accepts one value per dimension, and none is mandatory. You give them pitch-side, in the Qualify the goal screen, then you correct them in the post-match review. See Live match.

The facts, roles and dimensions your team declares. The app ships a starting template per sport, which you load and then change freely. An item is renamed without breaking anything and archived without losing history: it leaves the pickers, what was recorded stays counted. See Goal review.

A division entered by the staff when the team isn’t linked to the federation: teams (opponent files), fixtures and results, from which strivn computes the standings. Hidden but kept as soon as a federation link exists. See Official competition.