The conditions that triggered the application
Temperature and precipitation at the start of the operation, from an independent weather provider. The "why we de-iced" question gets a structured answer.
De-icing report software
De-icing reports with the conditions attached
Wintertrace produces a structured de-icing report for every operation — what was applied, where, when, by whom, and under what conditions. The weather record is independent. The GPS track is from the driver phone. The audit footer ties everything back to a locked database row.
Why de-icing is hard to document well
De-icing is documentation-heavy by nature. Unlike snow clearing, which is visible from the street the next morning, de-icing treatment is largely invisible after the fact. A property manager driving by at noon cannot see whether the morning treatment actually happened or whether the conditions justified the choice of material.
Good documentation answers both questions in the same report. What was done, and why doing it was reasonable. The first part is operational; the second part needs the conditions attached. Wintertrace captures both in the same record.
What a de-icing report includes
Five elements per operation, structured for aggregation across a season or a customer.
What was applied
Salt, brine, granular de-icer, or a combination, recorded as a structured field. Free-text notes are still possible, but the structured field is what reports aggregate.
Where it was applied
The GPS track from the driver phone shows the actual route, not the planned route. Coverage is visible at a glance.
When it was applied
Open and close timestamps from the device clock. Sub-minute precision. The order in which sites were treated is reconstructable from the timeline.
Who applied it
The driver account and the shift the operation sits inside. Several drivers across a long event produce a coherent multi-driver log per customer.
The "why we did this" half of the record
Operational records show what happened. De-icing records also need to show why the operator chose to act. Three cases the record handles.
Pre-treatment versus reactive treatment
A salt or brine application before snowfall is a different operational decision than reactive de-icing after the event. Wintertrace records the weather state at the moment of operation start, so the difference is visible in the record.
Why the choice of material
The application field captures what was used; the weather record captures why the choice was reasonable at the time. Together they answer the post-incident question of "would a competent contractor have done this?".
Why some sites and not others
Multi-site routes often skip some properties because the conditions did not warrant treatment. The weather record for each site explains the skip — particularly when the GPS track shows the driver did visit and decide not to treat.
Reports across operations
Individual operation records aggregate into the formats most operators actually need at the end of the month or the season.
Per-customer monthly report
A PDF stack of every operation at a customer site, with weather and application context.
Per-site seasonal summary
Aggregated counts of operations, total applied volumes where logged, and weather distribution across the season.
CSV export of application data
Useful for billing systems that compute per-application or per-tonne charges. The schema is open; standard tools consume it directly.
Audit footer on every PDF
Operation ID, generation timestamp, application version, checksum tied to the database row.
Customer portal access
Customers see their own de-icing reports through their portal login. No separate distribution step.
See also: analytics and reports, customer portal.
Common questions about de-icing reports
What is a de-icing report supposed to contain?
There is no single international standard. Most insurer questionnaires, property contracts, and industry guidance documents expect: time of application, conditions at the time, material applied, area covered, and identity of the person who applied it. Wintertrace captures all five for every operation.
Does Wintertrace track how much salt or brine was used?
The application field captures what was used. Quantity is optionally recorded in a structured field where the operator wants per-tonne or per-litre logging; for many operators a categorical record is enough. The schema is configurable on the operator side.
Can different sites have different material rules?
Yes. The site configuration allows per-customer or per-site preferences for material (e.g. brine-only on a particular property), and the driver interface surfaces those preferences during the operation.
What if a de-icing decision is later questioned?
The operation record carries the weather context, the GPS track, the time window, the driver, and the material applied. A reviewer can trace the decision back to the conditions that were present. Whether that record satisfies any specific framework is for the operator and their adviser to determine.
Do you support environmental reporting frameworks?
Wintertrace captures the data underneath such frameworks — material, quantity, location, time, weather. Translating that data into a specific framework (for example regional salt usage caps or environmental impact reporting) is custom work; the structured database makes it straightforward.
How are weather conditions verified independently?
The weather record is fetched from a third-party provider at the time of the operation — Open-Meteo by default, with country-specific providers available. The raw API response is archived alongside the operation record. The numbers can be traced back to a specific provider call.
Can operators sign the report?
The PDF is generated from the locked operation row and carries an audit footer tying it back to the database. Operators who want an additional signature can attach one to the PDF using standard tools; the underlying record stays locked regardless.
Note: De-icing reports describe operational actions and conditions. They are not legal opinions and do not assess regulatory fit with any specific environmental or contractual framework. Wintertrace provides documentation support and is not a substitute for legal advice.
Source code on GitHub. Free under GNU AGPLv3.
Try Wintertrace.
Upload one small file to your web hosting, open it in your browser, and the installer puts the latest signed Wintertrace core on your webspace. About ten minutes — no FTP client needed.