Mitigation

Use Mitigation to plan and complete avalanche control route sessions. The beta target is one route session: plan it, log shots, finish, review, and sign off.

Beta target

Run one route session from planning through signoff. Keep your operation's approved field record or fallback process in place during beta.

During beta, focus on the flow more than full production policy:

• Can your team set up a route and understand the session checklist?
• Is it clearer to log from the map, the session page, or both?
• Does the finished record match what your team needs to review later?

Workflow

flowchart TD
    Library["Build route library"] --> Daily["Choose today's route"]
    Daily --> Run{"Run the route"}
    Run --> Field["Field view: map cockpit"]
    Run --> Desk["Review view: session page"]
    Field --> Close["Finish route work"]
    Desk --> Close
    Close --> Record["Completed session record"]

Set up routes, shot placements, and team coverage before the first live session. After that, daily work is mostly planning and running route sessions.

Before first session

Confirm the minimum setup before live use:

Area	Ready when
Access	The mitigation module is enabled and the right users can open Mitigation.
Route setup	Each route exists and has the planned shot placements your team expects to log.
Team	Route leaders and members are assigned for the routes in scope.
First run	The session date, selected routes, and fallback field-record plan are clear.

Where setup happens

• Use Avalanche > Mitigation > Routes to create routes and shot placements.
• Use Avalanche > Mitigation > Team to assign route leaders and members.
• Use Avalanche > Mitigation > Sessions to plan the routes for the day.
• Planning multiple routes creates one planned session for each selected route.

Team, roles, and training

• Route leader: the person accountable for the route assignment and coverage.
• Team members: the people expected to work or support the route.
• Session in charge / blaster: confirm the session shows the right person for that route run before finish and review.
• Training and qualifications: use them as readiness context during beta. Do not assume they block work unless your SnowObs administrator has confirmed enforcement for your workspace.

Configuration check

• The mitigation module is enabled for your workspace.
• Users who need Mitigation can open the module.
• The people who manage routes, team coverage, sessions, and signoff know what they can edit.
• Signoff and training expectations are understood before the first run.
• The fallback field-record plan is clear.

Run a route session

A session is one route run. Start from either path:

flowchart TD
    Map["Map cockpit<br/>Where did it happen?"] --> Record["Session record"]
    Sessions["Sessions page<br/>What happened?"] --> Record
    Record --> Shots["Shot log<br/>status, result, size"]
    Shots --> Finish["Finish route work"]
    Finish --> Review["Review session record"]

Entry point	Best for
Map	Spatial shot logging in the mitigation cockpit.
Sessions page	Checklist logging, review, edits, and signoff.

During the session:

1. Open or start the route session.
2. Log planned and unplanned shots.
3. Record each shot status and result.
4. Add avalanche size when a triggered result requires it.
5. Finish the session.
6. Review the session record and sign off according to your beta process.

Both entry points update the same session record.

Map logging

Confirm the active route session before logging from the map, especially if more than one planned or active session is open.

Constraints

flowchart TD
    Route["Route setup"] --> Snapshot["Session snapshot"]
    Team["Team coverage"] --> Snapshot
    Placements["Planned placements"] --> Snapshot
    Snapshot --> Planned["Planned shots"]
    Snapshot --> Extra["Unplanned shots"]
    Planned --> Complete["Completed record"]
    Extra --> Complete
    Complete --> Review["Review step"]

• One session is one route run. Planning multiple routes creates multiple sessions.
• The same route can run more than once in a day by creating another session.
• The checklist comes from route setup. Fix route setup before planning if the checklist is wrong.
• Finish requires complete shot records. Triggered shots may require avalanche size.
• Signoff is a review step after finish. Follow your operation's beta process before treating a session record as complete.

Beta boundaries

• Use Mitigation as a connected workflow during beta. Keep your operation's approved field record or fallback process until your operation explicitly approves a change.
• Setup and daily logging are separate jobs. Keep route and team setup out of the field path when possible.
• The session page is the review surface. Use it to check times, shot results, unplanned shots, and signoff readiness.
• Report places where SnowObs forces extra steps, hides the active session, or does not match your field sequence.

Beta feedback

After the first live or dry-run session, send feedback through the agreed beta support path. Include the session date, workflow step, and issue type, and avoid unnecessary personnel or customer-specific detail.

Answer:

• Entry path: did you start from the map or the session page, and was the active route session clear?
• Shot logging: did the checklist match the field sequence, and were unplanned or additional shots easy to record?
• Team context: were route leader, session in charge / blaster, and roster labels clear, and did the roster match who worked the route?
• Setup and configuration: were training context, settings, permissions, and signoff expectations clear before the first session?
• Closeout: did finish, review, and signoff happen at the right point, and what needs to improve before changing the approved fallback process?

Troubleshooting

Common issues

Problem	Check
I do not see Mitigation	Ask an administrator to confirm the mitigation module is enabled and your user has access.
I cannot create or edit routes	Route setup is usually an administrator task. Ask a mitigation administrator to create or edit the route.
I cannot plan a session	Confirm that at least one route exists. If routes exist but show setup warnings, review missing shot placements or team assignments.
A route shows setup warnings	Open the route and check for missing geometry, shot placements, route leader, or team coverage.
I logged to the wrong active session	Pause logging, switch to the correct session, and report the affected session date, route, and shot rows through the agreed beta support path. Do not sign off until the record is corrected.
I cannot sign off	Confirm the session has been finished and that your user has the correct access for signoff.
The dashboard looks empty	If no sessions have been planned or signed off, the dashboard will show setup guidance and empty states. Plan the first session after routes, shot placements, and team assignments are ready.