Org chart software
An org chart that matches how your company actually works
01Several entities, one chart
Departments in Cyprus and Germany sit in one structure. Each person is tied to a legal entity and a location.02Line and team reporting
A person reports to a line manager and can work in a team led by someone else.03Every move has a reason
Each change is dated and tagged: promotion, transfer, reorganization, manager change.04No orphaned teams
When a manager leaves, their reports, departments, and approvals go to a named successor.The problem
Why org charts stop matching the company
A company with entities in Cyprus and Germany has three structures at once: legal, reporting, and the cross-functional teams people actually work in. They rarely line up. Most org charts show one of them, and HR redraws it by hand after every transfer. A month later the slide is wrong. The real cost shows up when someone leaves. On paper their reports have no manager, approvals wait for a person who is gone, and nobody can say when the last reorganization happened or why. Skailer changes that by building the chart from employee records. When a record changes, the structure changes on that date, and the change keeps its reason.
Multi-entity structure
Put every entity and country in one chart
International companies rarely have one org chart. They have one per entity, plus a spreadsheet that tries to join them. In Skailer, departments, divisions, locations, and legal entities live in one structure. A department in Cyprus and a department in Germany sit side by side, and each person's record shows which entity employs them and where they work.
01Department hierarchy
Nest departments under parent departments, each with its own manager.02Divisions and locations
Group departments into divisions and give every position a location.03Legal entities
Record which entity employs each person, with contract and employment type.04Department cards
Open any department to see its manager, active headcount, and members.Matrix reporting
Show line and team reporting so the chart matches real work
A developer often reports to an engineering manager and spends the day in a product team led by someone else. A single-line tree hides half of that. Skailer keeps reporting lines and teams as separate layers. Each person has a line manager and a department, and can also belong to teams with their own team lead. Both relationships stay visible on the person's record.
01Line manager
Every position names a manager, and the chain runs up to the top.02Teams with leads
Teams cut across departments, each with its own team lead.Org chart view
Drill into any team so people find the right person
People open the org chart to answer one question: who does what here. In Skailer they move from the top of the company down to one department or team, open a position, and land on the person's profile. Each viewer sees what their role allows. A colleague and an HR admin can open the same profile and see different amounts of it.
01Drill-down
Move from company level into a single department or team.02Position details
Open a position to see role, level, manager, and location.03Role-based visibility
Every viewer sees only the fields their role allows.04Field search
Press Cmd/Ctrl + F on a profile to jump straight to a field.05Status filters
Filter people by lifecycle status: Hired, Employed, On leave, Terminated.Structure history
Date and explain every change so you can trace it later
Most org charts show today and forget yesterday. In Skailer every change to a person's role, manager, department, or location is a new position record with an effective date. HR picks a reason from a shared list, so a year later the history still answers when and why. Changes can be scheduled ahead and apply on their date.
01Effective dates
Set a transfer for next Monday and it applies that day.02Required reasons
Every position change records why it happened.03Your own reason list
Add, rename, and reorder reasons; old records keep theirs.04Job profiles
Role, level, track, grade, and salary range come from one reference.05Position history
Past records stay visible to people with history access.Handover on exit
Hand over a leaver's team so no one loses a manager
When a manager leaves, the structure under them should stay intact. Skailer requires a replacement employee on every termination. The day after the termination date, direct reports move to that person with new position records. Managed departments, team-lead roles, and open approvals move too. If the successor has also left, Skailer goes up the manager chain to the first active person.
01Named successor
Every termination records who takes over the work.02Reports reassigned
Each direct report gets a new position record from the termination date.03Departments and teams
Managed departments and team-lead roles pass to the successor.04Approvals rerouted
Open approvals move over, and duplicate stages are skipped.05Audit log
Every automatic change is recorded on the termination.One HR platform
Change the structure once and the platform follows
Skailer starts with a working model of your company: roles, grades, and structure. Rules that point to a department, job role, or manager read from that model on every calculation. Move someone to a new team and their permissions, approval route, and leave policy follow without manual edits. Changes to work information can also trigger workflows. Position records hold the data. The org chart shows the structure built from it.
What is the org chart in Skailer?
Skailer vs. the alternativesMost teams keep their structure in one of three places. Slides and diagram tools give full visual freedom and suit a one-off reorg proposal. Org charts inside an HR system update from employee records, and many show additional supervisors. Skailer covers what matters when you run several entities and people change roles every month.
Compare the 3 ways companies keep an org chart
| Capability | Slides & diagram tools | Org chart in a typical HRIS | Skailer |
|---|---|---|---|
| Where the chart comes from | Drawn by hand | Employee records | Employee records, incl. legal entity and location |
| Visual freedom for one-off proposals | Full | Limited to the data | Limited to the data |
| Several legal entities and countries | Separate files or pages | Varies by vendor | One structure with entities, divisions, locations |
| Cross-team reporting | Extra lines drawn by hand | Additional supervisors in many tools | Line manager plus teams with their own leads |
| History of changes | Old file versions | Change history; reasons optional or missing | Dated position records with a required reason |
| When a manager leaves | Redraw by hand | HR reassigns reports as a separate step | Reports, departments, approvals go to a named successor next day |
| Rules tied to structure | None | Varies by vendor | Permissions, approvals, leave policies follow department and manager |
How it works
How to set up your org chart in Skailer
01Build the structure
Add legal entities, locations, divisions, and departments. Nest departments under parent departments and assign each a manager.02Define roles and change reasons
Create job profiles with role, level, track, grade, and salary range. Then set the list of reasons HR picks from when a position changes.03Place people in it
Create employees by hand or hire them from Recruiting. Give each a position: job profile, manager, department, division, location. Add teams and team leads where work cuts across departments.04Keep it current through records
Transfers, promotions, and terminations become dated records. The chart updates on the effective date, every change keeps its reason, and a leaver's team moves to the named successor.Questions about the org chart in Skailer
What is the org chart in Skailer?
It's a live view of your company structure built from employee records. It shows departments, divisions, locations, legal entities, managers, and teams, and updates when a position record takes effect.