Speaking in meetings as a site leader: facts, implications and a clear request
A superintendent has raised a ceiling coordination concern with the project manager, but it keeps returning in meetings without a clear response. He knows the affected area and upcoming work but is hesitant to speak. Preparing the issue can help him contribute without needing a long presentation.
Prepare three points: what is happening, what the supported effect is and what decision or information you need by a useful date. Use them as a concise opening, then answer questions and record the actual response. A three-sentence pattern can help organize your contribution; it does not guarantee that others will agree or that a decision can be made in the room.
Prepare the item before the meeting
- Confirm the facts and reference. Identify the location, current information and observed condition. Separate what you know from an assumption or unresolved technical question. Bring the relevant record through the approved system so participants can find it. Avoid saying the whole job is stopped when only a defined area has been affected.
- Explain the supported effect. Link the issue to the next task, access, sequence or commercial question where the evidence allows it. Check an important schedule or cost implication with the responsible person. State uncertainty plainly rather than inventing a delay or amount to make the item sound serious.
- Name the request and useful date. Ask for a specific response, review or authorized decision. Explain what drives the date and who needs the information. Coordinate the agenda item with the meeting lead where appropriate; a request for a technical answer is different from asking the room to improvise one.
- Speak and listen. Present the three points in plain language, then allow questions. Correct your information if new evidence changes it. If the matter needs another reviewer, ask for the referral and follow-up owner rather than forcing closure. Do not use the next routine meeting as a reason to delay an urgent reporting process.
- Check what was recorded. Confirm the response, owner, date and any unresolved question through the project's normal record process. Keep a pending item pending. A polite acknowledgement or silence does not establish that the requested direction has been issued.
Practise aloud with a colleague if it helps, using only information you are permitted to share. The aim is to make a field question understandable, not to perform confidence or apologize for bringing it. You can say what you observed and ask for the appropriate review without pretending to know another discipline's answer.
Common mistakes
- Reporting a general complaint without a location or request.
- Inflating an unverified effect to gain attention.
- Treating meeting silence as approval or closure.
What to say
Prepare your opening
Check your understanding
The meeting hears your item but cannot decide it. Has the contribution failed?
