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.”
Use a demonstration organization with the Tribal Government suite entitlement in Sandbox. The walk-through demonstrates that Vanguard VEM 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 VEM 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.”
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, confirm the state view shows every operational Nation expected for that state, use Show on Map to center the local Vanguard basemap on the Nation reference point, 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.”
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.”
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.”
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.”
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.”
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.”
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 Nation/community native-language greeting field and Hear greeting control when locally verified. Show the organization AOI Culture & Faith Profile and the shared Faith & Cultural Community Considerations references as responder aids for language access, trusted messengers, prayer/worship, 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.