A useful personal log makes it possible to see what you recorded, what you did not record and what you are unsure about. That is especially important when dates, reminders and later recollections sit together. A tidy-looking calendar is less useful than one that preserves those distinctions.
This article is about organizing personal records, not interpreting symptoms, choosing medication, changing doses or predicting contraception or fertility outcomes. Follow your prescriber’s directions for medication decisions. Dot: Period & Pill Tracker is a recording tool for iPhone and iPad, published by Valorem.
Choose what you want to review later
Start with one practical purpose: finding the dates you recorded, keeping a medication history together or preparing questions for an appointment. You do not need to track every available category. A smaller record that you can maintain accurately may be easier to review.
Choose a few consistent words for your own notes. “Observed,” “entered later” and “not sure” mean different things. Keep a question such as “What should I ask at my appointment?” separate from an observation such as “Recorded this event on Tuesday.” These are suggested note conventions, not claims about exact app fields.
If you use the same device for personal and shared activities, also decide what you want visible in notifications and widgets before entering real information. A brief trial with fictional details can help you understand the display without exposing a real record.
Keep an empty day different from a recorded absence
The current Dot App Store listing describes period dates, flow, symptoms and personal notes. It explicitly distinguishes spotting, a recorded no-flow day and a missing entry. Preserve those differences rather than filling every blank to make the calendar look complete.
Consider a fictional three-day record: on October 6 you entered an observation; October 7 has no entry; on October 8 you explicitly recorded no flow. October 7 is unknown from the log. It should not silently become another no-flow day, and this three-day record alone should not be treated as a medical interpretation.
If you add a recollection later, identify it as a later entry and preserve any uncertainty in the note. If you discover a clear recording mistake, correct the relevant date. Do not copy today’s entry backward merely because the earlier days look empty.
Separate a reminder from an event you recorded
A scheduled reminder describes an intended prompt. A recorded intake describes what you entered as having happened. A notification appearing, disappearing or being snoozed does not establish that you took anything.
Dot’s listing describes actual intake times, skipped-dose records and reminder snoozing, along with reviewing earlier entries. Use those records according to what you know happened, without turning uncertainty into a completed event. If you are unsure what to do about a medication, use your prescriber’s instructions or ask an appropriate professional; an incomplete log cannot decide for you.
Reminder delivery also depends on permissions, device settings and system behavior. The listing notes that some schedules need periodic renewal. Checking the app’s current reminder permissions and upcoming coverage is a separate housekeeping task from checking your recorded history. Neither is proof that every future notification will arrive.
Use a short record-review routine
- Check dates. Confirm that each entry belongs to the date you intended, especially when entering something later.
- Check meaning. Keep observations, uncertainties and questions distinguishable.
- Check omissions. Leave unknown days unknown unless you have a reliable basis to complete them.
- Check duplication. If information also exists elsewhere, make sure you know which source you are reviewing.
- Choose the next question. Write down one point you want clarified, rather than drawing a conclusion from a pattern yourself.
You might do this before an appointment or after noticing an entry mistake. There is no need to repeatedly audit the whole history. The useful outcome is a record you can explain, including its limits.
Prepare a report that fits its purpose
The current Dot 2.0 listing describes CSV export and a PDF report for a selected date range, with personal notes optional in reports. Start by deciding who the report is for and which period is relevant. Then review the file itself before sharing it.
Check dates, headings, included categories and whether personal notes are present. Remove unrelated information where the available export options allow it. A report for one appointment does not automatically need your entire history. Save the file somewhere you understand and share it only through a suitable route with the intended recipient.
If you open a CSV in a spreadsheet, verify a known date and entry before relying on its display. A spreadsheet can reformat dates or other values. Keep the original export so you can compare rather than guessing which version is correct.
Understand storage separately from sharing
Dot’s listing describes local storage and offline logging, optional Apple Health and iCloud connections, access protection and encrypted backups. These are separate choices. Optional sync is not the same thing as exporting a report, and the listing notes that Apple device backups follow device settings separately from Dot’s iCloud sync.
Review the connections you enable and the information they cover. Keep any backup passphrase private and accessible to you through an appropriate secure method. Do not include it in a report or a message asking someone to review your records.
Common questions
Do I need to use estimates to keep a history?
No. This routine is about reviewing recorded events and gaps, without relying on estimates.
Does a missed reminder mean a missed dose?
No. Reminder behavior and actual events are different. Record only what you know, and follow professional instructions for medication questions.
Should every report include my personal notes?
Only if they serve the report’s purpose and you want the recipient to see them. Review the generated file before sharing.
See the iOS edition page for product details and the private log selection guide for broader privacy considerations.