How the data actually reaches an app
Worth understanding, because it explains nearly every problem you will encounter.
Your Apple Watch measures heart rate and stores samples locally. It syncs to the iPhone over Bluetooth or Wi-Fi, where they land in the Health database. Third-party apps never talk to the watch directly — they request read access to Health, and Health hands over what it holds.
Three consequences follow. If the watch has not synced, the app cannot see recent readings no matter what it does. If you deny Health permission, the app sees nothing and cannot tell you why in any detail, because iOS deliberately does not reveal whether data exists but is withheld. And no app can make the watch sample more often — that is controlled by watchOS.
Granting the right permissions
On first launch the app requests Health access. iOS shows a per-data-type list with everything off by default. You must actively enable Heart Rate — tapping "Allow" without toggling the individual type grants nothing, which is the single most common cause of an empty chart.
To review or change it later: Settings → Health → Data Access & Devices, pick the app, and check what is enabled. You can also go through Health → Sharing → Apps.
A calendar-aware app will separately ask for Calendar access. These are independent permissions — granting one does not grant the other. Both are read-only for this purpose; neither needs write access.
Why your chart might look empty or patchy
- Heart Rate not individually enabled. Check the per-type toggle, not just whether the app appears in the list.
- Watch has not synced. Keep the watch near the unlocked iPhone for a few minutes. Sync is opportunistic, not instant.
- Watch worn loosely. The optical sensor needs skin contact. A loose band produces missing samples rather than wrong ones.
- Wrist detection off. With it disabled, background heart rate sampling stops entirely.
- Low Power Mode. Reduces or suspends background heart rate measurement.
- Tattoos or very dark skin tone over the sensor area. Optical sensing can struggle with certain ink and pigmentation, producing gaps. This is a known hardware limitation, not a setup error.
- Gaps are normal anyway. Outside workouts the watch samples periodically, so an uneven chart is expected rather than broken.
Getting more readings, legitimately
You cannot force a sampling interval, but you can improve coverage. Wear the watch snugly and high enough on the wrist that the sensor stays in contact. Keep wrist detection enabled. Avoid Low Power Mode during periods you care about. And starting a workout — even a "Other" walking session during a meeting-heavy afternoon — switches the watch to frequent sampling, which is the only reliable way to get dense data for a specific window.
What the pairing actually reveals
Once both sources line up, the useful patterns are recurring rather than individual. A single elevated meeting means little. The same meeting elevated across six weeks is a real signal.
Common findings people report: anticipation showing up before an event rather than during it, recovery taking longer after some interactions than others, and back-to-back scheduling producing sustained elevation with no return to baseline between items. The last is the most actionable, because the fix is a calendar change rather than a personal one.
Privacy worth checking once
Heart rate plus calendar is a detailed picture of your working life. Check the app's App Store privacy label and whether processing happens on-device. An app of this kind has no need to transmit health data anywhere, so any transmission should be explicit and explained.
Where 70 BPM fits
70 BPM reads heart rate from Apple Health and lays it across your day so you can scrub into specific periods and see the zones in context. Free on the App Store, for iPhone and Apple Watch.
70 BPM displays data Apple Health already holds. It is not a medical device and cannot diagnose anything. If a pattern worries you, or you notice symptoms alongside it, speak to a doctor rather than an app.