Groups & Teams

📁 Groups & Teams

The Groups and Teams feature allows you to organize your workforce in a way that reflects how your organization truly operates—whether you're grouping teams by geography, specialty, function, or a combination of all three. Groups and Teams are meant to structure your organization for reporting, provisioning and deprovisioning as well as ensuring that the correct people are notified when someone on their team uses a safety feature.

This flexible structure enables you to manage large or complex organizations without sacrificing clarity or control.

---

🔹 Groups: Regional or Operational Anchors

Groups represent higher-level organizational units. Most customers use them to reflect:

• Geographic regions (e.g., Florida, Northeast, Chicago)
• Operational zones or offices (e.g., a central hub or multi-state territory)

Each group includes:

• A group name
• A physical location (such as a main office or central hub)
• The total number of teams and members
• An option to add new teams

Groups help keep team organization scalable and align with how your business is structured at the regional or leadership level.

---

🔸 Teams: Functional Units Within Each Group

Teams sit within a Group and reflect how work is organized on the ground. These teams may be defined by:

• City-based coverage areas (e.g., Miami, Fort Lauderdale)
• Clinical specialties or departments (e.g., Behavioral Health, Skilled Nursing)
• Staffing models or employment types (e.g., Full Time, Per Diem)

Each team includes:

• Name and service location
• The number of active members
• A set of visual tags that describe the team’s function, structure, or operational status

This structure allows you to go as broad or as granular as needed while maintaining organizational clarity.

---

🏷️ Tags: Add Meaningful Metadata to Each Team

Tags give you a powerful way to describe teams across key operational dimensions. These tags are customizable and can reflect:

🏥 Service Type:

• Behavioral Health
• Skilled Nursing
• Wound Care
• Physical Therapy

👥 Workforce Type:

• Full Time
• Per Diem
• Weekend Only
• On Call

📍 Location or Coverage Area:

• Boston
• Worcester, MA
• North County
• Metro East

⚙️ Operational Labels:

• Start of Care
• POM Training Period
• Assessment
• Orientation
• New Referral Focus

Tags make it easier to:

• Filter and report on specific types of teams or roles
• Understand team purpose at a glance
• Identify staff in training or assigned to specialized workflows

Example:
A team called New Haven might be tagged with:

• Behavioral Health
• Full Time
• POM Training Period
  This tells you it's a full-time behavioral health team that is still in the process of onboarding or training on the POM platform.

Another team, like Skilled Nursing, might be tagged with:

• Skilled
• Worcester, MA
  Indicating its clinical focus and geographic assignment.

---

🧭 Flexible Granularity Options

You can tailor Groups & Teams to match your organizational complexity. Some customers structure by service type, others by geography, and many combine both.

Group	Example Teams	Strategy
Boston	Skilled, Behavioral Health	Teams by function/service within a region
Florida	Miami, Fort Lauderdale, Windermere	Teams by city, reflecting geographic assignments
Northeast	Behavioral Health, Skilled Nursing	Teams by clinical specialty, tagged by city or site
Behavioral Health	New Haven, New London, Rocky Hill	Teams by deployment location with tags for staffing

An example of a simple Groups and Teams structure is below.

This flexible framework supports any operational model, whether you assign staff based on location, skillset, training status, or employment type.

---

📡 Routing-Only Team Structures

Not every team needs to reflect a real-world department, specialty, or location. Some organizations use Teams purely as routing units, a way to control who gets notified during safety events.

This approach is useful when:

• The same staff float across multiple roles or geographies
• Coverage schedules change frequently
• You need to define escalation contacts outside of a formal team hierarchy

In these cases, the team’s name and tags might simply reflect routing logic, such as:

• After Hours
• Weekday
• Weekend Coverage
• Holiday

This lightweight structure ensures alerts from POM users always reach the right contact without requiring you to replicate your full org chart.

➕ Adding New Groups & Teams

Admins can easily build or scale the organizational structure by:

• Creating Groups with a name and central location
• Creating Teams under a group, assigning a location, and applying tags that reflect what the team does

This ensures teams are properly categorized and easy to locate, manage, and filter across the platform.

---

✅ Best Practices

• Use clear, consistent tags to describe services, locations, and roles
• Structure groups in a way that aligns with how supervisors manage staff or regions
• Consider creating temporary or status-based tags (e.g., Training, On Leave, Start of Care) to improve visibility
• Keep team naming intuitive so that users can quickly understand who does what and where

---

📋 Team Protocols

Each team can define its own safety and escalation protocols, ensuring that alerting logic is targeted and efficient.

Important:
➡️ Each POM User can only belong to one team.
This design ensures that all alerts—whether triggered via SOS or Check on Me—are consistently routed to the right people. The team a user belongs to governs which team leaders and emergency contacts are notified in a time of need.

Team Protocol Settings Include:

• Check on Me
  Enables the “Check on Me” feature for members of this team in the mobile app. By default, Check on Me escalations will go directly to POM Dispatch, who will call the user to confirm they're safe.
• Set List of Emergency Contacts (optional)
  Two emergency contacts can be defined per team. These individuals will be notified if a Check on Me alert escalates or if emergency services are engaged. - Speak with your Customer Success rep to learn more.
• Calendar Scheduling for Alerts (optional)
  Allows organizations to set custom windows for when emergency contacts should be notified—using a 7-day scheduling interface. Outside of scheduled times, default escalation rules apply.

These protocol options allow teams to tailor safety coverage to their availability, risk level, and team structure.