CONTRACT MATRIX

Make Triggers, Duties and Exclusions Explicit

Put each bidder against the same property facts and event definitions. A service label is incomplete until trigger, zone, responsibility and exception are explicit.

Compare Contract Terms Call (778) 764-1440 ext. 230

Weather outcomes remain variable.

Treatment, accessibility, fire-route, environmental, record-retention and liability questions require current authority and qualified review. No plan can guarantee surface or weather outcomes.

ROUTE 1

Name parties and property boundaries

“Name parties and property boundaries” needs a distinct entry for parties property boundaries in the contract matrix file. For parties property boundaries, tie to a numbered zone. Within parties property boundaries, add operating windows explicitly. Regarding parties property boundaries, name the decision owner. While reviewing parties property boundaries, record communications by action. Before closing parties property boundaries, keep with the contract map. Connect parties property boundaries to the affected proposal line. Keep parties property boundaries dates and locations together. Classify parties property boundaries as observed or unresolved. Verify parties property boundaries before dependent work. Retain parties property boundaries revisions in contract matrix.

ROUTE 2

Define season and event terminology

“Define season and event terminology” needs a distinct entry for season event terminology in the contract matrix file. For season event terminology, define a measurable trigger. Within season event terminology, name the observation source. Regarding season event terminology, set decision timing explicitly. While reviewing season event terminology, cover nights and weekends. Before closing season event terminology, record escalation and follow-up. Connect season event terminology to the affected proposal line. Keep season event terminology dates and locations together. Classify season event terminology as observed or unresolved. Verify season event terminology before dependent work. Retain season event terminology revisions in contract matrix.

ROUTE 3

State accumulation or observation triggers

“State accumulation or observation triggers” needs a distinct entry for accumulation observation triggers in the contract matrix file. For accumulation observation triggers, define a measurable trigger. Within accumulation observation triggers, name the observation source. Regarding accumulation observation triggers, set decision timing explicitly. While reviewing accumulation observation triggers, cover nights and weekends. Before closing accumulation observation triggers, record escalation and follow-up. Connect accumulation observation triggers to the affected proposal line. Keep accumulation observation triggers dates and locations together. Classify accumulation observation triggers as observed or unresolved. Verify accumulation observation triggers before dependent work. Retain accumulation observation triggers revisions in contract matrix.

ROUTE 4

List plowing, walking and ice zones

“List plowing, walking and ice zones” needs a distinct entry for plowing walking ice zones in the contract matrix file. For plowing walking ice zones, plot on the current map. Within plowing walking ice zones, number plow and walkway areas. Regarding plowing walking ice zones, protect fire and accessible access. While reviewing plowing walking ice zones, add operating windows and obstacles. Before closing plowing walking ice zones, assign map-update responsibility. Connect plowing walking ice zones to the affected proposal line. Keep plowing walking ice zones dates and locations together. Classify plowing walking ice zones as observed or unresolved. Verify plowing walking ice zones before dependent work. Retain plowing walking ice zones revisions in contract matrix.

ROUTE 5

Record method and material constraints

“Record method and material constraints” needs a distinct entry for method material constraints in the contract matrix file. For method material constraints, locate recurrent problem zones. Within method material constraints, trace runoff and refreeze paths. Regarding method material constraints, state approved treatment constraints. While reviewing method material constraints, record action and timing. Before closing method material constraints, require a follow-up observation. Connect method material constraints to the affected proposal line. Keep method material constraints dates and locations together. Classify method material constraints as observed or unresolved. Verify method material constraints before dependent work. Retain method material constraints revisions in contract matrix.

ROUTE 6

Set communication and escalation roles

“Set communication and escalation roles” needs a distinct entry for communication escalation roles in the contract matrix file. For communication escalation roles, use one consistent event record. Within communication escalation roles, log weather, arrival, and actions. Regarding communication escalation roles, attach zone photos when appropriate. While reviewing communication escalation roles, record exceptions and communications. Before closing communication escalation roles, set retention and review duties. Connect communication escalation roles to the affected proposal line. Keep communication escalation roles dates and locations together. Classify communication escalation roles as observed or unresolved. Verify communication escalation roles before dependent work. Retain communication escalation roles revisions in contract matrix.

ROUTE 7

Specify event photos and records

“Specify event photos and records” needs a distinct entry for event photos records in the contract matrix file. For event photos records, define a measurable trigger. Within event photos records, name the observation source. Regarding event photos records, set decision timing explicitly. While reviewing event photos records, cover nights and weekends. Before closing event photos records, record escalation and follow-up. Connect event photos records to the affected proposal line. Keep event photos records dates and locations together. Classify event photos records as observed or unresolved. Verify event photos records before dependent work. Retain event photos records revisions in contract matrix.

ROUTE 8

Expose add-ons and exceptional events

“Expose add-ons and exceptional events” needs a distinct entry for add-ons exceptional events in the contract matrix file. For add-ons exceptional events, define a measurable trigger. Within add-ons exceptional events, name the observation source. Regarding add-ons exceptional events, set decision timing explicitly. While reviewing add-ons exceptional events, cover nights and weekends. Before closing add-ons exceptional events, record escalation and follow-up. Connect add-ons exceptional events to the affected proposal line. Keep add-ons exceptional events dates and locations together. Classify add-ons exceptional events as observed or unresolved. Verify add-ons exceptional events before dependent work. Retain add-ons exceptional events revisions in contract matrix.

ROUTE 9

Document exclusions and owner duties

“Document exclusions and owner duties” needs a distinct entry for exclusions owner duties in the contract matrix file. For exclusions owner duties, compare identical property duties. Within exclusions owner duties, define inclusions and add-ons. Regarding exclusions owner duties, state owner responsibilities clearly. While reviewing exclusions owner duties, address exceptional events explicitly. Before closing exclusions owner duties, route legal questions appropriately. Connect exclusions owner duties to the affected proposal line. Keep exclusions owner duties dates and locations together. Classify exclusions owner duties as observed or unresolved. Verify exclusions owner duties before dependent work. Retain exclusions owner duties revisions in contract matrix.