Owners and leadership

How to run construction company meetings

Run a small set of recurring meetings with fixed agendas, the right people, a hard time limit, and an action list where every item has one owner and one date.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

To run construction company meetings well, keep a short list of recurring meetings, each with one purpose: a daily or weekly field huddle, a weekly project meeting per job, a weekly operations meeting across all jobs, a weekly leadership meeting on the numbers, and a quarterly planning session. Give each one a fixed agenda, a start and stop time, and a note-taker. End every meeting with actions that have one owner and one due date, and start the next meeting by checking them. Meetings that do not produce decisions should be cut or merged.

Most contractors do not have too few meetings. They have the wrong ones: long Monday sessions where every PM reads out job status, nobody decides anything, and the superintendents leave early to get back to the site. The fix is structure, not more time.

The five meetings a construction company needs

A meeting rhythm for a typical contractor
MeetingWhoWhen and how longPurpose
Field huddle or toolbox talkForeman and crewDaily or weekly, 10 to 15 minutesToday's work, safety topic, problems
Project meeting (OAC or sub coordination)PM, super, owner's team, key subsWeekly per job, 45 to 60 minutesSchedule, RFIs, submittals, changes on one job
Operations meetingOperations lead, PMs, supersWeekly, 60 minutesCrew and equipment allocation, problem jobs, look-ahead across all work
Leadership meetingOwner and seat leadersWeekly, 60 to 90 minutesScorecard numbers, company issues, decisions
Quarterly planningLeadership teamQuarterly, half day to full dayGoals, budget check, hiring, big priorities

Field and project meetings have their own guides: how to run toolbox talks and how to run an effective weekly construction meeting. This page focuses on the company-level meetings: operations, leadership, and quarterly planning.

How to run the weekly leadership meeting

  1. Start on time, every time. If the owner shows up 15 minutes late, everyone learns the start time is a suggestion.
  2. Good news, 5 minutes. One win per person. It sounds soft, but it sets the tone and surfaces things the owner would otherwise miss.
  3. Scorecard, 10 minutes. Each leader reads their numbers: cash, receivables over 45 days, backlog, hit ratio, job margins, incidents. On target or not. No discussion yet, just mark the misses. See how construction owners should review the numbers each week.
  4. Last week's actions, 5 minutes. Done or not done. If not done, it carries over or gets dropped, on purpose.
  5. Issues, most of the time. Pick the most important issue first. Discuss, decide, assign. Then the next one. Stop when time runs out; the rest wait a week.
  6. Recap actions, 5 minutes. Read each action aloud with its owner and date. The note-taker sends them out within the hour.

How to run the weekly operations meeting

The operations meeting exists to share crews, equipment, and attention across jobs. Do not walk every job line by line. Instead:

  • Review the crew and equipment board for the next two weeks. Who is short, who has extra?
  • Each PM names only jobs that are red: behind schedule, over hours, or waiting on a customer decision.
  • Check long-lead items and deliveries that affect more than one job.
  • Flag unsigned change orders over a set dollar amount.
  • Agree on moves: crew X goes to the school job Tuesday, the boom lift goes to the warehouse Thursday.

Use the three-week look-ahead from each job as the input. For multi-job crew planning, see how to schedule crews across multiple jobs.

How to run quarterly planning

Once a quarter, step away from the jobs for half a day. Review how the quarter went against the annual budget and goals, decide three to five priorities for the next quarter, assign each to one leader, and look at hiring needs against backlog. Keep the list short. A contractor that picks fifteen priorities usually finishes none of them. The annual version of this meeting builds the company budget for the year.

Worked example: fixing a three-hour Monday meeting

As an example, consider an electrical contractor around $12 million with six PMs and five supers. Every Monday from 7 to 10, all eleven of them plus the owner and controller sit in one room. Each PM reports on every job. Supers leave halfway through. Decisions get made in the parking lot afterward.

The owner splits it in two. A 60-minute operations meeting at 7 a.m. Monday covers crews, equipment, and red jobs only, with supers attending. A 75-minute leadership meeting Tuesday at 1 p.m. includes the owner, operations manager, chief estimator, and controller, built around the scorecard. PM job details move into weekly job reviews the operations manager holds with each PM.

Total meeting hours across the team drop from about 39 a week (13 people times 3 hours) to about 16 (11 people for one hour, plus 4 people for 75 minutes). Supers are back on site by 8:15. The action list gets shorter and actually gets done, because each item now has one name on it.

Remote and job-site meetings

Many leaders spend the day on different sites, so a video call is often the only way to get everyone together. Keep the same agenda and time box, share one screen with the scorecard or crew board, and ask people to join from somewhere quiet rather than from a running truck. A short meeting that starts on time works better remotely than a long one.

Meeting mistakes to avoid

  • Status reports instead of decisions. Status belongs in a report people read before the meeting.
  • Too many people. Every extra person adds talk time. Invite those who decide or do, not everyone who might be interested.
  • No written notes. If it is not written down, it did not happen. Use a construction meeting minutes template.
  • Shared ownership. "Ops and estimating will look at it" means nobody will. One name per action.
  • Solving everything in one week. Prioritize issues. The ones you do not reach still matter next week.
  • Letting the owner dominate. If the owner talks first on every issue, others stop offering opinions. Ask the team, then weigh in.

Templates and tools for better meetings

Use the construction meeting minutes template for action tracking and a construction project tracker template as the shared job list. Meetings go faster when job cost, change orders, and schedules live in one system that everyone can open before they walk in, so the meeting is for decisions, not for finding the numbers.

Smart Business Automator keeps projects, change orders, job costing, and daily log summaries in one place, so the operations and leadership meetings can open the same screens. See construction workflow automation.

Frequently asked questions

How long should a construction leadership meeting be?

Sixty to 90 minutes weekly works for most contractors. Hold to the end time so people trust the schedule.

Should superintendents attend company meetings?

Yes for the operations meeting, where crews and equipment are allocated. Usually not for the leadership meeting unless a general superintendent holds a leadership seat.

What is the difference between an operations meeting and a project meeting?

A project meeting covers one job in depth with the owner's team and subs. An operations meeting looks across all jobs to share crews, equipment, and attention.

How do I stop meetings from running long?

Set a fixed agenda with time boxes, send reports before the meeting, keep attendance small, and stop at the end time even if issues remain.

Who should take notes in a construction meeting?

Assign one person, often an office manager or project engineer, and rotate if needed. Notes should list decisions and actions with owners and dates, not a transcript.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment