A pair of small but useful nudges inside Intervals just got a polish. According to myintervals.com, the time-tracking app has overhauled two notifications aimed at people who lose track of running timers or simply forget to log their day. Both alerts live in the Notifications section of an account and can be tuned per user, which matters for mixed-discipline teams where designers, developers and producers all keep different hours.
The update is not a flashy product launch. It is the kind of quiet fix that quietly pays off in cleaner timesheets, more honest burn-down data and fewer awkward Monday-morning catch-up sessions.
Key facts
- Intervals refreshed two time-tracking notifications inside its web-based project management tool.
- One alert warns when a task or general timer has been left running too long.
- The other reminds users who have not tracked any time by a chosen cutoff each day.
- Both notifications are configurable per user, and admin-level users can set them on behalf of others.
- Tracking options already supported include task timers, general timers, manual entry, bulk weekly entry, mobile app entry and time import.
Background: why time-tracking nudges exist in the first place
Time tracking has always been a friction point on agile and Scrum teams. The whole point of logging hours is to feed retrospectives, capacity planning and client invoicing with real data, but humans are not great at remembering to stop a clock or start a fresh one after a meeting. Tools have wrestled with this for decades, and most modern project management suites now ship with some form of reminder system.
Intervals in particular is built for designers, developers and creatives, a crowd that often bounces between deep-focus coding blocks, client calls and review sessions. Interruptions are the norm, not the exception, which is exactly when a forgotten timer quietly inflates a timesheet by an hour. The original idea behind timer alerts is simple psychology: if a user gets a gentle poke after a timer has run longer than expected, they can stop it and move on. The daily reminder serves a different purpose. It is the safety net for people who got so heads-down that they forgot to log anything at all that day.
Our analysis: what the refresh actually changes
The mechanics sound familiar, but the value is in the configuration depth. Per-user thresholds mean a junior developer who needs a short cap can have one, while a senior designer running a long creative block can stay uninterrupted. Admin-level overrides matter too, because managers can set a sensible default across the team without policing every account.
There is a trade-off worth naming. Aggressive reminders feel like nagging and get muted. Too quiet and they do nothing. Teams that pair this with a short end-of-day ritual, such as a brief timesheet sweep during the daily stand-up's last slot, tend to see the cleanest data.
For Scrum Masters, the real win is downstream. Cleaner timesheets mean more reliable velocity and capacity reports, which means better sprint planning conversations and less "I think I worked on that, but I cannot remember when" fog in retrospectives.
A worked example: setting it up in your next sprint
Say you are a Scrum Master running a two-week sprint with developers and designers. During sprint planning you notice that last sprint's burn-down looked noisy and the team's average daily logged hours sat well below their contracted capacity.
In Intervals, open Notifications and set a timer alert for the developers and a longer one for the designers, since the designers tend to run longer creative blocks. Then set a daily "no time tracked yet" reminder for late afternoon across the team, with the admin-level override so you can adjust it during the first sprint review. Add a brief timesheet check to the end of each stand-up for two sprints. At the next retrospective, compare logged hours per day against the previous sprint. If the variance shrinks and the burn-down smooths out, the nudges are doing their job.
What to watch next
Watch how teams actually tune the thresholds over the first month. The notification refresh is only useful if people do not silence it, so adoption is the real metric. Bottom line: if your retrospectives keep surfacing "we do not trust our own timesheets," turn on both alerts this week and revisit them at the next sprint review.
Key takeaways
- Configure timer alerts and daily tracking reminders per user to match how each role actually works.
- Use admin-level overrides to set sensible defaults without micromanaging individual accounts.
- Pair the reminders with a brief end-of-day timesheet sweep for noticeably cleaner sprint data.
Frequently asked questions
Which two notifications were updated in Intervals?
The timer alerts notification, which flags timers left running too long, and the daily reminder that nudges users who have not tracked any time yet that day.
Can each team member set their own reminder time?
Yes. Every user can configure their own thresholds, and admin-level users can set or adjust reminders on behalf of anyone on the team.
What time-tracking methods does Intervals support?
Task timers, general timers, manual entry, bulk weekly entry, the mobile app and time import from other systems.
Where do I find these settings in Intervals?
Both notifications sit inside the Notifications section of your Intervals account, as described in the help documentation linked from myintervals.com.
Will these alerts help with Scrum sprint reporting?
Indirectly, yes. More consistent time entries feed cleaner velocity and capacity data, which makes sprint planning and retrospectives easier to trust.