Tracking Soccer Training Load Without a GPS Vest

2026-11-02 · 9 min read

Key takeaways

• Session load equals session RPE multiplied by duration in minutes, and it is a validated global load measure.
• Drill-level multipliers, such as 1.2 for small-sided games, make session load reflect intensity rather than duration alone.
• Sprint exposures counted per drill flag high-speed spikes that RPE-based proxies cannot see.
• ACWR is computed by dividing this week's total load by the four-week average, with 0.8 to 1.3 as a rough guide band.
• Manual tracking breaks down for return-to-play dosing, squads above roughly 30 players, and multi-team rollups.

You can estimate weekly soccer training load without a GPS vest by multiplying each player's session RPE by session minutes, weighting drills by intensity, and computing ACWR by hand. This framework gives you drill-level multipliers, a worked session calculation, and a weekly template, so a squad of 30 gets load management from a clipboard and a spreadsheet.

What does a GPS vest actually measure, and which of those metrics can you replicate manually?

The four GPS metrics that matter for load management

A GPS vest outputs four numbers that drive load decisions: total distance, high-speed distance, sprint counts, and accelerations. Total distance and high-speed distance feed session load; sprints and accelerations flag spike risk, especially across a match week.

What proxies can and cannot capture

The session-RPE method — multiplying RPE by minutes — has decades of validation as a global load measure, per work summarized on PubMed. That is the foundation of what we build on at XI Ready, and it is honest about its limit: proxies capture total load well and sprint/acceleration exposure poorly, so manual tracking needs compensating rules for high-speed spikes.

How do you calculate session load using RPE and minutes without any wearable?

The session-load formula is one multiplication: session load = RPE (0–10) × duration in minutes. A player who rates a 60-minute session at RPE 7 has a session load of 420 arbitrary units. The units are meaningless in isolation, which is fine. What matters is the comparison across players and across days in your microcycle, so collect every session the same way and never change the scale mid-season.

Worked example: one 90-minute session

Take a 90-minute Tuesday session two days out from a match (MD-2). You collect RPEs within 30 minutes of the final whistle. Your starting center back reports an 8, so her session load is 8 × 90 = 720. A returning winger coming off a hamstring issue reports a 5, so his is 450. Same session, very different internal loads, and that gap is exactly what a spreadsheet column reveals and guesswork hides. Add each player's daily figures across the week and you have the raw material for acute:chronic workload ratio (ACWR) calculations later.

Getting honest RPEs from youth and amateur players

The number is only as good as the collection. Ask within 30 minutes of the session ending, when memory of the hardest drills is still fresh, and ask privately rather than in a group where players copy each other. Anchor the scale: define RPE 3 as an easy warm-up pace, RPE 7 as a hard session they could repeat tomorrow, RPE 10 as nothing left in the tank. With U14s and younger, expect inflated and deflated answers; treat their numbers as directional signals rather than precise measurements, and weight your own observation of drill intensity alongside them.

Which on-field drills and small-sided games give the most reliable load signals?

Raw RPE × minutes treats every drill the same, but 20 minutes of 4v4 loads very differently than 20 minutes of passing patterns. Applying a per-category multiplier to your session load gets closer to what the drill actually demands.

Drill categories and adjustment multipliers

Use these illustrative multipliers, calibrated by your own RPE data over a microcycle:

• Passing patterns, walk-throughs: ×0.7
• Possession rondo, 6v4+: ×0.9
• Small-sided games (4v4 to 6v6): ×1.2
• Transition games, 8v8: ×1.1
• Conditioning runs, repeated sprints: ×1.3
• Technical warm-up: ×0.6

Adjust them against your squad's reported RPE: if a 4v4 block consistently scores higher RPE than the multiplier predicts, raise it. The goal is a session load that reflects drill intensity, not just duration.

Worked example: adjusting a mixed session

A 90-minute session: 15 min warm-up (0.6), 20 min passing (0.7), 25 min 4v4 (1.2), 20 min 8v8 (1.1), 10 min sprints (1.3). At RPE 7: (15×0.6 + 20×0.7 + 25×1.2 + 20×1.1 + 10×1.3) × 7 = 577 vs. 630 unadjusted. That gap matters across a match week, because ACWR spikes and sweet-spot debates remain contested in the literature (British Journal of Sports Medicine), so consistent drill-level estimates beat precision you cannot verify.

How can you track high-speed running and sprint exposure without GPS data?

Counting sprint exposures by drill type

GPS vests measure sprint distance directly. Without one, count sprint exposures instead: every rep where a player runs near-maximally for 3+ seconds. Different drill types carry predictable sprint loads. Transition games and counter-attack patterns produce the most; rondo work and possession grids produce almost none. Flag each session's drills in your log as high, moderate, or low sprint-exposure, then multiply by estimated reps per player. It is rough, but directionally useful for spotting a match week with zero sprint exposure before MD-4.

A simple weekly sprint tally

Keep one column per player: total sprint exposures across the week. A typical target for a match-week microcycle is exposures in every session, not just game day, because abrupt sprint spikes after quiet weeks are where hamstring risk concentrates. If your tally shows two near-zero weeks followed by a heavy scrimmage, cap the scrimmage reps or add a MD-4 acceleration block first. These proxies will not replace distance-at-speed data, but they catch the load-shape errors that spreadsheets full of minutes and RPE miss.

What simple field tests reveal accumulating fatigue across a training week?

Self-reported wellness is the cheapest validated fatigue signal you have: changes in players' own ratings track training stress in team sports even without any hardware (Saw et al., Sports Medicine).

The 60-second wellness check-in

Have every player text or submit four numbers before training: sleep quality, muscle soreness, mood, and fatigue, each on a 1–5 scale. That is a 30-player squad in under two minutes of your review time. Log the daily total next to yesterday's session load in your spreadsheet. A player running 4s all week after a heavy MD-4 session is telling you something before you see it on the pitch.

One repeatable field test per microcycle

Pick one test and never change it mid-season: a 20m sprint time, a standing jump, or a timed dribble run, done the same day each week (MD+2 works well). The absolute number matters less than the trend; a 5% drop across two weeks flags accumulated fatigue.

Honest limitation: wellness scores are subjective and players learn to game them. Pair them with the field test and the ACWR calculation covered next.

How do you compute ACWR by hand from manual session loads?

The rolling 4-week calculation

Acute:chronic workload ratio (ACWR) compares this week's total load against your 4-week average. Add up every session's load (RPE × minutes) for the current week to get your acute load. Then average the total weekly loads from the previous three weeks plus this one to get your chronic load. Divide acute by chronic.

Worked example with real numbers

Say your last three weeks totaled 3,200, 3,500, and 3,300 AU, and this week you logged 3,800 AU (five sessions, each RPE × minutes). Chronic load = (3,200 + 3,500 + 3,300 + 3,800) ÷ 4 = 3,450. ACWR = 3,800 ÷ 3,450 = 1.10. That sits inside the commonly used 0.8–1.3 band, so the week's spike is acceptable.

Interpreting the ratio when your inputs are estimates

Manual loads built from RPE and duration are estimates, not GPS-derived figures, so treat the 0.8–1.3 band as a guide rather than a rule. A ratio of 1.35 from rough numbers is a flag to check, not a diagnosis. Watch the trend across the microcycle and match week, and weight MD-4 sessions carefully since a hard session there inflates acute load exactly when players need freshness.

How should you adjust the next week's load based on manual tracking data?

Numbers only matter if they change what you write on the session plan. Three decision rules cover most cases at this level.

Decision rules for the next microcycle

If a player's ACWR crosses roughly 1.5, cut their prescribed volume in the next session by 20-30%: shorter drills, fewer repetitions, or an earlier exit. If two or more wellness check-ins come back low (poor sleep, soreness, low readiness score) for the same player across consecutive days, drop them to a technical-only session. If session RPE for the same drill starts climbing week over week at equal duration, treat that as accumulating fatigue and hold the next microcycle flat rather than progressing it.

Planning match week with proxy loads

Build the microcycle backwards from match day. MD-4 carries your highest training load, MD-2 tapers to roughly half that volume, MD-1 is short and sharp. Small-sided games let you hit high internal loads in short durations, which is why they anchor MD-4 research on small-sided games and internal load. Pull a player from session entirely when soreness plus low wellness persist past MD-2.

When is manual tracking no longer good enough and a wearable becomes necessary?

Signals you have outgrown proxies

Manual RPE-and-minutes tracking breaks down in three cases. First, return-to-play: you need per-player high-speed running and sprint counts to dose exposure precisely, and proxies cannot see them. Second, squads above roughly 30 players, where spreadsheet upkeep eats your week. Third, multi-team rollups where you need comparable data across coaches who score RPE differently.

Comparing your options honestly

The wearable route means hardware plus subscription: Catapult, STATSports, and Output Sports all sell systems priced for organizations, not grassroots budgets. If you stay manual, XI Ready's $49/mo Coach Pro tier (30 athletes) handles wellness check-ins, ACWR, and match-week scheduling in one dashboard, replacing your spreadsheet. Where it falls short: no GPS-derived distance or sprint data, so high-speed running dosing stays on your judgment. If that becomes your bottleneck, that is the moment to price wearables.

FAQ

Is RPE x minutes accurate enough to use for real load management decisions?

Yes, for total weekly load. The session-RPE method has decades of validation as a global load measure, which is why it anchors this framework. Its weakness is high-speed exposure: proxies cannot see sprint distance or accelerations, so pair the calculation with sprint tallies and drill flags before acting on match-week decisions.

How do I get youth players to give honest RPE ratings instead of copying each other?

Ask privately, never in a group, and collect ratings within 30 minutes of the session ending. Anchor the scale with concrete definitions: RPE 3 is easy warm-up pace, 7 is a hard session they could repeat tomorrow, 10 is nothing left. With U14s and younger, expect noise, so treat their numbers as directional and weight your own observation of drill intensity alongside them.

Can I use a smart ball or shin-guard sensor instead of a GPS vest to track load?

Not for load management. Smart balls measure ball interaction metrics like strike count and spin; shin-guard sensors typically capture impacts and kicks. Neither estimates total distance, high-speed running, or internal load, so neither can substitute for the RPE x minutes framework or replace GPS-derived sprint dosing in return-to-play situations.

What spreadsheet columns do I need to track training load for a whole squad?

One row per player per session: date, session duration, RPE, session load (RPE x minutes), drill-adjusted load, sprint exposures, and the four wellness scores (sleep, soreness, mood, fatigue). Then weekly totals per player for acute load, a four-week average for chronic load, and ACWR as a formula column dividing the two.

How long does it take each week to run manual load tracking for 25 players?

Roughly 15 minutes collecting RPEs after each session, two minutes reviewing wellness submissions before training, and 30-45 minutes on a weekend updating weekly totals and ACWR. That is about two hours per week total, most of it data entry your players can partially handle by submitting their own numbers.