All sections
Overview

Start here

Data and connections

Where your workouts come from, what the platform computes itself, and what happens when data doesn't arrive.

17 min read

In this article

A session reaches TriCoo by one of four routes, and none of them counts as more real than the others. The platform works out all its numbers itself, and a connected service is a way of delivering data, not a participant in the calculation. Which leads to something simple: you don't have to connect anything, and if what you did connect one day stops working, your training won't stop with it.

Who does the maths here

TriCoo calculates and stores everything: the plan, load scores, thresholds, fitness with recent load and form, and the day's readiness. External services bring the raw material — the fact that a session happened, plus the heart rate, power and pace traces — and give you somewhere to cross-check.

One requirement keeps this honest: the same session, whether it came from Strava, from intervals.icu, as a file or typed in by hand, gets the same load score from the same raw data, thresholds and calculation version. Services sometimes pass on different data, and then the scores can differ. If the data match and the scores don't, that's a bug, not a quirk of the source.

Four routes in

Strava brings the session itself and its detailed traces, and it does so soon after the session appears, without waiting for a scheduled sync. Strava doesn't hand over the planned calendar or wellness metrics at all — that's a limit of the service itself, and we won't pretend there's a way round it.

intervals.icu brings the same, plus two more things: wellness metrics — sleep, resting heart rate, variability (without saying whether it was taken overnight by a watch or in the morning by an app: the source does not pass that on) — if you've allowed them to be imported, and it can receive a copy of your plan so the session ends up on your watch.

Which watches, trainers and services connect, and what each one passes on, is in Connections.

A file — FIT, TCX or GPX, exported from your watch or from another service. Good both for bringing your history across and for the one-off session that didn't sync anywhere.

By hand — the sport, the duration and an effort rating on a scale of 0 to 10. That's enough for the session to get an honest score: a swim without a watch, strength work in the basement and a day hiking in the mountains are all counted exactly this way.

One session, even with two sources

With both Strava and intervals.icu connected, a single run will arrive twice. The platform merges such records: first by the service's own session id, then by ours, and if there's neither — by fingerprint: the same sport, a start within two minutes and a duration within 5%. Matching records become one, load isn't doubled, and the full provenance is kept — you can see who brought what.

Data completeness: all, some, none

Every record is marked with how complete it is. “All” — there's enough data for the chosen method of calculation. “Some” — not all of it is usable, so the calculation steps down a rung: from pace to heart rate, for instance. “None” — nothing whatsoever is known about that day.

The third state matters most. “Unknown” is not a missed session and not zero load: a silent sync says nothing about whether you trained, and the plan mustn't be redrawn because of it. Rest that you've confirmed is another matter entirely: that's a real fact with zero load.

If GPS got the distance wrong

Sometimes a watch loses the satellites and adds extra kilometres to a run. The platform finds impossible jumps in speed in the recording. If they made the distance noticeably longer, it recalculates the distance from speed without those jumps. The run card then carries the note GPS interference removed.

The distance can be known independently of GPS. For example, from a marked course or a loop of known length. Such a run has a card called Correct the distance. Enter the kilometres and press Apply. Remove my correction takes your number away. The platform will not accept a distance that, divided by the moving time, gives a speed above 13 metres per second.

Sometimes the distance in the recording does not match the time at all, and the platform cannot restore it. Then the card is called Distance not confirmed. Such a run has no distance and no pace, and it does not go into the weekly kilometres until you enter the number yourself. The run itself is not lost: its time and load are counted.

Your number does not change everything. There are three separate things here.

  • What you see. The distance and average pace of the run change, and so do the weekly kilometres and the running volume that Forecasts are based on.
  • Past load. It does not change. The load points, intensity, zones and records of this run stay as they were. Correcting the total distance does not change the original speed and heart rate recordings and does not recalculate past load.
  • Pace threshold. Your number reaches it in two cases only, described below.

The first case is a run threshold test scheduled in advance. If the track broke, the platform can work out the result from the distance you entered. An ordinary run does not become a test afterwards.

For this route the warm-up has to be a separate run recording of at least 10 minutes. The test starts after it ends, no later than 5 minutes afterwards. It is recorded separately, outdoors. The test is set for 30 minutes with no pauses. Stop the recording at 30:00. Follow the instructions of the scheduled test. After it, rate the effort as it actually was.

For the test to count, the effort has to be very high and the elevation and cadence recordings, that is step rate, have to be usable. The average descent over the whole test must not be steeper than one percent. The platform also checks that the recording is continuous and the result is plausible. Correcting the distance alone is not enough for the test to count.

The second case is a hard outdoor run already done, with your distance. The full time of the recording must be from 30 to 60 minutes inclusive. Usable elevation and cadence recordings are needed, and the platform uses them to check the terrain and that the run was continuous. The climb must not exceed 10 metres per kilometre. The difference in height between the finish and the start, in either direction, must not exceed 5 metres per kilometre. You rated the effort as very high yourself, or it was a race. From it the platform works out a cautious estimate: the whole distance divided by the whole time of the recording. Such an estimate can give you a first pace threshold or raise the current one a little, by no more than 2 percent and no more often than once in 14 days. One run raises the threshold once. A new estimate from such a run can only raise the threshold or give you a first one. It does not replace a confirmed threshold that is usable for the numeric targets of the plan. A confirmation mark alone is not enough for that. The original confidence of the estimate matters too. There are other safeguards too, so the threshold does not change after every such run. The confidence of the estimate is low. There is no separate message about it on the screen.

If you correct or remove your distance, the platform checks the calculation linked to it again. If the current threshold came from this recording, it can change. When its contribution is withdrawn, the platform returns the previous usable basis. If there is none, there may be no usable threshold left. Correcting the same run does not give an extra 2 percent raise. The load already calculated for past sessions does not change.

An outdoor ride has the same card. There your number changes the distance and the average speed. It does not touch the load either: that is calculated from power or heart rate.

A heart rate session without a rating

The platform rates a heart rate session by its main work. To do that it has to know where the warm-up ended and the work began. It takes these boundaries from laps. The simplest case is when the watch reported where a lap came from. For example, the watch guided you through a planned session and switched the steps itself. Or you pressed the lap button and the watch marked it.

Strava does not report this. A lap from Strava does not say whether it is a workout step, a press of the lap button or an auto lap that the watch sets every kilometre. So the platform checks the laps against the plan. If the whole recording fits the planned steps in order and in time, the laps count as steps and the session gets a rating. One extra lap after the last step is fine: for example, you walked home and did not stop the watch right away.

If the laps do not fit the plan, the session stays marked Execution not rated. This happens when you ran with your own laps or with auto lap.

Such a session does not count as missed. Its time and load are counted in the week. A single-step session without a warm-up is rated over the whole recording, it needs no laps.

When an external service goes quiet

An outage at the service, access revoked, a session that went missing — all of these give “unknown”, not zero. The plan keeps working, and fitness and recent load hold their values instead of collapsing. If the silence stretches to a week or more, the platform still won't declare that you missed anything, but it brings you back to load more carefully — as it would after a confirmed break.

A session deleted in an external service doesn't count as missed either, until you confirm it. And an edit made outside is accepted as your decision, but it goes through the same checks: you can't push volume past the guardrails or get round a medical restriction by going through an external service. More on that in How the plan adapts to life.

You can bring your history, or leave it behind

Past sessions come across as a file or from a connected service — then the platform can see your background straight away. Handy, but not required.

Without a history, the plan starts with calibration. If over the last 4 weeks you trained 3 times a week or more, you can turn it off. During calibration volume is set at around 70% of your usual weekly hours, hard zones aren't prescribed at all, and sessions are run by feel. A beginner gets easy work only; an experienced athlete gets no more than one controlled moderate session a week. While data is thin the platform says exactly that, calibrating, rather than passing a rough guess off as a precise estimate. More in Calibration.

Why other people's numbers are a second opinion

An external threshold estimate, someone else's load score, someone else's recovery status and someone else's heart-rate-to-pace decoupling: we store them and can show them, but we don't let them into the calculation.

It isn't pride. Someone else's load score was worked out from someone else's threshold with someone else's formula, and dropping it into our model would mix two scales. A discrepancy is useful as a reason to re-check your threshold, not as a ready-made number. For the same reason, only the raw measurements are taken from watches, rings and bands — their branded readiness scores are not.

Notifications

Every uploaded workout and everything the assistant puts in the thread while you are away can reach your phone or browser as a notification: the workout with how it went, a plan suggestion, a request to rate an effort, a receipt for a skip or an overshoot, the week review, the morning check-in, an updated threshold, team and follower events. The title names the reason, the text gives the gist: “There’s a plan suggestion — For Thursday”, “Skip recorded — Yesterday: 45 LU not completed, the plan stays”, “Week review is ready — 7–13 September”. For a workout the title is a short encouraging line (no reward for overshooting the plan) and the text reads like the Strava caption: “🏃 Threshold run — done on plan ✅, load ≈95% of planned. Fitness 52 ↗, race in 41 days 🏁”; tapping opens the workout. It never carries medical states, readiness or the reasons behind a suggestion: the notification sits on the lock screen where others can see it. The text itself is encrypted all the way to your device — Apple’s and Google’s servers only see that a message exists. A notification arrives as soon as the reason appears in the thread, at any hour of the day; at night, before 07:30 in your time zone, nothing rings — whatever piled up overnight comes at 07:30 as one message. The exception is a workout finished no more than two hours ago: it is announced right away, even at night. On a day when the medical layer has stopped the plan, nothing is sent. Permission is asked once, after the first published week; you can switch it off in your profile. On iPhone, notifications work only for the app added to the Home Screen.

Stroke count from the file

If a swim arrives as a file from your watch, the platform keeps every pool length: time, stroke style and the stroke count with its counting unit — Garmin watches count a full cycle of the arm wearing the watch. The metric is built only from the control block — freestyle without equipment inside a narrow pace band — and only with eight or more usable lengths; otherwise you see “usable lengths so many of so many”, and that is all. A number typed in by hand after the pool is stored separately and never mixed with the watch. Stroke count has no effect on load, readiness or thresholds.

Best results

The Best results section keeps your top three for each measure. That is your time over 1, 5 and 10 km, a half marathon and a marathon, your average bike power over 5 seconds and 1, 5, 20 and 60 minutes, your longest sessions and your race times. The platform finds them itself. In every session it looks for the fastest stretch of the right length. Your best 5 km may sit inside a 12 km run. Time is counted in full, stops included.

This needs a second-by-second recording without gaps. Treadmill runs do not count towards running distances: there is no exact distance. Power comes only from a power meter; estimated watts do not count. A session excluded as a duplicate, or one where GPS got the distance wrong, does not count either. In the pool, times over 100, 200, 400 and 1500 m freestyle come from the lengths in your watch file, with 25 and 50 m pools kept apart.

You can correct, hide or add any result by hand, for example an old marathon from before TriCoo. The platform keeps the corrected number next to the one it found, so you can go back. When a new session beats your best result of all time, the assistant tells you. After an easy session from the plan it stays quiet. Results do not affect the plan, thresholds or load.

Results sit in a table: this season, last season and all time side by side. Under this season's number is the difference from last season: the arrow shows which way the number moved, and the signed number shows by how much. For time, minus means faster; for power, plus means more watts. This season is still going, so the comparison is incomplete. The difference between best results does not tell you how your fitness changed: a best depends on whether you made such an attempt. There is no need to test your maximum on purpose.

If your profile is public, your results have their own page, and you can send the link. It shows all your results, including those from Strava sessions. Sessions you made private and results you hid are not shown.

Seasons

A season ends with your main race and the recovery weeks after it. The next one starts the day after, but no earlier than a year before its own end. Until you have a main race, the season is the calendar year. Seasons let you look at your results for this season and the last one.

All seasons are on the Races screen, in the Seasons card. You can change the dates with Edit. If the new dates touch the neighbouring season, it moves by itself. Your own dates only change the period in Best results. The plan and the training phase stay as they are.

What goes out, and what never does

One thing can go out: a copy of your plan, to intervals.icu, if you connected it yourself. What travels is the training plan itself: no health questionnaire, no wellbeing answers, no readiness status. If a workout's target is heart rate, heart rate targets travel too, as a percentage of your threshold heart rate, which the platform writes into intervals.icu settings. We add a short caption to your activity description on Strava. It is on from the start and can be switched off in your profile. It says what the plan was, how it went, load as a percentage of planned and in points, fitness and days to your race; nothing about health, readiness or the reasons behind plan changes. A session recorded on your race day gets a race day line. It can be switched off in the same place; captions already added stay on Strava. To others, your followers included, the public page of a Strava activity never shows Strava data such as the map, distance or pace: Strava's terms require it. It shows the sport, the date, our load estimate and what went into the caption. That display is also on from the start and can be switched off in your profile. You yourself see everything.

Medical and personal data are stored in our database in Russia. A language model receives part of it when you write to the AI assistant: your message, training data, the colour of your readiness light and its reasons, resting heart rate, heart rate variability and load restrictions. Yandex.Cloud LLC processes requests on infrastructure in Russia. Your profile name and contact details are not added to the request. Details are in Privacy and your data.

Terms in this article

What to read next