Skip to content
Menu

Time management

Got a minute? Clarify the consequence, answer time and responsible receiver

By Review.LivePublished 3 min readHow we write

The electrical foreman stops the superintendent with 'Got a minute?' The superintendent is already walking to a scheduled receiving check. Saying yes could open an unbounded discussion; saying 'later' could miss a decision that genuinely affects today's work.

Two colleagues in hard hats and high-visibility clothing discuss work at ground level.
Photo: RONNAKORN TRIRAGANON on Unsplash

Clarify the request before committing to the whole conversation. Ask for its consequence, needed answer time and actual decision owner. Then arrange the appropriate response. A short triage can be useful, but thirty seconds is not a rule or a guarantee that every request can be safely classified that quickly. Unclear consequential matters need clarification, not a convenient dismissal.

Make the first exchange useful

  1. Ask what the request is about. Try 'What answer do you need, and what depends on it?' Obtain the location and enough context to identify the consequence. Keep the site's established emergency and safety response available. Do not assume a calm tone means the matter can wait, or demand a perfect written submission before responding to something requiring immediate attention.
  2. Establish the real answer time. Ask whether work is waiting, a decision window is closing or another person needs an input. Separate preference from the actual commitment. A crew can be working now while a supplier's booking still needs an answer earlier than your next round. Where consequences are unclear, investigate further rather than guessing urgency from who speaks loudest.
  3. Identify the responsible receiver. Check whether you can answer within your role or need another person's review. Make a referral received, with the question and needed time attached. Do not give informal technical or commercial permission to save a conversation. If the correct receiver is unavailable, use the applicable escalation route instead of telling the requester to keep trying names.
  4. Agree the response and close the exchange. Respond now, arrange a specific later conversation or make the needed referral. State what information to bring and what remains pending. Confirm that the requester understands the next step. If the issue grows during triage, reassess the response; a quick first exchange should organize the question, not conceal its complexity.

Common mistakes

  • Saying later before understanding the consequence.
  • Equating no stopped crew with no time-sensitive decision.
  • Referring a person without the question or needed date.
  • Giving unauthorized permission to keep the exchange short.

What to say

A short request-triage script

  1. You:What answer do you need, and where?
  2. You:What depends on it, and when does the answer matter?
  3. You:Who has the actual decision or review responsibility?
  4. You:We will respond now, meet at an agreed time, or confirm this referral.
  5. You:Here is what remains pending and what information the receiver needs.

Check your understanding

Nobody is waiting on site, but a supplier decision closes before the next round. Can the request wait automatically?

Show the answer
Establish the actual needed answer time and route it to the responsible person. The absence of a stopped crew does not remove a closing decision window. Confirm the received question and next step instead of applying a fixed stock reply.

Related articles