Why the date moves

Logging a new period start, editing or deleting a period, or changing the cycle-length setting can move the next expected period and the dependent ovulation and fertile-window estimates. The period-length setting changes how many predicted bleeding days are shown, not the next start date itself.

The current day is also an input. If an expected cycle passes without a new recorded start, the app can advance to a later predicted cycle even though the saved records did not change.

Your most recent start is the anchor

Future cycles are projected forward from the latest recorded period start. Recording or correcting that date changes the anchor, so the next-period, ovulation, and fertile-window estimates generally move with it.

Older starts still matter because they can change the recent interval calculation. The latest start usually has the largest effect because it can change both the anchor and the estimated cycle length.

Cycle length is recalculated from recent intervals

MiniCycle uses up to 12 recent period starts. With at least two valid starts it calculates the intervals between them and uses a median-style representative value. When there are at least 10 intervals, it removes one shortest and one longest first.

If there is no valid interval, automatic mode uses a 29-day default. With few intervals, one correction can change the result noticeably; more records do not guarantee that the future cycle itself will be regular.

Ovulation and the fertile window shift with it

Ovulation is not pinned to a fixed day 14. MiniCycle counts it backward from the next expected period using a luteal phase that flexes between 9 and 14 days depending on your cycle length. The fertile window then runs from five days before that estimated ovulation through the day after it. All of it hangs off the next-period estimate.

So when the period date moves, ovulation and the sky-blue fertile band move with it, in the same direction. You do not adjust them separately. They sit downstream of the one date the app is really estimating.

Reminders and the widget

MiniCycle rebuilds local notifications after relevant records or settings change. Supported lead times remain relative to the new estimated dates.

The app also writes shared data and requests a widget reload. iOS controls the actual redraw time, so the widget can temporarily show an older prediction even after the app has recalculated.

What a moving date can and cannot tell you

A shifting estimate reflects your data, not your health. Cycles vary. An analysis of more than 600,000 cycles found that cycle length differs from person to person and from month to month for most people, which is the reason MiniCycle keeps re-estimating instead of trusting a single figure. A prediction that lands a few days off is ordinary, not a fault in the app or in you.

What the moving date cannot do is diagnose anything. It is reference information drawn from your own dates, not contraception and not a verdict on pregnancy. Mayo Clinic suggests checking with a clinician if your periods come less than 24 or more than 38 days apart, stop for more than 90 days without pregnancy, or turn irregular after being regular. If you want the predicted date to track you as closely as possible, the habit that helps most is logging each period start on the day it happens, so the anchor the app measures from is always right.

MiniCycle for iPhone

Try MiniCycle

MiniCycle is built for a clean iPhone period calendar, local records, simple statistics, and a home screen widget.

View on the App Store

Author

Chanwook Kim

Chanwook Kim builds MiniCycle and documents how the app works. Health guides are grounded in the cited sources and do not imply medical credentials or clinician review.

MiniCycle editorial

References

About this article

App details are checked against MiniCycle's current behavior. Health information is summarized from the linked clinical and public-health sources and is educational, not a diagnosis or a substitute for medical care. Read the editorial approach.