Snow Removal Documentation for Pacific Northwest Property Managers: What Premises Liability Law Actually Requires
Brad Caton • June 23, 2026
Last reviewed: November 2026
When a slip-and-fall claim lands on your desk, two questions matter: what was done at the property, and what records can help establish it? Building the record during the event is more useful than trying to reconstruct every decision later.
That distinction matters across the Pacific Northwest, but the legal rules are not identical. Mucsi v. Graoch Associates (2001) addresses reasonable care in Washington common areas; section 3 of BC Occupiers Liability Act sets out BC's occupier duty; and Portland City Code 17.28.025 specifically addresses adjacent sidewalks. None of these authorities makes a GPS record a substitute for the work itself.
The problem is easier to manage before a claim arrives. Decide who records inspections, service work, unresolved hazards, and return visits, and where copies will be kept. Don't assume the contractor's dispatch system will preserve everything your property team may later need.
Build your documentation system before the next service event, not after an incident. Ask for a sample report and check whether another person could understand what happened at the property from that record alone.
This guide separates the legal duty from recommended recordkeeping, explains what the Washington Mucsi case actually decided, and provides a practical documentation checklist. The checklist is an operating recommendation, not a court-mandated format.
What Washington Premises Liability Law Actually Requires
Washington does not give a landlord a blanket exemption for naturally accumulated snow and ice in common areas. In Mucsi v. Graoch Associates (2001) , the Supreme Court described a duty of reasonable care, while emphasizing that a landowner is not a guarantor of safety. The analysis includes notice or foreseeability and a reasonable time to address the condition.
The practical lesson is not that every fall proves negligence. Mucsi v. Graoch Associates (2001) rejected reliance on the natural-accumulation rule and considered whether the evidence supported a finding that reasonable care had not been taken. Record what your team knew, the routes it inspected, and what it did in response.
The duty discussed in Mucsi v. Graoch Associates (2001) includes conditions the possessor knows about or would discover through reasonable care, an unreasonable risk of harm, whether people can be expected to protect themselves, and the response to that risk. The court also recognized that an obvious hazard does not always end the inquiry.
In Mucsi v. Graoch Associates (2001) , the evidence included cleared main access, untreated side-exit walkways, knowledge that snow and ice remained, and available ice-melting material. The Supreme Court reversed the dismissal and remanded for trial because the evidence could support a jury finding. It did not find liability or establish a missing-documentation rule. For site planning, inspect secondary exits and foreseeable pedestrian routes, not just the main entrance.
Don't assume a claim automatically shifts the burden of proof to the property manager. Mucsi v. Graoch Associates (2001) assessed whether the claimant had presented sufficient evidence to proceed. BC's statutory duty and Portland's adjacent-sidewalk rule have their own wording. Build a separate obligation sheet for each jurisdiction rather than treating all three as one legal test.
Where Service Logs Need Supporting Detail
A paper route sheet can be useful if it is timely, accurate, and specific. Its limits are practical: an entry saying 'site complete' may not identify which stairs were checked, what conditions existed, or whether a return visit was needed. The same weakness can affect an incomplete digital record.
Location data needs context. For example, Android documents accuracy, connectivity, and notification limits for its geofencing service . That does not establish which platform a contractor uses. Ask how your provider identifies the vehicle or device, sets time zones, handles edits, and preserves original exports. Do not describe a record as immutable unless that specific system and its audit controls have actually been verified.
The ordinary personal-injury filing periods are generally three years in Washington under RCW 4.16.080(2) and two years in Oregon under ORS 12.110(1) , subject to the applicable accrual rules and exceptions. Those are lawsuit limitation periods, not snow-removal record-retention statutes. Don't turn them into an automatic deletion date.
A photograph taken days later is not a photograph of conditions at the time of an incident. Capture conditions during inspections and service when practical, label the location, and preserve the original file. If a later entry reconstructs an event, label it as a later entry and identify its source.
Embed documentation in routine work from the first service event. Keep the original service report alongside the property team's inspections and communications. If something was missed, record the gap and the corrective action rather than changing the record to make the event look complete.
Four Useful Documentation Categories for Your Winter Plan
Use these four categories as a practical checklist. They are not an exclusive set of evidence categories created by a court, and no combination guarantees a defense. The aim is a record that connects conditions, decisions, and work at the actual property.
1. Service timing and identity. Record the site, service date, arrival and departure, crew or operator, and the time zone used. Where available, retain location data alongside the service report and note any outage or manual correction. A boundary-crossing event can support a visit time, but it does not establish the entire scope of work.
2. Coverage and unresolved areas. Use a site map to identify the entrance, accessible route, stairs, side exits, loading areas, and other pedestrian paths inspected or treated. Record any inaccessible or untreated area and the follow-up plan. Mucsi v. Graoch Associates (2001) illustrates why secondary exits matter. GPS routes alone may not show handwork or prove a surface was treated.
3. Conditions and decisions. Record the conditions observed at the site, the time of inspection, relevant weather information, photographs, and why service or a return visit was initiated. Keep contract triggers separate from safety observations. Acting before an accumulation trigger is not, by itself, proof of an above-standard legal response.
4. Treatment and follow-up. Record the material used, application area, amount or rate if measured, and any relevant surface or temperature limitation. Identify who will recheck the area and what they found. A material log describes the work; it does not prove a complete legal standard of care was met.
How Geo-Fencing Can Support a Service Record
When evaluating Invictus Snowfighters or another provider, ask how the documentation offered in the proposal works at your specific sites. A sample export is more useful than a general promise of a court-ready record.
If geo-fencing is included, confirm what event is logged, which device is tracked, and how location data connects to the service notes. Ask separately how hand-shovelled routes, material application, missed areas, and return visits are recorded. Do not assume a truck entering a site automatically creates all of those records.
Before signing, request a demonstration of how a completed service report and its supporting files can be exported. Check that the export identifies the property, dates, route-level work, and any corrections. Preserve your own copies in a format your team can still open later.
For a multi-property portfolio, use consistent field names and site identifiers even if different contractors provide the work. A single provider may simplify reporting, but consistency still needs to be checked. Compare a sample from each location and assign someone to flag missing records.
If equipment or materials are stored on-site, include them in the plan: location, access, authorized users, and how any use will be recorded. A storage unit's presence is not evidence that a route was inspected or treated.
Building Your Documentation System Before the Next Storm
The time to build a documentation-ready snow management system is before you need to rely on it. Use the steps below to evaluate a new agreement or improve an existing one. You do not need to wait for summer to close an obvious records or inspection gap.
Step 1: Audit the actual records. Ask for a sample inspection and service report, plus any supporting location data and photographs. Can you identify the route checked, the treatment, any missed area, and the follow-up? Test the export process rather than accepting a yes-or-no answer about geo-fencing.
Step 2: Write access and retention terms into the contract. Specify which records you receive, the delivery schedule, how corrections are tracked, and how historical records remain available if the contract ends or a vendor changes software. Set the retention period with your insurer or legal adviser; the personal-injury filing periods are not a stand-alone retention mandate.
Step 3: Photograph and map the property. Before snowfall, identify the walking routes, stairs, parking connections, drainage areas, and places where snow will be stored. Keep dated baseline images separate from storm and incident photographs so the record does not imply they show the same conditions.
Step 4: Establish an incident response protocol. Identify who arranges immediate assistance, records the exact location and time, photographs conditions, contacts the insurer, and requests contractor records. Preserve relevant footage, messages, original files, and later corrections. Do not overwrite existing records to make them fit a later account.
Step 5: Keep local obligations separate. For Vancouver, record the daily 10am adjacent-sidewalk instruction in Vancouver's winter maintenance guidance . For Seattle, distinguish the timely-care duty described by SDOT's explanation of the sidewalk duty from SDOT's winter preparation guidance 's every-12-hours recommendation. For Portland, note the owners' and occupants' responsibility under Portland City Code 17.28.025 . A records-retention policy is a separate decision; Washington's three-year injury filing period is not a three-year snow-log law.
If you're managing commercial properties along the I-5 corridor, ask Invictus how the proposed service and reporting would work at each site. Review sample records, access to historical files, and the limits of any tracking system before the agreement is finalized.
Frequently Asked Questions: Snow Removal Documentation in the Pacific Northwest
Does Washington law require commercial property managers to document snow removal?
The cited Mucsi v. Graoch Associates (2001) decision addresses reasonable care, notice or foreseeability, and time to respond. It does not prescribe a GPS system or a particular snow-log format. Inspections, treatment notes, photographs, and communications are recommended ways to preserve what actually happened, not a substitute for reasonable action.
How long should I retain snow removal service records?
Set a written policy with your insurer or legal adviser. Washington's ordinary personal-injury period is generally three years under RCW 4.16.080(2) ; Oregon's is generally two years under ORS 12.110(1) , with applicable accrual rules and exceptions. These are not record-retention requirements. Suspend routine deletion when an incident, claim, or legal hold requires preservation, and do not assume the ordinary filing period is a safe destruction date.
Can my contractor's GPS records be used in litigation?
Ask your legal adviser which location records and supporting files are needed for the claim. Preserve the original export, device and site identifiers, time zone, and any correction history. A location point should be read alongside inspections, photographs, and service notes, not treated as automatic proof of treatment.
What's the difference between a paper service log and geo-fenced documentation?
A paper log records observations and work entered by a person. A geo-fence can generate a configured location event; Android provides one first-party example . The two records answer different questions. Use location data to support timing and service notes to explain the work, and preserve originals and later corrections. Neither format is automatically conclusive.
When should I review snow removal documentation?
Before the next service event, whenever the contract or reporting system changes, and after an incident exposes a gap. A pre-season review gives you time to test reports, confirm access, and agree on inspection and follow-up responsibilities. If winter has already started, make those checks now.
Recent Posts










