The Morning That Goes Right

The same person rings in at the same time with the same illness. In an operation that has done the preparation described across this collection, the morning takes under twenty minutes and costs nothing extra.

The practical issue in “The Morning That Goes Right” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring internal transfer policy, open the official page can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.

Nothing clever happens. Every element was put in place in advance, on an ordinary afternoon, by somebody with time to think.

For an independent benchmark relevant to “The Morning That Goes Right”, consult the Fair Work record-keeping 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.

What happens

The call reaches a line that is staffed at that hour. The person taking it asks two things: are you all right, and how long do you expect to be off. Nothing clinical is written down.

They open the requirement sheet for that shift. Six needed, one capability now uncovered, and the fixed work in that capability is a thirty-minute window at eight.

They open the call-out list, ordered by who is cheapest and most likely, with capabilities and constraints against each name. The second name holds the capability, is part-time with hours available at plain rate, and has said she will take Tuesdays with short notice. She says yes.

They tell the incoming shift leader, the person covering, and the one client with an appointment in the affected window. Three messages.

They write a line in the log.

What made it possible

A requirement, written down, so the gap was a lookup rather than a judgement.

A capability map, so the real shortfall was visible in seconds.

A call-out list that is current, ordered, and carries contracts and constraints.

A part-time population that has been asked what hours they would take.

A notification list prepared in advance.

An authority document that was not needed on this occasion and would have been if the second call had failed.

Six artefacts. None of them costs money. All of them were produced on afternoons.

What it is not

It is not an operation with no absence. The absence rate is ordinary.

It is not an operation with spare staff everywhere. It carries some margin, deliberately, and it knows what that margin absorbed last quarter.

It is not an operation with a system. Four of the six artefacts are sheets of paper.

The difference in the numbers

Over a year, against a comparable unprepared operation: resolution times in minutes rather than approaching an hour, cover drawn mainly from the free and cheap routes, agency used for a small minority of events, below-requirement shifts rare and recorded when they happen, and a quarterly cover spend a fraction of the other's.

And one thing that does not appear in any number: the person who handles the mornings does not dread them.

What it looks like when it fails

Even a prepared operation has mornings where nothing works: the list is exhausted, the agency has nobody, the capability cannot be bought at eight in the morning.

The difference is that the failure is fast and documented rather than slow and improvised. By seven the duty holder knows it cannot be covered, applies the reduction plan, tells the people affected, records it, and the day runs at reduced output by decision. That is a good morning too, and it is the one most operations never manage because they are still on the phone at nine.

The afternoon that made it

None of the nineteen minutes was earned that morning. The requirement was written at a meeting in March. The capability map came out of an hour with the scheduler. The call-out list was tested in April and refreshed in July. The part-time questionnaire went out once and takes ten minutes a year to maintain.

That is the whole trick and it is why this subject resists the usual improvement approaches. There is nothing to optimise in the hour itself — it is already being run as well as it can be by somebody doing their best under pressure. Every gain comes from work done calmly, weeks earlier, by somebody who was not under pressure at all.

Getting there

Not all at once. The order that works is the one in the first note of this collection: measure for a month, fix attribution and the obvious structural gaps, then the list, then the requirement, then the authority.

Each step is an afternoon and each step shortens the next morning. The whole thing is perhaps six afternoons spread over a quarter, and the payback shows up in the first winter.