How to Run a Weekly Electrical Contractor Management Meeting

Ask a contractor how the business is going and you usually get a feeling rather than a fact. Busy. Slammed. Quiet. Those feelings are typically accurate about the last three days and unreliable about the last three months, which is why companies can be running flat out and losing money at the same time without anyone noticing until the bank balance says so.

The gap is not information. Most contractors already have more data than they use — the accounting software knows the margin, the scheduling board knows the backlog, the estimator knows the win rate. What is missing is a recurring point in the week where someone looks at all of it together, decides what to do, and assigns the doing to a named person by a named date.

That is all a weekly management meeting is. Not a report, not a morale exercise, and certainly not a two-hour discussion that ends with everyone agreeing something should be done. An hour a week, a fixed agenda, a short scorecard, a ranked issues list, and a set of commitments carried into the following week. This guide covers how to build it, what belongs in each segment, and the mistakes that quietly turn a good operating rhythm back into a status update.

Why a Weekly Meeting Matters

Weekly is the natural cadence of an electrical contracting business. Crews are scheduled by the week, most estimates go stale within a week or two of being sent, payroll runs weekly or biweekly, and a receivable that slips a week is materially harder to collect than one caught immediately. A monthly review is too slow to change any of those things; by the time the month closes, the labor hours are spent and the job is finished.

A weekly rhythm also changes the character of problems. An issue caught within seven days is usually still a small decision — reassign a crew, call a customer, chase an invoice. The same issue at thirty days is a recovery project. Companies that meet weekly are not smarter than the ones that do not; they simply spend their management effort on smaller versions of the same problems.

There is a third benefit that owners tend to underestimate. A weekly meeting is a forcing function for the numbers themselves. If a scorecard has to appear every Monday, someone has to keep the job costing current, invoice on time, and update the pipeline. Plenty of contractors discover that installing the meeting fixes their reporting as a side effect, because the reporting now has a deadline.

Who Should Be in the Room

The rule is simple: everyone who owns a function, and nobody who does not. A function owner is someone who can commit to an action on behalf of an area of the business without going away to ask. If a person can only take notes back to whoever actually decides, that other person should be in the meeting instead.

In a small company that is often three or four people — the owner, whoever schedules and dispatches, the person doing estimates, and the office lead who handles invoicing and collections. Several of those hats may be worn by the same person, which is fine; the agenda still covers each function even when one person answers for three of them.

As the company grows, the seats change rather than multiply. A service manager, a project manager, an operations lead, an estimator or sales lead, a finance or office manager, and whoever owns marketing cover almost every business at this size. Our organizational structure guide maps how those roles typically appear as a company scales, and the meeting roster should follow the org chart rather than seniority or tenure.

Field crews do not belong here. Foremen and lead electricians run their own short planning conversations, and pulling them into a management meeting costs billable hours while removing the focus the meeting depends on. What field leadership should get is the output — the decisions that affect them — delivered clearly and quickly, which is a subject covered in the field leadership guide.

Guard against the drift toward a bigger room. Meetings grow attendees the way jobs grow scope: one person at a time, each for a good reason. Every additional attendee who does not own a decision makes the discussion more careful and less useful.

The Meeting Owner

Someone has to own the meeting itself. That person publishes the agenda and scorecard before the meeting, keeps time on each segment, makes sure every issue discussed ends with an assignment, records the commitments, and opens the following week by reading them back. Without that role the meeting will be well-intentioned and will still decay within two months.

Chairing is not the same as deciding. The chair's job is process — moving the agenda, cutting off circular discussion, asking "who owns this and by when?" The people who own functions still make the calls within their areas, and the owner still makes the calls that are genuinely theirs.

The owner should chair at first, because they are the only person who can establish that the meeting is not optional. But handing the chair to an operations or service lead within a few months is one of the highest-leverage moves available. A meeting the owner chairs tends to become a meeting where everyone reports upward and waits for the owner to resolve things — the exact pattern the owner dependency guide is about breaking.

A 60-Minute Example Agenda

The structure below works for most electrical contracting companies. Treat the minutes as an example rather than a rule — a service-heavy company may want more time on scheduling and callbacks, a project-heavy one more on job-cost variance and backlog. The sequence matters more than the exact allocation, because it moves from what happened to what is coming to what we are going to do about it.

Two structural details make this work. The scorecard is published before the meeting so nobody is reading numbers for the first time in the room. And the issues segment is protected — if earlier segments overrun, they get cut, not the decisions.

Prior-Week Commitments

Before anything new is discussed, read back last week's commitments. Each one is done or not done. No partial credit, no explanations at this stage, and no discussion of why beyond a sentence — an incomplete commitment either gets a new date or becomes an issue for the issues segment.

This takes two minutes and it is what separates an operating rhythm from a recurring conversation. When people know their commitments will be read aloud every week by name, completion rates rise sharply. When commitments are never revisited, the meeting quietly teaches everyone that agreeing to something is the same as doing it.

Watch the pattern over a few months rather than reacting to a single miss. A person who misses consistently is either overloaded, unclear on the expectation, or blocked by something they cannot control. All three are worth knowing, and all three are invisible without the read-back.

The Scorecard

The scorecard is a short, fixed set of numbers reviewed in the same order every week. Eight to twelve lines covers most companies. Every line should be something a person in the room can influence, and every line should have an expected range so that "off-trend" means something specific rather than being a matter of opinion.

A workable starting set: revenue invoiced, estimates sent, estimates won, booked backlog in weeks, labor utilization, job-cost variance on active jobs, cash on hand, receivables over sixty days, and callbacks. Which of these matter most depends on your mix of service and project work — the KPI guide works through how each is defined and what the numbers actually tell you.

Read the scorecard as a trend, not a snapshot. A single week of low utilization is weather; four weeks of declining utilization is a capacity or sales problem. Keeping thirteen weeks visible next to each number turns a list of figures into a picture, which is the same principle behind the financial dashboard that the weekly numbers roll up into each month.

Sales, Estimates and Backlog

The sales segment answers one question: is there enough of the right work coming to keep the crews busy and profitable in six to twelve weeks? Three numbers usually carry it — estimates sent, estimates won, and booked backlog expressed in weeks of crew coverage rather than dollars.

Backlog in weeks is the more useful framing because it compares directly with the labor you have. Two hundred thousand dollars of booked work means nothing on its own; three and a half weeks of coverage for your current crew tells you immediately whether to push marketing, hold hiring, or start sequencing work differently.

The most commonly wasted asset in this segment is the estimate pile. Quotes sent and never followed up are the cheapest work available to any contractor, and they decay fast. Reviewing what is outstanding and who is chasing it weekly is exactly the rhythm described in the estimate follow-up guide, and the meeting is where that rhythm gets enforced.

Keep the discussion on the pipeline rather than individual jobs unless a specific opportunity needs a decision from someone in the room. If win rates are drifting or the same objection keeps killing quotes, that is a process issue for the sales process and belongs on the issues list, not in a fifteen-minute debate about one customer.

Operations, Scheduling and Capacity

Operations covers next week and the two after it. The core question is whether the work booked can actually be delivered with the people, vehicles, and material available, and where it cannot, what changes.

Start with the schedule against available hours. Utilization — billable hours as a share of paid hours — is the single most revealing operational number a contractor has, because it converts a vague sense of busyness into something comparable week to week. Low utilization while everyone feels slammed almost always points at travel, rework, or waiting for material rather than a lack of work.

Then look at constraints. A crew short one person, a permit not issued, a piece of gear on a long lead time, a job that cannot start until another finishes — each of these is either handled inside the segment or promoted to the issues list. Chronic constraints that keep reappearing usually indicate a structural capacity gap rather than a bad week, which is where the capacity planning guide is more useful than another round of reshuffling.

Day-to-day sequencing does not belong here. How Tuesday gets assigned is a dispatch decision, and the systems for making it well sit in the dispatch and scheduling guide. The weekly meeting deals with the pattern, not the placements.

Job-Cost Variance and Material

Job-cost variance is where estimating meets reality, and reviewing it weekly rather than at close-out is what makes it actionable. A job estimated at 160 hours sitting at 120 hours with half the work complete is a decision you can still make; the same information at final invoicing is a lesson.

Review the exceptions only — active jobs running meaningfully over or under plan. Consistent overruns on a particular type of work point back at estimating assumptions; overruns concentrated on particular crews or sites point at execution. Both are useful, and only the weekly comparison tells you which one you are looking at.

Material issues sit naturally alongside this. Shortages, late deliveries, repeat trips to the supply house, and material that never made it back onto a job all show up as labor hours long before they show up as material cost. When they recur, the fix is almost always a purchasing or staging process rather than more urgency, which is the ground covered in the material management guide.

Scope changes deserve a specific check every week: what changed on site, and was it captured and approved? Unbilled extra work is one of the most reliable ways for a profitable job to end up flat, and the discipline for catching it lives in the change order guide.

Callbacks and Quality

Callbacks are cheap to review and expensive to ignore. Count them, look at what caused each one, and watch whether the count is drifting. Two or three a week can be normal depending on volume; the same failure appearing three weeks running is a process problem.

The value of reviewing callbacks in a management meeting rather than privately is that the causes are rarely confined to the field. A callback caused by the wrong part being specified belongs to estimating, one caused by a rushed finish belongs to scheduling, and one caused by unclear customer expectations belongs to sales. Getting those functions in the same room is what turns a callback log into a quality control system.

Attach a cost to callbacks where you can — hours, truck time, material. A number makes the case for fixing the cause in a way that a count never does.

Cash and Accounts Receivable

Profit is an opinion until the money arrives. The cash segment is short and specific: what is in the account, what is expected in over the next two to four weeks, what has to go out, and where the gaps are. Contractors who only look at the bank balance are looking at a snapshot when the useful information is the movement, a distinction worked through in the cash flow guide.

Then the aging report. Anything past due gets a name against it and a next action — call, statement, hold on further work, escalation. Receivables are a decay curve: the probability of collecting drops steadily with age, and the weekly review is what stops a thirty-day invoice from becoming a ninety-day argument. The systematic version of this lives in the accounts receivable guide.

One item is missed more than any other: completed work that has not been invoiced. It never appears on an aging report because the invoice does not exist. Asking "what finished last week and has not been billed?" every single week routinely finds money that would otherwise have surfaced at month end, if at all.

Hiring, Staffing and Customer Issues

Staffing does not need its own segment every week, but it needs a standing check. Open roles and where they are in the process, anyone leaving or at risk, apprentices approaching a milestone, and whether the crews you will need in three months are being recruited now rather than when the work lands. Recruiting is a pipeline with a lead time, which is why it belongs in a forward-looking meeting rather than a reactive one — the recruiting guide covers building that pipeline, and the hiring guide covers the decision to add a person at all.

Customer issues get a similar standing check. Any complaint, dispute, or relationship that needs attention from someone in the room, with an owner attached before the meeting ends. Most escalations become expensive because they sat unowned for a fortnight, not because the underlying problem was serious.

Finally, ask explicitly where the owner is the bottleneck. What is waiting on an approval, a call, a signature, or a decision that only the owner can make? Making that list visible weekly does two things: it clears the immediate blockages, and it builds an honest record of which decisions could be delegated with a clear enough boundary.

Issue Solving and Decisions

This is the segment that justifies the meeting, and the one most often squeezed. Protect it. Everything before it exists to surface issues; everything after it exists to make them stick. The meeting works best when you connect the weekly meeting to a broader business operating system that can turn those weekly issues into a prioritized operating plan with clear owners and due dates.

Work in three steps. First, rank — list the issues raised and pick the most important, not the loudest or the most recent. Second, identify the actual problem, which usually takes a couple of questions: the stated issue is often a symptom, and solving symptoms is why the same item reappears next week. Third, decide, and be explicit that a decision has been made rather than letting the discussion trail off into general agreement.

Expect to get through two or three issues in ten minutes and be satisfied with that. An issue genuinely solved at the cause is worth more than six discussed. Items that never make it to the top of the list for a month or two are answering a question about their own importance.

Be clear about who decides. Most issues belong to a function owner and the meeting is simply where they announce the call and get input. A few genuinely require the owner. Confusing those two is how a room full of capable managers ends up waiting for permission — the reason decision rights are worth writing down explicitly rather than leaving people to guess.

Commitments, Owners and Due Dates

Every decision produces a commitment, and every commitment needs three things: a single named person, a specific action, and a date. Not a team, not "we", and not "soon". Shared ownership is the most reliable way to guarantee something does not happen.

Read them back at the end, out loud, and have each person confirm their own. It feels slightly formal the first two or three times and then becomes the most valuable five minutes in the hour. The read-back catches the commitments people thought they had heard differently, and it makes the next week's review unambiguous.

Keep the list short. Five to eight commitments a week is plenty for most companies; a list of twenty means the meeting is generating tasks rather than making decisions, and almost none of them will be done. If a decision requires a lot of work, the commitment is the next step and a date to report back, not the entire project.

Documenting Decisions

Documentation here means one page, not minutes. The scorecard numbers, the decisions made with a sentence of reasoning, and the commitment list with names and dates. Anyone who missed the meeting should be able to read it in two minutes and know what changed.

The reasoning line matters more than it looks. Six months later, knowing that you decided to stop taking a particular type of work because margin was consistently below plan is far more useful than knowing that you decided to stop taking it. Decisions without recorded reasoning get relitigated, usually by whoever was not in the room.

Over time, the record becomes a source for your standard operating procedures. A decision that gets made once is a decision; a decision that gets made repeatedly in the same way is a procedure waiting to be written down, and writing it down is what stops it from consuming meeting time forever.

Common Meeting Mistakes

Turning It Into a Status Report

The default failure. Each person describes their week, everyone nods, nothing is decided, and the meeting ends having consumed six people-hours to distribute information an email would have carried. The cure is structural: publish the numbers beforehand, cap the reporting segments, and protect the issues time.

Solving Everything in the Scorecard Segment

A number looks wrong, the discussion starts, and twenty minutes disappear. The scorecard segment identifies; the issues segment solves. Naming the off-trend line and moving on takes discipline from the chair and is worth the mild awkwardness.

No Fixed Time or Cancelling for Busy Weeks

A meeting that moves is a meeting that will eventually stop. The weeks it gets cancelled for being too busy are precisely the weeks the decisions were most needed. Same day, same time, every week, including holiday weeks and slow weeks.

Too Many People in the Room

Attendees who do not own decisions make the conversation more guarded and less productive. If someone is there purely for visibility, send them the one-page summary instead.

Commitments Without Names

"We should get on top of the aging report" is not a commitment. Every action needs one owner and one date, and the read-back is what enforces it.

Never Reviewing the Meeting Itself

Once a quarter, spend ten minutes on the meeting: is the scorecard still measuring the right things, are the segments proportioned correctly, are commitments being completed? Meetings drift the same way processes do.

Rolling the Meeting Out

Do not build the full version in week one. Start with the three things that create the habit: a fixed time, a short scorecard even if half the numbers are estimates, and a commitment list that gets read back the following week. That is enough to be useful immediately, and it is small enough that it will actually happen.

Add structure as the habit holds. Once the scorecard is reliable, tighten the definitions of the numbers. Once the numbers are trusted, shorten the review and expand the issues segment. Once the issues segment is working, hand the chair to someone other than the owner. Expect two or three months before it feels natural — the first few meetings will overrun and produce commitments nobody completes, which is normal rather than evidence that it does not work.

The test of whether it has taken hold is simple. If you cancelled the meeting for a month, would anyone notice? In a company where it is working, the answer is obvious within two weeks: estimates sit longer, receivables age, and decisions start collecting on the owner's phone again. That is the whole value of an operating rhythm — not the hour itself, but everything that hour keeps from drifting.

Frequently Asked Questions