How to pick a representative count day for a capacity study

Pick a day that looks like every other Tuesday on that corridor, and your count holds up when someone questions the capacity analysis six months later. Pick a Friday before a long weekend, or a Wednesday during spring break, and you've baked a one-time anomaly into a number that drives a signal-timing decision for years.
The Tuesday-through-Thursday default exists for a reason
Most agencies default to Tuesday, Wednesday, or Thursday because Monday carries weekend recovery traffic and Friday carries early-leaver traffic heading into the weekend. The three middle days settle into something close to average for commute patterns, school traffic, and retail trips. If your corridor serves a school, a hospital shift change, or a weekly market day, check whether that pattern falls on one of those three days before you commit to a date.
School in session, or not, changes everything
A count taken during the first week of school or the week before winter break isn't representative, even if it falls on a Tuesday. Families change routes, buses run on altered schedules, and drop-off and pickup traffic compress into tighter peaks than normal. Pull the district calendar before you schedule anything. If a school sits along the corridor, aim for a stretch where school has been in full session for at least two or three weeks, not the first Tuesday back from a break.
Holidays skew in both directions
Most capacity studies skip the Tuesday after Thanksgiving on reflex. Fewer people think about the week before a three-day weekend, when some trips get pulled forward, or the week after, when errands and deliveries get pushed back to catch up. State and local holiday calendars, plus any festival or event that closes a lane or draws a crowd nearby, should rule out a date before it ever gets scheduled. If you're not sure, check the local events calendar for anything within a half mile of the corridor on your target date.
Weather, construction, and the stuff that doesn't show up on a calendar
Calendar-driven skew is the easy half of the problem, and the other half is whatever happened that specific day. A water main break two blocks over. A tournament that filled a parking lot and rerouted drop-off traffic. Rain heavy enough to push some trips to transit. None of that shows up when you schedule a count three weeks out. It shows up later, when you look at the raw data or the field notes and ask whether anything looks off for a plain Tuesday in April.
What this means for links nobody has instrumented
A link without a permanent counter still needs a count day picked with the same discipline, arguably more, since there's no baseline to catch an anomaly against. The hard part on these links is the field work: laying tubes or installing a sensor on a segment nobody has budgeted a crew for. Vehicle Counting handles that piece directly. Once you've picked the day, a single scheduled pass over the corridor gets detected and counted, delivered as a CSV by link and direction with the frame it came from.
Quick checklist before you lock in a date
- Tuesday, Wednesday, or Thursday, unless the corridor has a non-commute pattern that argues for a different day
- School in full session, at least two weeks clear of a break on either side
- No federal, state, or local holiday within three days
- No known construction, event, or lane closure on or near the corridor
- Forecast that looks like a normal day for the season, not a named storm or an extreme heat advisory
Get the day right and everything downstream, the LOS calculation, the signal-timing recommendation, the capacity justification sitting in a grant application, rests on a number that actually represents the corridor instead of one bad Tuesday. Once you've locked in the date, counting the segment itself doesn't have to mean a lane closure or a crew laying tubes.