How to avoid having multiple job descriptions for the same position, which makes updating tedious.
When departments have branch titles
we'll see a csv that looks like this for the tellers:
First Name | Last Name | Position | Department | Branch |
Example | Employee | Teller | Corporate | Corporate |
Example | Employee | Teller | Downtown | Downtown |
Example | Employee | Teller | 1st Street | 1st Street |
Example | Employee | Teller | Meridian | Meridian |
Example | Employee | Teller | Main Street | Main Street |
By giving these employees/positions department titles that represent your branches, you are likely adding reporting functionality in your HRIS or payroll systems. But in BalancedComp, position titles belong to departments. As a result, in the example above, we would have 5 duplicate positions in BalancedComp for your tellers:
- Teller position in Corporate department
- Teller position in Downtown department
- Teller position in 1st Street department
- Teller position in Meridian department
- Teller position in Main St department
The implications of this are:
- If you changed a compensable factor, you would have to update it in 5 separate places.
- If you changed part of a position description, you would have to change it in 5 places.
- If this was done for all your Branch Operations positions, 5-10 positions would easily become 50 positions, which could slow your system down.
- The system would forever consider those 5 Teller positions to be completely separate positions, meaning: you would never be able to run reports for all your Tellers at once, which we think is a valuable report.
- Bridging your HRIS or payroll system to BalancedComp may become more difficult. Referencing the example csv above, if you added a Teller at a new branch (called Campus), you’d have to remember to create a whole new Teller position in BalancedComp with the Campus branch before you imported or you would receive errors.
The solution!
Which happens to require no work on your part ;)
If you authorize us, we can make 1 of each position title, each belonging to a general department like “Branch Operations,” or whatever you’d like. We’d alter your csv to look like this:
First Name | Last Name | Position | Department | Branch |
Example | Employee | Teller | Branch Operations | Corporate |
Example | Employee | Teller | Branch Operations | Downtown |
Example | Employee | Teller | Branch Operations | 1st Street |
Example | Employee | Teller | Branch Operations | Meridian |
Example | Employee | Teller | Branch Operations | Main Street |
These 1 to 1 position and department associations would eliminate all the busy work of maintaining duplicate positions and bridging with them. Additionally, you’d still be able to run reports by branch – rather than department – if you wanted location-based reports. When it comes to bridging, you wouldn’t have to make any changes on your payroll/HRIS end. Since only 1 version of each position title would exist in BalancedComp (ex: 1 Teller position title would exist in the Branch Operations department), the bridge would dump all incoming Tellers into that single position, regardless of the department in the CSV.
As always, the decision is up to you! We are here to advise and then implement your final decision.