Apple Walking Steadiness Event

  • UnitNone
  • SinceiOS 15.0 (2021)
  • KindCategory

By PulsHealth. Updated

Research reviewed .

What does a Walking Steadiness notification mean?

A Walking Steadiness event records a notification associated with a Low or Very Low walking-steadiness classification. It is a category entry, rather than a gait score or a record of a physical fall. The underlying Walking Steadiness quantity is a separate type that provides the score history.

Apple uses motion measurements from an iPhone carried near the waist to assess walking steadiness. Phone carry and sufficient walking observations affect coverage. A notification can be a useful prompt to discuss balance and fall prevention, but the code does not diagnose the cause of unsteadiness or establish that an emergency has occurred.

How do the four event values differ?

Stored valueMeaning
1: initialLowInitial notification for a Low classification
2: initialVeryLowInitial notification for a Very Low classification
3: repeatLowReminder while a Low classification persists
4: repeatVeryLowReminder while a Very Low classification persists

The numbers identify categories; averaging them or treating 4 as twice the risk of 2 is not meaningful. A repeat notification is not another fall, and an initial notification is not necessarily the first day that walking quality changed.

Why are notifications much less frequent than scores?

Apple's developer presentation describes initial notifications about a month after entering a Low or Very Low classification, with repeat notifications about every three months while the classification persists. This is notification behavior, not a fixed cadence for every exported record. The same presentation describes weekly Walking Steadiness scores.

As a result, the time between event entries is not the time between gait measurements. It is also not a measure of how frequently instability occurred. Notification settings, phone carry and unavailable measurements can create gaps. No event entries cannot establish an OK classification or show that a fall will not happen.

How should events be read alongside other mobility data?

Review the separate Walking Steadiness score history, source coverage and changes in walking speed or other gait measures. Describe how many measurements were available in the comparison window. A nearby score is a temporal neighbor; without explicit linkage it cannot be assumed to be the exact score that triggered the notification.

An event timestamp does not establish when walking quality changed. Its stored start-to-end span should not be treated as the duration of a balance problem. The event is a summary notification about classification history.

What can the available example data tell us?

No Walking Steadiness event entries were available in the reviewed reporting-year snapshot. There is therefore no measured notification cadence, category distribution or event-linked mobility comparison to plot here. This says nothing about whether notifications were enabled or whether the underlying score was normal.

<details> <summary>Developer and recording details</summary>

This is a read-only category type with four defined values. Request authorization for the event separately from the score quantity. Keep initial and repeat notifications distinct, and retain source and timestamp provenance. The identifier does not promise a percentile, an exact triggering score or type-specific metadata keys. The iPhone-based assessment should not be described as an Apple Watch replacement for missing phone observations.

</details>

Understanding your records

Recording frequency, source and coverage affect what you can conclude from this data. Read the recording guide.

One record
A read-only category notification for initial or persistent Low/Very Low classification.
Frequency
Notification cadence differs from score cadence; Apple documents approximate initial and repeat delays.
Context
Timestamp overlap does not identify an actual fall or the time of a gait change.
Coverage and gaps
No raw records in the verified reporting-year snapshot; measured distributions and paired relationships are unavailable.
Summaries
Count notifications by category; counts have no monitored-time denominator.
Metadata
Producer-specific metadata requires a documented contract; no type-specific keys are promised here.

Recording guidance reviewed 2026-10-14

Technical details
IdentifierHKCategoryTypeIdentifierAppleWalkingSteadinessEvent
SourceHealthKit
AggregationNone
Availability
iOS 15.0 (2021)
watchOS 8.0 (2021)
Last updated: 2026-10-14

Related Metrics