Diwali week leave requests allocated fairly with a cover roster
Sorts overlapping festival leave requests for a team into approved, partly approved and declined, using rules everyone can see, builds a day-by-day cover roster and writes the reply to each person. Use it when half the team asks for the same Diwali, Chhath or year-end days and the work still has to run.
The output this prompt produced, unedited.
The prompt
Constraints first
Minimum staff on duty each day is fixed and never broken: [e.g. 3 of 8 in support, 1 senior always]
Apply the same written rules to everyone, in this order: [e.g. travel distance home, who worked last year's festival, request date]
Offer a partial approval or an alternative date before a flat decline.
Never weigh religion, family status or gender; use only the rules listed.
Inputs
Team, role of each person with a code and their skills: [paste]
Festival dates and the days that need cover: [e.g. 6 to 11 November 2026]
Leave requests: [paste rows: person, dates asked, reason given if any, date of request]
Who worked last year's festival week: [paste]
Any days already approved: [paste]
Output format
| Person | Dates asked | Decision: approved, partly approved, or alternative offered | Rule applied | Dates approved |
A roster: | Date | On duty | On leave | Senior on duty | Meets minimum: yes or no |
A reply to each person under 60 words, stating the decision, the rule and any alternative.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.