Writing Down the Morning

The record that matters is made by the person who ran the morning, at the end of their shift, on one line. Everything else in this collection depends on it existing and almost no operation has it.

The practical issue in “Writing Down the Morning” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring productivity software for business, the official site can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.

It is not a report and it is not an incident form. It is a log, in the sense that a ship's log is a log: short, contemporaneous, factual, and useful mainly in aggregate.

For an independent benchmark relevant to “Writing Down the Morning”, consult the IFRS standards resources. 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 line

Date and shift. Requirement and what it ran with. Duration of the shortfall. Capabilities uncovered, if any. Routes tried, in order, with outcomes. Who covered and at what cost. What was deferred or reduced. Who decided. Anything that went wrong.

Nine fields, most of them a word or a number. Ninety seconds if the sheet is in front of you and the morning is still fresh.

Who fills it in

The person who handled the morning, not a manager later and not an administrator from the absence record. Both of those produce a reconstruction, and the specific things worth knowing — how many calls, who refused, what was tried — are only in the head of whoever made the calls.

Within the shift. By the next day the call sequence is gone, and the line becomes "one short, agency booked", which is the absence record with extra steps.

Who keeps it

Operations. The log describes shifts and cover, not people, and putting it in an HR system both changes what it is and makes it harder to reach for the people who need to read it.

One sheet per site per month, collected quarterly. A folder is adequate. A shared spreadsheet is better because it adds up.

The three ways it dies

It becomes a form. Somebody adds dropdowns, mandatory fields, a free-text box for root cause, and a validation rule. The time goes from ninety seconds to six minutes and it stops being filled in.

Nobody reads it. Three months of lines accumulate and nothing happens, and the people writing them correctly conclude it was pointless. The quarterly summary is not optional — it is the thing that keeps the log alive.

It becomes evidence against somebody. The first time a line is used in a conversation about an individual's performance, the log stops being honest. Everyone will record one short, cover found, nothing went wrong, forever.

Keeping it about the shift

No names of absent people — the absence record already has those and the log does not need them. The shift is the subject.

Names of people who covered are useful and should be in a way that is visible to the person: knowing who absorbed how much is one of the main uses of the log, and it should be information the team can see rather than something kept about them.

No health information. It belongs in the absence record under whatever handling applies there, not in an operational log that a dozen people read.

The quarterly summary

One page, built from the lines. Shifts below requirement. Cover spend by route. Mornings by duration. Capabilities uncovered, counted. Who absorbed. What was deferred more than twice.

Circulated to the people who filled it in, and to whoever decides establishment and training. It is the only product of the log and the only reason it continues to exist.

Starting it

Do not design it. Take the nine fields, put them in a spreadsheet, print it, put it where the phone is, and ask the duty holders to fill in a line for a month.

At the end of the month the fields that were always left blank are the ones to drop, and the thing people kept writing in the margin is the field to add. That is the whole design process and it takes four weeks of real use rather than a workshop.

The first month

Expect the first month to be patchy. Some lines will be missing, several will be filled in two days late, and a few will say nothing useful.

That is normal and it is not a reason to add enforcement. What fixes it is the first quarterly summary landing in front of the people who wrote the lines, with something in it they recognise and something that changed as a result. Compliance after that is high and requires no chasing, which is the opposite of how most recording obligations behave.