Trust you slept like a lamb
away home base at the moment with two of the pups ... sleep very well with a warmer body on either side on the bed .. even if rolling over is a bit of a chore.
are you sure this comment passes onto every sheet?
in our case it's not carried forward and that's fine .. I am quite happy that the flightcrews review sufficiently far back to capture anything which hasn't gone away of its own volition
On the other hand, if that caveat didn't apply for a particular operation, then one would be looking to develop an alternative system to achieve the reasonable communication aim
What is wrong with a separate data dump in the tech log?
absolutely nothing at all .. for the sake of a trivial bit of maintenance control workload. While WE don't routinely use it, we have provision to do this sort of thing if we saw a need and I would certainly make sure it happened in such a case. Two sets of circumstances .. in the event of a known U/S for which the decision has been taken to defer maintenance, we use a separate document to record such ... for a grey item we would include a writeup in the ship's folder which, again, is subject to crew review at the start of a sequence. Just the way we do things .. works for our environment ... for someone else .. I would not expect exactly the same system.
Main thing is that the system is a case of horse for courses .. you design, set up, test, and use a system that works for the particular operation it serves. Therefore, my operation's procedures need not necessarily be similar in detail to the one used on the other side of the tarmac .. although both should show a sensible set of similar functions.