Phone and messages discipline for site leaders: when to answer and when to let it ring
The superintendent opens a drawing to check one interface and receives four routine calls before reaching the detail. A foreman then sends an urgent question into the same message stream. Simply silencing the phone would remove noise without giving the site a dependable way to reach the right person.
Make availability an agreement people can use. Explain which matters need the site's established immediate response, how routine requests reach you and when a callback can reasonably be expected. Arrange cover where your role requires it. The goal is useful response and room to complete work, not an arbitrary two-hour phone ban or a promise to answer every urgent call personally.
Give callers a dependable response route
- Identify what must reach the responsible person promptly. Use the actual site emergency, safety and operational arrangements. Include time-sensitive decisions whose answer cannot wait for your routine window. Confirm the contact route and cover with those responsible. An urgent message left in a group chat is not a dependable response arrangement merely because you usually look at it.
- Set realistic routine callback expectations. Tell frequent callers how to provide the location, question, needed answer time and relevant reference. Choose windows that fit your responsibilities and their work. Say how changed urgency should be raised. If another person owns the decision, route the request and confirm receipt instead of becoming the sole relay for every question.
- Check messages in a suitable setting. Use agreed cover for work that needs your attention, while retaining the necessary contact arrangements. Do not combine business calls with driving between sites. CCOHS advises avoiding phone use while driving and making calls from a safe parked location; a hands-free conversation still distracts. Plan stationary response time instead of promising callbacks during the journey.
- Close the response loop. Review the queued requests, return the needed answer or state its actual pending status, and record a meaningful next contact. Tell affected people if the window changes. Check recurring missed contacts and adjust the agreement. A notification marked read does not confirm that the foreman received a usable decision or that you understood its deadline.
Common mistakes
- Silencing the phone without an agreed urgent route.
- Offering callback windows that miss known decision deadlines.
- Making driving time the normal business-call period.
- Treating a read receipt as a received decision.
Action list
Agree phone availability around
- The site's actual immediate-response routes.
- Routine questions with location and answer time.
- Realistic windows and received decision handovers.
- Suitable stationary response settings and needed cover.
- Pending answers and changes to the agreement.
Check your understanding
A purchasing answer is needed before your routine callback window. What should the foreman do?
