Operations
See the live operation, understand what needs attention, and close the day with confidence.
Operations is Trailhead's command layer. It helps the company answer: what is happening now, what is blocked, who needs to act, and is the day ready to close?
What Operations is responsible for
Operations brings the important signals from across the company into one working view. It makes blockers visible, helps people reach the record that needs attention, and gives the team confidence about the live day and its closure.
Use Operations to:
- see the state of the field day and the work still in motion;
- identify blockers across trips, Programs, guide readiness, gear, accounts, and delivery;
- follow up on alerts and communications that need an owner;
- understand whether reporting and guide-payment work is ready to move forward; and
- see whether work is closed or exactly why it is not.
Operations starts with trusted source information
Operations does not create a second version of the company's work. It makes the right information easier to see and act on.
| When the question is about... | Start with the source area |
|---|---|
| A Program, execution, or Fishing Report | Fishing |
| A guide's readiness, gear, expenses, advances, or account | Guides |
| A client trip or the work it requires | CIS |
| The knowledge behind a better field decision | Field Knowledge |
Operations then gives the team the cross-lodge view: what is late, risky, waiting for review, or ready to move on.
Prepare weekly meal counts
Open Operations → Prepare → Weekly meals to calculate the lodge's daily client meal baseline, record explicit staff additions, resolve warnings, and confirm a version for the lodge manager to acknowledge. Unknown or conflicting source values remain visible and block confirmation; they are never counted as zero.
See the complete Weekly Meals flow, including lodge week boundaries, permissions, version history, and Live and Mock modes.
Turn a blocker into an action
A useful operational view does more than show a warning. It helps the person responsible find the exact trip, Program, report, or guide matter behind it. That keeps the team from guessing where a problem belongs or treating a count as the explanation.
For example, a day cannot be considered complete just because a Program has ended. The company may still need a reviewed Fishing Report, a clear guide or gear matter, or confirmation that the trip's required work is satisfied. The Operational Closure flow explains how those pieces come together.
Keep the boundary clear
Operations owns visibility, triage, and closure confidence. Fishing still owns the Program and its report. Guides still owns the guide's readiness and account context. CIS still owns the client trip. Field Knowledge still owns the curated context that improves future choices.
A healthy operation
At a glance, the team can tell what has not started, what is under way, what needs review, and what is genuinely complete. Every blocker has a clear owner and a useful path to resolve it.