Look before you raise the alarm.

Imagine a community theater preparing for opening night. During rehearsal, you notice that the lead actor's coat still has a torn lining. You are about to message the costume supervisor and copy the director: “This is still broken and needs to be fixed before tomorrow.” Then you open the costume board. The supervisor photographed the repair twenty minutes ago and marked the coat ready for fitting.

Your observation was reasonable. Your message would still have landed badly. It carried an extra claim: I assume you have not noticed or handled this. To someone who just completed the work, that claim overshadows the useful concern.

Herbert Clark used the term common ground for the pool of knowledge people believe they share. Every warning makes an estimate about that pool. When you flag a problem, you imply that the information is not yet in the other person's common ground. If that estimate is wrong, even a polite warning can sound like an accusation.

The solution is not adding softer words to an unchecked message. It is improving your estimate before you send it.

Use a thirty-second rule. Before raising a problem to a specific person, spend thirty seconds checking whether they already know. Look at the board, the handoff note, the latest message, the maintenance log, or whatever record that work leaves behind. If a quick check is available, use it.

Fast flagging can feel like diligence. Sometimes it is only transferring your uncertainty to someone else. They must stop, find the link, explain what they did, and reassure you that the work is moving. Your thirty seconds becomes several minutes of their attention.

After you check, you will usually find one of three cases.

First, nobody appears to be handling the problem. Raise it plainly: “I checked the costume board and do not see the torn lining listed. I found it during the second scene. Who can take it?” Saying that you checked gives the warning weight. It shows that this is not a reflex.

Second, the work is active. Usually, say nothing. If you can offer something useful, keep it light: “Saw the coat repair is underway. I can bring it to the fitting room if that helps.” You are acknowledging the work instead of demanding an account of it.

Third, someone started but the status is unclear. Ask a question: “Is the coat repair still moving, or is it waiting on material?” A started task can look exactly like an active one from a distance. Asking allows the person to update you without defending themselves against an alarm.

This distinction matters because repeated false alarms create a tax. The person doing the work must re-explain, re-link, and prove progress. Eventually they stop treating your messages as useful signals. You have become another status system they must maintain.

There are exceptions. If someone is in immediate danger, do not search a board while a light fixture falls. Raise the alarm. The thirty-second rule applies when a short check will not increase the harm. It is a communication rule, not a reason to hesitate in an emergency.

What if you receive a warning about something you already handled? Answer with the fact, not the irritation: “The lining was repaired at three twenty and is ready for fitting.” If the same person repeatedly skips the available record, name the pattern once: “Before flagging costume issues, check the board's latest update. It will save both of us a second round.” Specific guidance is more useful than sarcasm.

Do not demand that everyone inspect a maze of systems before speaking. Your records must be current and easy to find. If the costume board is routinely wrong, checking it is not a fair expectation. Common ground is shared work. The person doing the task updates the visible record; the person raising a concern looks at it.

Also separate observation from ownership. You may see a loose button without knowing who owns the repair. Start with the shared place, not the person you happen to associate with costumes. “The coat has a loose button and I do not see it logged” leaves room for the actual owner to respond. Naming the wrong person adds another needless correction and can make a useful report feel like blame.

Here is the practice. The next time you notice a problem in someone else's area, pause before typing. Find the last thing that person touched: a log entry, board update, handoff, or message. Spend thirty seconds deciding which case you have. Then choose the matching response: “I checked and do not see anyone on this,” “I see you are on it,” or “Is this still moving?”

That is the lesson. A warning is a claim about what another person knows. Check the shared record, make the claim accurate, and save the alarm for a problem that still needs one.