PMM best-practice questions

Hi all, curious about a few things and wondering if the collective wisdom of the Hub has some best practices to share.

1. Downsides to creating new Program records annually. I do understand how cohorts could be used to make this distinction; however where there are clear start/stop dates (summer classes for example), Service Schedule really (in my mind) should be the child of Program Cohort, and I want to see what Services are offered to each Cohort as well as that may change over time (A,B,C offerings last year, but this year A,B,D,E,F are available). Clearly I can move page layouts around and create additional relationships (or even objects), but wondering if other folks have gone the route of creating unique Program records. The main downside I see is that you would need to ensure units of measurement stay the same YoY, and create a way to bundle together Service records for reporting (i.e., I want to view a report that aggregates all "After School Enrichment" (Service) days attended and have separate records for a 2021 and 2022 Program). This could either be a picklist (Type = After School Enrichment) or separate object (meta-'Service').

I am a bit leery of diverting from the recommended data model; at the same time, a more seasonal model where programs change and evolve over time seems to argue for distinct Program records to better view those changes. Would love thoughts on this.

2. Downsides to offering the same Service in multiple Programs. See reporting consideration above (want to lump Service Deliveries together for reporting although Services might be different records). Use case/example - offering a comprehensive education support program that includes after school enrichment classes, one-on-one tutoring, and after-school meals. I also want to offer paid tutoring as a standalone service, not considering it part of education support program. So a blend of people who are participating in a service (tutoring) but in different contexts. A fair bit to unpack here, but it seems like either an additional Cohort-type object(s) that could provide cross-Program grouping or duplicate Services in different programs would get the reporting I'm looking for. Leaning towards the latter, but again - curious to hear what others think.

3. Events that are part program service offering part fundraiser. Campaign or Service Session? Or both? Lots of nuance to unpack and good arguments in both directions but curious from both a data architecture/reporting perspective as well as staff usability (knowing what object to create when).

Thanks all