
Yes and those cases where multiple subspecies overlap usually show up in the filters, although some still need to be searched for. One example being Volcano Hummingbird, when they do their non-breeding dispersal and torridus individuals show up on the volcanoes of the cordillera central that was not previously displaying by default and you had to search all birds to find any of the subspecies, but aff after I kept reporting those to ssp. level they updated the filters.You are probably right that the majority can be assumed, but there must be a few more examples from Costa Rica where this is not the case - Yellow Warbler (Northern) and Yellow Warbler (Mangrove)? There was an recent article in British Birds that made the case for us all being more interested in subspecies - a subspecies at a strange location or at a strange time of year, of no less impressive than a species - just we can't tick it. And I thought the whole point of EBird Groups (we are not really recording to subspecies level) was based on identifiable taxa, so is there a reason we should abandon the use?
I am surprised that the reviewers configure the filters. So how does this get passed back up into the filters in the phone app, or is this why spurious races can be selected at time of input?
I would suggest that reviewers should be encourages to properly set the filters - they will be be helping themselves in the long run, and protecting themselves from being swamped by records from annoying people like me that try to use the groups, even when common and expected.
Conversely, I live on the Caribbean side where Scarlet-rumped Tanager occurs and the subspecies does show up in eBird (Passerini's). But that's the subspecies to be expected so listing it to subspecies level doesn't really add much useful data. If I saw an out of range Cherrie's then listing the subspecies would be useful data.