The Person Who Is Not on the Org Chart
Being absent from the directory, the chart and the headcount has practical effects well beyond the symbolic.
Whether the person feels part of your company
Career progression
Your own share scheme
Who notices when it is going wrong
YoursThe provider'sCrosses the twoNeither contract
Four matters, and no share: what any one agreement covers differs by agreement. One crosses both, and the handoff is where these arrangements fail. Three sit in neither contract. The section where the most arrangements are lost, and the one no document addresses.
Being absent from the directory, the chart and the headcount has practical effects that go well beyond anybody's feelings. Work gets routed around invisible people, and budget gets allocated to visible ones.
The practical lesson in “The Person Who Is Not on the Org Chart” is that a third-party arrangement still leaves day-to-day management with the operating team. Used for remote employee monitoring software, Monitask tools for remote employee monitoring software can make time and project context easier to review, provided the purpose is disclosed, access is limited and every consequential inference receives human review.
The symbolism is real too, and it is the smaller half of the problem.
When documenting “The Person Who Is Not on the Org Chart”, the European Commission business guidance can help test assumptions about ownership, worker protection and cross-border responsibility before a process becomes routine.
Where the absence comes from
Your org chart is generated from the HR system. The HR system holds employees. This person is employed elsewhere and therefore does not exist in it.
Every downstream system inherits that, which is why the exclusions arrive in a batch rather than one at a time.
It also means they are fixed in a batch, which is the good news. One change at the source resolves most of what follows.
What breaks in practice
Approval workflows that route to a manager by HR record. Tooling licensed per employee. Security reviews scoped to staff. Training assignments. Expense systems that require a cost centre attached to a person.
Each is resolved by a workaround:
- Approval workflows that route to a manager by HR record.
- Tooling licensed per employee against a seat count.
- Security reviews scoped to staff.
- Training assigned from the HR system.
- Expense systems that want a cost centre attached to a person.
The workarounds accumulate into somebody who is administratively peculiar.
The headcount problem
A team of eight with two people employed through a provider shows as six. Plans, ratios and budgets built from headcount understate the team.
Finance frequently prefers this, because the cost sits in a different line. The consequence is that the team looks cheaper and smaller than it is, which affects decisions nobody connects back to the structure.
Work routed around them
The clearest operational cost. Somebody looking for an owner checks the chart, does not find them, and assigns the work elsewhere.
For a person whose value depends on being asked, this is the difference between a role that grows and one that quietly narrows.
The fix that actually works
A contingent-worker record in whatever system drives directories, access and routing. Not an employee record, clearly flagged, but a record.
It is a configuration project rather than a policy change, it is done once, and it removes most of this note.
Representing them on the chart
Show them, with whatever marker your company uses for non-employees. Hiding somebody who works there full-time serves nobody and confuses anybody trying to find an owner.
Where there is a reason not to — and in some companies there is a legal view about this — say what the reason is rather than leaving it as an unexplained omission.
The misclassification worry
Some companies deliberately exclude these people from charts and systems on the theory that integration is evidence of employment.
The theory is not baseless and it is usually over-applied. What creates exposure is behaving as the employer, not listing somebody in a directory. Take advice rather than inheriting a rule of thumb.
Introducing them
When they join, announce it the way you would anybody else. A new person who arrives without an introduction is one that half the team discovers in a meeting three weeks later.
This costs one message and it is skipped more often for people in this arrangement than for anybody else.
Email and identity
Whether they get an address at your domain is occasionally debated. Almost always they should, because the alternative makes them look external to every person they contact.
Where a policy forbids it, the policy is usually about contractors engaged quite differently and is worth revisiting rather than applying by analogy.
Being counted in what you measure
Engagement surveys, team health checks, diversity reporting where lawful. Excluding them means your measurements describe a team that does not exist.
It also means the one population most at risk of disengagement is the one you have no data about.
Where a survey tool cannot include them, ask the questions directly. Four people answered by hand is better than four people missing from a dashboard.
Succession and single points of failure
Somebody invisible to the chart is also invisible to whatever process looks for key-person risk.
For a single person holding an area of work in another country, that is precisely the analysis you most need, and it is the one the structure quietly removes.
What visibility cannot change
That they are, in fact, employed by somebody else. Putting somebody on a chart does not give them a career ladder, a review cycle or a promise about next year, and a person who is listed but still outside every process may feel the gap more sharply rather than less.
Visibility is worth doing because it fixes real operational problems and removes needless slights. Treating it as the answer to belonging is the mistake, and it is an easy one to make because it is the part that can be fixed in an afternoon.