Induction, and What It Says
Running a contractor through the process designed for new employees is the commonest way a business tells itself and everybody else it has taken somebody on.
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.
Running a contractor through the process designed for new employees is the single most common way a business tells itself, and everybody else, that it has taken somebody on.
The practical issue in “Induction, and What It Says” becomes clearer when expectations and evidence are visible to both sides. Used for gdpr employee monitoring, a structured way to review gdpr employee monitoring can add time and project context, provided the purpose is disclosed, access is limited and every consequential interpretation receives human review.
It happens because the process exists, it is the only one anybody has, and the person who runs it is not thinking about arrangements at all.
The workflow in “Induction, and What It Says” can be cross-checked against Teamwork client-work resources. A useful review should end with named owners and written decisions instead of a copied checklist.
What induction is designed to do
Turn somebody into a member of the organisation. That is its explicit purpose and it does it well: the values session, the introductions, the handbook, the team lunch, the mentor, the thirty-day check-in.
Every one of those is about belonging rather than about a piece of work, and belonging is precisely what distinguishes an employee.
What a supplier actually needs on day one
A much shorter list, and all of it about the job:
- Access to whatever the work requires, scoped and dated.
- The material: specification, standards, context, examples.
- Who to ask about what, with names and a route.
- Site rules where they apply, particularly safety ones.
- How and when to invoice, and who approves it.
Half an hour, usually, and it can be a document rather than a session.
The handbook problem
Staff handbooks describe conduct, grievance routes, disciplinary procedures, leave entitlement and performance management. Issuing one to a supplier, and particularly asking them to sign that they have read and accepted it, is an odd document to have in a file.
Where some of its contents genuinely apply — site safety, information handling — extract those into a short document for suppliers. That takes an afternoon once and solves it permanently.
The welcome email
Small and surprisingly consequential. A message to the whole department saying somebody has joined the team, with a photograph and a note about their background, is a statement.
Nobody means anything by it. It is simply the template that exists, and the alternative — a note saying which supplier is doing what, and who is managing it — takes the same effort and says something accurate.
Buddies, mentors and probation
Each of these is an employment instrument wearing ordinary clothes. A buddy assigned to help somebody settle in. A mentor for their development. A thirty-day or ninety-day review of how they are getting on.
The commercial equivalents exist: a named contact for questions, nothing at all for development, and a first small piece of work treated as the test of whether this is going to work.
The badge that says the same as everybody else's
Building passes, email addresses, directory entries and name badges are usually produced by a single process with a single output.
Where a visible distinction is available at no cost — a different badge colour, a directory entry that says the supplier's company — it is worth taking, not as a gesture but because it keeps your own systems describing the arrangement accurately.
Who runs it
Almost always the people team, because induction is theirs. That is the root of the problem and also the easiest point to fix.
A one-page internal note — when somebody is engaged as a supplier, this is the process instead — removes most of what this article is about, and it is the kind of thing that no one gets round to writing until after it has caused trouble.
What to do about somebody already inducted
Nothing retrospective, and nothing dramatic. Removing a person from a mailing list two years in is a gesture with no substance and it looks exactly like what it is.
The useful work is at the other end: fix the process so the next engagement starts correctly, and look at whether the arrangement as it now stands is one you would describe the same way you did at the beginning.
The first-day calendar
A small artefact that carries the whole article. New employees get a schedule: introductions at ten, systems at eleven, lunch with the team, a session on the values at two.
A supplier starting work needs access and the material, and can begin. Where somebody has built a first-day calendar for a contractor, they have not done anything wrong; they have used the only template available, and the template describes a different arrangement.
The signal this sends internally
Worth naming, because it is the reason the detail matters. How a business inducts somebody tells its own staff what that person is.
A supplier who went through the full employee induction is treated by everybody in the building as a colleague, which means every manager who deals with them will reach for the instruments they use on colleagues. The induction is not just evidence of the drift; it is one of the things that causes it.