△
Meeting Cue
Task-specific guidance for ordinary meeting-preparation and facilitation issues.
Project 09
Run a Jobsite Coordination Meeting
Plan, conduct, document, and close one residential jobsite coordination meeting that produces decisions, commitments, constraint removal, and accountable action items, using the current schedule, lookahead, procurement, RFI, change, safety, quality, inspection, and cost information as the controlling meeting content.
Field Cue System
These cues appear at the point of work. They identify authority, documentation, and coordination issues before they become missed commitments, unresolved constraints, or unrecorded decisions.
✋
Critical Coordination Cue
An unassigned action, an undocumented decision, or an unresolved safety issue is possible.
⛑
Field Safety Cue
Practical guidance for opening every meeting with safety, access, and public-protection issues.
▤
Authority Alert
Confirm which attendee actually holds decision authority before recording a decision.
▧
Contract Instruction Cue
Follow the executed agreement's specific terms for formal notice when a meeting decision requires it.
▱
Documentation Cue
Recordkeeping, distribution, and traceability guidance for meeting records.
Job Overview
This project qualifies you to plan, conduct, document, and close one residential jobsite coordination meeting. The finished work product is one completed meeting record: a distributed agenda, verified attendee list, reviewed schedule and safety status, recorded decisions, assigned action items with owners and due dates, and published minutes filed in the project job file.
You will define the meeting purpose and required attendees, review prior action items before building the agenda, collect current project-control information, run the meeting starting with safety, walk the schedule, procurement, trade handoffs, quality, inspections, RFIs, changes, and owner decisions, assign every action item to one named person with one due date, publish minutes promptly, and update every project-control log the meeting affected.
This project depends on the scope baseline from Project 01, the job file from Project 02, the schedule from Project 05, the lookahead from Project 06, the procurement plan from Project 07, and the trade-coordination system from Project 08. A coordination meeting that is not built on current versions of those documents produces decisions based on stale information. The coordination-meeting discipline built here also directly supports Project 10 through Project 17, because RFIs, changes, safety issues, quality deficiencies, inspections, and owner communication are all reviewed and actioned through this same meeting structure.
Skills You Will Demonstrate
- PM-049 — Prepare a meeting agenda.
- PM-050 — Review schedule status.
- PM-051 — Review safety issues.
- PM-052 — Review open questions.
- PM-053 — Assign action items.
- PM-054 — Publish meeting notes.
Where This Skill Fits
The coordination meeting is the recurring control point where every other project-management system in this book is checked, updated, and advanced. The schedule from Project 05 and the lookahead from Project 06 are reviewed here for actual progress and near-term commitments. The procurement log from Project 07 is reviewed here for items threatening installation dates. The trade-handoff system from Project 08 is reviewed here for unresolved interface deficiencies. The RFI process in Project 10, the change-control system in Project 11, the safety plan in Project 12, the quality plan in Project 13, and the inspection system in Project 16 all rely on this meeting to surface issues, assign owners, and record decisions.
The discipline of distinguishing discussion from decision, and assigning one named owner and one due date to every action, taught in this chapter, is the same discipline used later throughout the book whenever an issue must be tracked from identification to verified closure.
Scope and Intended Use
This project covers:
- defining the meeting purpose, frequency, location, platform, duration, required attendees, and decision authority
- reviewing prior minutes and open action items before building the agenda
- collecting current schedule, lookahead, procurement, RFI, change, safety, quality, inspection, and cost information
- preparing and distributing an agenda that opens with safety and covers status, schedule, procurement, inspections, RFIs, changes, owner decisions, trade interfaces, and closeout
- conducting the meeting, recording actual commitments, and distinguishing discussion, recommendation, decision, instruction, approval, and pending information
- assigning each action item to one responsible person with one due date and one closure criterion
- publishing minutes promptly and updating every project-control log the meeting affected
- following up on overdue items before the next meeting
This project does not authorize the learner to:
- approve scope, cost, schedule, or design changes in the meeting unless the meeting attendee holds the decision authority identified in the Project 01 scope statement or the executed agreement
- direct unsafe work, bypass a safety control, or override a required inspection to satisfy a schedule commitment made in the meeting
- record “team” or an unnamed group as the responsible party for an action item
- treat verbal discussion in the meeting as a substitute for the written notice method the executed agreement requires for formal decisions
Any conflict between what is discussed in the meeting and the current approved scope, schedule, or budget baseline must be identified and routed through the appropriate change-control, RFI, or schedule-update process rather than treated as an informal revision.
Reference Conventions
Establish these references before the first meeting, and do not change them mid-project without a recorded revision.
| Term | Definition |
|---|---|
| Discussion | An exchange of information or opinion that does not by itself authorize or direct any action |
| Recommendation | A proposed course of action offered for approval by the party holding decision authority |
| Decision | An authorized determination made by the party holding decision authority for that subject |
| Instruction | A direction to perform, stop, or change work, issued by a party authorized to issue it |
| Approval | Formal acceptance of a scope, cost, schedule, design, or acceptance item by the authorized approver |
| Pending information | Information that has been requested but not yet received, recorded with a responsible party and due date |
| Action item | A task assigned to one named responsible person with one due date and one stated closure criterion |
Coordination Meeting Record
Before distributing the minutes, record the meeting identification directly on the meeting minutes template:
Project name: ______ Meeting date: ______ Meeting number: ______ Location or platform: ______
Attendees: ____________ Absentees: ____________ Recorded by: ____________ Next meeting date: ____________
Prerequisites
- An approved scope baseline (Project 01), job file (Project 02), and current baseline schedule (Project 05) and two-week lookahead (Project 06) available for reference
- Access to the current procurement log (Project 07), trade-handoff records (Project 08), RFI log, change log, safety records, quality plan, inspection register, and job-cost report
- Identification of the meeting purpose, required attendees, and the decision authority for scope, cost, schedule, design, and safety subjects likely to arise
- A meeting agenda template, action-item log, decision register, and minutes template ready for use
- A defined confidentiality rule for cost, billing, personnel, and payroll information that may be discussed
Common Field Fundamentals
Every coordination meeting in this book, from a routine weekly jobsite meeting to a Chapter 20 capstone project meeting, follows the same sequence: prepare, open with safety, review status, review open items, decide, assign, publish, follow up. Learning that sequence here, on one residential project, means every later coordination meeting starts from a method you already trust.
PreparationPrior action items reviewed and current project-control information collected before the agenda is built
AgendaDistributed with enough advance notice for informed attendance and preparation
Safety openingEmergency, safety, access, weather, and public-protection issues reviewed first
Status reviewSchedule, procurement, handoffs, quality, inspections, RFIs, and changes reviewed against current logs
DecisionsDistinguished from discussion and recorded with the authorized decision maker named
Action itemsOne named owner, one due date, one closure criterion per item
MinutesPublished promptly with a defined correction period
Follow-upOverdue items tracked and addressed before the next meeting
Discussion, Recommendation, Decision, Instruction, and Approval
A coordination meeting record must distinguish these five categories every time information is exchanged. A comment made in discussion is not a decision until the authorized decision maker states it as one, and the minutes must record it that way. Treating discussion as decision, or a recommendation as an instruction, is a leading cause of work performed on an unauthorized basis.
PM-049 – PM-054
Coordination / Meeting-Management Qualification
Residential Jobsite Coordination Meeting
A. Finished-Project Specification
Deliverable: one completed residential jobsite coordination meeting record, containing a distributed agenda, verified attendance, a safety review, current schedule and status review, recorded decisions distinguished from discussion, assigned action items with owner, due date, and closure criterion, and minutes published promptly and filed with updates carried to every affected project-control log.
B. Meeting Record Document Schedule
| Section | Content | Source | Purpose |
|---|---|---|---|
| Meeting identification | Project name, date, meeting number, location or platform, attendees, absentees, recorder | Meeting minutes template | Establishes the meeting the record governs |
| Agenda | Project status, safety, quality, schedule, procurement, inspections, RFIs, changes, owner decisions, trade interfaces, closeout | Agenda template, prior minutes | Defines the topics to be covered and prepared for |
| Safety review | Incidents, near misses, observations, corrective actions, upcoming high-risk work | Safety plan, incident records | Confirms hazards are addressed first through the approved safety process |
| Schedule and lookahead review | Milestone status, forecast, near-term committed work by area, trade, crew, material, and constraint | Baseline schedule, two-week lookahead | Confirms actual progress and near-term commitments against the baseline |
| Procurement and handoff review | Items threatening installation dates; unresolved trade-interface deficiencies | Procurement log, trade-handoff records | Surfaces material and interface risks before they affect the schedule |
| Quality and inspection review | Checkpoints, mockups, first-work inspections, deficiencies, punch status; inspections scheduled, passed, failed, corrected, pending | Quality plan, deficiency log, inspection register | Confirms quality and inspection status are current and tracked |
| RFI and change review | Open RFIs by age, impact, and required response date; change events, pricing, authorization, schedule effect, work status | RFI log, change log | Confirms open questions and changes are tracked to resolution |
| Owner decisions and cost | Pending selections, allowances, approvals; cost or billing issues reviewed only with appropriate attendees | Owner-decision log, job-cost report | Confirms owner-dependent items and cost issues are visible and assigned |
| Decisions and actions | Decisions distinguished from discussion with authorized decision maker named; action items with owner, due date, closure criterion | Meeting discussion, decision register, action-item log | Records what was authorized and what remains to be done |
| Distribution and follow-up | Draft or final minutes distributed promptly; correction period; overdue items tracked before next meeting | Minutes template, distribution list | Ensures the record reaches affected parties and is acted upon |
C. Information and Document Takeoff
- Source records: prior meeting minutes, current baseline schedule, two-week lookahead, procurement log, trade-handoff records, RFI log, change log, safety records, quality plan, inspection register, and job-cost report, sufficient to prepare every agenda topic without inventing missing status information.
- Attendance records: the required-attendee list and the decision authority for scope, cost, schedule, design, and safety subjects likely to arise, confirmed before the meeting begins.
- Action and decision records: the action-item log and decision register, updated during the meeting rather than reconstructed afterward.
- Distribution record: the confirmed distribution list and any confidentiality restriction applicable to cost, billing, personnel, or payroll information discussed.
D. Acceptance Standards
| Check | Standard |
|---|---|
| Agenda | Distributed far enough in advance for preparation; covers status, safety, quality, schedule, procurement, inspections, RFIs, changes, owner decisions, and trade interfaces |
| Safety opening | Emergency, safety, access, weather, and public-protection issues reviewed first, before status topics |
| Status accuracy | Schedule, procurement, quality, and inspection status reviewed against current logs, not general impressions |
| Decisions | Distinguished from discussion; recorded with the authorized decision maker named |
| Action items | Each item assigned to exactly one named responsible person with one due date and one closure criterion; "team" is never recorded as the responsible party |
| Minutes | Published promptly with attendees, absentees, documents reviewed, decisions, actions, and next meeting date; distributed to attendees and affected parties |
| Log updates | Action log, schedule, procurement log, RFI log, change log, inspection log, and decision register updated to reflect the meeting |
E. Preparation — Define the Meeting and Build the Agenda
- Define the meeting purpose, frequency, location, platform, duration, required attendees, and decision authority. Record these facts before the first meeting and confirm they remain current for each recurring meeting.
- Review prior minutes and open action items before creating the agenda. Identify every item that remains open, overdue, or newly closed since the last meeting.
- Collect current schedule, lookahead, procurement, RFI, change, safety, quality, inspection, and cost information. Pull the current version of each log rather than relying on memory of the last meeting.
- Identify decisions required during the meeting and who must attend to make them. Confirm the person holding decision authority for each anticipated decision is invited.
- Prepare an agenda with project status, safety, quality, schedule, procurement, inspections, RFIs, changes, owner decisions, trade interfaces, and closeout. Order the agenda so safety appears first.
- List open action items with owner, due date, and status. Attach the current action-item log to the agenda.
- Attach or link only the documents needed for informed discussion. Avoid distributing unrelated documents that dilute preparation.
- Distribute the agenda far enough in advance for preparation. Confirm the distribution list matches the required-attendee list.
- Require trade leads to update staffing, material, constraints, and commitments before the meeting. Confirm each trade lead's update is received before the meeting begins.
F. Open the Meeting and Review Safety and Schedule Status
- Start with emergency, safety, access, weather, and public-protection issues. Address these before any status topic, regardless of agenda length.
- Review incidents, near misses, observations, corrective actions, and upcoming high-risk work through the approved safety process. Confirm each item has a responsible party and status.
- Review the baseline milestone status and current forecast. Compare actual progress against the Project 05 baseline schedule.
- Review the two-week lookahead by area, trade, crew, material, inspection, and constraint. Use the current Project 06 lookahead as the reference.
- Record actual commitments rather than general intentions. Do not record a trade's statement of intent as a committed date unless it is stated as a commitment.
- Review procurement items that threaten installation dates. Use the current Project 07 procurement log.
- Review deliveries, storage, lifting, access, and shared equipment. Confirm logistics conflicts are identified and assigned for resolution.
- Review trade handoffs and unresolved interface deficiencies. Use the current Project 08 trade-handoff records.
G. Review Quality, Inspections, Open Questions, and Owner Decisions
- Review quality checkpoints, mockups, first-work inspections, deficiencies, and punch status. Use the current quality plan and deficiency log.
- Review inspections scheduled, passed, failed, corrected, and pending. Use the current inspection register.
- Review RFIs and field clarifications by age, impact, and required response date. Identify any RFI at risk of affecting the schedule.
- Review pending owner decisions, selections, allowances, and approvals. Confirm each pending decision has a required-by date visible to the owner.
- Review change events, pricing, authorization, schedule effect, and work status. Use the current change log.
- Review cost or billing issues only with the appropriate attendees and confidentiality. Exclude attendees who do not require this information.
H. Record Decisions, Assign Actions, Publish, and Follow Up
- Distinguish discussion from decision and record the authorized decision maker. Use the reference conventions above for every recorded item.
- Assign each action item to one responsible person. Do not defer this assignment to "after the meeting."
- Assign one due date and one closure criterion to each action. State the observable condition that will close the item.
- Do not record "team" as the responsible party. Name the individual, not the group they belong to.
- Read back critical decisions, dates, and commitments before adjournment. Confirm agreement from the relevant attendees before closing the meeting.
- Record unresolved disagreements and required escalation. State who is responsible for escalating and by what date.
- Publish draft or final minutes promptly according to project rules. Do not allow minutes to lag so far behind the meeting that commitments are forgotten.
- Include attendees, absentees, documents reviewed, decisions, actions, due dates, and next meeting. Complete every field on the minutes template.
- Distribute minutes to attendees and affected parties. Confirm the distribution list matches Step 8 plus any party affected by a recorded decision.
- Provide a defined correction period for factual errors. State the correction deadline in the distributed minutes.
- Update the action log, schedule, procurement log, RFI log, change log, inspection log, and decision register. Carry every meeting outcome into the affected project-control log before the next meeting.
- Follow up on overdue items before the next meeting. Contact the responsible party for any item past its due date.
- Archive the agenda, attendance, attachments, notes, issued minutes, and corrections. File the complete meeting record in the project job file established in Project 02.
Common Meeting-Record Inspection
Inspect every coordination meeting record using the same checks regardless of project size or meeting frequency.
- Agenda check: confirm the agenda was distributed with adequate advance notice and covers every required topic in the standard order, with safety first.
- Safety check: confirm emergency, safety, access, weather, and public-protection issues were reviewed before status topics.
- Status check: confirm schedule, procurement, quality, and inspection status were reviewed against current logs, not general impressions.
- Decision check: confirm every recorded decision names the authorized decision maker and is distinguished from discussion or recommendation.
- Action-item check: confirm every action item has exactly one named owner, one due date, and one closure criterion.
- Publication check: confirm minutes were published promptly, distributed to attendees and affected parties, and that every affected project-control log was updated.
Complete the Coordination Meeting Inspection Checklist in the Inspection Checklist section below before beginning Project 10.
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Failure Points and Troubleshooting
Cleanup
This project ends with the meeting record filed and every affected log updated, not left as an open draft.
- Confirm the minutes are published, distributed, and past the stated correction period
- Confirm the action-item log shows every item with one owner, one due date, and current status
- Confirm the decision register reflects every authorized decision with the decision maker named
- Confirm the schedule, procurement log, RFI log, change log, inspection log, and job-cost report reflect every update the meeting required
- File the complete meeting record — agenda, attendance, attachments, minutes, and corrections — in the project job file established in Project 02
Field Terms
- Coordination Meeting
- A recurring project meeting used to make decisions, assign actions, remove constraints, and confirm commitments.
- Discussion
- An exchange of information or opinion that does not by itself authorize or direct any action.
- Decision
- An authorized determination made by the party holding decision authority for that subject.
- Action Item
- A task assigned to one named responsible person with one due date and one stated closure criterion.
- Decision Register
- A record distinguishing authorized decisions from discussion and recommendation, naming the decision maker.
- Action-Item Log
- A log tracking each assigned action to owner, due date, closure criterion, and status.
- Read-Back
- Restating a critical decision, date, or commitment aloud for confirmation before adjournment.
- Constraint
- An unresolved condition, such as missing information, labor, material, or access, that could prevent a scheduled task from proceeding.
- Escalation
- The defined process for raising an unresolved disagreement or overdue item to a higher decision authority.
- Correction Period
- The defined window after minutes are distributed during which attendees may report factual errors.
Skill Check
- Why must every coordination meeting agenda begin with safety, access, weather, and public-protection issues before status topics?
- What is the difference between discussion and decision, and why must a meeting record distinguish them?
- Why must an action item never be assigned to "team" as the responsible party?
- What three elements must every action item carry, and why is a closure criterion necessary in addition to an owner and a due date?
- Why must the read-back of critical decisions and commitments occur before adjournment rather than after minutes are published?
- What must occur before a meeting attendee's statement can be recorded as an authorized decision?
- Which project-control logs must be updated after a coordination meeting, and why does delaying these updates create risk?
- What are three possible causes of an action item that is never completed, and how does the learner confirm which one occurred?
- Why must cost or billing issues be reviewed only with appropriate attendees rather than the full meeting group?
- What must happen when the same constraint remains unresolved across consecutive meetings?
Competency Rubric
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-049 | Prepares and distributes a meeting agenda covering status, safety, quality, schedule, procurement, inspections, RFIs, changes, owner decisions, and trade interfaces with adequate advance notice | |||
| PM-050 | Reviews baseline milestone status, forecast, and two-week lookahead commitments against current schedule documents | |||
| PM-051 | Opens the meeting with incidents, near misses, observations, corrective actions, and upcoming high-risk work through the approved safety process | |||
| PM-052 | Reviews open RFIs, changes, and pending owner decisions by age, impact, and required response date | |||
| PM-053 | Assigns every action item to one named responsible person with one due date and one closure criterion, distinguishing decisions from discussion | |||
| PM-054 | Publishes minutes promptly with attendees, decisions, and actions, and updates every affected project-control log |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
Inspection Checklist — Coordination Meeting Inspection Checklist
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Agenda | Distributed with adequate advance notice; covers required topics in standard order | ||
| Safety opening | Emergency, safety, access, weather, and public-protection issues reviewed first | ||
| Schedule and lookahead status | Reviewed against current baseline and lookahead documents | ||
| Procurement and handoff status | Threatening items and unresolved interface deficiencies reviewed | ||
| Quality and inspection status | Checkpoints, deficiencies, punch, and inspection results reviewed | ||
| RFI, change, and owner-decision status | Reviewed by age, impact, and required response date | ||
| Decisions | Distinguished from discussion; authorized decision maker named | ||
| Action items | One named owner, one due date, one closure criterion per item | ||
| Minutes publication | Published promptly; distributed to attendees and affected parties; correction period stated | ||
| Log updates | Action log, schedule, procurement, RFI, change, and inspection logs updated |
Open action items carried forward: ____________ Overdue items requiring escalation: ____________
Meeting record declared complete: ______ (Pass/Fail) Date: ____________ Recorder name: ____________
Performance Check
With the meeting conducted and minutes drafted, review the record against the Acceptance Standards table and confirm the agenda was distributed with adequate notice and covered every required topic beginning with safety, that schedule, procurement, quality, and inspection status were reviewed against current logs, that every decision is distinguished from discussion and names the authorized decision maker, that every action item carries exactly one named owner, one due date, and one closure criterion, and that minutes were published promptly, distributed, and used to update every affected project-control log. Complete the Coordination Meeting Inspection Checklist and correct any failed item before beginning Project 10. If an item fails, identify whether the error occurred in agenda preparation, safety review, status review, decision recording, action assignment, or minute publication before revising.
Project Closeout
You have completed the ninth project in the construction project management sequence: running a jobsite coordination meeting. This project required you to prepare a meeting agenda (PM-049), review schedule status (PM-050), review safety issues (PM-051), review open questions (PM-052), assign action items (PM-053), and publish meeting notes (PM-054).
You now have a completed coordination meeting record with a distributed agenda, a safety-first status review, recorded decisions, assigned and tracked action items, and published minutes filed in the project job file. That recurring meeting discipline carries directly into the next project: managing requests for information and field clarifications, which relies on the same meeting structure to surface ambiguities, track responses, and update field documents.
File your completed agenda, decision register, action-item log, and published minutes where Project 10 can reference open RFIs and field clarifications first raised in this meeting. Every later coordination meeting in this book follows this exact prepare-review-decide-assign-publish-follow-up sequence.