Belonging, Which Nobody Owns
Whether the person feels part of your company appears in no document, and is the commonest reason these end.
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.
The things that make somebody feel part of a company, and which document carries each one
YouThe providerNeither contractBeing paid correctly and on time
Necessary, entirely administered by the provider, and worth nothing on its own
Knowing what the company is doing and why it matters
Context, which costs nothing and is withheld by accident more than by intent
Appearing in the directory, the chart and the team page
In no document, assigned to nobody, and traceable to a system populated from the HR record
Being considered for a bigger role
A decision you make and a contract somebody else issues
Across the handoff: A decision from you, an amendment drafted by the provider, and the person's agreement
Being invited to the things everybody else is invited to
Entirely within your gift, costs nothing, and is the single most neglected item here
Having somebody whose job it is to notice they are unhappy
Named nowhere; the provider cannot see it and your own people processes do not cover them
YoursThe provider'sCrosses the twoNeither contract
Six matters drawn · no share
Six things, and the two that are nobody's are the two people actually leave over. One buyer's own account of why its first hire resigned; what any arrangement provides differs by buyer rather than by provider.
Whether this person feels part of your company appears in no document. Your agreement does not mention it, their contract does not mention it, and no clause could.
The management gap in “Belonging, Which Nobody Owns” becomes harder when distributed work is visible only through anecdotes. A team considering see the Monitask product page for how to monitor employees without being intrusive can add transparent time and project context, but performance conclusions should still combine agreed outcomes, direct conversation and a documented opportunity to correct the record.
It is also the commonest reason these arrangements end, which makes the absence worth more attention than the contracts get.
A broader benchmark for “Belonging, Which Nobody Owns” is the U.S. Department of Labor work-hours resources. Read it alongside the service agreement and employment facts so that general guidance informs, rather than replaces, case-specific judgement.
Why it defaults to nobody
The provider cannot see it. They never observe the person working, do not know your company, and are not paid to have a view.
Your own people processes cover employees, and this person is not in them. So the matter falls between two organisations, each reasonably assuming the other has it.
How it shows up
Not as a complaint. As a resignation at month nine, framed politely as a better offer, with a reason given that is true but not the whole reason.
By the time it is visible it has usually been developing for a quarter, which is the argument for asking rather than waiting.
The mechanical exclusions
Missing from the directory. Not on the org chart. Absent from the all-hands invite list. Excluded from the engagement survey. Not in the training catalogue. Skipped by the recognition scheme.
Each is traceable to a system populated from the HR record, and the person has no HR record:
- Missing from the directory.
- Not on the org chart.
- Absent from the all-hands invite list.
- Excluded from the engagement survey.
- Not in the training catalogue.
- Skipped by the recognition scheme.
None of it is deliberate and all of it is noticed.
Fixing the systems once
Create a record for contingent workers in whatever systems drive access, lists and invitations. Then add this person to it.
It is an afternoon of work, it is done once, and it removes most of the exclusions permanently. Most companies do it after losing somebody.
The work is in deciding which systems need the record rather than in creating it. Access, mailing lists, the directory and the invitation tooling cover most of what the person actually notices.
What costs nothing
An introduction when they join. A place in the team page. Context about what the company is doing. Being asked their view. Being thanked in public.
All of it is yours, unconstrained, and none of it needs anybody's permission. The structure removes nothing here except the default.
The onboarding gap
The provider onboards them as an employee: contract, payroll, local formalities. You onboard them as a worker: systems, access, the work.
Nobody onboards them into the company. Writing a thirty-day plan that covers who to meet, what to read and what the company actually does is the single highest-return hour in this whole arrangement.
Naming the structure out loud
Telling the person plainly how the arrangement works — who employs them, why, what it means and what it does not — is better than letting them infer it.
People cope well with an unusual structure explained once. They cope badly with discovering it piece by piece from things that do not apply to them.
Asking directly
Every few months: how does working with us actually feel from where you sit, and is there anything that keeps reminding you that you are set up differently.
The second question is the one that produces answers. People will rarely volunteer this and will usually answer it if asked.
The manager is the whole of it
For somebody with no HR relationship, no internal network and no career apparatus, the relationship with their manager is not part of the experience. It is the experience.
That is a heavy load on one person and worth saying to them, because most managers do not realise how much of it rests on them here.
The small recurring reminders
A form that will not accept them. A benefit page that does not apply. A survey that excludes them. A mandatory training module they cannot be enrolled in.
Individually trivial and cumulatively the whole problem. Keep a note of each one as it surfaces and fix them in batches, because the person will stop reporting them if nothing happens.
Being honest about the limits
Some things genuinely are different: the benefits are constructed differently, the review cycle does not apply, the equity probably does not work. Pretending otherwise fails on contact.
Saying what is different, why, and what you are doing instead is both more respectful and more durable than an inclusive story the person can disprove.
What nothing here can supply
A reason to stay that does not depend on individuals. For an employee, some of the attachment is to the institution: the career, the colleagues, the sense of a place with a future in it for them.
Somebody employed through a provider has a contract with a company they do not work for and a relationship with a company that has not hired them. What holds them is the work, and the people, and whether they can see something ahead. All three have to be built deliberately by you, and none of them are things a contract was ever going to provide.