Your sprint plan assumes 10 days × N people. Your calendar disagrees.
Name where your team sits and the window you’re planning. This subtracts the public holidays each country actually observes and the time off you’ve booked — then shows the working days and person-days that are left, and whether what you’ve committed fits inside them.
Step 1 — the real-capacity audit
Nothing is stored and no account is created — the result lives in the link, so you can send it to someone. See a distributed example over Easter — 3 × United States, 2 × Germany and 2 × Poland. Good Friday is German and not Polish, Easter Monday is both, and the Americans work through.
What this can and cannot see
Holiday dates are computed from rules rather than fetched from a list, so they hold for any year — but coverage is national only, and each country’s exclusions are spelled out beside the result. The commitment check is arithmetic on the numbers you enter plus the sprint totals you give us. No cross-team benchmark stands behind it, because none exists: nobody can tell you how often commitments like yours land elsewhere, and a number that claimed to would be invented.
Nothing you type here is stored. The whole read is encoded in the URL, which is also how you share it.
Want the same correction applied continuously, with your team’s own calendar and estimates behind it? That’s Ambera Forge · Read what AI-written code costs your team in review