Winter operations in the Nordics: planning for the season, not the forecast
By navichain team

Every autumn the same conversation happens in Nordic transport offices, about six weeks too late. Someone reads a forecast, sees the first cold snap coming, and starts asking about tyres. By then the decision that mattered has already been taken — or, more often, quietly not taken.
Winter is not weather. Weather is what happens on a particular Tuesday. Winter is a season with known dates, known constraints and a known effect on how much work a fleet gets done in a day. Planning for it is a capacity decision, and the month to make it is October.
The dates are fixed even when the weather is not
The regulatory calendar is the one part of winter that needs no forecasting, which makes it a sensible anchor for everything else. Checked against Transportstyrelsen at the time of writing:
- Heavy lorries and heavy buses over 3.5 tonnes, and trailers coupled to them, must have winter tyres or equivalent equipment from 10 November to 10 April — regardless of whether there are winter road conditions.
- Through that same window, all tyres on heavy lorries and heavy buses must have a tread depth of at least 5 mm. A trailer coupled to such a vehicle must have at least 1.6 mm.
- Winter tyres on these vehicles must carry the alpine symbol — a three-peak mountain with a snowflake — or the POR marking (Professional Off Road); studded tyres are a further alternative. The marking rules differ by position on the combination, so read them axle by axle rather than assuming one specification covers the whole vehicle.
- Studded tyres are permitted from 1 October to 15 April, and outside that period if there are, or are expected to be, winter road conditions.
Note the asymmetry that catches people out. For cars the requirement runs 1 December to 31 March and applies only in winter road conditions. For heavy vehicles it is a fixed five-month window with no weather test in it at all. A mild November is not an exemption, and neither is a dry road.
The above is a summary, not the regulation, and rules change. Confirm the current text with Transportstyrelsen before building a compliance calendar on it, and check each country you run into separately — Norway and Finland set their own requirements.
Buffer time is capacity you spend on purpose
The whole argument in one sentence: winter costs you time, and you pay it either as planned buffer or as unplanned failure. There is no third option where the season is free.
The same lane takes longer in February than in August. Speeds drop, ploughs and gritters occupy the road you wanted, hills queue, and every load and unload takes longer in cold and darkness. None of that is dramatic on any single leg. It compounds across a multi-drop route and lands on the last stop of the day — which is where your least forgiving customer usually is, because the schedule was built around the ones who complain.
If the plan is built on summer running times, the driver absorbs the difference: pressure on driver hours, missed windows, a stop attempted where it should have been rescheduled, decisions made on ice by someone already behind. A buffer in the plan is the alternative to a buffer in somebody’s judgement.
The discipline this requires is the awkward part: you are planning slack you hope to waste. A buffer that goes unused is not a wasted buffer — it is the price of the delivery windows you kept. Most organisations are bad at this for a structural reason: unused slack is visible on every report, and the failure it prevented is visible nowhere. If the spring review counts only idle minutes, the buffer gets cut, and the next winter makes the case for it again at customer expense.
Be honest about the trade-off, because it is real: buffer reduces daily utilisation. Fewer stops per vehicle per day, higher cost per shipment for five months. Work that number out in October and say it out loud to whoever owns the margin, so December’s figures are a plan being executed rather than a problem being discovered.
Where the buffer goes matters more than how much of it there is. A uniform percentage on everything is the lazy version and mostly wrong: it over-pads the motorway leg, cleared first and driven fastest, and under-pads the last 20 km into an unploughed industrial estate. Put the time where the risk is — the first run of the morning, the exposed or elevated stretch, the stops with the tightest windows.
Daylight is a planning constraint, not a driver problem
Nordic winter light is a resource with a schedule, and a short one. Loading and unloading in the dark is slower and less safe, particularly at sites with unlit yards, and slower stops compound exactly as described above. North of the Arctic Circle the question stops being how much light there is and becomes how the working day is organised without it.
Two practical moves. Identify which customer sites are effectively daylight-only in winter — awkward access, no yard lighting, a reversing manoeuvre nobody should attempt blind — and record that against the site rather than in a planner’s memory; it is a planning attribute, so treat it like one. Then spend the light on those stops, and put well-lit terminal work at the ends of the day.
Readiness is a schedule, not a shelf
The list itself is easy: winter tyres fitted, tread measured, chains aboard and someone trained to fit them, shovel, sand, warm kit. What is hard is knowing, on 12 November, which specific vehicle has which of those things.
A whiteboard solves that right up until the first week someone is off sick. Tie readiness to the vehicle record instead: tread depth measured and dated, changeover completed, chains issued, statutory dates falling inside the season flagged before it rather than during it. The changeover has a known deadline attached, so book it as work with a date — a fleet-wide tyre change is a workshop capacity problem long before it becomes a compliance problem on the road.
Winter is also when deferred defects stop being deferrable. A vehicle that would have limped through September on a marginal battery, a tired heater or a sticking brake does not limp through February; it fails somewhere cold, with a load on. This is the season when daily vehicle checks that actually get done pay for themselves, and when a defect that grounds a truck in the yard beats the same defect found 300 km out.
Plan next winter from last winter
Padding by anecdote produces a plan shaped like whichever route went memorably wrong last year. The useful input is planned versus actual per leg across a whole season: which lanes ran long, by how much, in which conditions and at which time of day. That tells you where buffer belongs and — just as valuable — where it does not, which is how you buy back the lost utilisation.
This is cheap if the system already records planned and actual times, and expensive if it means asking drivers to remember January. It is the same argument we made about the gap between route planning and reality: a plan never compared with its outcome cannot improve, and winter is where the gap is widest and therefore most informative.
Have the customer conversation in October too: which delivery windows hold through winter, which become best-effort, and who is told when a weather exception is invoked. A winter schedule agreed in advance is accepted; a missed window explained afterwards is remembered.
Where navichain fits
navichain is built so most of the above lives in the system rather than in someone’s head: daily walk-around checks that open a defect when something fails, with a failed inspection grounding the vehicle and a critical defect keeping it grounded; maintenance due on distance or on the calendar, so the changeover and the statutory dates become scheduled work rather than recollection; vehicle specs, documents and compliance dates tracked per truck and trailer; routes judged against real limits — driver hours, vehicle class, delivery windows — with a weather overlay for severe conditions; and a dispatch board that flags what will not fit before you commit. Every feature is on every plan, driver seats are included with every vehicle, and billing is monthly with no lock-in, from 995 kr a month. The platform page shows what is inside, and pricing is public.