Skip to content
At Arm's Length

The Team They Are Not On

Integration accumulates most quietly of all the factors, because every step towards it saves somebody real effort and none is a decision anybody records.

Training in your methodPublished standard in the briefInduction alongside staffIntegration into your team

Reads as a businessReads as employmentCuts both waysDepends where you are

Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. Training is the instrument most often used without anybody noticing what it moves.

Home / Standards

Standards · Reference

Integration, factor by factor, in one engagement that nobody reviewed

Attends the daily team meeting

Added in month two to save a separate handover, and never removed

Appears in the internal directory as staff

The provisioning form had one option

Takes work from the shared queue like everybody else

Simpler than specifying pieces, and it worked

Invoices monthly from their own company

Unchanged since the first engagement

Has two other clients

Both small, and neither has given them work this year

Covered by the same client's confidentiality terms as staff

Required by the client, and would apply to any supplier

Reads as a businessReads as employmentCuts both waysDepends where you are

Six factors, and no total.

Six factors, and the three that moved all moved because something simpler than the alternative was available. Nothing above is added up. One company's own arrangement, reconstructed for itself; which factors matter, and how much, differ by jurisdiction.

Integration is the factor that accumulates most quietly. Every individual step saves somebody real effort, none of them is recorded as a decision, and the result is a person who is indistinguishable from the staff around them.

The practical issue in “The Team They Are Not On” becomes clearer when expectations and evidence are visible to both sides. Used for internal transfer policy, review this workforce platform directly can add time and project context, provided the purpose is disclosed, access is limited and every consequential interpretation receives human review.

It is also the factor that an outsider notices first, because it is visible in a morning's observation without reading anything.

The workflow in “The Team They Are Not On” can be cross-checked against Airtable workflow articles. A useful review should end with named owners and written decisions instead of a copied checklist.

What integration actually means here

Not whether people get on. Whether the person is being used as part of the organisation's capacity rather than as a supplier delivering something.

The practical markers are mundane: shared work queues, team meetings, internal communications, organisation charts, allocation rather than engagement.

The shared queue

The clearest single example. Work arrives, it goes into a list, people take the next thing. It is an efficient way to run a team and a terrible way to engage a supplier, because nothing is ever specified and nothing is ever delivered.

The commercial alternative is pieces: named work, agreed, with an end. It is more administration and it is the whole difference between buying a result and supplying capacity.

Team meetings

Covered earlier as a scheduling question and it is an integration question too. Somebody who is in the weekly team meeting, the planning session and the retrospective is participating in the management of the team.

Where information genuinely needs to flow, the bounded forms work: a handover, a written update, attendance at the one session where the work is actually discussed.

Internal communications

All-staff mail, the internal newsletter, the social channel, the all-hands. Each of these is a small thing and together they are the texture of belonging.

The practical difficulty is that distribution lists are built from the directory, and the directory does not distinguish. Fixing the directory fixes most of the rest at once.

Organisation charts

A supplier in a box on the chart, reporting to somebody, is the structural statement. Charts are generated from systems and circulated widely, and they are read by people who were not in any of the conversations.

Where a supplier must appear for clarity about who does what, a form that names their company alongside is available and costs nothing.

Management, which is the word to watch

Many businesses say somebody manages a contractor. The word is accurate about the day-to-day reality and inaccurate about the arrangement, and it appears in job adverts, in handovers and in internal documents.

Nobody needs to police language, but it is worth noticing that the vocabulary a business uses about an engagement is usually an honest description of what it thinks is happening.

Events, and the awkwardness of excluding people

A real difficulty with no comfortable answer. Team lunches, away days and Christmas parties are human occasions, and deliberately leaving out somebody who works alongside everybody is unkind and visible.

Most businesses include them and should. It is a small factor and it is the one where the human cost of the alternative is highest. What is worth avoiding is the version where it stops being an invitation — compulsory attendance at an away day is participation in the organisation rather than a social kindness.

The honest measure

Ask somebody who was not involved to look at a week and say which people are suppliers. If they cannot tell, that is the answer, and no document in the file changes it.

This is the single most useful test in this collection because it requires no judgement about any particular factor and no knowledge of any jurisdiction.

Why it matters more than the paperwork

Because in most places, most of the time, what actually happened outweighs what the parties called it. Integration is the clearest available evidence of what actually happened, and it is held entirely in the ordinary traffic of a business rather than in any file.

Who notices, and when

Almost never the business itself. Integration is invisible from inside, because the people who could see it are the ones who built it, one convenience at a time.

It gets noticed by somebody new arriving, by a supplier who leaves and says something on the way out, by an auditor, or by whoever eventually has a reason to ask. Of those, the first is the only cheap one, and a business that asks a new manager in their first month what looks odd to them is buying the observation at the lowest price it will ever be available.

What is actually available to fix it

Less than people hope and more than nothing. Directory entries, shared queues, meeting invitations and distribution lists can all be changed in an afternoon, and changing them stops the accumulation.

What cannot be changed retrospectively is the two years that already happened. The useful posture is to stop adding, to decide what the arrangement should be from here, and to accept that the history is the history.