> ## Documentation Index > Fetch the complete documentation index at: https://help.rytz.com.au/llms.txt > Use this file to discover all available pages before exploring further. # Parenting calendar > Visualise your routine schedule, school holidays, special occasions, and one-off variations as a calendar — see at a glance who has the children when, across weeks, months, or the whole year. import { Card, CardGroup, Note, Tip } from '@mintlify/components' The Parenting Planner has a **parenting calendar** view that turns the text of clauses 2 (Live with / spend time with) and 5 (Special occasions) into a visual calendar. Useful for understanding what the routine you've drafted actually looks like across a year. ## Why a calendar view Drafting a routine in text — "alternating Friday-to-Sunday with Wednesday-evening dinners" — is straightforward. Imagining what that produces across a 12-month year is harder. The calendar view solves the imagination problem by showing it. Two specific moments where the calendar pays off: A parent who can see exactly which weekends, school holidays, and special occasions sit with whom is harder to talk into a deal that turns out worse than they expected. The calendar visualises the deal. Some routines look clean in text but produce ugly patterns in practice — every public holiday falling with one parent, all of school holidays falling outside the alternating pattern, etc. The calendar surfaces these edge cases. "Can the children be with me on Easter weekend this year?" — easier to assess against the calendar than against the text. Short circuits a lot of arguments. Older children often want to know what their schedule looks like. The calendar is the format that makes sense to them. ## What's on the calendar Five layers, each colour-coded: | Layer | What it shows | | ---------------------- | ------------------------------------------------------------------------------------------------------ | | **Routine schedule** | The week-by-week alternating pattern from clause 2 | | **School holidays** | School-holiday blocks per the school calendar for the children's school region, allocated per clause 5 | | **Special occasions** | Mother's Day, Father's Day, children's birthdays, parents' birthdays per clause 5 | | **Public holidays** | Public holidays in the children's home state | | **One-off variations** | Specific exceptions logged ("Children with mother for cousin's wedding 14 March") | You can toggle layers on and off. Useful for "show me only the routine" when you need to verify the underlying pattern. ## Calendar views Standard week view. Useful for "next two weeks at a glance". Standard month grid. Useful for planning the upcoming month. Compact yearly grid. Useful for assessing the full annual pattern at a glance — what proportion of the year sits where, where the imbalances are, where school holidays fall. Breakdown by % time per parent — annual, term-time-only, holiday-only. Useful for the "how much time is each of us actually getting?" question without manual maths. ## Generating the calendar The platform produces the calendar from your drafted clauses 2 and 5 plus your children's school region (set in the Master Case File). If your clauses are precise enough to produce a calendar, the calendar appears immediately. If a clause is too vague — "alternating weekends" without specifying which weekend the alternation starts — the platform asks a few clarifying questions to anchor the calendar, without requiring you to change the clause text itself. ## One-off variations Real life produces variations. The platform handles them as overlays on the underlying schedule: * **Add a variation** — pick a date or date range, specify who has the children for that block, and add a note ("school camp", "cousin's wedding", "parent's surgery recovery"). * **Variations don't change the underlying schedule** — they're overlays that show on the calendar as visually distinct blocks. * **Variations log to a history** — useful when you want to remember what variations have happened over time, particularly for chronology purposes. * **Variations can be agreed via the platform** — propose a variation, the other party accepts (if they're also using RYTZ in a connected matter, future feature), or accept by message. ## Exporting the calendar Three export formats: * **PDF** — printable monthly or annual view. Useful for fridge or wallet reference. * **iCal feed** — subscribe from Apple Calendar, Google Calendar, Outlook. Updates automatically when the routine changes. * **CSV** — for analysis in spreadsheet form, e.g. computing exact-time splits for s75(2)(c) future-needs purposes. For the iCal feed, see the privacy note in the [Case Planner](/court-process/case-planner) entry — court-date and parenting-time information is sensitive when shared. ## Sharing with the other party Where the parties are co-operating, the calendar is one of the most useful shared artefacts: * **Read-only share link** — the other party gets a link that lets them view (but not edit) the calendar * **Joint subscription** — if the other party is also a RYTZ user (in a future feature), both calendars stay in sync * **PDF export** — for the simplest case, just email the PDF Where the parties aren't co-operating, the platform's defaults keep the calendar private to your account. ## Calendar and Court Readiness The calendar feeds into the broader [Court Readiness Matrix](/evidence/court-readiness-matrix): * A clearly-drafted routine that produces a clean calendar is evidence the plan can be implemented * One-off variations logged over time become evidence of how the plan has actually operated * Time-percentage stats are useful for s75(2)(c) future-needs assessments in any related property matter ## What the calendar will not do * **It will not enforce the schedule.** The calendar shows what the plan says; if the other party doesn't follow it, the platform's [Non-Compliance Playbook](/court-process/non-compliance-playbook) covers the response. * **It will not handle late changes from the other party.** Variations logged through the platform record what happened; they don't make the change automatically. * **It will not advise on whether a routine works.** The calendar is descriptive; the [Strategic briefing](/parenting-planner/strategic-briefing) is where evaluation happens. ## What's next Clause 2 (Live with / spend time with) + clause 5 (Special occasions) drive the calendar. Where the routine is initially drafted. Where the platform evaluates whether the routine works. Court-date calendar (separate from parenting calendar).