What a night quality desk should keep, and what it should stop copying
A night desk that pastes the alarm dump into the morning mail trains the day shift to skip the mail. The useful object is a short exception list: sector, counter, hour, and whether a ticket already exists.
Agree the exception list before the block starts. If CSSR on a sector falls below the desk’s own threshold for two consecutive hours, it is an exception. If a region average moves, it is not. Region averages are for monthly packs, not for 07:00.
Repeating sectors belong on a separate page that survives the week. If the same cabinet appears four nights running, the morning supervisor should not discover it by memory. Releasegridpath’s overnight review is built around that repeating page.
Do not add new counters mid-block because a vendor slide named them. New counters without a baseline become noise. If the vendor mix changes, freeze the block, write a dictionary addendum, then start a new block.
The local tracking utility can store these night notes without sending them out of the building. It will not page anyone. Paging remains the NOC’s job. Confusing a record-keeping utility with a paging system is how night notes become ignored again.