Do you annually recreate some projects so you can update for the new year, like 2023 Marketing Requests? Or even worse, frequently recreate monthly or weekly projects, for example, Week 24 Dev Sprint?
Stop that! (I’ll explain . . .)
For ongoing process projects, like a marketing or operation team’s workstream, where work flows in, is actioned, then completed only to be replaced by more work, there’s a simple tweak you can make to simplify and clarify.
Just recast that project instead as “evergreen.” Remove the year (or month or week) from the name and just call it Marketing Requests (or Current Marketing Requests if you prefer).
If you think that “renaming a project” is not much of Forum Leader Tip, well consider that it has just saved you from having to update all reporting dashboards, saved search reports, portfolios, the project URL itself which may be in bookmarks, intranets, and emails, and who knows what else by effectively making something static that you previously changed regularly.
You may have noticed there’s a catch, unless you have very low volume: Your evergreen project will grow and grow, and you might want to age tasks from it annually, say, both to keep performance fast and perhaps to make reporting easier too.
You can annually create 202x Marketing Requests aging project, or even just a single Marketing Requests Archive to hold the aged off tasks. Either sort+filter the project or use advanced search within the project to group and multi-select (in batches of 50) the completed tasks to be aged off by re-homing them (replacing the project membership) to the aging project. Having batches of tasks already in separate aging projects may simplify reporting and metrics.
By having evergreen projects, the more frequent, day-to-day active-oriented searches and reporting needs are now streamlined.