Guide
How to use period and cycle context in Helen
Period changes can remain useful context during perimenopause, especially when symptoms and HRT routines are changing at the same time. Helen lets you log period days, mark period starts, view calendar context, and use period starts to anchor supported progesterone schedules.
Key takeaways: How to use period and cycle context in Helen
- Helen stores period logs with date, flow level, and whether the day is a period start.
- Period starts can anchor period-linked progesterone schedules when that matches your regimen.
- Future period estimates stay separate from actual logged period history.
Log what happened on a specific date
Period logging in Helen is date-based. You can record flow level for a day, clear an entry if needed, and mark whether a day is the start of a new period sequence.
Helen uses shared logic to avoid treating consecutive days in the same sequence as multiple new starts.
Use starts as cycle anchors
A period start can be important when a progesterone routine is period-anchored. Helen uses logged starts to keep schedule calculations and calendar dots aligned.
If you create or edit a period-anchored regimen with a start date, Helen can create the corresponding period-start anchor so the routine has a clear reference point.
View periods alongside hormone context
The calendar combines hormone schedule information, logged state, and period logs. That makes it easier to see routines and cycle context together instead of in separate apps or notes.
Future actual period logging is guarded because future days should remain estimates until they happen.
Keep estimates separate from history
Helen can use logged period starts to estimate future period windows when enough reliable context exists, but estimates do not become actual period logs.
That separation helps keep your entered history clean while still giving useful calendar context.