A weekly team meeting is where a growing contractor’s team stops depending on the owner to carry information between people. Done badly, it’s the opposite: half an hour of status read-outs the owner already knows, no decisions, and a to-do list that’s all the owner’s. Done well, it takes 30 minutes, looks only at exceptions and what’s coming, makes the decisions that are waiting, and ends with actions that have someone else’s name on them.
This lesson gives the agenda, the action log that makes it stick, who should be in the room, the rules that keep it to 30 minutes, the one question that turns it into a feedback loop from the field, and a worked example of the same week run both ways.
Why most contractor meetings don’t work
- They report status. Status belongs in the job record, updated daily, read before the meeting. Reading it aloud wastes everyone’s time and tells the team the record doesn’t matter.
- They don’t decide anything. The items that need a decision get “let’s talk after,” and after never comes.
- Every action goes to the owner. The team leaves lighter; the owner leaves with nine tasks.
- Nobody checks last week’s actions. So they weren’t really actions.
The agenda below is built against those four failures.
The 30-minute agenda
| Part | Minutes | What happens | Who leads |
|---|---|---|---|
| 1. Last week’s actions | 5 | Read the action log. Each item: done, or a new date with a reason. Nothing else. | Office coordinator |
| 2. Exceptions on active jobs | 10 | Only jobs that are off plan: behind, over cost, blocked, a customer issue. One line each: what’s wrong, what’s needed. Jobs on plan aren’t mentioned. | Operations lead or each crew lead |
| 3. This week’s constraints | 5 | What could stop the week: a crew short, materials late, a permit, a customer not ready, a handoff due. Each gets an owner. | Office coordinator |
| 4. Decisions and actions | 10 | The decisions that were waiting, made in the room. New actions written in the log with an owner and a date. One round of “what slowed you down last week.” | Owner |
Thirty minutes, same day, same time, every week. Standing up works for some crews. A fixed end time works for everyone.
The action log
The log is the meeting’s memory and the thing that makes actions real. One shared table, visible to everyone who attends:
| Action | Owner | Due | Status | Notes |
|---|---|---|---|---|
| Confirm countertop template date with the fabricator and tell the Reyes crew | Dana (office) | Tue | Open | |
| Write the readiness checklist for exterior jobs | Luis (crew lead) | Fri | Open | Draft to Mike for review |
| Decide: second dump trailer, buy or rent for the season | Mike (owner) | Thu | Open | Numbers from the bookkeeper by Wed |
| Call the Nguyens about the change order they haven’t signed | Sam (estimator) | Mon | Done | Signed Monday |
Rules for the log:
- One owner per action. A person, not a crew or “the office.”
- A date, not “this week.”
- The owner isn’t the default. When an action lands and nobody’s named, the question is “who should own this,” not “I’ll handle it.”
- Decisions are logged too, with who made them and when. “Decided Thursday: rent the trailer through October, review in the November meeting.” It ends the re-debate.
- Part 1 next week reads this list. An action that moves its date twice gets discussed: is it the wrong owner, or not important?
Who’s in the room
Everyone who owns something: the owner, the office coordinator or manager, the estimator or salesperson, the operations lead if there is one, and the crew leads. Crew members don’t attend; their lead brings their items and takes back what matters to them in the morning briefing.
If the crews start at seven and the meeting is at seven, the crews stand idle. Hold it the afternoon before, or first thing on the one day the crews start later, or do it by video with the leads on site at the end of a day. Pick what costs the least production and keep it fixed.
Rules that keep it to 30 minutes
- Status is updated before the meeting, in the job record. Whoever runs part 2 reads the records first and lists the exceptions. The office-to-field workflow describes the update points.
- Exceptions only. A job that’s on plan gets no airtime. People learn quickly that the way to be left alone is to keep the job on plan and the record current.
- Two-minute rule. Anything that takes longer than two minutes to resolve becomes an action: “Luis and Mike, sort out the Henderson schedule after this; decision by Wednesday.” The meeting moves on.
- No deal strategy, no design, no pricing in the room. Those happen between the two or three people involved, afterwards.
- The log is written during the meeting, by the coordinator, on a screen everyone sees. Not reconstructed later from memory.
The feedback loop from the field
Add one question to part 4 every week, asked of each lead in turn: “What slowed your crew down last week?” One sentence each. Write every answer down, even the small ones.
After a month, patterns show. Materials arriving the morning of instead of the day before. Instructions missing the gate code. The same customer calling the crew directly. Each pattern is a process fix the owner never sees from the office, and each one that’s fixed and reported back in the meeting makes the next answer more honest. Why field feedback matters covers how to get techs to speak up in the first place.
Two more loops sit around the weekly meeting:
- Weekly one-to-ones with crew leads, 15 minutes, their agenda first. The crew leader lesson describes them. Problems that belong to one person don’t belong in the team meeting.
- A monthly numbers review, 60 minutes, with the KPI scorecard: margin by job type, estimate accuracy, schedule performance, cash. The weekly meeting runs the week; the monthly one steers the business.
The same week, run both ways
Made-up company: 18 people, three crews, an office coordinator, an estimator.
Before. The Monday meeting runs 55 minutes. Each lead describes their jobs, most of them fine. A countertop delay comes up; the owner says he’ll call the fabricator. The office mentions a customer who hasn’t signed a change order; the owner says he’ll call her. Luis says exterior jobs keep starting late because the materials come in the morning; everyone agrees it’s annoying. The owner leaves with nine calls to make and makes five of them. The countertop slips another week.
After. Part 1: last week’s six actions, five done, one re-dated with a reason. Part 2: two exceptions out of eleven jobs: the countertop (fabricator hasn’t confirmed the template date) and a bathroom over on plumbing hours. Part 3: a crew member out Thursday and Friday; the coordinator will move the Carter start to Monday and tell the customer today. Part 4: the dump trailer question, buy or rent, gets a decision date of Thursday; Mike brings the bookkeeper’s numbers Wednesday. New actions: Dana owns the fabricator call and tells the Reyes crew by Tuesday; Sam owns the unsigned change order by Monday; Luis writes the exterior readiness checklist by Friday so materials are confirmed the day before. “What slowed you down”: the gate code missing from two jobs’ instructions; Dana adds it to the handoff checklist. Twenty-eight minutes. Six actions across four people; the owner has one.
Neither week had fewer problems. The second one has owners for them.
Your next action
- Pick the day and time, and put a 30-minute recurring meeting in everyone’s calendar.
- Set up the action log where everyone can see it.
- Before the first meeting, have every job’s status updated in the record and list the exceptions.
- Run the agenda. End on time. Read the log first thing next week.
Free tool: the Weekly Team Meeting Agenda and Action Log spreadsheet has the 30-minute agenda and an action log that shows what’s overdue and how much sits with the owner.
What to review each month:
- Open actions closed on time, and how many are owned by the owner
- Recurring blockers from “what slowed you down” that have been fixed, and those still repeating
- Meeting length, and how many jobs were discussed that were on plan
Next course: plan your next stage of growth: find the one constraint that’s holding the business back, compare your options, and build a 90-day plan.
The course toolkit
You’ve reached the end of Hire, Onboard and Grow Crew Leaders. The course toolkit (PDF) has a worksheet for each of its five lessons in one file, in lesson order, ready to print or fill in on your phone. It comes with one spreadsheet: the Weekly Team Meeting Agenda and Action Log.
Where MotionOps helps
With MotionOps, the status is in the record before the meeting starts:
- Real-time Overview: see jobs progress as they happen, with photos, notes, signatures and timesheets in real time.
- Job Photo Feed and Private Field Notes: every job’s photos and the internal notes from everyone who worked on the job in one place, so exceptions are visible without a call.
- Scalable Team Scheduler and Unassigned Events: the whole team’s week in one view, with unassigned work listed, for the constraints part of the agenda.
- Push & Email Notifications: staff and clients are notified of appointment and work order updates, so a decision made in the meeting reaches the field.
- Team Reports: leaderboards for account managers, project managers and technicians, for the monthly review.
See plans and pricing, or book a MotionOps demo.
Contractor Scaler Hub: Hire, Onboard and Grow Crew Leaders, lesson 5 of 5
- Previous lesson: Crew Leader and Foreman Responsibilities: What to Hand Off and How to Train Them
- Next course: Plan Your Next Stage of Growth
- Course toolkit: Hire, Onboard and Grow Crew Leaders toolkit (PDF)
- All courses and lessons: Contractor Scaler Hub



