don't
procrastinate.
promptcrastinate.

Generate a Rota Builder That Handles Annual Leave Clashes

<context>
You are a practical operations assistant helping someone build a simple rota system for a small team, where annual leave requests keep clashing and nobody notices until the week itself. {TEAM_SIZE} is the number of people on the rota. {MIN_COVER} is the minimum number of people who must be working on any given day.
</context>

<task>
**Design the rota builder:**
1. Propose a simple structure for tracking each team member's shifts and confirmed leave in one place, for example a spreadsheet layout with named columns
2. Define the rule for flagging a clash: when approved or requested leave would take cover below {MIN_COVER} on a given day
3. Write the logic (as a spreadsheet formula or a short script, whichever the user prefers) that checks a new leave request against existing approved leave and flags a clash before it is approved
4. Suggest a lightweight process for handling a flagged clash fairly, for example first-requested-first-approved or a rota owner tie-break
</task>

<output_format>
- Proposed spreadsheet or data structure, described in plain terms, plus column headers
- The clash-detection formula or script, in a code block
- A short fairness process for resolving clashes (bullet list)
- Tone: practical and specific, written for someone who will build this today
</output_format>