To combine workouts, sleep, and nutrition in Apple Health, choose one primary writer for each category, grant only the required read and write permissions, verify source priority, and check a sample day for duplicates, missing intervals, timestamps, and units. Apple Health becomes the shared record; a dashboard such as Metric can then read the authorized categories and place them on one review timeline.
Editorial note
Published 2026-07-16. Last reviewed 2026-07-16. Evidence, interpretation, and Metric’s implementation are identified separately below.
Understand the three data paths
- Workouts: Apple Watch, another workout app, or compatible equipment can write workout records and related samples.
- Sleep: Apple Watch or another compatible sleep source can write sleep-analysis intervals and related measurements.
- Nutrition: a nutrition app or manual entry writes dietary energy and individual nutrient quantities. Apple Watch does not infer what you ate.
A reliable setup, step by step
- Choose the primary writer for workouts. If you record on Apple Watch, avoid having a second app create a duplicate workout for the same session.
- Choose the primary writer for sleep. Confirm the source records complete intervals on the nights you expect.
- Choose the nutrition logger you will actually use. Confirm whether it writes energy, macros, individual nutrients, or only keeps data inside its own database.
- Open each app in Health under your profile and enable only the categories required for the intended workflow.
- For each important category, open Data Sources & Access and place the intended source at the correct priority.
- Audit yesterday: compare the workout start and end time, sleep interval, meal timestamps, calorie units, and nutrient totals.
- Connect a dashboard only after the shared record is clean; otherwise it will summarize the same source errors more attractively.
What “combined” should and should not mean
Combined data should mean that records share a consistent timeline, units, provenance, and review surface. It can help you ask better questions: whether late meals often coincide with shorter sleep, whether protein logging is complete on strength days, or whether hard sessions cluster after several short nights.
It should not mean that temporal overlap proves cause. A late meal, short sleep, and elevated resting heart rate can occur together for many reasons. Use repeated patterns to form a question, then change one controllable behavior at a time when practical.
A practical weekly review
- Coverage: How many workouts, sleep periods, and meals were actually captured?
- Timing: Are sleep and meal timestamps in the correct day and time zone?
- Demand: Which workouts created the most duration or intensity?
- Support: Were energy and key nutrients logged consistently enough to interpret around demanding sessions?
- Recovery context: Did sleep duration and schedule remain stable as workout demand changed?
- Next experiment: What single, realistic behavior will you keep consistent for the coming week?
What official documentation supports
HealthKit explicitly supports workout, sleep, food, dietary-energy, and nutrient records. Apple also documents how users authorize apps and how Apple Health prioritizes multiple sources. That supports a shared-data workflow. It does not guarantee that every app writes every field, that records use identical definitions, or that a relationship among categories is causal.
How Metric combines the domains
Metric reads authorized workout and sleep histories and provides nutrition capture and editing. It can present these domains in one app and use them as context for trends and Cortex conversations. Users should still treat nutrition completeness as an input-quality question and should inspect Apple Health when a workout or sleep period looks missing or duplicated.
Common failure modes
- Two apps write the same workout, inflating duration or active energy.
- A sleep app and Apple Watch both contribute overlapping intervals with different stage labels.
- A nutrition app writes calories but not macros or micronutrients expected by the dashboard.
- Serving sizes or unit conversions make a meal total implausible.
- Travel or time-zone changes place a meal or sleep period on the wrong day.
- Read access was denied, so the dashboard sees an empty category and cannot distinguish it from no data.
Limitations
Nutrition logging is inherently incomplete when meals are missed or portions are estimated. Wearable sleep is also estimated, and workout energy depends on personal settings and sensor conditions. Combining the records improves context; it does not remove uncertainty from any input.
Sources and further reading
- Apple Developer Documentation (2026): HealthKitHealthKit is the permission-controlled repository through which apps read and write health and fitness data.
- Apple Developer Documentation (2026): HealthKit data typesDefines HealthKit records for heart rate, resting heart rate, HRV (SDNN), sleep, workouts, nutrition, oxygen saturation, respiratory rate, and other categories.
- Apple Support (2026): Manage Health data on your iPhone, iPad, or Apple WatchExplains manual entry, compatible apps, source priority, permissions, and how multiple sources contribute to Apple Health.
- Apple Support (2026): Track your sleep on Apple Watch and use Sleep on iPhoneExplains sleep setup, sleep stages, sleep score inputs, historical views, and fit/battery limitations.
Continue exploring
- Nutrition and recovery
- Apple Health dashboard
- What data Apple Watch collects
- Interpret HRV, RHR, and sleep
Health information disclaimer
Metric is a wellness product. This article is educational and does not provide medical advice, diagnosis, or treatment. Wearable measurements and app-generated scores are estimates; discuss symptoms, unusual readings, medication effects, and changes to a care or training plan with an appropriate healthcare professional.