Calorie data for your clients appears in several places on Gymkee:

Activities tab. In the client detail screen, the Activities tab shows all logged and synced activities. Each activity row displays the calories burned (when available). Click on any activity to see the full detail, including whether the calories came from a wearable or from Gymkee's MET estimation.

Weekly summary. At the top of the Activities tab, the weekly summary card shows the total calories burned across all activities and workouts for the selected week, along with total duration and activity count.

Completed workouts. When a client finishes a workout (séance) on Gymkee, the workout data includes an estimated calorie burn. This appears in the workout history.

Gymkee uses two different calculation methods depending on the type of activity.

Gymkee applies the standard MET formula:

Calories = MET x weight (kg) x duration (hours)

MET (Metabolic Equivalent of Task) is a research-backed measure of exercise intensity. Walking has a MET of about 3.8. Running ranges from 6.5 to 14.8 depending on speed. Gymkee assigns MET values from the Compendium of Physical Activities for over 75 activity types across 12 categories.

Each activity type has up to three intensity levels (Low, Moderate, High), each with a different MET value. Example: outdoor cycling uses MET 4.0 for Low, MET 8.0 for Moderate, and MET 12.0 for High.

The client's body weight is pulled from their profile. If no weight is recorded, Gymkee defaults to 70 kg.

Strength training calorie estimation is more complex. Gymkee uses a 4-layer priority waterfall:

The system tries each layer in order and uses the first valid result. This is entirely automatic.

When looking at a client's calorie data, it helps to understand where the numbers come from.

When a client logs an activity manually (tapping the + button and entering the type, duration, and intensity), calories are calculated using the MET formula. These estimates are solid for tracking trends, but they are formulas, not measurements. They depend on the client having their weight updated in their profile.

When activities sync from Apple Health or Google Health Connect, they arrive with calorie data from the wearable's sensors. This data uses real-time heart rate, motion, and the device's proprietary algorithms. It is generally more accurate than MET estimates, but the quality depends on the device and how it was worn.

You can distinguish the source in the activity detail. Gymkee tracks whether calories are estimated (MET formula) or measured (wearable import).

After a client completes a Gymkee workout, the calorie number is computed using the 4-layer system described above. The source of the final number depends on whether the client wears a connected device.

It is normal to see different calorie values from different sources. Here is why:

MET estimates vs. wearable data. The MET formula is a generalized population average. A wearable uses the individual's real-time heart rate and sensor data. The two will rarely match exactly. Differences of 10-30% are common and expected.

Different wearables, different algorithms. An Apple Watch and a Garmin may report different calorie numbers for the same workout. Each brand uses proprietary algorithms, different sensor configurations, and different calibration models.

Profile data gaps. If a client has not updated their weight, height, age, or gender, Gymkee uses defaults (70 kg, 175 cm, 30 years, male). This can cause significant over- or under-estimation for clients who differ from these defaults.

Intensity selection on manual logs. When clients log manually, the intensity they choose directly affects the MET value (and therefore the calorie estimate). A client who always selects "High" will have inflated numbers.

Calorie estimates are most valuable as relative measures. Compare the same client's data week-over-week. A 15% increase in weekly calories burned is meaningful, even if the absolute number is not perfectly accurate.

Pair calorie data with training volume, RPE ratings, and activity frequency for a fuller picture. A client burning fewer calories but reporting higher perceived effort may need a program adjustment.

If a client's calorie numbers seem unusually low, check their profile. A missing or outdated weight is the most common cause. Remind them to update it.

If numbers seem unusually high, check whether they are logging activities at the right intensity level. Some clients default to "High" for everything.

The weekly summary in the Activities tab gives you a quick snapshot of total activity volume (duration, calories, activity count). Use this during check-ins to discuss workload and recovery.

Clients who wear connected devices will have more complete and accurate calorie data. Clients who log manually will have MET estimates. Both are useful, but keep in mind the difference in precision when comparing across clients.

Why it happens: The client may not have completed any exercises during their workout (all sets skipped), or their profile has no weight data, or they are not logging activities at all.

How to fix it: Check the client's profile for weight data. Review whether they are completing sets during workouts. Encourage them to log activities or sync a wearable.

Why it happens: The client may be logging all activities at "High" intensity, or their profile weight is significantly higher than actual. For workouts, a very long session with heavy loads produces higher estimates.

How to fix it: Review the intensity selections on their recent activities. Check their profile weight. If the numbers come from a wearable, the data is likely accurate for that device.

Why it happens: The wearable app (Apple Health, Garmin Connect) includes both active and resting calories in its daily total, while Gymkee only shows active calories for individual activities. Also, different formulas and sensor configurations produce naturally different results.

How to fix it: This is expected. Explain to your client that differences between devices are normal. The important thing is tracking trends within the same source over time.

Why it happens: The weekly summary includes both external activities and completed Gymkee workouts. If you are only looking at the activity list, you may be missing the workout calories that are counted separately.

How to fix it: The weekly summary aggregates all sources. Review both the activities list and completed workouts for the full picture.

What is MET? MET (Metabolic Equivalent of Task) is a standard measure of exercise intensity. 1 MET = energy at rest. Higher MET = harder effort. Gymkee uses MET values from the Compendium of Physical Activities to estimate calories.

What formula does Gymkee use? For activities: Calories = MET x weight (kg) x duration (hours). For workouts: a multi-factor analysis that considers exercise types, load, rest periods, warm-up, tempo, EPOC, gender, and individual BMR correction.

Why do some activities show calories and others do not? Calorie estimation requires the client's weight. If no weight is set in the profile, manually logged activities may not display a calorie number. Imported activities from wearables usually include their own calorie data regardless of profile completeness.

Which wearables are supported? Gymkee syncs with any device that writes to Apple Health (iOS) or Google Health Connect (Android). This includes Apple Watch, Fitbit, Garmin, Samsung Galaxy Watch, Whoop, Polar, Suunto, Amazfit, COROS, Oura, and Xiaomi bands.

Can I edit a client's calorie data? No. Calorie data is calculated automatically by Gymkee or imported from the client's wearable. You cannot manually adjust calorie numbers.

What is the 70 kg default? If a client has not entered their weight in their profile, Gymkee uses 70 kg as a fallback for all MET-based calorie calculations. This is a common source of inaccuracy. Encourage clients to keep their weight updated.

What is the afterburn (EPOC) factor? EPOC (Excess Post-exercise Oxygen Consumption) represents the extra calories burned after intense exercise as the body recovers. Gymkee adds 10% to workout calorie estimates to account for this effect, based on published research.