Structure per-push, seasonal, and per-inch snow contracts correctly
domain: sima.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For per-push contracts, define the trigger depth (e.g., 1" or 2") in writing and document snowfall at the time of each trigger to support billing.
For seasonal flat-rate contracts, spell out included services explicitly (plowing, treatment, refreeze monitoring) since price doesn't vary with storm count in either a light or heavy winter.
For per-inch tiered pricing, agree in advance on the snowfall measurement source used to determine which tier applies, since tiered billing disputes hinge on measured depth.
Address the 'liability gap' risk in per-push contracts: a property with no new snowfall can still have refreeze/black ice, so specify whether between-storm ice monitoring is included.
Put trigger depths, the agreed measurement source, included/excluded services, and invoicing cadence into the written contract rather than leaving them as verbal understandings.
Known gotchas
Per-push contracts without a documented, agreed measurement source for trigger depth are hard to defend in a billing dispute.
Seasonal contracts often need caps or true-up clauses for unusually heavy winters — confirm these are negotiated up front, not assumed.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?