Frequently Asked Questions

Training Signals turns the workouts you already log on Wahoo or Hammerhead (or Strava, for existing connections) into an ongoing training plan and coaching insight: tracking your fitness, fatigue, and form, and adjusting your plan as you train.

Yes. Training Signals sees your training through a connected source: rides, runs, distance, elevation, and effort. Wahoo and Hammerhead connect directly from the Connections page (and existing Strava connections keep working too). Almost anything else can reach us through Apple Health via the Training Signals iOS app, or through RunGap (see below). You can connect or disconnect any time from Connections.

No. Training Signals works the same for everyone, Strava Premium or not, and computes its own effort score rather than depending on anything Strava's plan tiers gate. It takes the best input each session actually has, in this order: your head unit's own TSS, then normalized power against your FTP, then average power, then heart rate, then duration alone as a last resort. Every session says which one produced its number, and if you think the wrong one is being used for you, you can talk to your coach about changing it (see below). Either way, every activity gets a comparable effort score and feeds the same Fitness, Fatigue, and Form numbers.

The Basic tier (activity sync, fitness trends, adaptive training plans, and weekly coaching reports) is free. An Intelligent Coaching tier personalizes your weekly check-ins using Claude; it's $4.99/mo or $49.99/yr (2 months free) after a 14-day free trial, self-serve from the Subscription page.

Yes, it's free. Get it on the App Store. Beyond everything the website does, the app adds what only a native app can: workouts imported automatically from Apple Health (the bridge for Zwift, Rouvy, and most training apps), push notifications for your daily plan, synced activities, check-in reminders, and coach replies, and Sign in with Apple. Your account, plans, and coaching history are the same everywhere, sign in and pick up where you left off.

Sign in to Training Signals, open Connections, and click "Connect Wahoo" or "Connect Hammerhead". You'll be taken to that service's official authorization screen to approve access; once you approve, you're returned to Training Signals and workouts logged on your device begin importing automatically.

No. Existing Strava connections keep working exactly as before, including sync and disconnect. Wahoo and Hammerhead are what we now offer new accounts, but you're welcome to keep using Strava, connect Wahoo or Hammerhead as well, or use more than one at once. If the same workout is reported by more than one, we keep only one copy of it.

Five. "user_read" identifies your account so we can link it to your Training Signals profile. "workouts_read" lets us read your workouts (date, sport, distance, duration, elevation, and heart rate/power when available) which is the data all of the coaching is built from. "offline_data" lets us keep syncing without you having to reauthorize constantly. "plans_read" and "plans_write" power workout push: the Send to Wahoo button that puts today's structured workout on your ELEMNT with targets in your own watts, no file import needed. We request nothing else, and your Wahoo data is only ever shown to you, never to other users.

Just one. "activity:read" lets us read your Hammerhead activities (date, sport, distance, duration, elevation, and heart rate/power when available) which is the data all of the coaching is built from. We never request write access to your routes, workouts, or metrics, and your Hammerhead data is only ever shown to you, never to other users.

Yes. Connect Oura or WHOOP from the Connections page, or simply use the iOS app with an Apple Watch (it reads sleep, heart-rate variability, and resting heart rate from Apple Health with your permission). Each morning's measured recovery flows to your coach automatically: a genuinely rough night ahead of a hard session gets you a proposed easier day (which you approve or dismiss, never applied silently) and you can ask the coach about your recovery trends any time in chat. We store daily summaries only (scores, sleep duration, HRV, resting heart rate), never raw sensor streams, and disconnecting a service deletes its stored recovery data. One note on Oura and WHOOP: both limit how many athletes can join through a new integration, so if the slots are full you'll see a "notify me" button instead, joining that list helps us request more capacity and gets you an alert the moment it opens.

Almost certainly, through one of two bridges. First, Apple Health: the Training Signals iOS app imports workouts from Apple Health automatically, and most platforms can write there, most watch and training apps on iPhone or iPad have an Apple Health toggle in their settings. Turn that on, allow workout access in our app, and your sessions flow in with no extra services involved. Second, RunGap: a separate iOS app (not made by us) that pulls workouts from many services we don't connect to directly and pushes them to us automatically. RunGap's Custom Webhooks feature is a paid add-on (their annual plan is a few dollars a year), once you have it, click "Connect RunGap" on our Connections page and paste the generated webhook URL and passkey into RunGap's own Webhook destination settings. Whichever route (or routes) you use, if the same workout arrives from more than one source we keep only one copy of it.

Going forward, when the same workout arrives from more than one connected source we automatically keep only one copy. But activities that synced before you had both sources connected can occasionally sit in your history twice. Open Settings, find "Duplicate Activities," and press "Review duplicate workouts" to scan your history. We group likely duplicates by date and sport and pre-check the copy with less complete data as our suggested delete, but you review every group and choose exactly what gets removed. Deleting a duplicate updates your Fitness, Fatigue, Form, and weekly totals right away.

You can set an activity aside without deleting it. Excluding is reversible: the activity stays in your history but stops counting toward your Fitness, Fatigue, Form, weekly volume, FTP, personal records, and plan, and you can restore it with one tap. Every synced activity on your Today page has a "not my ride" option to exclude it, tucked inside the activity once you tap to open it. Anything that looks physically impossible for a workout, like a "ride" at driving speed from a device left recording in the car, is caught the moment it syncs, set aside automatically, and flagged for you to confirm or restore. And on Intelligent Coaching, you can just ask your coach in chat to find rides that look like a different rider, typically lower power at a higher heart rate than your own, as happens when a lighter family member shares your bike computer, and it'll walk you through which to exclude before anything changes. This is different from duplicate cleanup: there the same workout is counted twice, here the activity is real but isn't your training.

Only two. "read" identifies your account so we can link it to your Training Signals profile. "activity:read_all" lets us read your activities (date, sport, distance, duration, elevation, and heart rate/power when available) which is the data all of the coaching is built from. We request nothing else, and we removed the older "profile:read_all" permission because we no longer needed it. Your Strava data is only ever shown to you, never to other users.

In near real time. When you upload a workout to Wahoo, Hammerhead, or Strava, it notifies Training Signals and we import just that new activity within seconds. You don't have to open the app. You can also press "Sync" on Connections any time to pull manually for any connected source. As a backup, Wahoo connections are also checked every 30 minutes and every connected source gets a once-a-day full check, so a missed notification never goes unnoticed for long. We only ever fetch new or updated activities, never your whole history repeatedly.

First, confirm the activity finished uploading to Wahoo, Hammerhead, or Strava itself, and that the connection is still active on Connections (re-connect if it was revoked): rides, runs, and swims are the activity types that feed the training math. Pressing "Sync" on Connections pulls the latest manually for any source (Strava also offers a "Full re-sync" for older history). If a workout never made it to any connected service at all, add it by hand with the "+ Add activity" button on the dashboard. Still stuck? Email support@trainingsignals.cc.

Wahoo won't share the full details of a ride that started in a third-party app like Zwift and was only relayed through Wahoo. This is a restriction on Wahoo's side, not something we can sync around. We still detect that the ride happened, so it isn't silently dropped: a card appears near the top of your Today page (and a "Needs details" badge on the activity itself) as soon as we spot one. If you have more than one waiting at once, drop all their .fit files in together, each one is matched to the right activity automatically by date, so you don't have to complete them one at a time. From the Wahoo app or Zwift's activity export, uploading the .fit file gives an instant, fully-detailed import; entering duration, distance, elevation, and heart rate by hand works too. Either way, once completed it counts toward Fitness, Fatigue, and Form like any other activity. We'll also email you when one of these turns up, if you have activity emails turned on in Settings.

Fitness (CTL) is your long-term training load built up over roughly 42 days. Fatigue (ATL) is your short-term load from the last week or so. Form (TSB) is Fitness minus Fatigue, a signal for how fresh and race-ready you are. You can see all three on the Progress page.

Both are rolling averages that need time to reflect your training history, so they read low for new accounts or after a big gap in activity and build up over the first few weeks of consistent syncing.

Not by default, the reported distance and effort for e-bike and other motor-assisted rides is excluded from Fitness, Fatigue, Form, your longest-ride stat, and how your plan is sized, since pedal assist changes the effort behind the numbers. If you'd rather they count like any other ride, turn on "Count e-bike and other motor-assisted rides" in Settings. Either way, those rides still show up in your activity feed, the setting only affects the training-stat math.

Your plan is generated around the goal you set: a specific race with a date, distance, and elevation, an open-ended general fitness goal, or (for cycling-family sports) an FTP target by a deadline, combined with your current fitness level and the days you have available to train.

Set a general fitness goal instead. Your plan will focus on steady, sustainable training rather than counting down to an event.

FTP (Functional Threshold Power) is a cycling-specific power benchmark, so this goal type is only offered for cycling, mountain biking, gravel cycling, and e-bike, set a wattage target and a deadline instead of a race. Plans built around an FTP goal lean on Threshold and VO2 intervals (Zone 4 at 91-105% FTP and Zone 5 at 106-120% FTP) rather than distance-based long rides, because sustained high-intensity work is the primary stimulus for raising your FTP. When your FTP is known, every workout is prescribed in your own numbers (exact watt ranges and W/kg alongside the %FTP zone) so a session like "3 x 10 minutes at threshold" reads with the actual watts to hold and translates directly onto any head unit or trainer app. Your current FTP comes from whichever source is most trustworthy: a value you enter yourself in Settings always takes priority, otherwise a free estimate Training Signals computes from your best recent power-meter ride (labeled "Estimated (basic)" since it's a rough approximation, a precise, streams-based estimate is planned for the Intelligent Coaching tier). Training is organized in blocks whose interval dose steps up week over week (3 x 10 at FTP, then over/unders, then 2 x 20) so the same session never just repeats, and an FTP Test is scheduled automatically at the end of each block (on fresh legs, during the recovery week): a 20-minute all-out effort whose result updates your FTP and recalibrates the next block's watt targets.

Your power zones (Active Recovery through Neuromuscular Power) are calculated from your current FTP using the standard 7-zone %FTP model, whether that FTP came from a value you entered in Settings or an estimate from your power-meter rides. You can see your current zones under Settings, and they update automatically whenever your FTP changes.

Talk to your coach about it, on Intelligent Coaching. Tell it a number looks wrong, for example your head unit's TSS reading high off a stale FTP, and it checks your actual rides before answering, explains the real calculation, and only if your reasoning holds up, offers a personal override for that input specifically. Nothing changes until you confirm it, it applies everywhere your numbers appear, and you can revert it any time from Settings without asking anyone. Often the explanation alone settles it: your coach can just as easily tell you the number is already right, and say why. Today this covers which input your effort score is built from.

On the ride itself. Open any ride on the Today page and its best 1, 5, 20 and 60 minute power sit alongside the other stats, worked out from that ride's own second-by-second power rather than from any average. A duration only appears if the ride was long enough to contain it, and a window never spans a stop, so a twenty-minute number is twenty unbroken minutes. Which rides have it depends on where they came from: Hammerhead, RunGap and .fit files you upload carry the data in the file, so those are automatic; Strava rides fill in a batch at a time as your activities sync; Wahoo can do it if you turn on "Import full ride detail" on the Connections page, which applies from then on rather than backfilling; and Apple Health sends a summary with no second-by-second data at all, so rides that arrive that way will not have it. As a rule of thumb, about 95% of a genuinely all-out 20-minute effort is the usual FTP estimate, but a 20-minute best set inside a long steady ride is not that, and your coach will tell you which it was looking at.

Both are, and the difference is a naming one. "Normalized Power" is a TrainingPeaks trademark, so Strava publishes the same idea under its own name: what your Strava screen calls Weighted Average Power is the figure we show as normalized power, and it is the number we use for variability, efficiency factor and intensity factor. For a ride that came from Wahoo, Hammerhead or Zwift we use the normalized power your head unit itself recorded. We never compute one ourselves and we never mix the two within a single ride, so the number you see here always traces to one source, which is named in the tooltip on the ride. Two tools can still differ by a few percent on the same file because they smooth the data and handle gaps slightly differently, and neither is wrong.

Once Training Signals knows your FTP (entered in Settings, from a logged FTP test, or estimated from your power-meter rides), cycling workouts are written in your personal numbers: the exact watt range for the session's zone, plus W/kg when your weight is set in Settings. The ranges come from the same 7-zone model as the Power Zones panel in Settings, so your plan and your zones always agree at the moment each workout is written. Your Power Zones panel itself always reflects your current FTP the instant it changes, but the watt ranges already written into upcoming scheduled workouts don't rewrite themselves retroactively; they update the next time that workout is regenerated, which happens automatically at your plan's next block or FTP test, or right away if you press "Adjust plan." No FTP yet? Workouts fall back to zone labels and feel-based descriptions.

Right away. Your estimate (when you don't have a manual value or FTP test result set in Settings) recalculates every time a new activity syncs, not just once a day, so a standout power effort is reflected immediately rather than waiting on a background job. If it comes out higher than before, you'll see a "Your FTP just went up" card on your Today page (and an email, if activity emails are turned on in Settings), dismiss it once you've seen it. As above, this updates the number itself right away; already-scheduled workouts pick up the new watt ranges the next time your plan regenerates or you press "Adjust plan."

Every scheduled session comes with an indoor alternative (a structured trainer session, a free Zwift/Rouvy route, or a pacer group matched to your fitness) and an outdoor suggestion pulled from your own ride history, so bad weather or no daylight never has to mean a skipped workout. You can turn off any of indoor, outdoor, cross-train, or coach's prescribed from Settings if you don't want a category suggested at all.

Yes. Set your intensity preference from Settings to Easy, Balanced, or Aggressive. It shifts how readily your plan unlocks threshold, VO2, and tempo work based on your readiness; taper and recovery weeks still pull back load regardless of this setting.

Use the catch-up and adjust options on the Plan page to reshuffle your remaining schedule around what actually happened, instead of just falling further behind an unrealistic plan.

Yes, on Intelligent Coaching. Tell your coach what's in the way, "I'm away Wednesday to Friday", "Tuesday I've only got 40 minutes", "the pool's shut next week", and it writes those days down against your account. From then on the plan is built around them: a day you can't train isn't scheduled at all and its work moves to the days you do have, and a day with a time limit on it gets a shorter session rather than one you were never going to finish. Interval sessions move to a day that fits them instead of being trimmed, because a session that says "3 x 10 minutes at threshold" can't honestly be squeezed into half an hour. It's one question, not a form: the days you don't mention are left alone. Recording it doesn't reshuffle your week on the spot, the plan picks it up next time it's built or adjusted, and you can ask your coach to reshape the week right away.

Four things, and it's on every tier. How much today matters (key sessions are marked as such, and most days aren't, deliberately, if everything were a key session the label would tell you nothing). What missing it actually costs, including when the honest answer is "very little", and for a key session a warning against stacking it onto tomorrow, because two hard days back to back costs more than the session was worth. The shortest version that still counts: about 60% of the prescribed time is the line where a session stops being logged as cut short. And the other ways to do it, outside, indoors, or as cross-training, which your plan writes for you and which used to be buried in the session's detail view.

Capped at a safe rate, even if your goal is a big jump from where you are now. Long-run and long-ride distance can only grow so much week over week, a guardrail based on the same 'too steep a ramp' injury risk that shows up in your goal feasibility check, so the plan builds toward an ambitious goal without setting you up for an overuse injury along the way.

Log it yourself, either check off the scheduled workout and enter what you actually did (distance, duration, elevation), or use the "+ Add activity" button on the dashboard for anything without a matching scheduled session. Manually-logged activities count toward Fitness, Fatigue, and Form exactly like a synced activity. If a connected source later syncs the real activity for that day, the manual entry is automatically removed so it's never double-counted.

Yes. Any manually-logged activity has Edit and Delete buttons in your Recent activities list (look for the "Manually logged" tag). Fix a wrong date, duration, or distance, or remove it entirely, and your Fitness, Fatigue, Form, and weekly totals update right away. Activities imported from Wahoo, Hammerhead, or Strava can't be edited or deleted here, those stay in sync with the source itself, so make any changes there.

It's recognized automatically, the rest day is marked done once that activity syncs, so it counts toward this week's progress instead of looking skipped. If the extra effort pushes your fatigue too high, your plan will pick that up the same way it catches any other overtraining signal, and propose a rest day going forward.

Yes. If a significant session (75+ minutes) shows up on the same day of the week in most of your recent weeks (the classic standing group ride or club session) Training Signals detects it as a training habit. Two things happen: new plans default your long workout to that day automatically (unless you've explicitly set a different long-workout day in Settings, which always wins), and your Intelligent Coaching coach sees the pattern, treats that ride as part of your real week rather than a scheduling conflict, and will offer to formalize it as a plan preference. Tell your coach what the pattern is ('that's my Saturday group ride') and it'll remember and plan the rest of the week around it. Your daily brief narrates the week the same way, acknowledging the group ride as part of the plan, opening the week with an overview of its shape, and if a ride ran well past what was planned, folding that into the next day's guidance. And every easy day on your plan explains its place in the week ('keeping today controlled so you're fresh for Thursday's threshold intervals').

Because sometimes that hole is the plan working. A build block deliberately loads you harder than you can immediately recover from (coaches call it functional overreaching) and then schedules a recovery week to absorb it, that's how fitness is built. When your Form (TSB) is deep but not critical, your plan already eases up next week, and your daily check-ins look okay, the coach's read will say you're absorbing planned load and to hold the line rather than nag you to add rest days. Three things always override that and bring back the rest recommendation: Form dropping below the critical threshold, your check-ins showing multiple days of poor sleep and high fatigue, or you simply telling your coach you're wrecked, your body outranks the plan, every time.

On an easy or recovery day, yes, the sport is just the vehicle for the effort, so an easy spin in place of a recovery run (or vice versa) of comparable duration is credited automatically once it syncs, and any stale "catch-up" suggestion clears itself. For a goal aimed at a specific race or FTP target, hard and long sessions stay sport-specific: a ride won't check off a key run, because the adaptations that prepare you for race day aren't interchangeable and we won't tell you you're ready when you're not. Either way the effort still counts toward your Fitness, Fatigue, and Form. And if the automatic read gets it wrong, on Intelligent Coaching you can simply tell your coach the session covered that day, and it's credited as done differently rather than missed.

Yes, on Intelligent Coaching. Everything we work out about a session is inferred from the numbers, and the numbers can't tell a race from a hard endurance day, a bunch ride from a failed interval session, or a commute from training. Tell your coach what it actually was, "that was a race", "that was the Saturday group ride", "that's just my commute", and it's recorded as your word on it, which outranks anything we worked out. Your coach then reads the session in that light rather than congratulating you on a target you were never chasing. If it covered that day's planned workout, say so and the day is credited as done differently rather than missed, because a plan that ignores a hard ride for not being the prescribed one isn't worth following. "Not training" also takes the session out of your Fitness, Fatigue, and Form, reversibly.

Yes, for cycling sessions. Open any scheduled ride or its Coach's prescribed alternative and download it as a .zwo file (for Zwift) or a .mrcfile (for Wahoo SYSTM, Rouvy, or most other trainer software), both encode the workout as a percentage of your FTP, so each platform applies your own numbers automatically; you don't need to enter an FTP into Training Signals.

Zwift: on a computer, log into zwift.com, go to your profile, and upload the .zwofile under "My Workouts" (or drop it into the Documents/Zwift/Workouts folder on your computer if Zwift is installed there). It'll appear in the Custom Workouts section in-game.

Wahoo SYSTM: import the .mrcfile from the SYSTM desktop app under Settings → Import Workout, or via the web dashboard's workout library. It'll show up alongside SYSTM's own plans, ready to ride.

Rouvy: log into the Rouvy web app, open My Workouts, and use the import/upload option to add the .mrcfile. It'll be available to select before your next ride.

Running sessions don't get this option, structured pace files aren't standardized across platforms the way power-based cycling files are.

It's how much of your plan you've actually followed this month. Every day your plan asks something of you is judged against what it asked of you, never against a distance or a wattage, so a prescribed half-hour walk and a five-hour ride are worth the same: one day, done as asked. A rest day your plan asked for counts as following the plan, because it is. Turning up and cutting a session short keeps most of the day rather than nothing, and going longer or harder than prescribed doesn't earn extra, because an easy day is meant to stay easy. Days in a row are worth a little more, up to a ceiling that's reachable inside even a short plan, so consistency pays without handing an advantage to whoever was given the most to do. A missed day costs less than a completed day earns and takes your run of days down rather than wiping it, and your total never drops below zero. You can see the full arithmetic under "How this is worked out" on the Progress page.

No. Tell your coach what happened and the day is written down as what it was: ill, injured, away, a session that never reached us, or a day the two of you agreed to drop. Any of those leaves the reckoning entirely, so it earns no points, costs no points, and your run of days carries straight across it. A score that penalized rest would be a score that paid you to train through illness, which is the opposite of what the coach is for. A day you simply decided to skip is recorded as exactly that and still counts, because a score that forgives everything isn't measuring anything, and your coach won't hold it over you either way. Setting a day aside happens in the coach chat, which is part of Intelligent Coaching; the score itself is on every tier. It's completely private, there's no leaderboard and no ranking against other athletes, and if you'd rather not have a score at all you can switch it off in Settings, which stops it being worked out rather than just hiding it.

Both tiers get activity sync, fitness trends, adaptive plans, and weekly coaching reports generated from your training data. Intelligent Coaching additionally has your weekly check-ins personalized by Claude, written like advice from a coach who knows your training rather than a generic template. It's $4.99/mo or $49.99/yr after a 14-day free trial, start either plan anytime from the Subscription page.

Two a day at most, and usually fewer. There's a hard cap of two unprompted push notifications per athlete per day, counted on your own calendar day, and at most one of those can be good news rather than something to act on. Things you asked for don't count against it: a reply from your coach, the daily plan at the time you chose, and anything about billing. Nothing is lost to the cap, whatever is held back is still waiting on the app's notification list when you next open it, so you get the information without getting buzzed four times for it. You can also turn any of it off in Settings.

It will notice, and it will ask once. If you go quiet, or if you're still training but the sessions your plan asked for keep going by, your coach checks in to ask what's getting in the way rather than telling you off. It also writes down things you say you'll do, in your own words, "I'll get the long ride in on Sunday", and asks how it went afterwards. That's your commitment rather than the plan's, nothing about it touches your score, and "didn't happen" is a perfectly good answer. What it won't do is nag: the daily notification cap applies to check-ins like everything else, and once you've explained a day it's answered and won't be raised again.

Yes. Opt in to daily plan emails from Settings to get that day's session (or a well-earned rest day) delivered to your inbox each morning. You can turn this off any time from the same page.

Opt in from Settings and Training Signals runs the same coaching check the "Refresh plan" button uses, once a day (re-syncing your Strava activity first, if connected, Wahoo and Hammerhead already sync in near real time via webhook). If it spots overtraining, falling behind, or a plan running out of scheduled workouts, it doesn't change anything on its own. It proposes a rest day, catch-up day, or fresh plan cycle on the Plan page for you to approve or dismiss, and emails you when one's ready to review.

Yes, if you're on Intelligent Coaching, pick Encouraging, Tough, Funny, Sarcastic, or Dismissive from Settings. It only changes how your daily brief, weekly report, and coach chat are written, never what they actually recommend.

Just you. See the Privacy Policy for the full breakdown of what we collect and who processes it on our behalf (Supabase for storage, Wahoo, Hammerhead, RunGap, and/or Strava for activity data, and Anthropic for AI-coaching message text only).

Yes, and we ask before any of it goes in the first place. The coach shows you what gets sent and who receives it (Anthropic, who run the model that writes your coaching) and waits for an answer. Change your mind either way under "How your data is used" in Settings. With it off you keep your plan, your sync, your charts and your records, and you stop getting written coaching: daily briefs, weekly reports, and the coach chat all go quiet, because all three are written by the model. Turning it off stops the next send rather than recalling anything already sent.

Yes, from Settings. It's easy to end up with two accounts if you started on the web and later used Sign in with Apple (or the other way around). Open Settings, find "Merge accounts," and enter the other account's email. We send a 6-digit code to that inbox to confirm you own it, then show both accounts side by side (activities, connections, plans, goals, and subscription) so you can choose which one to keep. The other folds into it, nothing is deleted from your history, and both emails keep working to sign in afterward. One rule: if both accounts have an active subscription, cancel one first so you're never double-charged, then come back and merge.

Disconnecting any of them is available from the Connections page at any time. It deletes your synced activities and FTP estimates from that source, but keeps your goals, training plans, and coaching history. For Wahoo, Hammerhead, and Strava, disconnecting also revokes our access on that service's side. RunGap has no such handshake to revoke on our end, since it only ever pushes to a URL you gave it, after disconnecting here, also remove the webhook from RunGap's own settings, or it'll keep trying to send workouts to a URL that no longer accepts them. Deleting all of your data instead is available from Settings and removes everything, including those.

We aim to meet WCAG 2.1 AA across both the website and the iOS app, and we've completed an internal accessibility review covering color contrast, keyboard and screen-reader navigation, form labeling, focus management in dialogs, and reduced-motion support. It's ongoing work, not a finished checkbox, if you hit a barrier using a screen reader, keyboard, or any assistive technology, email support@trainingsignals.cc and we'll prioritize it. Our full Accessibility Statement is at /accessibility.

Email support@trainingsignals.cc for anything, bugs, account issues, Intelligent Coaching access requests, or general questions.