How should I set up my organization's Locations, Departments, and Teams?

A guide on creating Locations, Departments, and Teams to optimize your reporting insights.

Preciate Premium Admins have the ability to create and manage their organization's Locations, Departments, and Teams within Preciate. These entities can then be mapped to users allowing for deeper insights from Preciate's reporting. You'll be able to understand how recognition activity flows across and within Locations, Departments, and Teams. This greater visibility will empower you to identify areas within your organization that are excelling and struggling within your recognition program.

When determining how to set up these areas, it's important to understand how they operate within Preciate. 

 

For Locations, Departments, and Teams, there will always be a Default one of each. This Default entity cannot be removed, but you do not need to map any users to it. If a user is added to your organization and has not been mapped to any custom Locations, Departments, or Teams, he/she will be assigned to the Default one of each.

Locations and Departments

Both Locations and Departments are stand alone entities in our system and because of this are pretty straightforward. Most organizations choose to create Locations based on their physical office locations and their Departments based on the division of functional groups: i.e.: Sales, Marketing, Operations etc. If your organization only has one office, you can choose to create a new location for your office or use the Default location. 

 

You can create as many Locations and Departments as you want, but each one must have a unique name. You cannot have two Sales Departments. 

 

For steps on how to create Locations and Departments, check out these guides.

Teams

Teams must be mapped to both a Location and a Department. Because Locations and Departments always have a Default entity, Teams that are not associated with a custom Location or Department will be mapped to the Default one of each. To understand how this will work with your organization, let's review a few examples.

 

Example: 1 - 1 - 1

You have a Marketing team that belongs to your Marketing Department and everyone is all located at your Dallas office. 

You would create a Dallas Location, Marketing Department and Marketing Team that is mapped to both Dallas and Marketing.

 

Example: 1 - 1 - M

You have a Customer Success team that belongs to your Operations Department, but the team is spread out over 3 different locations: Dallas, London, and Denver.

Since a team can only belong to one Location and one Department, you will need to create 3 different Customer Success teams and map each one accordingly.

Customer Success - A maps to Operations and Dallas

Customer Success - B maps to Operations and London

Customer Success - C maps to Operations and Denver

 

When creating multiple teams that fulfill the same function like the example above, add some identifier like A, B, C to help you distinguish each one from the other.

 

For a guide on how create teams, check out this article:

If a portion of your organization is remote, consider creating at least one Remote Location so you can understand how your remote workforce interacts with your users located in offices.