Explaining a Bad Week
The explanation that gets accepted is specific, checkable and arrives before the question. What goes in it.
The variance is adverse and somebody will ask. How the explanation is constructed decides whether it is accepted or treated as an excuse.
The practical lesson in “Explaining a Bad Week” is to connect every record to a named decision. Organisations exploring the provider's overview for remote workforce management software can add structured workforce context, provided the use is disclosed and the interpretation is reviewed with the people affected.
Do the six causes first
The previous note's order: demand, mix, absence, premium cover, operational change, schedule.
For an independent reference related to “Explaining a Bad Week”, consult the OSHA worker-fatigue resources; it provides a useful external check on scheduling, working-time and workforce-planning assumptions.
Ten minutes, one line each.
Writing an explanation before doing this produces the generic version, which is the one that gets dismissed.
The structure that works
What moved, in a figure.
Why, specifically.
What it would have cost to avoid it.
What you are doing about the recurring part.
Four sentences.
The "what it would have cost" line
The one people omit and the strongest one.
"Covering that absence at agency would have cost more than the variance" is a complete defence.
"Being properly staffed on Saturday would have cost four hours and we would have taken the extra trade" is an argument for next time.
It shows the decision was made rather than suffered.
Separating the recurring from the one-off
A one-off needs explaining once.
A recurring cause needs a change, and saying which it is prevents the same conversation monthly.
Most adverse variances contain both, and separating them is what makes the response proportionate.
Sending it before being asked
A short note on the day the figures land, unprompted.
It changes the dynamic entirely: you are reporting rather than defending.
And it buys credibility for the week when the explanation is genuinely "I got it wrong", which will happen.
Admitting the schedule was loose
Sometimes it was.
Saying so plainly, once, with what you changed, costs far less than defending it.
A manager who never concedes this is not believed on the occasions when it was something else.
What not to do
Blame the forecast without checking it was wrong.
List five causes without weighting them.
Or explain at length, which reads as anxiety.
Four sentences, specific, with a figure.
The repeated bad week
If the same explanation arrives three times, it is not an explanation — it is a condition.
At that point the honest statement is that the budget or the establishment is wrong, with the arithmetic.
Which its own note covers, and it is a different and more productive conversation.
What to check
Did you work the six causes before writing?
Is there a figure in your explanation?
Does it say what avoiding it would have cost?
And have you sent the same explanation three times?