The Seven O'Clock List: an auto repair shop daily checklist for the work that's stuck

The list, in the order the video builds it

Nothing in a repair shop breaks loudly, so the money that leaves tends to leave quietly. The seven o'clock list is one short list the manager reads before the first customer arrives. It holds three kinds of stuck work:

1. An estimate with no reply. Sent, then silence. The page this guide comes from uses an estimate with no answer for eight days as its example.
2. A repair order sitting in one stage. Waiting on parts, waiting on approval, waiting on a tech, for longer than it should.
3. A late part nobody mentioned. The delivery slipped and the customer still expects the car tomorrow.

Every line shows where it came from and when that source last updated, and the manager decides what happens to each one. When a fact is missing, such as a delivery time, the line says "unavailable" instead of guessing.

Who this checklist is for

Service managers and owners who start the day by checking the shop system, a few sticky notes, a text from the parts counter and their own memory. It works for one shop and for a group, where each location gets its own list. You can run it by hand from your shop system's reports; you don't need new software to start.

What you need first

• Your shop system's open estimates and repair orders, with the date each one last changed. Tekmetric, for example, has real-time reports for employees, sales and declined jobs, and most systems can list open work by age.
• Your parts orders, with promised delivery dates.
• A limit for each kind of stuck work. The suggested limits below are a starting point; set your own.
• One named owner for each kind of item, even if it is the same person.

The checklist

Print this or copy it into a spreadsheet. Fill it in at 7:00, before the phones start.

Stuck item	Suggested limit (set your own)	What to check	Owner	Decision
Estimate with no reply	2 days after it was sent	Was it sent? Did the customer open it? Any questions?	Advisor	Follow up, close, or wait with a reason
Repair order in one stage	3 days in the same stage	Which stage, and what is it waiting for?	Manager	Chase the part, the approval or the tech
Part past its promised date	Any slip that affects today or tomorrow	New date, or "unavailable"	Parts or advisor	Tell the customer, reschedule the bay
Promised callback	The time you promised	Who promised it, and when	Advisor	Call or hand off
Car ready, customer not told	1 hour after the job is done	Is the invoice ready?	Advisor	Call or text

For each line, write two things next to it: the system it came from and when that system last updated. A list that shows yesterday's data as if it were this morning's will send people the wrong way.

Step by step, every morning

1. Pull open estimates older than your limit. Sort them oldest first.
2. Pull repair orders that haven't changed stage within your limit. Note the stage each one is in.
3. Pull parts orders past their promised date. If the supplier gave no new date, write "unavailable". Do not pencil in a guess.
4. Add promised callbacks and finished cars nobody has called about.
5. Write the source and last-updated time next to each line.
6. Assign an owner to each line. By 7:15 every line has a name.
7. Decide each one. Follow up, chase, reschedule, or leave it with a written reason, for example "customer asked us to wait until payday".
8. At close, hand the list over. The next person sees what is still open, who owns it and when the information was last refreshed.

Why the data is usually already there

Most shops don't need more reports. They need someone to read the ones they have, in the right order, every morning. Technician time is a good example of how much goes unwatched: in Ratchet+Wrench's 2024 survey, 27% of shops reported technician efficiency below 80% and 18% did not track it at all. The article's own bands overlap in places, so treat these as a rough picture, not a target.

Close ratio is another number worth a glance once a week. A 2016 FenderBender piece offered examples such as a service consultant close ratio under 50% being "poor", and says some of its figures are illustrative. Your own history is the better yardstick. If you want to see whether a slow morning is a flow problem or simply fewer cars, pair the list with average repair order and car count.

Where AI helps, and where it should stop

AI is useful for building the list: reading open estimates, repair orders and parts from several systems, ranking the stuck items, and drafting a follow-up for the owner to edit. It is still early days for this kind of use. In the 2026 Ratchet+Wrench Industry Survey, 17% of shops using AI tools said they used them for scheduling, so a small, checkable first step makes sense.

It should stop at the decision. A person decides:

• Whether an aging repair order is a real problem or a customer who asked to wait.
• What to tell a customer about price, timing or a delay.
• Who works on what, and which job gets the open bay.
• Whether to send a draft, edit it or drop it.

What to watch out for

• Lists that grow every day. If the list is longer than one screen, your limits are too tight or nobody is deciding. Fix the limits first.
• Stale readings. A repair order entered late looks stuck when it isn't. The last-updated time on each line catches this.
• Guessed dates. A delivery time that was invented becomes a promise to a customer. "Unavailable" is the honest answer.
• No owner. A stuck item without a name stays stuck.

How to tell it is working

After two weeks:

• The oldest estimate on the list is younger than when you started.
• Fewer customers call to ask where their car is.
• The list fits on one screen most mornings.
• Every line has had a decision by mid-morning.

For more on the same idea, see auto repair estimate follow up software and operational visibility. The RevvOS daily operations view is built around this list: stale estimates, aging repair orders, delayed parts, callbacks and pickups, with the source and last-updated time on each line and a named owner for the next step.