diff --git a/CHANGELOG.md b/CHANGELOG.md
index 610b96b5..c589e20e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- `passenger_events.event_count` description clarified to specify when values > 1 are appropriate, direct aggregated APC data to stop_visits, and clarify that 0 is distinct from null ([#236](https://github.com/TIDES-transit/TIDES/issues/236))
+
 ## [1.0] - 2025-12-23
 
 ### Changed
diff --git a/spec/passenger_events.schema.json b/spec/passenger_events.schema.json
index 0e91a7e3..699e19b5 100644
--- a/spec/passenger_events.schema.json
+++ b/spec/passenger_events.schema.json
@@ -132,7 +132,7 @@
       "name": "event_count",
       "type": "integer",
       "title": "Event count",
-      "description": "Count for this event, e.g., 3 for a Passenger Boarding event with 3 boardings, default is  `1`",
+      "description": "Count for this event. Default is `1`. Use values > 1 only for truly simultaneous events (e.g., a parent carrying a child through a doorway as a single boarding event). Aggregated APC counts (e.g., '6 passengers boarded at this stop') should be recorded in stop_visits, not passenger_events, since passenger_events is intended for discrete, instantaneous events. A value of `0` indicates that the event was recorded but no passengers were counted (e.g., door opened but no one boarded), which is distinct from null/missing data.",
       "constraints": {
         "minimum": 0
       }