Best practice for active/inactive seasons

Hi Shelly! I'll be curious to see what advice the community provides. Here at Tessitura, this is what we recommend:

Inactivate or close the following items in order to improve the efficiency of Analytics and certain database processes. Inactive or closed items remain fully available for reporting.

• Seasons – Inactivate after all performances are past, and any outstanding transactions are settled. It is possible to make new transactions for performances and fees in inactive seasons.
• Campaigns – Close after the campaign end date, and the campaign is financially reconciled. It is possible to make new payments on existing pledges associated with closed campaigns, but new contributions cannot be entered. It is possible to make new ticketing transactions for products associated with closed campaigns.
• Appeals – Close after you are finished recording responses to the sources associated with the appeal. Transactions cannot be recorded to sources associated with a closed appeal.

We inactivate campaigns yearly.  Seasons-we have a couple reports that only show active seasons in the parameter selection (probably custom reports-so you probably wouldn't have this problem) for this reason I leave the most recent past season active until I create the next season, so two are active at a time.

Thank MFW! I have been looking for this written explicitly every year for a while and never think to ask when I have the opportunity. I wonder if there is somewhere in the documentation where (if it doesn't already exist) it could state that pledge payments can continue after closing campaigns/appeals. 

I think the End of Fiscal Year (Annual) Checklist might be of help (the above is from the Ticketing & Admissions section) - it has entries on Pledges in there (but it doesn't elaborate on keeping them open)

Accompanying video is https://www.tessituranetwork.com/en/Items/Videos/Training/End_of_Fiscal_Year