The Checklist to Run After Any iOS Update

Published August 28, 2026 · Last reviewed September 2, 2026

The checklist

1. Privacy & Security — confirm Tracking is still off, check Location Services for apps moved back to Always, and look for permission categories that did not exist before.
2. Notifications — look for apps that were re-enabled and for any new system app added by the update.
3. iCloud — open Settings, tap your name, then iCloud, and confirm no new sync category was switched on by default.
4. New features — read the release notes and decide deliberately about anything on by default rather than discovering it a month later.
5. Backup — run a manual backup so your first backup on the new version exists.
6. Focus and Screen Time — confirm schedules and limits survived, since these occasionally need reconfiguring after a major release.

Why battery looks worse for a few days

After a major update, iOS rebuilds indexes: Spotlight re-indexes files and mail, Photos re-analyses the library for search and faces, and apps migrate their data formats. All of this runs in the background, uses the processor heavily, and is finite. It typically settles within three to five days.

Judging battery life on day one is the single most common post-update mistake, and it causes people to change settings, restore devices, and occasionally buy new phones in response to a temporary condition. Wait, then measure. If drain is still bad after a week, work the per-app battery breakdown — by then the numbers mean something.

What to check specifically

Action

Re-check Location Services for any app that moved from While Using to Always.

Why it helps

Major releases occasionally reset or re-prompt permissions, and an app returning to background location is both a privacy and a battery cost.

Verification

Only Find My and any deliberate exception show as Always.

Action

Look for new permission categories introduced by the update.

Why it helps

New iOS versions sometimes add a permission type, and existing apps may be granted a default that you would not have chosen.

Verification

Every category in Privacy & Security contains only apps you would deliberately allow.

Action

Read the release notes for features that are on by default, and turn off anything you do not want.

Why it helps

Deciding deliberately once is far better than discovering a new behaviour weeks later and not knowing what changed.

Verification

You can name what the update added and what you chose to disable.

Action

Run a manual backup immediately after updating.

Why it helps

Your existing backups were taken on the previous version; a fresh one gives you a restore point on the version you are now running.

Verification

Last Successful Backup shows a time after the update completed.

Action

Test one thing you rely on — a work app, a car connection, a hearing aid, a payment card.

Why it helps

Compatibility problems are easier to deal with when found deliberately than when discovered at a bad moment.

Verification

Each critical function works as before.

If something broke

1. Restart the phone. A surprising share of post-update oddities resolve here.
2. Update your apps. Developers often ship compatibility fixes within days of a major release.
3. Wait for the first point release, which typically arrives within a couple of weeks and addresses the most-reported problems.
4. Report it to the app developer and to Apple, since problems that are not reported are not prioritised.

Downgrading is generally not possible after a release, because Apple stops signing the previous version shortly afterwards. This is exactly why the backup before a major update matters, and why waiting a week or two on a major release is a reasonable strategy rather than timidity.

Make it a habit worth keeping

Ten minutes, four or five times a year. The value is not that any single check finds something dramatic — usually nothing is wrong. It is that you stay aware of what your phone is doing, rather than accumulating years of defaults nobody chose.

How it works

A major iOS update does three things that all cost energy and time. It migrates data formats, converting app databases and system stores to whatever the new version expects. It rebuilds indexes, so Spotlight can search your files and Photos can search your library by content and by face. And it re-optimises installed apps for the new runtime. All of this is background work with a finite end, which is why battery and warmth are temporarily worse and why the effect disappears without intervention.

Settings behave inconsistently across updates for a structural reason: a new iOS version can introduce permission categories that did not exist when your preferences were set. There is no previous answer for the system to carry forward, so it applies a default. That default is chosen to be reasonable, but it is not your decision — which is precisely why a review after each release is worth ten minutes.

The inability to downgrade follows from the signing model. iOS will only install a version Apple is actively signing, and signing for the previous release stops shortly after a new one ships. That makes a major update effectively irreversible, and it is the entire reason the pre-update backup is the one precaution that genuinely matters — a backup can restore your data onto the new version, but nothing can restore the old version itself.

Worked example

Ten minutes after a major release, on a phone whose owner had carefully configured privacy settings a year earlier.

Three findings. Location Services shows a food-delivery app back on Always, having been set to While Using the App previously — it re-prompted during the post-update setup flow and was tapped through while the owner was skimming. It is moved back. Notifications shows two newly added system apps enabled by default and one third-party app whose alerts were re-enabled; all three are switched off. Under iCloud, a new sync category introduced by this release is on by default; the owner reads what it does and decides to leave it on, which is the point — a decision rather than a default.

Tracking is unchanged and still off, and Focus schedules survived intact. A manual backup is run and confirmed. A CarPlay connection and a work chat app are both tested and work.

Over the following days, battery drain is visibly worse: the phone reaches 20% by 16:00 rather than 21:00, and the back is warm. No settings are changed and nothing is restored. By day four it is back to normal, because Photos had finished re-analysing 34,000 images and Spotlight had finished reindexing. The owner of an identical phone in the same household, who reacted on day two by resetting all settings and restoring from a backup, arrived at the same battery life two days later after considerably more work.