Team Absence Calendar & Coverage View

The problem this kills

You approve a vacation day. It looks fine on its own. What you can't see is that two other people on the same team already booked that week - and now Thursday has nobody who can cover the desk, the shift, or the on-call rotation. By the time someone notices, it's the day before and you're scrambling.

Most PTO tools are great at saying "yes, this person has the days" and terrible at saying "but your team will be dangerously thin if you approve it." Coverage is the part that actually hurts when it goes wrong, and it's the part nobody can see at a glance.

This tool makes coverage visible. It shows who's off, by team and by day, color-coded by leave type, with a clear red flag on any day that drops below the minimum staffing you've defined. And when a manager is about to approve a request that would create a gap, it warns them first - and makes them write down why if they approve anyway.

What you'll build

A simple, login-protected web app where:

• Your time-off data and team rosters load in (from your PTO tool's CSV or a spreadsheet).
• A month/week calendar shows absences grouped by team, color-coded by leave type.
• Each day is checked against your minimum-coverage rules (e.g., "always at least one nurse," "never more than 2 off in Support").
• Days that fall below the minimum are flagged in plain sight.
• When a manager reviews a pending request, an overlap warning appears if approving it would breach coverage.
• Any approval past the minimum requires the manager to acknowledge and record a reason - and that reason is logged.
• Everything exports to CSV and to an .ics calendar file you can subscribe to.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook for an AI coding agent (Claude Code). You don't write code - you paste, answer questions, and approve.

It opens by interviewing you about your business. Before it builds anything, the plan has the agent ask about your actual teams, how your leave data is shaped and named, your real minimum-coverage rules, your busy seasons and peak overlap periods, your holidays and time zones, and your messiest edge cases (half-days, partial-week leave, role-specific cover). It reads back a short tailored spec, you confirm it, and only then does it build - so you get a tool shaped around your team, not a generic template.

From there it walks step by step through the database, the calendar UI, the coverage-rule engine, the approval-time warnings, the override log, email alerts, and the exports - each step ending with a ready-to-copy prompt.

The governance it includes (this is the point)

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own people and absences.
• A complete audit trail - who approved what, when, and why.
• A human-in-the-loop override gate - approving below minimum coverage is never silent; a manager must acknowledge and record a reason before it's committed.
• Duplicate guards keyed on employee + date, so the same absence can't be double-counted or double-rendered.

Who it's for

Managers and schedulers who approve PTO without an easy way to see overlap - and keep ending up short-staffed. If you run a shift team, a clinical rotation, a support queue, or any group where "everyone off at once" is a real risk, this is for you.

You've got this - paste the first prompt and let the agent interview you.