Log the start first, and the app fills the rest
Tap the day your period began and choose period start. MiniCycle creates a closed range that starts on that day and runs for your period length, so a single tap marks more than one day. With the default period length of five days, marking June 3 as a start fills the range through June 7 without another tap.
The length it uses is your setting, not a fixed number. Leave period length on automatic and the app estimates it from your recent finished periods; set it manually and that value wins. Either way the start tap is enough to get a usable span on the calendar, and you can adjust the end afterward if the real one differs.
Set the real end when the bleeding stops
When your period ends, tap that day and choose period end. The app moves the range's end to the day you picked, as long as it lands on or after the start. Tap a day before the start and MiniCycle declines and asks for an end on or after the start instead.
There is a ceiling. A single period range can run at most 14 days from start to end, counting both, so an end that would stretch the span past two weeks is refused. If you tap period end on a calendar with no start logged yet, the app stops you and asks for a start first, since there is no range to close.
Will logging a start twice create two periods?
No, and that is deliberate. Day one is often a guess, and you may tap the wrong date and want to move it a day. So MiniCycle treats a new start logged within seven days of an existing start as a correction: it replaces the old range rather than stacking a second one beside it. Log June 3, realize it was really June 4, tap June 4, and you end with one period, not two.
The seven-day window cuts both ways, before or after the saved start. A start logged eight or more days from any existing one is read as a genuinely new period and kept on its own. When the replacement would change dates you already saved, the app asks you to confirm before it overwrites.
When two periods overlap, the most recent start wins
Records can still end up overlapping, usually from an end date pushed long or two starts logged close together. When ranges cover the same day, MiniCycle resolves it by start date: the range with the most recent start takes priority for what shows on that day. The newer entry, in other words, is treated as the better one.
In practice a fresh, accurate start quietly wins over a stale range you forgot to close. If a day still looks wrong after that, the fix is to correct or remove the older range rather than to add another on top of it.
What these dates feed, and what they can't
Your start dates are the engine for everything the app predicts. The next period is estimated from the start dates you have saved. Ovulation is counted back from that estimate using a luteal phase that flexes between 9 and 14 days with your cycle length, not a fixed two weeks, and the fertile window runs from five days before that estimated ovulation through the day after. Better start dates mean better predictions, which is the whole reason the logging is worth getting right.
What the dates can't do is diagnose or decide anything medical. The predictions are reference information drawn from your own pattern, not contraception and not a verdict on pregnancy. They stay on your device, since MiniCycle keeps records locally with no account, so the cost of fixing a wrong date is one tap and the benefit is a calendar that matches what actually happened.
MiniCycle for iPhone
Try MiniCycle
MiniCycle is built for a clean iPhone period calendar, local records, simple statistics, and a home screen widget.
MiniCycle editorial