Property maintenance winter service software
Wintertrace is built for the documentation side of winter service. For property managers, that side is the whole conversation: tenant complaints, owner reports, insurance questionnaires, contractor coordination across a portfolio. One record set per building, one audit trail per operation, one portal both sides can see.
Most winter service software is built from the contractor's perspective — the team that does the work. For a property manager, the work is usually outsourced, but the documentation burden is not. The manager is the one answering tenants in the morning, owners at the end of the month, and insurers at renewal.
The questions the property manager has to handle are different from the contractor's. "Did this happen?" comes first. "Can you show me?" comes second. "Can I have it in writing?" comes third. Wintertrace answers all three from the same record.
A complaint about an icy entrance reaches the property manager within minutes; the documentation about whether and when service happened sometimes does not exist in any retrievable form at all. The asymmetry favours the complainer until the records catch up.
A portfolio manager sometimes deals with three contractors across five buildings, each with its own clipboard or text-message style of reporting. Reconciling that into one view is the property manager problem, not the contractor problem.
Owner reports — to landlords, condo boards, REITs — expect structured numbers and dated documents. "Yes, we treated it" is not a deliverable; a PDF stack with timestamps is.
Renewal questionnaires increasingly ask about winter service documentation practices. A property manager who can answer those questions in two minutes is in a different position than one who has to call three contractors first.
Four features that map to portfolio-scale documentation work.
Each building is a customer; each entrance or walkway can be a site. The records aggregate naturally to the building level, the portfolio level, or the contractor level.
When the property manager owns the Wintertrace installation, contractors get accounts to log their work into the same system. When the contractor owns the installation, the property manager gets customer portal access. Both directions work.
A PDF stack of every operation at a building, generated per month, ready to attach to the invoice the contractor sends or the report the property manager forwards to the owner.
When a complaint surfaces a question — "was anyone here on the morning of the 14th?" — the answer is a single query with a timestamped record and a GPS track behind it.
Which side runs the installation depends on the relationship. Three workable shapes.
Property manager hosts, contractors log into it
For larger property management firms managing multiple buildings with multiple contractors, hosting one Wintertrace instance and giving each contractor access keeps everything in one record set.
Contractor hosts, property managers get customer access
For property managers using a single contractor, the more common pattern is the contractor running their own Wintertrace and giving the property manager customer-portal access to the records.
Both sides run their own
Both parties may run installations and reconcile at the report layer. Less common, but workable; CSV exports make reconciliation tractable.
Yes. Some property management firms run Wintertrace as the system of record and require their winter service contractors to log work into it. This is the inverse of the typical pattern, and it works the same way technically.
Depends on who owns the installation. If the property manager hosts, contractors get driver and admin accounts inside that instance. If the contractor hosts, the property manager gets customer-portal access to their buildings. Either way, both sides see the relevant records.
In one Wintertrace installation, yes — if the contractors all log work into that installation. Across multiple Wintertrace installations, reconciliation requires combining CSV exports. The clean answer for portfolio-level visibility is one installation that everyone uses.
Insurance renewal questionnaires often ask about winter service documentation processes. Wintertrace makes the answer concrete: structured records per operation, weather-attached, GPS-tracked, audit-logged, retained for a configurable period. Whether the documentation level satisfies a specific insurer is a question for the insurer.
Monthly and seasonal aggregation reports per customer or per site are available out of the box. PDFs are exportable individually or as a per-month bundle. CSV exports go into whatever owner reporting system the property manager already uses.
Some property managers expose a building-level "what was done last night" view to tenants through the customer portal. This is optional and configurable per building.
GPS data is recorded only during an active operation, not during the rest of the shift. Movements between sites or back to the depot are not retained in the operation record. The data protection tools allow retention and anonymisation policies; specific handling is a contract matter between property manager and contractor.
Note: Wintertrace provides documentation support for winter service operations. It does not certify fit with any specific lease, contract, insurance policy, or jurisdiction. Property managers should confirm with their own counsel and insurer how a Wintertrace deployment aligns with their obligations.
Source code on GitHub. Free under GNU AGPLv3.
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.