Wintertrace On GitHub →

Digital plowing records

Plowing records that survive the season

Wintertrace replaces paper plowing logs with structured digital records. Each operation carries a GPS track, an independent weather record, optional photographs, and an audit trail — all stored in the operator's own MySQL database, exportable in a single command, searchable in seconds.

Where paper plowing records run out of road

Paper has worked for decades. It still works — until the moment someone asks a specific question several months later.

They depend on the handwriting

A driver in a dark cab at 04:30 produces handwriting that is hard to read by 09:00, let alone in a contested call eight months later. Digital records are typed once and stay legible forever.

They are hard to search

"Show me every operation we did at this address in February" is an afternoon of going through binders on paper. In a database it is one query, indexed, with the PDFs already sorted by date.

They are easy to lose

A binder gets wet, a clipboard gets left in a truck that gets traded, a notebook goes home with the driver who leaves the company. A digital record sits in a database that is backed up nightly.

They can be rewritten without trace

A paper log that has been edited usually leaves visible marks. But it can also be replaced entirely — a fresh sheet, copied over. Digital records carry an audit log that survives rewrites.

What goes into a digital record

Eight categories per operation. The fields are structured, not freehand — which is what makes them searchable in the first place.

Customer and site

Tied to a structured record, not free text. The "B-block at 33 High Street" cannot be confused with "B block, High St".

Time window

Open and close timestamps from the device clock. Sub-minute precision, immune to backdating from the application.

GPS track

The actual route of the truck during the operation, stored as a series of coordinates and drawn into the PDF as a vector path.

Weather record

Independent provider data for the time window. The raw API response is archived alongside.

Application record

Salt, brine, mechanical clearing, sanding — recorded as structured fields, not freehand notes.

Driver identity

The driver account and the shift the operation sits inside.

Photographs

Optional photos, each carrying its capture timestamp and GPS fix as metadata.

Audit trail

Every state change of the record — opened, closed, edited, exported — with a timestamp and an actor.

Moving from paper, practically

The transition does not require a clean break or a big project. Three principles cover almost every operator case.

No retroactive digitisation required

Past paper records do not need to be re-entered. Wintertrace starts recording from the day it is installed; old paper records stay paper.

Coexistence during the first season

Operators commonly run both for the first storm or two — paper as a familiar backup, digital as the working record. Confidence builds quickly; paper is dropped when the team is ready.

Export is a database dump

If the operator ever wants out of the Wintertrace database, a MySQL dump contains every record. Standard tools take it anywhere — including back to paper, if needed.

Why digital records hold up better in disputes

The strength of a record in a dispute is not just its content — it is how plausibly the record was made at the time. Three Wintertrace properties carry that weight.

Contemporaneous capture

Timestamps come from the device clock at the moment of capture, not from typed dates.

Independent corroboration

Weather data comes from a third-party provider, not from the operator's own note.

Locked rows + audit log

Once an operation closes, the record is locked. Subsequent edits leave traces in the audit log.

Common questions about digital plowing records

Are digital records accepted by courts and insurers?

In most jurisdictions, yes — when they are well-kept. Acceptance depends on the jurisdiction, the contract, and the quality of the records. A Wintertrace record is structured, contemporaneous, and audit-logged, which are the properties that tend to matter. Whether any specific reviewer accepts a given record is for the operator and their adviser to determine.

Do I have to digitise my old paper records?

No. Wintertrace records the operations going forward from the install date. Past paper records keep their existing status. Mixing record formats across a season is normal during the transition.

What if I want to keep a paper backup?

You can. Each operation produces a PDF that can be printed. Some operators keep a printed copy of the final monthly PDF stack as a physical archive in addition to the digital one.

Are my records safe if the hosting fails?

Backups are the operator responsibility, exactly as they would be for any other business data on hosting. Wintertrace makes backup easy by storing everything in a single MySQL database — one mysqldump command produces a complete export. Most hosting plans run automated nightly backups already.

Can I edit a record after the fact?

A small set of fields can be edited; most of the operation record is locked once the operation is closed. The audit log records every change, with a timestamp and an actor. There is no way to edit a record without leaving a trace inside the application.

How long are digital records kept?

Retention is configurable per data type. The data protection tools let operators set retention windows and anonymise records past their retention. Common operator practice is to keep records for the contract period plus a buffer; Wintertrace does not impose a fixed retention.

Can my customer see the records too?

Yes, through the customer portal. Each customer has their own login and sees only their own operations. The PDF service proof is downloadable from the portal.

Note: Wintertrace provides documentation support for plowing operations. It does not certify regulatory fit in any specific jurisdiction and is not a substitute for legal advice.

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.

install.php · Ed25519-signed core · GNU AGPLv3

Read the installation guide →