Allow each club to determine what works best for them, with respect to when a meeting becomes a "past meeting". Make it a club-specific parameter, maybe a "delta" from the meeting start time, which each club can configure to meet that club's needs and can reconfigure, when the club's needs change, and allowing "delta" to be pretty much any value, even negative values. (That's just the first approach that popped into my head. I'm sure there are others.)
Those who want "past meeting" to be when the meeting starts could set "delta" to 0 hours 0 minutes.
Those who want the "past meeting" to be midnight could... examples:
meetings start at 10:30 AM, set "delta" to 13 hours 30 minutes
meetings start at Noon, set "delta" set to 12 hours 0 minutes
meetings start at 7:00 PM, set "delta" to 5 hours 0 minutes
Those who want "past meeting" to be when a typical meeting ends would set "delta" to, say, 1 hour 30 minutes.
Those who want to "lock down" their agendas BEFORE their meetings start could set "delta" to a negative value, say, -2 hours 0 minutes --- or even -24 hours 0 minutes if they want to "lock down" agendas one day in advance.
Yes, an approach like this would result in inconsistency, from club to club, in "when a meeting becomes a past meeting". But, each club IS different, as reflected by the diversity of opinions expressed on this topic.
On the other hand, I do understand that it might be awkward or difficult to implement a club-specific parameterized solution, depending on the existing software architecture. I don't know the slightest thing about the guts of FTH, so if you awesome volunteers say it's not a reasonably feasible approach, the rest of us just have to accept that.
As far as the potential for confusion that a parameterized solution could cause, I hear you. On the other hand, despite years of administering club websites, I freely admit that I remain befuddled by certain FTH features. There's plenty of confusing features already. What's one more?
Sue Worden DTM
Club 311 et.al.