What Board Level Reports Should Say About People, Not Just Progress

A board pack shows green across the delivery slides. Six weeks later a date slips badly, and the reason turns out to be that one person left and nobody else knew how that part worked. The information existed. It just was not on any slide.

A board report should carry four people numbers alongside the progress ones: how much critical work depends on a single person, how long key roles have been open, what leave and notice is coming in the next quarter, and where the load is concentrated. Each one is a leading indicator of a date that is about to move, which is exactly what a board is there to hear early.

Number one: work with only one person who can do it

Call it single point coverage. Count the pieces of work that are important to the plan and have exactly one person who could do them.

Report it as a small number with names attached in the appendix, not in the room. The board does not need the names. It needs to know whether the number is going up or down, and which of those pieces are on the critical path this quarter.

This is the one that predicts the nastiest surprises, because it converts a personal event, a resignation or an illness or a long holiday, straight into a delivery event.

Number two: how long a role has been open

Not how many roles are open. How long each one has been open.

An open role is a decision that has already been made and not yet delivered. Once it passes a certain age it stops being a hiring update and becomes a delivery risk, because the work it was meant to absorb is being absorbed by somebody else instead.

Present it as days open per role, with the work that role was meant to take on written next to it. That second column is what makes it a board matter rather than a recruitment status.

Number three: known absence in the next quarter

Leave that is already approved, notice periods already running, parental leave already dated. Resignations that have not happened yet are harder, though a project board often shows the warning signs first. All of it is known today and none of it usually appears on a plan.

The useful framing is capacity, not calendar. Do not put a heat map of who is away when in front of a board. Say which committed dates fall inside a period where the team is meaningfully smaller, and what you have done about it.

Number four: where the load sits

Look at who is assigned to the work that matters most and count how much of it lands on the same few people. Concentration is not automatically bad. Concentration you have not noticed is, and it is easier to see once you start reading a sprint board for overload instead of progress.

The presentation trick here is to pair it with the plan. If three of your top five deliverables all run through the same person, say so and say what the second name on each one is. If there is no second name, that is your first number again in another form.

How to present it without alarming anyone

Boards react badly to raw risk with no owner, the same gap that sits a level down between what managers ask for in reports and what they actually use. They react well to a named problem with a decision attached. Four rules help:

• Always pair a number with what you are already doing about it
• Show the direction, not only today's value. A worsening small number matters more than a stable large one
• Ask for exactly one thing per number, or nothing
• Keep names out of the room unless the board is being asked to act on a specific person

The tone that works is calm and specific. "Two of our four critical deliverables have a single owner. We have started pairing a second engineer on each, and expect both covered by the end of next month." That is a risk being managed, and it reads as competence rather than panic.

Why this is usually missing

It is missing because the information sits in two systems. The delivery status comes from the project tool. The leave, the notice periods and the open roles come from HR. Nobody owns the join, so the join does not happen, and every quarter someone rebuilds it by hand the night before the meeting.

Putting both on the same records fixes the joining problem. That is what SicherOne is built to do: project management and HR on one set of records, so the board already knows who is on leave and an agent asked to draft a summary is working with full context rather than half of it. A person approves anything an agent produces before it goes anywhere. It is sold per seat with the modules separable.

The tool is not the point though. The point is that a board hearing about people a quarter early can still do something. A board hearing about them afterwards can only ask why.