A Reporting Group is a vertical grouping of employees. In most cases this will be aligned with your departments. For example: Sales, Marketing, HR, IT, etc.
What are reporting groups for?
Reporting groups allow you to put your employees into groups that you would like to report on. We can then provide advanced reporting and data analysis. i.e. director reports (for the management team to compare performance against other departments) and for overall program analysis in the administration portal (i.e. How are Sales doing vs Marketing?).
Why do I need to map my departments to reporting groups?
To allow us to provide the above reporting reliably, we must map your employees to a reporting group and the best way to do that is for you to map your departments to a defined list of reporting groups.
In a perfect world we would just map your departments to your reporting groups on a one-to-one relationship but due to the nature of different client’s data structures it is not always that simple. Our approach allows you to setup the reporting groups that you want for your program and then map your departments to them, either one-to-one or many-to-one.
Can’t I just setup one reporting group and map all my departments to it?
Although technically you can run with just one reporting group, in doing so you would remove a major advantage of the above reporting (i.e. director reports, cross functional analysis, etc.). If you're a small business, we recommend you just map them one-to-one with your departments.
How about the managing director or CEO?
Usually, you will have created a department in your Human Resources Information System (HRIS) that contains your MD or CEO (and possibly their PA). If this is the case, just map this department to the appropriate director reporting group.
Example
Let's look at a practical example where Company A has the following departments:
Department Name | Department Reference |
Sales North | 0001 |
Sales South | 0002 |
Sales East | 0003 |
Sales West | 0004 |
Marketing | 0005 |
HR | 0006 |
IT | 0007 |
Finance | 0008 |
Payroll | 0009 |
- It’s obvious that all the “Sales….” ones are the same overall department but in this case the client wants “Marketing” to be combined so we can map them to a reporting group called “Sales & Marketing”
- “HR” and “IT” are individual departments so we can map those to appropriate reporting groups of “HR” and “IT”
- And finally, the client wants to combine “Finance” and “Payroll” so we can map them to a reporting group called “Finance & Payroll”
This then becomes:
Department Name | Department Reference | Reporting Group |
Sales North | 0001 | Sales & Marketing |
Sales South | 0002 | Sales & Marketing |
Sales East | 0003 | Sales & Marketing |
Sales West | 0004 | Sales & Marketing |
Marketing | 0005 | Sales & Marketing |
HR | 0006 | HR |
IT | 0007 | IT |
Finance | 0008 | Finance & Payroll |
Payroll | 0009 | Finance & Payroll |
- These mappings can now be setup in the Admin portal, and when the employee feed is uploaded the employees will be added to the appropriate reporting groups
Using department names vs references
In the above example we have shown a department name as well as a department reference. You can use either, but they must be unique so we highly recommend you use something that doesn’t change.
For example, if you were using “Sales North” and it was mapped to “Sales & Marketing” everything would be fine until someone decided to rename “Sales North” to “Sales - North” in your HRIS, at which point the employee feed would generate errors as it could no longer find “Sales North” in the department mapping. If, however, you had used “0001”, then changing the name in your HRIS would have no effect.
Multiple Countries
When multiple countries are involved, it is even more important to have unique reference for the departments in your employee feed. For example, we can have:
- UK > Sales
- US > Sales
- ES > Sales
If your feed contains just the string “Sales” then you can only map them all to one reporting group which would be in one country.
See Department mapping to reporting groups for how-to instructions.
Comments (0 comments)