"Duct support looks wrong, level 2." A note like that gets no reply, and the support stays as it is.
The engineer who wrote it saw something real. The note failed because whoever received it had to guess where, what, against which document and how urgent. A note that gets acted on answers those before anyone has to ask.
- Say where and when. Level, grid lines, the duct or equipment tag, date and time, and a photo that shows the tag.
- Say what you saw, as a measurement where you can. A line such as "Hanger spacing 3.6 m between grid C and D" is an observation; "looks wrong" is an opinion.
- Quote what the drawing or specification says, with the document number and revision. If you cannot find the requirement, say so. It may be your reading that is off.
- State the consequence if it is left, and when it becomes expensive: once the ceiling closes, or after the pressure test.
- Propose an action, name an owner and give a date.
Written this way the note takes ten minutes where the first took two. It also survives being forwarded, as most site notes are, to someone who was never on level 2.
Our engineers are trained with on-the-job mentoring by senior leads. Looking up the requirement before sending is how a young engineer gets to know the specification.

