Your HR system already tracks leave.You still need to see team availability.

The first problem is timing. People book leave in HR when they're sure, and that's often late. In sprint planning six weeks before a release, the trip someone mentioned at lunch isn't in HR yet because the flights aren't booked. It will be, two weeks before they go, after you've already set the date.

The second problem is shape. HR tools are built around a leave request: a person, a leave type, a start date, an end date, an approver. A conference isn't leave. An offsite isn't leave. On-call and release duty aren't leave. A half day might be, depending on policy, but it often never gets booked at all. None of that shows up, and all of it changes who can actually pick up work on a given Thursday.

The third problem is access. Many companies restrict who sees what in HR, sensibly. You might see your direct reports but not the two contractors on the team, or not the people from the platform team you share a release with. Your PM may see nothing. And even when you can see everything, it's usually a list or a month grid for one person at a time, not a timeline with your release dates on it.

Keep the planning view about one thing: whether a person is available to the team on a given day. These are the entries that matter for that, and most of them never live in HR: tentative plans (“probably out the week after Thanksgiving”), half days, conferences and offsites, on-call and release duty, and public holidays in each person's own country. If Marcus works from Canada through a contractor agreement, his holidays may not be in your company's HR system at all, and they won't line up with the US ones.

Then put the work on the same timeline: release dates, code freeze, release week, the offsite. The point of the planning view is to see people and dates together, so that “Emma is out November 23 to 25” and “the release is November 24” are on one screen instead of two systems. If you're choosing that date right now, the availability checks before choosing a release date go through it in order.

A good test: if an entry would change who you assign a ticket to or when you'd ship, it belongs in the planning view. If it only changes someone's paycheck or balance, it belongs in HR.

Don't copy balances. You don't need to know that Ben has nine days left, and keeping a second number that drifts from the real one causes arguments. If someone asks about their balance, send them to HR.

Don't record reasons. “Out” is enough. You don't need “medical appointment”, “family”, or “interview”, and the people on your team shouldn't feel they have to explain a day off to get it on the calendar. For sick days, “sick” or just “out” is the most detail anyone needs. Never put sick-note details, diagnoses or anything resembling a medical record in a planning tool.

Be careful with who sees it. A planning view that the whole team can open should show availability, not personal context. If you share it outside the team, show only that a person is out, not what kind of leave it is. That's also your best argument with HR later: you hold less sensitive data than a shared Google Calendar does.

The fear with any second system is double entry. The way around it is to make the planning step lighter than the HR step and earlier than it. You're not asking people to book leave twice. You're asking them to tell you about a plan as soon as it exists, in one place, and to book it in HR when it's firm, the same as they do now.

Pick one channel and say it once in a team meeting: “If you're thinking about time off, tell me early, even if it's not booked. Post it in #team-availability or send it through the request link. Book it in HR whenever you're sure.” A Slack channel works. A form works. What doesn't work is “mention it to me sometime”, because then it lives in your DMs, your memory and three standup notes.

You do the entry, not them. When a plan comes in, you add it as tentative. When HR approves it, you flip it to confirmed in the weekly check. For the team that's one message, and HR stays the place where leave is officially booked. The same idea scales down if you're still on a sheet: a team vacation spreadsheet for engineering managers uses the same tentative and confirmed split.

Once a week, say Monday morning before planning, open the HR leave view for your team for the next four weeks next to your planning view. Go person by person and look for four kinds of mismatch. It takes about five minutes for a team of eight.

Picture Monday, November 16, 2026. In HR, not on the board: Ben's approved leave for December 21 to 31 never came through the channel. Add it. On the board as tentative, now approved in HR: Emma's November 23 to 25. Flip it to confirmed. On the board, not in HR, and that's correct: David's conference on November 18 and 19 isn't leave, so leave it alone. On the board as tentative, not in HR, and getting close: Chloe's December 28 to 31. Send her a short message asking whether it's still on, so you're not planning around a trip that was cancelled in October.

That's the whole ritual. It catches the late bookings HR gets first, and it catches the stale tentative plans that only your board has. Do it before sprint planning and the numbers you plan with are current; planning a sprint when three people are away picks up from there.

Tell HR before they find it. A short note works: “I keep a planning calendar for my team so I can see availability next to our release dates. HR stays the system of record for leave. I don't track balances, reasons or anything medical, and I check it against HR every week.”

Then make that true in practice. Never approve or deny leave in the planning view. Never tell someone their time off is “approved” because it's on the board. If there's a conflict between the two, HR wins and you fix the board. If HR has a policy on what managers can keep about absences, read it and follow it, and ask if anything is unclear.

Most HR teams are relieved by this, not threatened. A manager who hears about leave early and plans around it is a manager who isn't pressuring someone to cancel a trip a week before a release.