ROUTE 1Identify event and weather reference
“Identify event and weather reference” needs a distinct entry for event weather reference in the event evidence file. For event weather reference, define a measurable trigger. Within event weather reference, name the observation source. Regarding event weather reference, set decision timing explicitly. While reviewing event weather reference, cover nights and weekends. Before closing event weather reference, record escalation and follow-up. Connect event weather reference to the affected proposal line. Keep event weather reference dates and locations together. Classify event weather reference as observed or unresolved. Verify event weather reference before dependent work. Retain event weather reference revisions in event evidence.
ROUTE 2Record arrival, observation and action times
“Record arrival, observation and action times” needs a distinct entry for arrival observation action times in the event evidence file. For arrival observation action times, define a measurable trigger. Within arrival observation action times, name the observation source. Regarding arrival observation action times, set decision timing explicitly. While reviewing arrival observation action times, cover nights and weekends. Before closing arrival observation action times, record escalation and follow-up. Connect arrival observation action times to the affected proposal line. Keep arrival observation action times dates and locations together. Classify arrival observation action times as observed or unresolved. Verify arrival observation action times before dependent work. Retain arrival observation action times revisions in event evidence.
ROUTE 3List zones visited and actions taken
“List zones visited and actions taken” needs a distinct entry for zones visited actions taken in the event evidence file. For zones visited actions taken, plot on the current map. Within zones visited actions taken, number plow and walkway areas. Regarding zones visited actions taken, protect fire and accessible access. While reviewing zones visited actions taken, add operating windows and obstacles. Before closing zones visited actions taken, assign map-update responsibility. Connect zones visited actions taken to the affected proposal line. Keep zones visited actions taken dates and locations together. Classify zones visited actions taken as observed or unresolved. Verify zones visited actions taken before dependent work. Retain zones visited actions taken revisions in event evidence.
ROUTE 4Capture material or method records
“Capture material or method records” needs a distinct entry for material method records in the event evidence file. For material method records, locate recurrent problem zones. Within material method records, trace runoff and refreeze paths. Regarding material method records, state approved treatment constraints. While reviewing material method records, record action and timing. Before closing material method records, require a follow-up observation. Connect material method records to the affected proposal line. Keep material method records dates and locations together. Classify material method records as observed or unresolved. Verify material method records before dependent work. Retain material method records revisions in event evidence.
ROUTE 5Note blocked access and exceptions
“Note blocked access and exceptions” needs a distinct entry for blocked access exceptions in the event evidence file. For blocked access exceptions, tie to a numbered zone. Within blocked access exceptions, add operating windows explicitly. Regarding blocked access exceptions, name the decision owner. While reviewing blocked access exceptions, record communications by action. Before closing blocked access exceptions, keep with the contract map. Connect blocked access exceptions to the affected proposal line. Keep blocked access exceptions dates and locations together. Classify blocked access exceptions as observed or unresolved. Verify blocked access exceptions before dependent work. Retain blocked access exceptions revisions in event evidence.
ROUTE 6Attach dated photos where appropriate
“Attach dated photos where appropriate” needs a distinct entry for dated photos appropriate in the event evidence file. For dated photos appropriate, use one consistent event record. Within dated photos appropriate, log weather, arrival, and actions. Regarding dated photos appropriate, attach zone photos when appropriate. While reviewing dated photos appropriate, record exceptions and communications. Before closing dated photos appropriate, set retention and review duties. Connect dated photos appropriate to the affected proposal line. Keep dated photos appropriate dates and locations together. Classify dated photos appropriate as observed or unresolved. Verify dated photos appropriate before dependent work. Retain dated photos appropriate revisions in event evidence.
ROUTE 7Log tenant or customer reports
“Log tenant or customer reports” needs a distinct entry for tenant customer reports in the event evidence file. For tenant customer reports, use one consistent event record. Within tenant customer reports, log weather, arrival, and actions. Regarding tenant customer reports, attach zone photos when appropriate. While reviewing tenant customer reports, record exceptions and communications. Before closing tenant customer reports, set retention and review duties. Connect tenant customer reports to the affected proposal line. Keep tenant customer reports dates and locations together. Classify tenant customer reports as observed or unresolved. Verify tenant customer reports before dependent work. Retain tenant customer reports revisions in event evidence.
ROUTE 8Set retention and privacy rules
“Set retention and privacy rules” needs a distinct entry for retention privacy rules in the event evidence file. For retention privacy rules, use one consistent event record. Within retention privacy rules, log weather, arrival, and actions. Regarding retention privacy rules, attach zone photos when appropriate. While reviewing retention privacy rules, record exceptions and communications. Before closing retention privacy rules, set retention and review duties. Connect retention privacy rules to the affected proposal line. Keep retention privacy rules dates and locations together. Classify retention privacy rules as observed or unresolved. Verify retention privacy rules before dependent work. Retain retention privacy rules revisions in event evidence.
ROUTE 9Review closeout and unresolved issues
“Review closeout and unresolved issues” needs a distinct entry for closeout unresolved issues in the event evidence file. For closeout unresolved issues, use one consistent event record. Within closeout unresolved issues, log weather, arrival, and actions. Regarding closeout unresolved issues, attach zone photos when appropriate. While reviewing closeout unresolved issues, record exceptions and communications. Before closing closeout unresolved issues, set retention and review duties. Connect closeout unresolved issues to the affected proposal line. Keep closeout unresolved issues dates and locations together. Classify closeout unresolved issues as observed or unresolved. Verify closeout unresolved issues before dependent work. Retain closeout unresolved issues revisions in event evidence.