Poudra was born from snow removal — its name comes from the French word for blowing snow. The truck that plows in January often mows in July, for the same customers, on the same properties: the software serves all four seasons from one book.
You say “this route, every seven days”. The evening before, Poudra PROPOSES the next day’s outing; you confirm with one tap. The frequency counts from the last REAL visit, not from the one that was planned: a rainy week does not create three mowings to catch up.
Rain warns, it does not decide
Past the threshold you set, the next day’s proposal arrives with its warning: “18 mm forecast”. It is never postponed on its own. You are the one who knows whether your ground holds, and a postponement always carries its reason.
Mowing, edging, blowing: what was actually done
You name your services once. A programme says which ones it plans; on arrival the operator finds them checked and unchecks what they did not do. The gap — “edging: planned, not done” — shows in the proof file, and your customer only sees what happened at their place.
A skipped stop is not a billed stop
Soaked ground, closed gate, dog in the yard: the operator skips the stop by choosing the reason. It is not a visit — so it is not billed, by construction — and your customer learns it with the reason, before calling you.
The same book all year
Your customers, properties, routes and proof do not change season. A contract carries its own: the same customer’s summer contract and winter contract live side by side, each with its instalments and its renewal.