Site Meetings Should Produce Decisions, Owners and Deadlines, Not Only Minutes
A site meeting creates value only when the discussion produces clear decisions and controlled follow-up.
Managing construction, renovation, or fit-out projects in Thailand requires more than just gathering stakeholders in a room. Site meetings are essential checkpoints where progress is reviewed, issues are addressed, and the project’s direction is confirmed. Yet, many meetings end with lengthy minutes that document discussions but fail to translate into actionable outcomes. This article explains how structured site meetings should convert project issues into decisions, assigned actions, and deadlines, ensuring effective project control and delivery.
Defining the Purpose of the Site Meeting
Site meetings serve as a platform to review multiple aspects of the project. Their purpose is to ensure alignment among all parties and to resolve outstanding matters that affect progress. Key topics typically include:
Progress updates against the programme
Review of design information and any changes
Procurement status and upcoming deliveries
Site access and logistics
Quality control and safety compliance
Requests for Information (RFIs) and their responses
Variations and change orders
Inspections and testing results
Identification of open risks
Decisions required from the owner or client
Each meeting should focus on these areas to maintain momentum and avoid surprises later in the project.
Preparing a Focused Agenda
A well-prepared agenda is the backbone of an effective site meeting. It should be issued in advance to all participants, clearly outlining:
Topics requiring information, discussion, or decisions
Relevant documents to review during the meeting
Responsible presenters or experts for each topic
Time-critical matters that need urgent attention
Routine updates or information that do not require discussion can be circulated separately before the meeting. This approach keeps the meeting focused and efficient.
Using Current Project Information
Discussions must be based on the latest, controlled project information. This includes:
The current programme or schedule
Latest approved drawings and design documents
RFI register and status updates
Action logs from previous meetings
Procurement schedules and delivery timelines
Variation logs detailing approved and pending changes
Inspection and testing records
Risk registers highlighting potential issues
Evidence of progress such as photos or reports
Relying on memory or informal messages risks miscommunication and delays. Using verified data ensures all parties have a shared understanding.
Separating Discussion, Decision, and Action
Each agenda item should be clearly broken down into three parts:
Discussion summary: A brief record of the key points raised
Decision: The confirmed outcome or instruction agreed upon
Action: Specific tasks required to implement the decision
For every action, record the responsible owner, due date, current status, supporting documents, and whether escalation is needed. It is important to remember that a discussion does not automatically become a decision.
Recording Decisions Precisely
Decisions must be documented with clarity and precision. A proper decision record should include:
What was decided
Who authorised the decision
Any conditions or limitations attached
The scope affected by the decision
Required follow-up actions
Effective date of the decision
Documents or drawings that need updating
Avoid recording proposals, opinions, or suggestions as approved instructions. This prevents confusion and protects contractual clarity.
Assigning One Action Owner
Every action must have a single, clearly named owner responsible for coordination and completion. Assigning actions to departments or groups often leads to no one taking full responsibility. A named individual ensures accountability and progress.
Setting Realistic Deadlines
Deadlines should be specific dates, not vague terms like “soon” or “next week.” When setting due dates, consider:
Impact on the overall programme
Procurement lead times
Inspection and testing sequences
Time needed for owner or specialist approvals
Dependencies on other information or decisions
Realistic deadlines help keep the project on track and avoid bottlenecks.

Site meeting with project managers reviewing plans and schedules
Maintaining an Action Register
An action register is a living document that tracks all open and closed actions. It should include:
Action ID for easy reference
Description of the action
Origin or meeting where it was raised
Assigned owner
Date raised and due date
Priority level
Current status
Evidence required for closure
Closure date
Impact on programme or cost
Overdue items must be carried forward until formally closed. This register provides transparency and helps prioritise work.
Defining Action Status Clearly
Use clear and consistent status categories such as:
Open
In progress
Awaiting information
Awaiting approval
Overdue
Completed pending verification
Closed
Superseded
Marking an action as “completed” should not mean it is closed until evidence has been reviewed and accepted.
Protecting Contractual Authority
It is crucial to clarify that meeting minutes do not automatically authorise:
Additional costs
Programme extensions
Design changes
Supplier appointments
Contract variations
Payments
Acceptance of defective work
Formal approvals must follow the project’s contractual procedures. This protects all parties and maintains legal clarity.
Issuing Minutes Promptly
Minutes should be circulated promptly while the discussion remains fresh. Participants should have a defined period to review and identify factual errors. Corrections should be recorded without altering the history of decisions.
Beginning the Next Meeting with Overdue Actions
Start each meeting by reviewing:
Previous open actions
Overdue decisions
Blocked activities
Actions affecting the critical path
Outstanding evidence
Avoid creating new minutes if old actions remain unresolved. This focus ensures accountability and progress.
Common Mistakes to Avoid
Many site meetings fail to deliver value due to common pitfalls:
Using the meeting as a general status update without decisions
Discussing issues without assigning actions
Assigning actions to departments instead of individuals
Setting vague or unrealistic deadlines
Recording proposals as approvals
Failing to identify cost or programme impacts
Issuing minutes late, reducing their relevance
Allowing verbal instructions to replace formal approvals
Marking actions complete without verifying evidence
Omitting unresolved actions from minutes
Producing long minutes that hide key decisions
Avoiding these mistakes improves meeting effectiveness and project control.

Detailed action register helps track project progress and responsibilities
Conclusion
The value of site minutes is not measured by their length. It is measured by whether the project can identify what was decided, who must act, when the action is due and what evidence will confirm closure.
Structured site meetings that convert discussions into clear decisions, assigned owners, and realistic deadlines improve project control and reduce risks. Using tools like action registers, decision logs, and programme control systems supports this process.
At AD ASIA Consulting, we provide comprehensive site-meeting management, action tracking, decision logs, programme control, issue escalation, document control, and construction-management services tailored for projects in Thailand. Our expertise helps foreign property owners, developers, investors, and hospitality operators maintain control and achieve successful project outcomes.
If you want to improve your project’s site meeting effectiveness, consider requesting a Site Meeting and Action-Control Review with AD ASIA Consulting. This service will help identify gaps and implement best practices for your project’s success.
Disclaimer: Authority, instructions, variations, payment, and contractual decisions must follow the specific project agreements and authorised procedures.




Comments