An org structure is a company's map: units, positions and reporting lines. In an HR system it is not an illustration for a slide deck but a reference table that approvals, access rights, goal cascading and unit-level reporting all depend on.
Why this is a technical rather than a decorative entity
Almost every personnel action leans on the structure. A leave request goes to a manager — which one? A turnover report is compiled by unit — by which units? A site manager sees their own staff — on what basis does the system decide they are theirs?
While the structure exists only in a file, all of those are answered by hand and from memory. Hence the familiar symptoms: requests go to the wrong person, a departed manager keeps their access, and a department report is missing the two people transferred last month.
What matters when describing it
The mistake here is usually the same one — describing the structure through people rather than positions.
- The unit of structure is a position within a department, not an employee: the person leaves, the position stays.
- Reporting has to be unambiguous. Matrix arrangements are fine, but an approval always has one primary route.
- The structure is tied to the staffing table: filled and vacant positions are one and the same chart, not two documents.
- Change history is kept: to read last quarter's report you need the structure as it was then, not as it is today.
How this works in Verifix
In Verifix the org structure is a working reference: approval routes in E-Docs, managers' access rights, goal cascading in Perform and reporting breakdowns by unit all derive from it.
Transferring an employee changes the structure, the staffing table and their record in one action rather than three. So reports stop containing people who formally remained in their old department.
In short
An org structure is not a slide but a reference table that approvals, access and reporting depend on. Describe it in positions, not in people.