IT operations workflow for Tallyfy

Plan system upgrades that minimize downtime

Poorly planned upgrades cause outages and frustrated users. This 2-4 week workflow covers identification of what needs upgrading, timeline planning around business-critical periods, budget approval, execution with rollback plans, and post-upgrade review.

6 steps

2 automations

Import into Tallyfy Preview steps

Cloud Services upgrade

Run this workflow in Tallyfy

Import this template into Tallyfy and assign to your IT operations team with deadlines spread across the upgrade cycle for identification, planning, budgeting, execution, and review

Configure Tallyfy automations to notify stakeholders when maintenance windows are scheduled and alert teams when rollback procedures may be needed during execution

Track every upgrade in Tallyfy with documented lessons learned, updated warranty and support end dates, and new items added to the maintenance schedule

Import this template into Tallyfy

Process steps

Software upgrade schedule steps

2 days from previous step

task

Here's how to schedule your software upgrade:

Go to Settings
Software update
Scheduled software update and set the time you want the update done

Identify what needs upgrading

3 days from previous step

task

Go through your hardware, software, and systems and look at age and performance. What's out of support? What's causing problems? Rank your list by risk and business impact so you know where to focus first.

Plan the upgrade timeline

5 days from previous step

task

Decide when each upgrade should happen. Factor in your budget cycles, any business-critical periods you need to avoid, and which systems depend on each other. Build in buffer time -- upgrades rarely go exactly as planned.

Budget and approve

7 days from previous step

task

Work out the costs for each upgrade -- licenses, hardware, labor, and training. Get budget approval before you commit to anything. If you're dealing with larger upgrades, you may need to spread the funding across phases.

Execute upgrades

14 days from previous step

task

Follow your change management process step by step. Test before you deploy, and make sure your rollback plan is ready to go if something breaks. Let affected users know what's happening and when, and document everything you do along the way.

Review and update schedule

21 days from previous step

task

After each upgrade, take time to capture what you learned. Add new items to the schedule as they come up, and make sure you're tracking warranty and support end dates so nothing catches you off guard.