A commercial roofing crew pulled up to a building last month that their company had serviced for six years. Same client, same roof, a file thick with past invoices. And nobody on the truck could tell you what they were about to walk onto. What kind of membrane it was. How old. Where the ponding always came back. What got patched last spring and whether it held.
All of that existed once. It was in the head of a lead hand who left in the fall. So the crew did what crews do. They climbed up, re-diagnosed a roof the company already knew cold, and quoted a repair on a section that had been flagged eighteen months earlier and never followed up. The knowledge was never gone because it was hard to get. It was gone because nobody ever wrote it down where the next person would find it.
This is the quiet tax on any business that services the same equipment more than once. Rooftop units, water heaters, alarm panels, pumps, coolers. The make, the model, the serial, the age, the last thing that went wrong. Your best tech carries a map of every site in his head. It is genuinely valuable, and it is completely undocumented, and the day he leaves it drives away in his truck.
Most owners try to fix this with a better memory or a stern reminder to "write it up." That is not a system. Paper forms end up in the door pocket. A note in the job description gets buried and is never searchable. The information needs to be captured at the one moment it is guaranteed to be correct, when the tech is standing in front of the equipment, and it needs to land somewhere the next visit will actually see it.
If you are on ServiceM8, that place already exists and most people never build it. It is custom forms (https://www.chanautomation.com/servicem8-setup). You design a short form once, one that matches how you actually work, an asset form for a rooftop unit or a site form for a roof section. Make, model, serial, condition, a couple of photos, a notes line. The tech opens the job on his phone on-site, taps through it in under a minute, and the photos attach right there. It saves as a PDF to that job's diary.
Now the next time anyone pulls up that client, last visit's form is right there in the job history. Open it and you see what is on the roof, how old, what you flagged last time, what it looked like. The crew knows what it is walking into before it leaves the yard.
The reason this matters more than it sounds is that captured asset data quietly becomes three other things. It becomes a quote, because you can see the unit is fifteen years old and due for replacement instead of another patch. It becomes a follow-up, because the thing you flagged is now a record instead of a memory. And it becomes continuity, because when the lead hand does leave, the site knowledge stays on the account instead of walking out with him.
Setting this up is not a big project. The trap people fall into is building a monster form with forty fields that techs quietly stop filling out. The version that works is short, matched to the specific thing you service, and mandatory on that job type. Five fields a tech will actually complete beat forty he ignores.
Here is the one to run this week. Think about the last time a crew went back to a site you have serviced for years, and someone had to phone the office, climb up, or guess to figure out something the company already knew. Not something new. Something you had already learned and simply never wrote down. If you can think of one, it is not a one-off. It is happening on every repeat visit where the person who knew is not the person on site. That gap is exactly what a custom form closes.
Reply and tell me what you service that repeats, the units or the sites you go back to. I will tell you what the form should capture.
Kevin Chan
The Ops Shortcut by ChanAutomation
https://www.chanautomation.com/servicem8-setup