Snow Event Communication for Property Managers

The fastest way to lose a commercial snow account in Central Ohio isn’t a missed push or a high invoice. It’s a property manager waking up to angry tenant emails because nobody told her the lot had been salted, the plow was on the way, or the storm was bigger than forecast. Communication is the difference between a contractor who keeps the account for ten years and one who gets replaced after the second winter.

I’ve been running commercial snow accounts across Pickaway, Franklin, and Fairfield counties for more than ten years, and the communication protocols I run now were written one bad event at a time. This is the playbook I follow on every Lawn Harmony commercial account, and the same playbook I recommend to property managers writing snow contracts this December.

What’s the right way to communicate during a snow event?

Pre-storm notification 12 to 24 hours out, dispatch notification when the crew rolls, completion notification with photos when the property is cleared, and a post-event summary with documentation for the file. Every notification goes to the same contact at the same channel, time-stamped, and with the same format every time. If you change channels or formats mid-storm, somebody misses something and that somebody is usually the person who matters most.

OSU Extension and most commercial property management associations recommend documented snow event protocols as a slip-fall liability defense, and the documentation is only useful if it’s actually generated in the moment. After-the-fact reconstruction doesn’t hold up the same way real-time notifications do.

The four notifications: what each one says

Pre-storm (T-12 to T-24 hours). Sent when the forecast firms up enough to commit to a service plan. Says: “Forecast is X inches starting at Y time. We plan to push at Z trigger depth. Estimated start of service is W time. Salt will / will not be applied. Contact me at this number if anything changes on your end.”

The pre-storm notification gives the property manager time to alert tenants, adjust hours, or override the plan. On a Lancaster medical complex I service, the property manager often asks for an extra early-morning salting on storm days because the clinic opens at 6 a.m. and patients are already arriving in the dark. Without the pre-storm notification, I’d never know.

Dispatch (when the crew leaves the shop). Brief. Says: “Crew rolling to your property now. ETA to first push approximately X minutes.”

This one matters less than the others, but it lets the property manager set tenant expectations if anyone calls asking when the lot will be clear. On a Bexley office building I service, the building manager forwards the dispatch text to her tenant Slack channel automatically. Tenants know help is on the way.

Completion (when the property is cleared). Full message. Says: “Property cleared at X time. We pushed Y depth, applied Z amount of salt to walks and lot, identified the following hazards (or none), and stockpiled snow at the southeast corner per the routing plan. Photos attached. Next planned visit is at the next trigger or a re-salt at Y depth additional accumulation.”

The completion notification with photos is the slip-fall liability defense in writing. Time-stamped photos of cleared walks, cleared accessible routes, salted entries, and stockpile location. Every time, on every push.

Post-event summary (within 24 hours). A summary email or PDF with: total pushes, total salt applied, hours on property, any hazards identified, any tenant complaints relayed and how handled, photos before and after, and invoice estimate. This gets filed by the property manager for the building’s records.

Communication channels: pick one and stick with it

The biggest mistake I see new contractors make is mixing channels. They text on Monday, email on Tuesday, call on Wednesday. By Friday the property manager doesn’t know where to look for the next update.

Pick one primary channel and one backup. My setup:

• Primary: SMS to a dedicated cell line for the property manager
• Backup: Email to the same property manager, cc’d to the building owner
• Emergency only: Phone call (storm escalation, equipment failure, hazard discovered)

For property managers who run multi-site portfolios, I’ll set up a single shared channel (a Teams chat, a Slack channel, or a dedicated SMS group) where all event notifications flow. The PM forwards or filters from there.

Whatever the channel, every notification follows the same format. Pre-storm has the same fields every time. Completion has the same fields every time. Predictability is what makes communication useful.

Trigger depths and what they actually mean

Most commercial snow contracts in Central Ohio operate on a per-event basis with a defined trigger depth. The trigger depth is the snow accumulation at which the contractor begins service. Common triggers:

• 1 inch: Medical, daycare, high-traffic retail with overnight customers
• 2 inches: Standard office, retail, professional services
• 3 inches: Industrial, low-traffic, employee-only access

The trigger needs to be in writing and the communication has to reference it. If the contract says 2 inches and the storm drops 1.8 inches, the contractor isn’t pushing unless the property manager calls and authorizes a non-trigger event.

On a Circleville professional building I service, the trigger is 2 inches, but the property manager has standing authorization for a “courtesy salt” on any event under trigger that produces ice on the walks. That authorization is in writing in the contract and confirmed in the pre-storm notification.

Pre-treatment and post-treatment communication

Pre-treatment (anti-icing brine applied before a storm) is different from post-treatment (deicing after snow has fallen). The communication has to be clear about which is happening.

For pre-treatment:

• Why are we pre-treating? (Forecast shows freezing rain or quick changeover)
• What product? (Salt brine, beet blend, or magnesium chloride brine)
• When? (Window of application)
• What does the property manager need to do? (Usually nothing, but inform tenants if pavement looks wet)

For post-treatment:

• What product was applied?
• What rate?
• What surfaces (walks only, lot only, both)?
• When and how often will we re-apply?

Tenants who see a contractor in a parking lot at 5 a.m. with a salt spreader will email the property manager asking what’s happening. The completion notification with the product and rate gives the PM the answer.

Tenant complaint handling

The contractor doesn’t talk to tenants directly unless the property manager explicitly authorizes it. Tenant complaints go from tenant to PM to contractor. The contractor responds to PM with documentation and PM relays.

The protocol:

• Tenant complaint received by PM
• PM forwards to contractor with as much detail as possible
• Contractor checks the documentation (completion notification, photos, GPS log if available)
• Contractor responds to PM in writing within 4 hours during a storm, 24 hours otherwise
• PM responds to tenant

On a Grove City retail strip last winter, a tenant complained that the walk in front of her store was icy at 9 a.m. The completion notification showed the walk had been salted at 5:30 a.m. and photographed clear at 6:00. Between 6 and 9, freezing drizzle had moved in and re-iced the walk. The PM had the documentation to explain, and we sent a crew back for a re-salt at no charge as a goodwill gesture. Tenant was satisfied. PM was protected.

Equipment failure and escalation

When equipment fails mid-storm, the property manager needs to know immediately and needs to know the plan.

The escalation notification: “Plow truck went down at X time. Backup unit is being dispatched. Estimated delay is Y minutes. Your property is currently at Z status.”

Honest, fast, specific. Property managers can manage a delay if they know it’s happening. What they cannot manage is a plow contractor who goes silent for two hours during an active storm.

On a Pickerington commercial account in February 2024, a hydraulic hose blew on the lead truck mid-push. The notification went to the PM at 3:47 a.m., the backup truck was on site at 4:22 a.m., and the property was complete by 5:55 a.m. instead of the planned 5:00 a.m. The PM thanked me. The honesty mattered more than the delay.

Documentation that survives a lawsuit

Every notification gets archived. Every photo gets timestamped and saved. Every event gets a completion summary in the file. If a slip-fall claim lands in March, the documentation is what the insurance adjuster and the attorney work from.

What to keep:

• All SMS and email notifications, with timestamps
• All photos with embedded GPS and timestamp metadata
• Service tickets with crew, equipment, products, and rates
• Property maps with stockpile and routing
• Any tenant complaints and the response chain
• The original contract with trigger depths and protocols

I keep a digital folder per property per winter. By April it usually contains 200 to 400 photos and 50 to 80 notification records for a typical commercial account. That folder is the defense.

Common communication mistakes I see

• Mixing channels mid-storm (text, then email, then call)
• Skipping the pre-storm notification on smaller events
• Completion notifications without photos
• Vague language (“we’ll be there soon”) instead of specific times
• Talking directly to tenants without PM authorization
• Going silent during equipment problems
• Not archiving notifications in real time
• Promising a service level the equipment can’t deliver

The going-silent one is the killer. Property managers will tolerate a delay, an equipment failure, a billing error, or a missed re-salt. They won’t tolerate radio silence at 4 a.m. when their phone is ringing with tenant complaints.

Setting up communication before December 15

For a property manager taking on new accounts or signing new contracts this December, the communication setup needs to be done before December 15. Specifically:

• Primary and backup contact saved in the contractor’s phone
• Primary and backup channel agreed in writing
• Format and frequency of each notification documented
• Tenant complaint protocol documented
• Escalation protocol documented
• Property map and trigger depths confirmed
• Test message sent and received both directions

The test message matters. I’ve had contracts where the property manager’s phone blocked SMS from unknown numbers and we discovered it on the first storm at 3 a.m. Five-minute test on December 10 prevents that.

Communication at a glance

• Pre-storm: T-12 to T-24 hours, plan and trigger
• Dispatch: when crew rolls
• Completion: with photos, products, rates, hazards
• Post-event: 24-hour summary for the file
• One primary channel, one backup, consistent format
• Trigger depths and authorizations in writing
• Tenant complaints routed through PM
• Honest, fast, specific on equipment failures
• Everything archived for liability defense

Want a commercial snow partner with documented communication?

Lawn Harmony Landscaping services commercial properties across Pickaway, Franklin, Fairfield, Ross, and Fayette counties with a documented communication protocol on every account. Pre-storm notifications, dispatch alerts, completion photos, post-event summaries, and a property file maintained for the season.

Call 614-425-9789 or email Lawnharmonyohio@gmail.com for a free written quote. Commercial properties can request a walkthrough at /quote/commercial. Residential clients can get a quote at quick-mow-quote.emergent.host.

Related reading: winter property walk for commercial owners, snow plow equipment readiness checklist, and salting concrete vs asphalt.

Service area: Circleville, Columbus, Grove City, Bexley, Upper Arlington, Pickerington, Canal Winchester, Groveport, Lancaster, Baltimore, Chillicothe, Washington Court House, and Jeffersonville.