Snapdragyn
Well-known member

My personal list uses such an approach. I chose dates with the aim of minimizing taxonomic while connecting date thresholds to geological time periods. I won't say this was the 'best' approach, but it was simply very easy to find dates to consider that way.
With orders set at roughly* 66 MYA, I end up w/ 45 orders.
With families set at roughly* 23 MYA, I end up w/ 603 families.
Gotta head to work now, but if anyone is interested I can do a similar 'change by group' list later. I know most of the family increase on my list comes in the non-passerines; there are a LOT of clades there far older than some of the ridiculous (IMO) 9-primaried oscine 'families' (some of which are only tribes in my list).
* I took a somewhat different approach than you on the 'soft/hard limit' issue. For me, anything below <rank threshold> could NOT be that rank. Anything between the threshold & 1/4 of the time to the threshold above could be the rank, but didn't have to be. If, for example, there were multiple branches in a clade all falling within that 'soft zone', I might split the 1st branch at the relevant rank while demoting the next branch to the next lower rank (especially if there otherwise would be no splits at that next lower rank). I felt this fuzzy approach at times allowed for a better reflection of clade branching within the list.
With orders set at roughly* 66 MYA, I end up w/ 45 orders.
With families set at roughly* 23 MYA, I end up w/ 603 families.
Gotta head to work now, but if anyone is interested I can do a similar 'change by group' list later. I know most of the family increase on my list comes in the non-passerines; there are a LOT of clades there far older than some of the ridiculous (IMO) 9-primaried oscine 'families' (some of which are only tribes in my list).
* I took a somewhat different approach than you on the 'soft/hard limit' issue. For me, anything below <rank threshold> could NOT be that rank. Anything between the threshold & 1/4 of the time to the threshold above could be the rank, but didn't have to be. If, for example, there were multiple branches in a clade all falling within that 'soft zone', I might split the 1st branch at the relevant rank while demoting the next branch to the next lower rank (especially if there otherwise would be no splits at that next lower rank). I felt this fuzzy approach at times allowed for a better reflection of clade branching within the list.