How people schedule random reminders: data from 267 live schedules

Weekly is the most common interval in Untimely's 267 active schedules. Most schedules request a single nudge per interval, most allow every day of the week, and the largest time-window groups are the eight-hour and twelve-hour buckets.

Here are the counts behind those findings:

• 122 schedules (46%) use a weekly interval, ahead of daily, monthly, and yearly.
• 213 schedules (80%) request one delivery per interval.
• 145 schedules (54%) allow all seven days.
• 130 schedules (49%) fall into the eight-hour or twelve-hour window buckets combined. These are the largest individual buckets, together just under half of the sample.

This is a snapshot of enabled rules on non-deleted events, taken on September 30, 2026. All use random scheduling. It describes schedules, not distinct people, and cannot tell us whether a reminder was useful or acted on.

Weekly leads, but daily is close behind

Interval	Active schedules	Share
Weekly: 7 days	122	46%
Daily: 1 day	95	36%
Monthly: 30 days	42	16%
Yearly: 365 days	8	3%

These labels describe interval lengths. Monthly means a 30-day interval here, rather than a particular date each calendar month.

Weekly is the largest group, though it is not a majority. Daily schedules are also common. The distinction matters when choosing a starting point: a prompt you welcome occasionally may feel different when it arrives every day.

For a flexible check-in or a personal project, try a weekly interval first. Choose daily when the action would be welcome that often. Those are starting suggestions, not evidence that either interval produces better results; these counts measure configuration, not outcomes.

One nudge per interval is the clear preference

Deliveries per interval	Active schedules	Share
1	213	80%
2	20	7%
3	17	6%
4	8	3%
5	9	3%

Frequency and interval answer different questions. One delivery per daily interval is a different commitment from one per monthly interval. The aggregates do not show which frequency belongs to which interval, so we cannot say how many schedules send exactly one weekly reminder.

Start with one delivery in your chosen interval. If the message remains useful and you want to encounter it more often, increase the frequency. If you tend to dismiss it, consider changing the message or interval before adding more deliveries.

Most schedules leave every day available

Allowed days per week	Active schedules	Share
7	145	54%
5	85	32%
6	11	4%
1–4 combined	26	10%

Allowing all seven days does not mean receiving a reminder every day. It gives the random schedule more eligible days; frequency still controls the requested deliveries per interval.

The next-largest group allows five days. We do not have the identities of those days, so calling that group “Monday to Friday” would go beyond the data.

Leave every day available if your prompt fits throughout the week. Restrict the days when it belongs to a particular routine. A work-related prompt and a personal reflection need not share the same boundaries.

Broad time windows are common

Window length	Active schedules	Share
8 to under 9 hours	76	28%
12 to under 13 hours	54	20%
Under 1 hour	12	4%
All other lengths	125	47%

Window lengths were rounded down to whole hours in the source aggregates. An eight-hour bucket therefore does not necessarily mean exactly eight hours, and a zero-hour bucket means under an hour.

The leading buckets suggest that broad windows are common in this sample. Choose a span during which you could welcome the reminder, then narrow it if some of those hours prove inconvenient. A longer window gives timing more room to vary; it does not add deliveries.

Check the timezone as well as the hours. Only 12 schedules have a timezone explicitly set; 255 default to UTC. Stored start and end hours therefore cannot support claims about people's local mornings, afternoons, or evenings. Window length is the safer comparison.

Delivery and timing are separate measures

The channel counts are 265 email and 2 webhook. In the run history created during the preceding 90 days, 3,128 runs succeeded and 87 failed, a 97.3% success rate.

For that same period, 3,139 runs (about 98%) fired within five minutes of their scheduled time, and all 3,215 fired within fifteen minutes. Firing measures when a run started relative to its scheduled time. It does not establish when an email reached an inbox or was read, and it includes failed runs. These observations are not a future delivery guarantee.

To put the configuration findings into practice, choose a message from 10 everyday uses for random reminders, start with a modest frequency, and set days and hours that fit the action. The random reminder app guide explains the setup.

Methodology

This September 30, 2026 production snapshot used read-only aggregate queries. Only counts were returned; no message content, email addresses, or per-account records were exported. “Active” means enabled rules on non-deleted events; all 267 were random schedules. Small counts are shown as-is. Schedule shares use 267 as the denominator and are rounded independently, so totals may differ from 100%.

The distributions are separate aggregates, not linked records. They cannot establish relationships between settings, individual preferences, or effectiveness. Run history is retained for approximately 90 days; the run figures describe that recent window, not all-time usage.