May 1, 2026
A restoration company meeting architecture is a structured cadence of recurring meetings — daily huddles, weekly WIP reviews, and monthly leadership meetings — designed to create operational visibility, surface problems early, and maintain team accountability without consuming productive time. Well-designed meeting cadences replace reactive owner involvement with proactive system-based visibility.
Most restoration companies have too many wrong meetings: long, unstructured check-ins that produce conversation without decisions; update meetings that could have been an email; and owner-driven reviews that create dependency rather than accountability. And they don’t have enough right meetings: the short, data-driven, decision-forcing cadences that create operational visibility and surface problems while there’s still time to fix them.
The meeting architecture below is designed for restoration specifically — accounting for the operational reality that field teams can’t be pulled off jobs for long administrative sessions, that margin problems are easier to prevent than to fix, and that owner bottleneck is almost always made worse by informal communication patterns that route everything through the owner rather than through structured accountability processes.
When: Every morning, 7:00–7:15 AM, before field teams deploy.
Who attends: Operations manager (or owner if no OM), PMs, field supervisor. Not every field technician — the field supervisor represents the field.
What it covers: Jobs dispatching today — who’s going where, what the scope is, any special conditions. Jobs active from yesterday — any issues that need resolution before field teams arrive. New intake calls from the prior 24 hours — which need immediate response. Any resource constraints (equipment, crew availability) affecting today’s dispatch. That’s it. Not a problem-solving session. Not an update on jobs from last week. Fifteen minutes maximum.
What it replaces: The stream of texts, calls, and ad-hoc conversations that currently carry dispatch information. When information flows through a structured daily meeting, it stops flowing through informal channels that route to the owner. The owner’s phone stops ringing at 6:45 AM with “what should I do about this job.”
When: Every Friday morning, 8:00–8:45 AM.
Who attends: Owner (or operations manager), PMs, office manager.
What it covers: Every active job reviewed against five metrics: estimated vs actual cost to date, percent complete, billing status, open supplements, days on site vs estimated duration. Each job gets a Green/Yellow/Red status. Every Red job gets an assigned owner, a specific action, and a deadline before next week’s review. AR aging review — any account over 30 days gets a follow-up assigned. Jobs closing this week — is billing ready to submit within 5 business days?
The pre-condition: This meeting only works if the WIP data is current before the meeting starts. The PM’s job is to update their job data by Thursday end of day. If the data isn’t there, the meeting becomes a data-assembly session rather than a decision-making session. Build data entry into the PM accountability structure — it’s as important as the meeting itself.
When: Within the first 10 business days of each month, covering the prior month’s results.
Who attends: Owner, operations manager, office manager. Not the full PM team.
What it covers: Prior month P&L reviewed against target: revenue, gross margin by service line, overhead vs target. AR aging summary and collection results. WIP summary — jobs closed vs opened, average closeout cycle time. HR items: any performance issues that need formal resolution, any open roles. One or two strategic items — a decision that needs the leadership team’s input but doesn’t require the full team.
What it is not: A comprehensive debrief on every job from the prior month. A therapy session for operational frustrations. A forum for airing interpersonal conflicts. The monthly meeting is a performance review and decision-making session. Problems that belong in the daily huddle or weekly WIP review don’t belong here.
Start with the weekly WIP review. It produces the most immediate financial value — problems caught on Friday can still be fixed this week. Run it for 30 days before adding the daily huddle. Add the monthly leadership meeting last, once the weekly rhythm is established. Don’t try to introduce all three simultaneously — the team’s adjustment to structured meetings is itself a change management process that benefits from staged implementation.
Three: a daily dispatch huddle (15 minutes, operational coordination), a weekly WIP and margin review (30–45 minutes, financial and job visibility), and a monthly leadership scorecard meeting (60–90 minutes, performance review and decisions). Companies that implement only the weekly WIP review see the most immediate financial impact — it’s the meeting that catches margin problems while they’re still fixable.
Today’s job dispatches (who’s going where), active job issues requiring same-day resolution, new intake calls from the past 24 hours requiring response, and any resource constraints affecting today’s field coverage. Fifteen minutes maximum. Not a problem-solving session — problem-solving happens after the huddle between the relevant parties. The huddle surfaces what needs attention; the one-on-ones that follow resolve it.
Pre-populated WIP report covering all active jobs with five metrics (estimated vs actual cost, percent complete, billing status, open supplements, days on site). Review each job in order: Green jobs get noted and passed; Yellow jobs get a specific action assigned; Red jobs get an owner, an action, and a deadline. Finish with AR aging review — follow-up assigned on any account over 30 days. Total time: 30–45 minutes with 8–15 active jobs.
Daily huddle: 15 minutes hard stop. Weekly WIP review: 30–45 minutes depending on active job count. Monthly leadership meeting: 60–90 minutes. These are not guidelines — they’re design constraints. Meetings that run longer have unfocused agendas. If the WIP review consistently runs 75 minutes, the problem is data quality going into the meeting, not insufficient meeting time.
Make the meetings earn their time by producing decisions and actions — not just information exchange. Start every meeting on time and end it on time. Follow up on actions from the prior meeting at the beginning of the next one (accountability loop). Show the team, within the first 4–6 weeks, at least one example of a problem that was caught in a WIP review and fixed before it became expensive. When the team sees the meeting producing outcomes, it earns credibility. Meetings that feel like reporting to the owner produce resistance. Meetings that feel like a tool the team uses to protect margin produce buy-in.
Mike McCabe is a restoration business consultant and the founder of Profit Detective. He works with restoration operators to find and fix the margin leaks that don’t show up until it’s too late.
Most engagements pay for themselves within the first week.