Presenter Guide · September 19, 2026

Tribal Community Demonstration Walk-Through

Vanguard Command · Tribal Emergency Management / Sovereign Government Configuration

30-minute presenter flow

Use a demonstration organization with the Tribal Government suite entitlement in Sandbox. The walk-through demonstrates that Vanguard Command supports the Nation's own terminology, sovereign-government context, controlled sharing, government-to-government coordination, incident operations, EOC/ICS, decision support, assistance and recovery without forcing a county-centric operating model.

Before the demonstration: Sign in to the Tribal demonstration account, verify the active organization includes the Tribal Government suite entitlement, use the National Tribal Reference Directory or AOI Selection to choose a practice Tribal Nation AOI, and keep the scenario fictional. Existing memberships inherit organization suites unless an Administrator has explicitly selected Restricted suites.
Suggested scenario

Wildfire smoke, a regional utility disruption and possible evacuation affect the Tribal community. Tribal departments, utilities, neighboring governments, healthcare/public-safety partners and voluntary organizations must coordinate while the Nation retains control of priorities, terminology and information sharing.

Core message

“Vanguard Command is one connected operating environment. The Tribal Nation remains the primary jurisdictional context, and the same information can carry from preparedness and intelligence through response, assistance, recovery and improvement.”

0–2 min

1. Start with the operating context

Show My Workspace and explain that AOI, organization, role and permissions follow the user through the program.

Say: “The program starts with what the user needs to do, not with a long software menu.”
Open Step →
2–5 min

2. National Tribal directory, state filter and Nation-defined AOI

Open the National Tribal Reference Directory, filter by the scenario state, select the practice Nation with Use as Tribal AOI, then confirm the Tribal Nation / community / facility context. Explain that the Nation can use its preferred leadership, governing-body, emergency-management and community terms.

Say: “A Tribal Nation does not have to be represented as a county subdivision. The Tribal jurisdiction can remain the primary AOI.”
Open AOI Selection →
5–8 min

3. Open the Tribal Government workspace

Show Tribal leadership/government operations, government structure, departments/functions and Nation-defined configuration.

Say: “This is the Vanguard core platform configured for sovereign Tribal government operations—not a disconnected side program.”
Open Tribal Workspace →
8–10 min

4. Government-to-government coordination

Show that sovereign/government relationships are distinguished from ordinary partner relationships, while coordination calls and partner actions remain connected.

Say: “Government-to-government relationships stay visible as government relationships rather than being flattened into a generic contact list.”
Open G2G →
10–12 min

5. Tribal data governance

Review internal Tribal government, government-to-government and restricted Tribal information concepts. Emphasize minimum-necessary sharing and authorized release.

Say: “The system helps keep the sharing classification visible; it does not make the sovereignty or release decision for the Nation.”
Open Data Governance →
12–15 min

6. Intelligence, CAN-P and GIS / COP

Show how field/community information can be structured into Conditions, Actions and Needs, then viewed geographically in the common operating picture.

Say: “Narrative reports can become usable operational data while the original record remains available.”
15–19 min

7. Response, EOC and ICS-300/400 controls

Show incident assignments/IAP, EOC coordination and the newer command/planning guardrails: Planning P, span of control, Unified Command, delegation and transfer of command.

Say: “Vanguard supports ICS without silently reorganizing the incident. It identifies issues and lets authorized leadership document justified exceptions.”
19–22 min

8. Incident Dashboard and “What needs my attention?”

Build an incident-specific view, change the time window, and show attention items/changes rather than forcing leadership to read every record.

Say: “The dashboard is a decision-support layer. The source record remains authoritative, and every important count should drill back to its evidence.”
22–24 min

9. Ask Vanguard for a specific graph

Use a plain-language example such as “Show unresolved needs by community for the last 24 hours” or “Show EOC staffing vacancies by department.” Review the interpreted criteria before generating.

Say: “The user can ask a real operational question, see how Vanguard interpreted it, change the filters, and then open the records behind the graph.”
Open Graph Builder →
24–26 min

10. Assistance and outside support

Show how a need can move through Tribal, mutual-aid, government, VOAD/nonprofit and private-sector channels without losing the Nation's context.

Say: “Outside assistance is connected to the Tribal government's identified need; it does not replace Tribal priorities or authority.”
Open Assistance →
26–28 min

11. Cultural resources, faith and community considerations

Show the Tribal cultural-resources pathway first and explain that sensitive cultural information should not be placed into broadly shared operational records. Then show the shared Faith & Cultural Community Considerations reference as a general responder aid for language access, trusted messengers, shelter/service accommodations and community engagement.

Say: “Nation-provided protocols and Tribal cultural-resource authority come first. The shared reference helps responders ask better questions; it never substitutes for the Nation’s guidance.”
28–30 min

12. Recovery + continuous improvement

Close by carrying unresolved needs and Nation priorities into recovery, then show that problems/remedies can be captured during the incident or exercise rather than waiting for the AAR.

Close with: “The information does not stop at response. Vanguard carries the same operational context into recovery, improvement and future preparedness.”

Optional questions to ask the Tribal Emergency Manager

What terminology should the system use for leadership, governing body, communities/districts and emergency management?
Which information categories should default to internal Tribal government, government-to-government or restricted sharing?
Which departments, enterprises, cultural-resource authorities and external government relationships should appear in the standard configuration?
Which recurring reports, dashboards or briefing products would save your staff the most time?

Demonstration rule: use fictional incident data unless the Tribal Nation has expressly approved use of real operational information. Do not infer cultural practices, identity, membership, sacred-site information or community-specific protocols; use Nation-provided terminology and guidance.

Optional 10-minute advanced intelligence extension

Leadership Intelligence: show What Changed, leadership decisions, high-risk signals and controlled external-sharing visibility.
Resource & Workforce: review staffing, assignments, resource needs, training/skill gaps and fatigue/sustainment indicators.
Community Vulnerability: connect access, lifeline and service gaps to priority community-support actions.
Predictive Resilience: move between Digital Twin, Predictive Future State, AI Operational Watchtower and human-reviewed decision support.

New: Sovereign Assistance & Decision Workflow

Vanguard Command now connects a Tribal Declaration & Assistance Case Manager, Government-to-Government Coordination Board, Recovery & Grants Portfolio, and Leadership Decision Register. These workflows retain Nation-defined authority, controlled sharing, AOI/incident context and searchable operational history.

Demonstrate: leadership authorization → evidence completeness → G2G request/commitment → recovery funding/project → leadership decision and follow-up.

Operational Automation

Show how an authorized leadership decision, declaration/RFI requirement, G2G commitment or recovery milestone becomes a reviewed Vanguard Command assignment rather than an untracked note.

  1. Open Tribal Operational Automation.
  2. Review why the recommendation fired and the source record/version.
  3. Approve one assignment and confirm it appears in My Work.
  4. Send an in-app assignment notice.
  5. Generate the What Changed briefing and explain that external release still requires Nation authority.
Open Operational Automation

Operational Assurance & Mission Performance

Show how Vanguard Command verifies execution after decisions and automation create work.

  1. Open Tribal Operational Assurance.
  2. Review an overdue, changed-source, declaration evidence, G2G or recovery finding.
  3. Open the authoritative source and validate the condition.
  4. Record an authorized disposition and create follow-up when needed.
  5. Generate the leadership assurance briefing and explain the Nation-control safeguards.
Open Operational Assurance

Executive Resilience & Outcomes

Show how leadership moves from operational assurance to long-term mission outcomes without relying on an opaque score.

  1. Open Tribal Executive Resilience & Outcomes.
  2. Review the transparent resilience dimensions and the records behind each.
  3. Show Mission Impact and Executive Operational Value indicators.
  4. Create one Nation-defined strategic priority/outcome.
  5. Save a resilience snapshot, then generate the executive briefing.
Open Executive Resilience & Outcomes

Current Tribal operating architecture

The presenter route now starts with the Tribal Operations & Sovereignty Dashboard and six operating areas: Sovereign Operations, Community & Lifelines, Preparedness & Readiness, Response & Resources, Recovery & Assistance, and Leadership Intelligence.

Open Tribal Dashboard Open Sovereignty Center