HomeWorkshopsField Manual
All articles

Operational Teardown

My Tech Walked Into That Property With No Warning. It Almost Went Very Wrong.

Ray dispatched a tech into a property with an aggressive dog and an unsafe propane setup — both buried in a closed job. Here’s the hazard flag we built; try it below.

Anthony
AnthonyFounder · Apr 28, 2026 · 5 min read

In Houston, TX, Ray V runs a 8-tech hvac operation. A near-miss: a tech walked in blind to hazards that were noted on a job nobody thought to pull up.

What was actually bleeding

Ray dispatched a tech to a property that had an aggressive dog flagged and an unsafe propane setup — both noted on a closed job nobody thought to pull up. The tech walked in blind. It was a near-miss, and Ray couldn't stop thinking about how close it came.

What Ray asked us to build

“Put a property hazard flag that surfaces for every future tech BEFORE they arrive.”

Ray V, HVAC — Houston, TX

What we built

We built property-level hazard tagging across fifteen to twenty categories. Once a property is flagged, the hazard surfaces at dispatch, fires an en-route push to the assigned tech, and requires a pre-job safety sign-off before work begins.

● Live demo the actual tool — try it In the field · iPhone
9:41
Service OSProperty FlagsLive
Tag a hazard before a tech rolls
1423 Oak StNo flags yet
Pick hazard categories

How the tool works

Flag a property in the demo below, then dispatch a tech — the hazard surfaces before arrival and requires a safety sign-off before the job can open.

Inside our Service OS

Property-level safety is one module of the Service OS we build. It rides along with dispatch, job records, and customer history so what one tech learns protects the next.

What came back

It's the feature Ray is most glad exists. Every hazard a property has ever shown now reaches the next tech before they pull up.

every hazard surfaced pre-arrival

That’s not a projection — it’s what changed after we shipped the build.

The tool you just used isn’t a mockup — it’s the kind of thing we build inside our Service OS, one module of a system made for your trade and owned by you. If you’re carrying a version of this problem, the fastest way to see what a system would catch in your operation is to run your own numbers.

The takeaways

  • Hazards a property showed once must reach the next tech automatically.
  • Surface the flag at dispatch and en-route — before arrival.
  • Require a safety sign-off before the job can open.
Anthony
Anthony
Founder, Corporate Synergy Solutions

Ex-Microsoft operations and fractional COO for $5M+ field service operations. He writes about the systems that let trade companies scale without the owner holding everything together by hand.

These are the things we build inside our Service OS.

Every tool in this story is one module of a custom operating system we build for trade businesses — built for your trade, owned by you. Spin up a free OpsVault account and run your own operation through it: the Live Bleed Calculator, the Journey Map, the whole Vault. No credit card, no sales call.