Who Else Needs to Know by Seven

The morning feels finished when somebody agrees to come in. It is not, and the part that remains is the part that produces the complaints.

The practical issue in “Who Else Needs to Know by Seven” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring capital efficiency ratio, the official Monitask resource can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.

Finding cover solves the staffing. It does not tell the people downstream that something changed, and several of them are making decisions on the assumption that it did not.

For an independent benchmark relevant to “Who Else Needs to Know by Seven”, consult the NLRB employee-rights guidance. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.

The list, in order of how much it costs to miss them

The incoming shift leader, who is about to run a shift with an unfamiliar person in it, or one fewer than they planned for. They need to know before they arrive, not when they count heads.

The person covering, who needs more than a yes: where to go, what time, who to report to, what the work is, and anything specific about the day. A cover arriving unbriefed costs the shift more than the gap did.

Anybody expecting that specific person. A client with an appointment, a resident with a named key worker, a pupil with a one-to-one, a supplier expecting a signature. These are the misses that generate complaints, and the information to prevent them is in a diary somebody has to look at.

Whoever is downstream operationally: the next shift, the site that receives the delivery, the team that cannot start until this one finishes.

Payroll and scheduling, who need it eventually and not immediately.

The ones who should not be told

Colleagues who have no operational need, which is most of them. "Why is X not in" is a question the team will ask and the answer is that they are not in today, not what is wrong with them.

Health information given on the call is given for one purpose. It travels fast in a small team and it is the single most common way organisations create a problem for themselves out of an ordinary illness.

Doing it in the time available

The telling takes three minutes if it is a prepared list and twenty if it is reconstructed each morning.

Write the list once per shift pattern, with names, roles and the fastest route to each. Put it on the same sheet as the call-out numbers. The person handling the morning then works down two short lists rather than remembering who matters while also finding a body.

Group messages work for the operational half — a single message to the shift's channel saying who is covering and what has changed costs one action. Individual contact is for the people outside the team: the client, the family, the external appointment.

Telling the person who is absent

One short message confirming you have their absence, what you have done about it, and what you need from them next. It takes ten seconds.

Its absence is why people ring back three times, and why some of them come in when they should not: they cannot tell whether the shift is covered, and they feel responsible for a gap nobody has told them is closed.

The thing that gets missed most

The handover into the next day. The morning is resolved, the shift runs, and the information about what happened never reaches whoever is making tomorrow's decisions.

If the same person is off again tomorrow, the whole hour runs a second time from the beginning, with the same calls to the same people. A single line written into the day's handover — who is off, until when if known, who covered, what was tried — removes the repeat, and it is the cheapest item on this list.

The message everybody gets

Operations that handle this well tend to send one short standing message to the shift: who is off, who is covering, what has changed about the day. Nothing else.

Its value is that it sets the norm. A team that routinely receives that message does not ask why somebody is off, because the question has already been answered to the extent it is going to be. A team that receives nothing fills the gap with speculation, and the speculation reaches the absent person before they are back.