How to Run a Weekly WIP Meeting That Doesn't Waste an Hour

Most weekly WIP meetings are a book club where the book is the job board. Everyone reads it aloud together, in order, starting at the top, even though every project manager in the room already read it that morning. By the time the group reaches the jobs that need a decision, somebody's phone is ringing and the hour is gone.

A work-in-progress meeting can be the most useful hour in a restoration company's week. It's where stuck jobs get unstuck, where carrier follow-ups get a name attached, and where finished work turns into an invoice. It just needs a format that does those things on purpose, and the one below fits comfortably inside an hour.

What the meeting is for

The goal is simple. Every open job leaves the room either moving or with a named person responsible for whatever is stopping it.

It is not a status report. If a job is on track, nobody needs to describe it. It is also not the place to solve a hard problem. The meeting finds problems, assigns them, and checks a week later that they got handled. The solving happens afterward, with fewer people.

If you already run a weekly leadership meeting, keep this one separate. That meeting is about the company. This one is about the jobs. Our post on running restoration on a business operating system covers the leadership side.

Who sits at the table

Keep the group small enough that everyone in it has a reason to be there.

• Whoever runs production. An operations or production manager owns the meeting, keeps time, and keeps the list.
• Project managers. Each one speaks for their own jobs and nobody else's.
• Estimating. Whoever writes estimates and follows up on supplements.
• Accounting or AR. The person who knows what has been invoiced, what hasn't, and what is past due.
• The owner, sometimes. Owners are welcome, and it goes better when they listen more than they talk. A meeting where the owner answers every question soon becomes a meeting where nobody else decides anything.

Lead techs and rebuild leads can join for the jobs they're on. Anyone who isn't needed for a decision gets the notes instead of the hour.

Prep is where the time gets saved

The board should be current before the meeting starts, not during it. Set a deadline, such as the end of the previous workday, for every project manager to update the stages and notes on their jobs. Then whoever runs the meeting pulls the same few lists every week:

• Jobs that have sat in one stage longer than your limit. Pick a number of days that fits your work, and keep it the same so the list means something.
• Estimates and supplements waiting on a carrier response.
• Work that's finished but not yet invoiced.
• Receivables past your follow-up age.

With those lists in hand, the meeting can skip everything that's moving and go straight to what isn't.

A fixed agenda, in the same order every week

Same day, same time, same order. Rough time boxes keep everyone honest:

• Last week's action items, five minutes. Each one is done or not done. If it's not done, it gets a new date and a one-sentence reason. No stories.
• The board by the numbers, five minutes. How many jobs sit in each stage and what changed since last week. Counts, not job-by-job narration. In a busy spring, when basement losses pile into the drying stage all at once, this is where you'll see it first.
• Stuck jobs, fifteen minutes. Only the jobs on the over-the-limit list. For each one: why it's stuck, the next step, who owns it, and when it will happen.
• Waiting on the carrier, ten minutes. Estimates without a response, pending supplements, reinspections to schedule. Adjusters carry heavy caseloads, so the follow-up should be polite, specific, and documented. Decide who sends it and when.
• Ready to bill, ten minutes. Work that's done but not invoiced, and what's missing: final photos, final readings, a signature, a completion document. A surprising amount of money hides here.
• Aging receivables, five minutes. Anything past your follow-up age gets an owner and a next contact date.
• Read-back, two minutes. The person running the meeting reads every new action item aloud with its owner and date.

That adds up to under an hour with a few minutes to spare. Notice that the money items have fixed slots of their own. If billing and receivables always sit at the bottom of the agenda, they get skipped whenever the stuck-jobs discussion runs long, which is roughly every week.

One owner and one due date per action

Every action item gets one person's name and one date. Not "we." Not "the office." Not "someone should call the adjuster." Shared ownership feels collaborative in the meeting and turns into nobody's job by Thursday.

Keep the list where everyone can see it, and start next week's meeting by reading it back. The first few weeks of that review are uncomfortable. After that, people start arriving with their items already done, because nobody enjoys saying "not done" twice in a row.

Solve it offline

When a discussion runs past a couple of minutes, or only involves two of the people in the room, stop it. Write it down as an action item: who is meeting with whom, about what, and by when. Then go to the next job.

This is the habit that does the most to keep the meeting short, and the hardest one to keep. A good problem is tempting, and six people watching two people solve it is an expensive way to spend a morning. If your team already talks about jobs in job-linked messaging, the follow-up can happen right there, next to the job it's about.

The numbers on the screen

Put the same report on the screen every week, so trends show up without anyone hunting for them:

• Open jobs by stage, as counts and as dollars.
• Jobs past your stage limit.
• Work finished but not invoiced.
• Receivables grouped by age, such as under thirty days, thirty to sixty, sixty to ninety, and over ninety.

If building that report takes someone half a morning, sooner or later it stops getting built. Our guide to analytics and reporting covers which numbers matter and why.

Riivet's reports and analytics show WIP and aging AR from the same job records your team already updates, so the meeting can open with current numbers instead of a spreadsheet someone assembled at seven in the morning. If you want to see how that looks with real job stages, book a demo.

Before next week's meeting

• Keep the group small: production, project managers, estimating, AR, and the owner when it helps.
• Update the board before the meeting, and pull the same lists every time.
• Run a fixed agenda in a fixed order, with protected slots for billing and receivables.
• Give every action one owner and one date, and read last week's list back first.
• Take any long discussion offline.
• Stop before the hour is up, even if it feels early.

When the format is working, nobody reads the job board aloud anymore. They've already read it, and they came to decide things.