Calendar and Reminders Documentation
Create household events and reminders, understand recurrence and time handling, and distinguish reminders from financial records.
Audience: Household members coordinating dates and obligations. · 4-page PDF · v6.26.1
How to read this document
Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.
- Point lists call out operator-visible behaviour.
- Callouts mark warnings, limitations, or important qualifications.
- Worked examples use round numbers so you can reproduce the arithmetic by hand.
Purpose
The household calendar organizes shared dates and reminder context.
- Create dated events
- Assign useful context
- Configure reminders
- Review repeated events
Event anatomy
- Title and description
- Start and end date/time
- All-day status
- Household visibility
- Reminder and recurrence settings
Time zones and boundaries
Local time, all-day treatment, daylight-saving changes, and device settings can affect presentation. Confirm time-sensitive obligations with their authoritative source.
Recurring events
A recurring event represents a schedule. Editing one occurrence or the series can have different results.
No expense generation claim
A recurring calendar item or reminder does not by itself create a household expense or prove a bill was paid.
Reminder delivery
Reminder timing is derived from the event and configured lead time, but delivery remains subject to channel availability.
Reminder time concept
EventTime − LeadTime
Good practice
Create a bill reminder
- Use the contractual due date.
- Add a non-sensitive title.
- Choose a useful lead time.
- Create or reconcile the payable separately.
The date is visible without confusing the reminder with the financial ledger.
Visibility and editing
- Household roles govern access.
- Avoid private details in shared descriptions.
- Check attendees or ownership before deleting a series.
Privacy, advice limits, and what we do not publish
AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.
- Household data is scoped to your household; other families cannot see your ledger.
- Public documentation explains product behaviour and calculation concepts, not proprietary internals.
- Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
- Calendar reminders are convenience tools and do not guarantee deadline compliance or delivery.
Intellectual property boundary
This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.