TrailheadAccesses & LandownersAccesses & Agreements
AA-02Route mapping

Link Beats to Required Accesses

Operations turns a route known by people into a dependable sequence of Accesses for every Beat.

Track

Accesses & Agreements

Phase

Route mapping

Starts with

Beat without a complete crossing path

Ends with

Ordered Access requirements

You are here

AA-02
  1. AA-01Register An Operational Access
  2. AA-02Link Beats To Required Accesses
  3. AA-03Create Or Link A Landowner Agreement
  4. AA-04Configure A Fee Rule And Payment Path
  5. AA-05Renew Or Supersede An Agreement

The situation

A Beat requires one or more crossings for entry, exit, or both.

What starts it

Operations creates or edits a Beat's access requirements.

How it unfolds

OperationsGuideSystem
  1. 1

    Operations opens the Beat in reference-data management.

    Operations
  2. 2

    Operations selects every Access required to reach the Beat.

    Operations
  3. 3

    Operations marks each Access for entry, exit, or both and orders the route.

    Operations

    This is the key moment: the Beat now carries a complete operational crossing path.

  4. 4

    Trailhead saves the Beat links against stable Access records.

    System

Who's involved

Operations

Defines the crossings required by the Beat.

Guide

Uses only the route instructions relevant to the Program.

System

Keeps Beat links attached to stable Accesses.

What each person sees

Operations

The complete ordered crossing path for the Beat.

Why: Keep route requirements accurate.

Guide

Relevant Access steps when the Beat appears in a Program.

Why: Follow the correct field route.

The rule to remember

Beats link to Accesses; effective Agreements are resolved later for the usage date.