When The Board Knows Who Is On Leave: What Changes In Planning

You commit to a date on Monday. On Wednesday you find out the only person who can do the middle part of the work is away for ten days, and has been booked off for a month.

When the board knows who is on leave, three things change: you stop planning around people who will not be there, handovers get arranged before the absence instead of during it, and a stalled item is correctly read as an absence rather than as someone dropping the ball. What does not change is that somebody still has to decide what to do about it. The data removes the surprise, not the judgement.

The failure this actually prevents

Most teams do have leave records. They live in an HR system that project people do not open, and project plans live in a board that HR people do not open.

Nothing is wrong with either system. The failure is in the gap. A planner making commitments on Monday has no reason to go and check an HR calendar for six people, so they do not, and the mismatch surfaces later as a missed date that gets explained as poor estimation.

What improves, concretely

Commitments get made with the right capacity. A two week piece of work with one person on it, where that person is away for five of the ten days, is not a two week piece of work. Knowing that at the point of committing changes the date or changes the plan.

Handover happens before, not during. The most expensive part of an absence is usually not the missing days. It is the two days at the start where nobody knows the current state of the work, and the two days at the end where the returning person catches up. A visible upcoming absence turns that into a scheduled conversation.

Stalled items get read correctly. A card that has not moved for a week reads very differently when you can see the owner was away for it. Reviews stop generating quiet suspicion about individuals, and start asking the useful question, which is what the work needed while they were out. A board with a column for each kind of wait makes that reading easier still.

Single points of failure become visible. When you can see who is away and what they own, you notice that four important items all belong to one person. That is worth knowing before the leave, not after. A single reviewer is the same pattern in another form, and it is why work sits in review for days.

What still needs a person

Plenty. Be honest about this, because software that claims to plan around absence tends to oversell.

• Deciding whether to move a date or move the work. Both are legitimate. Only a human knows what the commitment is worth to the customer.
• Knowing who can actually pick something up. Availability is not capability. The system can tell you who is present. It cannot tell you that one of them has never touched this part of the work.
• Judging when an absence does not matter. Some work is genuinely fine to pause. Reflexively reshuffling everything around every absence creates its own churn.
• The conversation with the person going on leave. What is in flight, what to hand over, what to let sit. That is fifteen minutes of talking that no record replaces.

The part managers get wrong

Seeing leave on the board tempts people to treat every absence as a problem to be solved by redistribution.

That is often worse than doing nothing. Handing a half done piece of work to a second person costs both of them context, and if the original owner is back in a week, you paid that cost twice for a small saving. The default should be to let short absences sit and only redistribute when the work genuinely blocks someone else. Redistribution also quietly raises how much is in flight, which is exactly what work in progress limits exist to hold down.

The value of visible leave is mostly in what you avoid committing to, not in what you rearrange.

How the records fit together

This only works if the two records are one record. Copying leave dates into a project tool by hand fails in the ordinary way: someone changes their leave and the copy stays stale, and now you have a confident board that is wrong, which is worse than a board that is silent.

SicherOne exists for this pattern. Project management and HR sit on one set of records, so a board reflects who is available without anyone syncing anything, and its AI agents work against the same records rather than a separate copy. Anything an agent produces gets approved by a human before it ships, which is the right arrangement for planning decisions that depend on things a record cannot know.

Get the data in one place. Keep the decisions with people.