Field note 12 · Training inputs
Before You Trust a Workout Calorie Estimate, Check the Minutes
An estimate can look precise while using the wrong minutes. Check the duration, its source and its definition before deciding what the calorie number means.
The number underneath the calorie number
A workout estimate says 360 kcal. Before deciding whether that sounds reasonable, open the underlying entry. Does it describe the activity you did? Does it contain the duration you intended? Do those minutes represent the whole appointment, the recorded session or only the active part?
This is a useful first check because an estimate can be neatly presented while answering a different question. If its duration was guessed, changing the display to a more precise-looking calorie number does not make the missing input known.
The practical rule: establish where the minutes came from before interpreting what the calories mean. A duration check can identify an input mismatch; it cannot independently validate energy expenditure.
Four kinds of duration that should not look identical
A saved number alone does not tell you how it was obtained. Keep these four states separate when reviewing a generated workout entry.
| State | What it means | Your next check |
|---|---|---|
| Entered | You supplied a duration, or a named device supplied a recorded duration. | Confirm the saved value, unit and definition match that source. |
| Inferred | A system interpreted a duration from text, such as “half an hour.” | Compare the interpretation with the original wording and any pauses. |
| Assumed | A duration was supplied without evidence of how long this particular session lasted. | Replace it with a known duration where possible; otherwise retain the uncertainty. |
| Missing | The relevant duration is unavailable. | Do not translate “not recorded” into zero minutes or a typical session length. |
These are evidence labels, not a ranking of people’s record-keeping. A device-recorded duration also needs a definition: a timer left running through a break and a timer paused during that break need not describe the same interval.
What prompted this checklist
In a technical review of Nutrinaut’s training data path, we traced how submitted workout information becomes an AI result and then a saved diary entry. The inspected path accepts duration as an input; when duration is unknown, an estimate can include an assumed value. The stored result does not, by itself, reliably establish whether its minutes were entered, inferred or assumed.
That is a reason to expose provenance and verify the final entry, not evidence that every generated estimate is wrong. A saved short title is also not necessarily the original description: a generated summary cannot reconstruct all the details of the request that produced it.
This was a source-and-data-handling review, not an independent calorie-accuracy benchmark. It does not measure the effectiveness of training or establish how much energy an individual used.
Two examples you can check without trusting a model
Example 1: 1 hour 30 minutes is not 1.30 hours
Invented example, not a user record: you mean a 90-minute ride. A form expects decimal hours, and you enter 1.30. If interpreted as a decimal, that is 1.3 × 60 = 78 minutes, not 90.
1.30 decimal hours = 78 min
The difference is 12 minutes. The correction is to use the field’s stated format, then inspect the saved duration. Do not “fix” the calorie figure manually while leaving the mismatched duration underneath it. If the field is in minutes, enter 90.
Example 2: a long visit is not necessarily a long active session
Invented example: a gym visit lasts 70 minutes, including a 20-minute break. A paused-timer record contains 50 active minutes. Another screen shows the 70-minute elapsed interval. Both can describe the visit, but their definitions differ.
For a deliberately simplified arithmetic demonstration only, suppose a calculation uses a fixed, invented rate of 6 kcal per minute:
70 × 6 = 420 kcal
Those are not estimates of anyone’s actual workout. Real calculations need not use a fixed rate. The example shows why changing the meaning of “minutes” changes the question being calculated. Identify the intended interval before comparing results.
Apple’s HealthKit documentation makes this distinction concrete: workout duration can come from a start-to-end interval, an explicitly supplied value or active duration calculated using workout events. That does not establish how every connected app displays it. Apple’s duration documentation.
A one-minute check of the saved entry
- Minutes and unit: compare the saved value with your original input or source record. Check minutes versus hours and decimal versus clock notation.
- Interval: establish whether the value includes pauses, warm-up, cool-down or time outside the session. If the definition is not shown, note that rather than guessing.
- Activity: confirm the saved category and description still identify what you meant. A concise AI title may omit useful context.
- Origin: distinguish device-recorded, self-reported, inferred and assumed information. A plausible value is not proof of its origin.
- Diary day: check the intended date, particularly for late entries or travel. When a result arrives is not necessarily when the workout happened.
If you edit an entry, check it again after saving or reanalysis. Compare the final record rather than assuming an edit on one screen propagated everywhere. Preserve the original source when a discrepancy needs investigation.
Then check which calories you are comparing
Even matching durations do not make unlike calorie fields equivalent. Garmin distinguishes daily active calories from resting calories and defines activity calories as including both active and resting calories during a recorded activity. Read the actual label rather than comparing two numbers merely because both say “calories.” Garmin’s calorie definitions.
A daily activity summary is also not automatically an additional workout. Avoid adding overlapping summaries and sessions. The wearable source checklist explains how to separate the source, coverage window and individual observation.
For calendar questions, continue with One Night, Two Dates. For a generated recommendation, use the AI evidence card. Correcting minutes improves the description of the input; it does not turn an estimate into a measurement or justify a nutrition prescription.
Keep this short record
Activity: ____ Intended diary date: ____
Duration and unit: ____ Includes pauses? ____
Source or original wording: ____
Saved duration matches? ____ Unresolved detail: ____
A useful outcome can be “duration confirmed, calorie method unverified.” You do not need to resolve every unknown to avoid treating one unknown as a fact.
Sources and scope
The examples are constructed arithmetic demonstrations, not private user records, device tests or a recommended calorie rate. Technical observations refer to the Nutrinaut path inspected on 10 October 2026, not every historical record or platform version.
- Apple Developer Documentation: HKWorkout duration — the possible duration definitions, not calorie accuracy.
- Garmin Support: tracking calories and calorie terminology — Garmin’s categories, not a universal definition for every app.
- Nutrinaut Connections & Data Guide — connection scope and source checks.