Define the operational purpose of the log
Decide who uses the record and what decisions it should support. A property manager may need to verify completed zones, understand an exception, reconcile an invoice or identify a recurring trouble spot. A service contact may need consistent handoff information between shifts. State these purposes before choosing fields. Avoid collecting information merely because it might be useful someday. Legal, insurance and retention requirements need qualified review; the website cannot determine the legal effect or required lifespan of a particular record.
Record conditions without claiming certainty
Capture the date, approximate time and relevant observed conditions at the property. Distinguish direct observation from a forecast, automated source or report by another person. Note active snowfall, drifting, freezing rain, standing water, compacted snow or refreeze where relevant. Do not convert a municipal snow-event definition into a private-property conclusion. The City of Prince George's public operations provide local context, while the private log should describe what informed the actual property decision.
Use arrival, departure and observation times carefully
Record when a visit began and ended, plus the time of a material observation or later recheck if those are part of the scope. A timestamp should describe what it represents; an automated message time is not necessarily the time a surface was observed. If work continues through multiple passes, keep the sequence understandable. Where time data comes from devices or apps, confirm how it is created and corrected. The goal is an accurate operational chronology rather than a misleading impression of precision.
Tie every action to a mapped zone
Use the same zone codes that appear on the approved property map. For each zone, record the action and any relevant method or material information required by the agreement. This may include plowing, walkway clearing, relocation, observation, application, recheck or no action. Avoid vague entries such as site complete when some areas were blocked or scheduled later. A zone-based log allows the property team to compare priorities, find recurring exceptions and understand which instruction applied.
Describe exceptions and unresolved conditions
When an area cannot be completed, identify the zone, reason, communication and next decision. Common factual categories might include parked vehicles, active loading, locked access, continuing weather, equipment restriction or a condition requiring property review. Do not assign blame or speculate about a cause in the operational field. Separate an observed obstruction from the later resolution. If the condition affects access or safety, follow the responsible organization's escalation process rather than relying on the log alone.
Use photos as context, not as the entire record
A photo can show a mapped location, bank position, obstruction or surface at one moment. Label it with the zone and time, and explain what it is intended to document. Do not photograph people, licence plates, access controls or tenant activity unnecessarily. Follow the organization's privacy, security and device policies. Photos do not capture every condition and should not replace clear written fields, communication or direct inspection. If imagery is corrected or removed, preserve an appropriate audit trail according to approved policy.
Capture communications and authorizations
Record the operational message, recipient, channel and time when a blocked zone, optional service or change requires attention. For hauling or another separately authorized item, record who approved it and which proposal term applies. Avoid copying long personal conversations into the event log; keep the entry focused on the property decision. Maintain a current contact list so instructions do not go to a former manager or unavailable employee. Communications should connect to the same event and zone codes as the work record.
Track concerns through a follow-up decision
If a tenant, employee or property contact reports a slippery or blocked area, record when it was received, the location, who reviewed it and the resulting action or escalation. Distinguish the original report from what was later observed. Do not close the item simply because a message was sent. The responsible parties should define what constitutes acknowledgement, reinspection and closure. Repeated reports at one map location can indicate a drainage, traffic or sequencing issue that deserves a broader site review.
Review the season and preserve only approved records
At regular intervals and season end, summarize recurring exceptions, map conflicts, storage decisions, communication failures and scope changes. Use the findings to update the property map and next agreement. Confirm access controls, correction procedures and retention through the organization's approved operational, privacy, insurance and legal process. Remove duplicate or unnecessary collection where policy permits, but never alter a record to conceal a decision or exception. A consistent closeout makes the next winter brief more precise.
City snow information can supply public-road context, while WorkSafeBC supplies workplace hazard context. Private event logs should distinguish those sources from what was directly observed and done at the property.
City of Prince George — Snow Clearing · WorkSafeBC — Slips, Trips & Falls
Sources reviewed September 22, 2026. Confirm current requirements for the exact property and proposed scope.