Weekly Maintenance Review: A 20-Minute Agenda for Owners

It is Monday morning and you are on a call with your three area managers. Someone says the walk-in at store six "has been acting up." Nobody knows if a contractor was called, who called them, or whether it was last week or the week before. Ten minutes later the call has drifted to staffing, and the walk-in is still nobody's problem. A short, fixed maintenance review meeting fixes that.

It is not a status update where everyone reads out what they already know. It is a meeting where every segment ends with a decision and a name.

This agenda runs 20 minutes. It works from a spreadsheet, a shared inbox or software. If you are also rolling out a new system, the 30-day rollout plan covers the setup. This post covers the questions to ask and what each one should produce.

Ground rules before you start

• Same time, same people, every week. The owner or operations lead chairs. Area managers attend. Skip a week and the habit dies.
• One list in front of everyone. Open jobs, by site, with age. If you have to build it during the meeting, you will lose five minutes.
• Decisions get a name and a date. "We should look at that" is not a decision.

Minutes 0-4: what is waiting, and why

Pull up every open job older than a week. Go site by site, but only for jobs that are stuck.

Ask each one:

• Is it waiting on the vendor, on a part, on approval or on us?
• When did anyone last touch it?
• Does the store manager know the current status?

Decision to leave with: each stuck job gets one of three outcomes. Chase the vendor, reassign to another vendor, or close it because it was resolved and nobody recorded it. The third happens more than people expect.

Minutes 4-9: what broke fast, and what it cost to respond

Look only at the urgent jobs from the past week: anything your team treated as High or Emergency.

Ask:

• How long from first report to a vendor on site?
• Who found out first, the store manager or you?
• Was it a true emergency, or was it labelled one to get attention?
• Did anyone pay a premium rate, and was there an alternative?

Decision to leave with: whether your urgency definitions still match reality, and whether you need a second option in a trade where you only have one vendor. A single HVAC or refrigeration contractor is a risk you can see coming.

Minutes 9-14: repeat problems

Look for the same fault on the same piece of equipment, or the same fault across several sites. Ask:

• Is this the third call for this unit this year?
• Are we paying to repair something that should be replaced?
• Is the cause something a manager can prevent, such as blocked condenser coils, dirty filters or a door left open?

Decision to leave with: one of four calls. Keep repairing, get a second opinion, put replacement in next year's plan, or add a routine check so store staff catch it earlier.

You only see repeats if each repair is tied to a specific piece of equipment with a make, model and install date. That is the practical case for keeping equipment records, whatever tool you use.

Minutes 14-18: money

Ask:

• Which site spent most this week, and is that explained by one job?
• Is any spend waiting on a sign-off that is holding up a repair?
• Are there invoices from vendors you have not matched to a job?
• Which site spends noticeably less than similar ones?

Decision to leave with: sign off or decline anything waiting, and name who chases unmatched invoices.

A note on tooling. In Concoct, spend and budget views are on the Professional tier, and vendors email their invoices rather than uploading them through the portal, so someone on your side attaches them. On other tiers, this segment uses your invoices and your accounting system. Either way, the questions are the same.

Minutes 18-20: next week

Close with three things:

1. What is scheduled? Preventive visits, inspections, vendor appointments at stores that need someone on site.
2. What is at risk? Anything that might become an emergency if ignored, such as an ageing compressor or a roof leak before bad weather.
3. Who owns what? Read back every action, name and date.

Someone writes the actions down and sends them to the group that day. The first item next week is whether last week's actions happened.

Keeping the maintenance review meeting to 20 minutes

Meetings drift. A few habits that help:

• Park anything that needs more than two minutes. Give it an owner and a follow-up.
• Track one number across weeks. The count of jobs open longer than 14 days is a good one. It should fall.
• Do not let the chair become the only fixer. If every action lands on one person, the meeting will grow until it fails.

How a system helps, and what it does not do

Concoct keeps each work order with its equipment, vendor, status and history, so the list for this meeting exists without anyone assembling it. Vendors respond through a passwordless link and an assignment nobody answers within 24 hours is unassigned, with an alert to owners and operations managers. Someone still has to reassign it by hand. The review stays a human conversation.

If you are building the habit first, pair this agenda with the maintenance checklist for restaurants and convenience stores. You can add software later.

Try it on your own sites

The per-location rates are on the pricing page. If you would like to run this meeting from a live list of your own work orders, book a demo and bring a week of real issues.

FAQ

How long should a maintenance review meeting be?

Twenty minutes tends to work for operators with up to roughly a dozen sites, though your mix of sites matters. Longer than that and people stop preparing, because they assume it will run over anyway. If you have more sites, split the meeting by area rather than lengthening it.

Who should attend?

The owner or operations lead who chairs, plus the people who dispatch work and approve spend. Store managers do not need to attend weekly; pull one in when their site has a stuck job or a repeat problem.

How often should we hold it?

Weekly. Monthly reviews turn into clean-up sessions, long after the emergency is over.

What if we have no software and only a spreadsheet?

Run it anyway. You need a list with the site, equipment, vendor, date opened and status. A spreadsheet that gets updated before the meeting is better than a tool nobody opens.

What should we track week to week?

Keep it small. The number of jobs open more than 14 days, the number of repeat faults and the time from report to vendor on site for urgent jobs. Use your own baselines rather than outside benchmarks, and compare against your own last month.

Does Concoct run the meeting for us?

No. It gives you the current list of jobs, equipment history and vendor status, so you are not assembling them by hand. The decisions, and who does what, stay with you and your managers.