If It Isn't Written Down, It Didn't Happen

Ever had someone on your team tell you "nobody told me"?

I just got the family version.

My daughter blew up the engine in her car. She ran it out of oil.

I was frustrated. Obviously.

And it gets worse.

Three Drivers, One Big Gap in the Records

We bought that car brand new. Over the years it got handed down from my oldest daughter, to my son, to my third oldest.

Based on what happened, the repair should have been covered under warranty.

It wasn't. We didn't have the records for the oil changes.

Nearly $7,000. For a repair that should have been covered.

When we talked about it, she said she was confused. She said she didn't know the engine was out of oil, or what the messages on her dashboard meant.

Sound familiar? It's what a lot of our employees say when something breaks.

"I didn't know."

"Nobody showed me."

"I thought that was someone else's job."

Maybe that's real. Maybe it isn't. You've probably wondered the same thing about someone on your team.

Here's What I Had to Sit With

Before I could judge whether her answer was real, I had to look at what I'd actually taught her.

I never taught her how to check the oil. I never walked her through what those dashboard messages mean. How was she supposed to know?

That's on me. All of it.

And the records? There's a big gap in the oil change history from when my other two kids had the car. Maybe the oil got changed. Maybe it didn't.

To a warranty company, "maybe" doesn't count. If it isn't written down, it didn't happen.

So two lessons, and they cost me about $7,000:

1. If you never taught it, you can't hold them accountable for it.

2. If you didn't write it down, you can't prove it.

The first one is about your people. The second one is about your systems. Most owners are weak on at least one. A lot of us are weak on both... and we don't find out until something blows up.

The Dashboard Check: Four Questions for Your Business

Run these on your own team. Be honest. No team? Run them on your own routine, or on the next contractor you hand something to.

1. What warning lights can't your team read yet?

Every business has a dashboard. A client who's gone quiet two weeks before the event. A booking that's light on details. A piece of gear that's starting to act up. A review that's a little too polite.

You can read those lights because you've been burned by them. Your team hasn't. If you never told them what a light means, they'll drive right past it.

2. What did you assume somebody else taught them?

This one gets worse with every handoff. The person who trained your new hire might have learned it from someone who learned it wrong. Or never learned it at all.

If you can't name who taught it and when, assume nobody did.

3. If something broke tomorrow, could you prove it was maintained?

Vans, trailers, speakers, booths, lighting, laptops. Warranty claims and insurance claims run on records. So do resale values.

"We always take care of our stuff" is not a record.

4. When a job changed hands, did the knowledge and the records go with it?

My car had three drivers and a big gap in its records. Every handoff was a chance to pass along what mattered: how to check the oil, what the dashboard was saying, where the records were.

The same thing happens when a role changes hands in your business. A new coordinator. A new lead tech. A new person running the van.

Can't answer one of these? You just found your next oil change.

The Handoff Checklist

Use this every time something changes hands: a vehicle, a piece of gear, a client, a role. Copy it, change the words to fit, and keep it where the next person can find it.

Before the handoff

• Who owned this before, and who owns it now? Both names, written down.
• Where are the records? (Service history, receipts, warranty papers, logins, client notes.)
• Any gaps in the records? Write down what's missing now, while someone might still remember.

During the handoff, out loud and in person

• The warning lights: what does it look like when this is starting to go wrong?
• The routine checks: what gets checked, how often, and how? (Show it. Don't just say it.)
• The "never do this" list: the mistakes that cost real money.
• Who to call when something looks off.

After the handoff

• The new owner shows it back to you. If they can't explain it in their own words, you're not done.
• The first maintenance date goes on a calendar, with a name next to it.
• Check in once, two weeks later. Questions show up after the first time they're on their own.

A Simple Maintenance Log

This doesn't need software. A shared sheet works. A notebook in the glove box works. What matters is that every entry has the same five things:

Three rules make it work:

1. Log it the day it happens. Not at the end of the month. You won't remember.
2. Keep the proof. Snap a photo of the receipt and link it in the row.
3. One owner per item. If everyone owns the log, nobody does.

Where AI Fits

Here's an easy start. Take a photo of the dashboard, the manual page, or the back of the gear, and ask ChatGPT, Claude or Gemini to turn it into a one page "what the warning lights mean" sheet for your team. Then have the person who uses it every day check it, and fix anything that's wrong.

AI can write the first draft of the sheet. It can't sit in the driver's seat with them. That part's still yours.

This Week

Pick one warning light on your team's dashboard.

Teach it out loud. Have them show it back to you.

Then write it down.

It's a lot cheaper than $7,000.