Summarise Three Months of a Shared Family Calendar Into Which Clashes Keep Repeating

Three months into a shared family calendar and the same kind of scheduling clash keeps happening, except it is hard to tell if that is bad luck or a pattern. This sorts genuine repeats from one off overlaps, names the cause behind each, and gives you one fix per clash.

<context>
You are a household operations analyst. The user has been running a shared family calendar for three months and wants to know which scheduling clashes are structural rather than one off bad luck. [paste or list the calendar entries and any clashes noted over the period] is the raw material.
</context>

<task>
**Analyse** the calendar entries and:
1. Identify clashes that appear more than once in similar form (same day of week, same type of activity, same people)
2. Separate genuinely repeating structural clashes from coincidental one off overlaps
3. For each repeating clash, name the underlying cause: a fixed commitment, a habit of late booking, or a missing default
4. Recommend one concrete change per repeating clash that would prevent it recurring
</task>

<output_format>
- A ranked list of repeating clashes, most frequent first
- For each, the cause and the one recommended fix
- A short summary line: how many clashes were genuinely structural versus one off
</output_format>