Question rounds: group routine requests and keep consequential answers moving
Three foremen visit the trailer separately about next week's access. Each conversation interrupts the superintendent's current coordination task, but none has the drawings needed for an answer. A planned round could collect those routine questions together if everyone also knows which matters must reach the responsible person sooner.
Group suitable routine questions into announced rounds with the crews. Choose their timing and frequency from the work's actual needs; two rounds may suit one day and fail another. Provide a clear route for matters that cannot wait. The arrangement creates a predictable conversation, not a guarantee that forty interruptions become two or permission for the leader to become unreachable between visits.
Use rounds for questions that can genuinely wait
- Agree the round with the affected crews. Check locations, shift arrangements, decision lead times and when foremen can bring useful inputs. State when and how the round will happen, including coverage if you are diverted. A fixed visit after a crew's needed answer time is not a useful routine. Change the schedule when the actual phase or receiving conditions change.
- Explain the route for earlier response. Keep the site's emergency and safety arrangements clear. Also consider stopped work, expiring decision windows and other consequential constraints under the actual site process. The examples are not an exhaustive list. Ask crews to identify the needed answer time rather than deciding every non-emergency request can automatically wait until afternoon.
- Bring questions ready for an answer. Ask for the location, current reference, observed gap and decision needed. Review shared interfaces together where appropriate. Record a received answer, a required review or an owned follow-up; do not guess a technical response simply to finish the circuit. Give routine questions a place to wait without losing their consequence or their owner.
- Check whether the arrangement is working. Review missed deadlines, repeated visits and questions arriving without inputs. Adjust timing or preparation where the round is causing a delay. Confirm that referred matters reached their receivers. The number of fewer interruptions alone does not establish success if a crew waited unnecessarily or an answer was never actually delivered.
Common mistakes
- Choosing rounds without checking actual decision lead times.
- Making three example exceptions the entire urgent-contact policy.
- Giving guesses to keep the circuit short.
- Counting fewer visits while missing received answers.
Checklist
A useful question round has
- Agreed time, crews, route and coverage.
- An earlier-response route for consequential matters.
- Prepared questions with location and needed answer time.
- Received answers or owned required reviews.
- A check of actual delays and handover results.
Check your understanding
A non-emergency request needs an answer before the next round. Should it wait because it is routine?
