Retail
A regional structure
Branches roll up to regions and regions to head office. The branch manager sees their own team and the regional manager sees every branch, in the same chart.
The chart belongs in the system, not in a slide deck
Units, positions and reporting lines are defined in one place; joiners, promotions and leavers show up in the chart the same day. Approval chains are read from the same structure.
What this runs on today
- A slide deck updated once a year
- a headcount list kept on the side
Org chart
Why it is needed
What happens without this module
The three situations we run into most often. If one of them sounds familiar, we have something to talk about.
- 01
The chart is always out of date
The newest version of the deck is six months old. Leavers are still in boxes, joiners are nowhere to be seen.
- 02
Who reports to whom is unclear
Where an approval should go is learned by asking around; during cover periods requests simply stall.
- 03
Open headcount is invisible
Which positions are filled and which are vacant lives in another list, and the hiring plan gets lost between that list and the chart.
What it does
What the module covers
Every item is a real screen or flow in the product; we walk through them one by one in the demo.
A live chart
Units, positions and people in one view; hires, promotions, transfers and exits appear immediately.
Positions and headcount
The chart is built from positions, not people; filled, vacant and pending roles are shown separately.
Source of the approval line
Leave, expense and advance approvals read this structure; when it changes, the chains follow.
Delegation
When a manager is on leave, their authority passes to a named deputy so requests do not stall.
Multiple companies and sites
Group companies, branches and cost centres are managed as separate branches of the same chart.
Headcount reports
Headcount per unit, span of control and vacancy listings come as ready-made reports.
How it works
The cycle in four steps
Once it is set up, every period runs in the same order, and most of the steps happen on their own.
- Step 01
The structure is built
Units, positions and reporting lines are defined and the current headcount is mapped onto them.
- Step 02
People are attached
Every employee sits in a position, so the chart and the employee file run on the same data.
- Step 03
Changes are recorded
A promotion, transfer or exit updates the chart and the approval line the moment it is entered.
- Step 04
The structure is read
Headcount reports and approval chains are produced from the live chart — no side list is kept.
Data flow
A link in the chain, not an island
The same data is entered once. What this module takes in and produces is below — you do no extra work to move data between modules.
Neyden beslenir
- Employee recordsPeople, positions and service
- Recruitment (ATS)Positions opened and filled
- PerformancePromotions and role changes
Org chart
Takes the data in once and shares the same record with the other modules.
Neyi besler
- Requests and approvalsApproval chains and authority
- Leave managementTeam calendar and approver
- ReportingHeadcount and unit distribution
In the field
How it is used, and under what constraints
Not promises with numbers, but real setups. Let us go into the one closest to yours in the demo.
- Group companies
A holding structure
Each company sits on its own branch while shared service functions are defined once. When someone moves between companies, their record moves with them.
- Manufacturing
Shift responsibility
The same line has different leads on different shifts. The approval line is defined per shift, so requests land with the right person.
FAQ
Frequently asked about Org chart
No. The chart is fed by employee records; hires, promotions, transfers and exits update it on their own. There is no separate deck to maintain.
Usually set up alongside this one
Let’s see the Org chart module with your own data
A demo is not a presentation: we build your scenario and run it on screen. You leave with a written proposal covering scope and timeline.