Maintenance of library technology systems is a continual challenge and not always front and centre in technology planning. We know each year that our various systems will require maintenance and upkeep, but our planning efforts may focus on the upcoming new projects, developments, and deployments as opposed to maintenance activities. This can leave technology units feeling squeezed and relegate the maintenance of existing systems to an afterthought. This presentation will discuss an analysis project we undertook to address this issue. To understand the existing ‘maintenance load’ of our library’s systems, we reviewed all past tickets in our JIRA tracking system over the course of a year. Tickets were grouped by system (e.g., institutional repository) and then roughly coded to see what percentage went to maintenance versus the development of new applications or improvements. This helped provide a clearer picture of the maintenance load of each system. Using that as a baseline, we were able to plan for the coming year’s general maintenance efforts and determine which activities should take place in each quarter of the year. By determining how much resources and time was needed for maintenance and when, we were able to better anticipate how much time was available for new projects and developments. We hope these planning efforts will reduce staff stress, project overruns, and provide a more accurate picture of our unit’s capacity over a year. Additionally, this exercise highlighted how we track and document JIRA tickets, improving our categorization for future analyses. This presentation will discuss this method of project planning, how it has been working so far, and anticipated future improvements for next year.