The Relationship With No Document
The working relationship you have with this person every day is recorded nowhere and governed by nothing.
Day-to-day direction
Any employment obligation to the person
Promising the person anything about their job
Being the person's employer
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. One sits in neither contract. The line that is not there, and the one people keep acting as though were.
The working relationship you have with this person every day is recorded nowhere. No document describes it, no clause governs it, and nobody signed anything about it.
The practical lesson in “The Relationship With No Document” is that a third-party arrangement still leaves day-to-day management with the operating team. Used for employment of relatives policy, open the corresponding product resource can make time and project context easier to review, provided the purpose is disclosed, access is limited and every consequential inference receives human review.
That is unusual enough to be worth sitting with, because almost every other working relationship in your company has paper behind it.
For a separate perspective on “The Relationship With No Document”, consult the Velocity Global employment resources. Compare it with the actual contract, country and operating process rather than using a general resource as a local conclusion.
What ordinarily fills this space
For an employee, an employment contract, a job description, a handbook and a performance framework. For a supplier, a statement of work and a specification.
Here, none of it. The person has a contract with somebody else and a job description that may bear little relation to what you actually ask for.
Why it functions anyway
Because most working relationships run on expectation rather than on documents, and the documents are only consulted when something breaks.
For long stretches this arrangement is indistinguishable from managing an employee. The difference appears at precisely the moments the documents would have been read.
The first thing the absence costs
Nothing specifies what you may ask of this person. Their contract says what job they hold; it does not say that they report to you, or that you set their priorities, or what hours you may expect.
Everyone proceeds as though those things are settled. They are settled by custom, which holds right up until somebody disagrees.
Custom also varies by manager. A person on their second manager in this arrangement frequently finds the unwritten rules have changed without anybody saying so.
The second thing it costs
No record of what was agreed between you. A conversation about working patterns, about an expense, about what happens when a project ends, lives in somebody's memory and in nobody's file.
Two years later the people who had the conversation have both moved on and the person is holding an expectation nobody else can see.
The document worth writing anyway
A short working-arrangement note between you and the person: who they report to, what the role actually involves, working pattern, equipment, expenses, and who to ask about what.
One page, no legal effect, signed by nobody:
- Who they report to, and who covers when that person is away.
- What the role actually involves, as against the contract description.
- Working pattern, and the hours you will contact them in.
- Equipment you are providing, and expenses you will meet.
- Who to ask about work, about employment, and about a problem.
Its value is that it exists and can be pointed at, which is most of what documents do in practice.
What that note must not do
Create obligations about employment. Pay, notice, leave, title, promotion and termination belong in a contract you are not party to, and a note of yours promising any of them is a promise you cannot keep.
Keeping the note strictly to the work is what makes it safe to write.
Keeping a record of changes
When the role changes materially, write it down and send it. Where the change affects the employment contract, say so and route it to the provider.
The discipline costs five minutes per change and is the single cheapest protection available in this arrangement.
The job description problem
The provider needs a job description for the employment contract. It is written once, at hiring, and never updated.
Eighteen months later the person is doing something quite different. In several countries that matters, because a material change to the job requires agreement. Keeping the contract description roughly current is worth doing deliberately.
Why managers find this uncomfortable
Because every instinct says that somebody you work with daily, assign work to and review should have a document connecting them to you.
The instinct is sound and the arrangement does not satisfy it. Naming that openly is better than acting as though the document exists.
Where the absence is actually helpful
A relationship that runs on explicit agreement rather than on inherited policy can be clearer than an employment relationship. Nobody can appeal to a handbook neither of you has read.
Buyers who write the working-arrangement note find they have described the job more precisely than they ever did for their own staff.
The handover risk
When you leave or change roles, everything undocumented goes with you. Your successor inherits a person, a provider and no account of what was agreed with either.
That is the strongest practical argument for writing things down, and it applies regardless of how the arrangement is structured.
What no note can create
A relationship the law recognises. Writing down that this person reports to you does not make you their employer, and it does not give you the authority that would come with being one.
Several buyers reach for documentation hoping it will close the gap. It will not, and a note that tries to will be read against you if the question of who the real employer is ever arises. The note is for clarity between two people, and that is the whole of what it can be for.