Use Screen Time to identify one pattern you want to understand, then add context before deciding what to change. A total number of hours cannot explain whether you were navigating somewhere, finishing work, talking with someone you care about, or scrolling longer than you intended.
This review is a practical reflection exercise. Screen Time is not a diagnosis, a measure of your worth, or a score of recovery. There is no target number in this worksheet that everyone is supposed to achieve.
Open a report and choose its scope
On iOS 26, open Settings → Screen Time → See All App & Website Activity. Use Devices to choose the device you want to review, then select Week or Day. Apple describes reports covering app and website time, pickups, and notifications. If activity reporting is not enabled, turn on App & Website Activity in Screen Time first; allow a useful observation period before drawing conclusions. Apple's Screen Time guide.
Apple also documents Share Across Devices, which can combine usage and share Screen Time settings across compatible devices using the same Apple Account. Confirm the report's device scope before comparing periods. Apple's cross-device reporting explanation. For a different iOS version, use Apple's version selector rather than assuming the menu is identical.
Make a fair comparison
Write down exactly what you are comparing: this iPhone during two completed weeks, or the same part of two comparable days. Comparing an unfinished Tuesday with an entire Saturday is unlikely to answer a useful question.
Then add a short context note. Travel, illness, a deadline, a video call, or using a different device can change the meaning of a total. A decrease on one phone also does not show whether the activity moved elsewhere. You do not need to track every minute; simply note the circumstances you already know.
Choose a question before interpreting the chart. Examples include: “Did my evening browsing run into the time I had set aside for cooking?” or “Which app sends updates I rarely act on?” Those questions point toward a decision. “Was my number good?” does not tell you what to do next.
Look closely at one pattern
Pick a single observation that matters to your chosen question. Keep the observation separate from your explanation:
- Observation: “This app accounted for more time on two evenings.”
- Possible explanation: “I was waiting for a reply and kept reopening it.”
- What I still do not know: “I cannot tell from the total how much time was the conversation itself.”
This example is invented to show the method. Your report may suggest a different explanation, or no concern at all. Avoid treating an app category as proof of what a person was thinking or viewing.
Copy the weekly review worksheet
| Prompt | My note |
|---|---|
| Report period and device scope | ___ |
| Context that affects the comparison | ___ |
| One observation from the report | ___ |
| What I wanted that time to be for | ___ |
| One possible explanation, still uncertain | ___ |
| One change I want to try | ___ |
| When I will review it | ___ |
Keep the next change specific. You might remove an unwanted alert, choose a check-in time, prepare an offline activity, or decide no change is needed. Write what you expect to notice, such as “I will be able to finish dinner without reopening the feed.” That gives the next review something concrete to assess beyond a smaller total.
End the review with a decision
After the next comparable period, ask whether the adjustment helped the activity you cared about and whether it created any inconvenience. Keep it, revise it, or drop it. A useful review can end after one decision; it does not need to become another dashboard you check repeatedly.
If notifications are the pattern you want to change, use the iPhone notification audit to turn that observation into a small settings experiment.
Sources and further reading
This article is an educational resource from the Unhook product team, not personalized medical advice. Examples and worksheets are illustrative. Read our content standards.
