Setup Considerations: organisational hierarchy

What this achieves

Humavera models your structure as business units containing departments containing teams. How you use those three levels decides what your reporting groups by and how your approvals route, and both are awkward to change once people are assigned.

Decision 1: how many of the three levels you actually need

You have three levels available. You do not have to use all of them.

Option	Description
Departments only	Simplest. Suits an organization small enough that departments are the natural grouping.
Business units and departments	Suits a company with genuinely separate divisions or a multi-entity group.
All three, with teams	Suits departments large enough that a team is the real working unit.

Use a level because it corresponds to something real in your organization, not because it exists. An unnecessary level is a field on every employee record that somebody has to keep correct.

Example: HC Corp UK Ltd’s Engineering department of 34 people genuinely needs teams beneath it. Its People department of 6 does not — teams there would be a level with one person in each.

Decision 2: depth costs accuracy

Every level you add is another assignment to maintain per employee, and another way for a record to drift out of date. A structure three levels deep with 40 units in it will have wrong assignments in it within a year unless somebody owns keeping it right.

Decide who owns structural accuracy before you build depth. If the answer is nobody, build less.

Decision 3: departments are not reporting lines

This is the distinction most often missed. A department groups people by function. It does not determine who approves whose work.

Approvals route along the reporting line, which comes from each employee’s manager, not from the department tree. A department has a head, and that head is not automatically everybody’s approver.

Example: an HC Corp UK Ltd engineer whose department head is Olivia Bennett may report to a team lead. Approvals reach the team lead because that is their manager, not Olivia because she heads the department.

Plan the two together but do not assume one implies the other.

Decision 4: structure or attribute

Some things look structural and are better held as an attribute of the employee.

Option	Description
Department	Function. Genuinely structural, drives reporting groupings.
Location	Where somebody works. A separate record, not a level of the hierarchy.
Cost centre	An accounting code held on the department.

A common mistake is creating a department per site — “Engineering London” and “Engineering Manchester” — when what you have is one department in two locations. That splits your reporting on the wrong axis and doubles the structure.

Example: HC Corp UK Ltd keeps one Engineering department and records London and Manchester as locations. Reporting can then group by either.

Decision 5: deletion is guarded, so empty before you remove

The delete confirmations for business units, departments, and teams state that the action cannot be undone, and each names what blocks it: employees or sub-departments for a department, departments or child units for a business unit, and assigned employees for a team.

That is the same protection locations and positions carry, both of which block deletion or require reassignment first. It is consistent across the hierarchy.

Before deleting any structural unit, check what is assigned to it and move those assignments first. That is the work either way — the difference is that the deletion will be refused rather than let through.

What is expensive to change later

Decision	Cost of changing later
Deleting a unit with employees assigned	Blocked until they are moved. The cost is the reassignment, not the deletion.
Splitting one department into several	High. Every affected employee is reassigned, and reporting spans two shapes across the change.
Adding a level after people are assigned	Medium to high. Every employee needs the new assignment.
Removing a level you stopped using	Medium.
Renaming a unit	Low.
Adding a new department alongside existing ones	Low.

What happens next

Build the structure, then assign employees to it. Departments become selectable on the employee record, approvals route along reporting lines you set per employee, and reporting groups by whatever levels you have used.