Onboarding a Contractor for a Six-Week Engagement

A short engagement changes the economics of onboarding completely. For a permanent hire, a slow first fortnight is an investment. For a six-week contractor it is a line item, and it is usually paid without anyone noticing it was optional.

"Week one of six is spent finding out who to ask."

Week one is seventeen percent

Six weeks is thirty working days. A week of orientation is five of them, and on most engagements at least two of those go on access: accounts, permissions, a repository they cannot clone, an environment variable nobody has documented.

Access delays are the purest waste in the whole arrangement, because they are entirely predictable and require no domain knowledge to prevent. Whatever else you do, start the access requests a week before the contractor's first day.

Why contractors ask less

An employee who asks a lot of questions in week one is learning. A contractor who does the same worries about looking as though they were the wrong hire, and there is a commercial relationship in the background that makes that worry rational.

So contractors under-ask even more than new employees do, and they compensate by guessing or by working around things rather than resolving them. On a six-week engagement that produces work that fits the codebase poorly and needs unpicking after they leave.

Two counters. Say explicitly, on day one, that questions are expected and that the clock is yours rather than theirs. And give them a route that has no social cost attached, which matters more here than anywhere else.

Day one checklist

• All access working before they arrive. Repository, environment, board, channels, any third-party accounts. Tested, not requested.
• One named contact, with two protected slots a week. Not the team collectively, which produces nobody.
• A written statement of the outcome. What done looks like at week six, in one paragraph, agreed with them on day one.
• The decision boundary. What they can decide, what needs sign-off, and from whom. Write it down; contractors are the group most often left guessing about this.
• A first small task for day two. Something shippable, so the whole pipeline is exercised while there is still time to fix it.

Scope for the time available

The most common failure on a short engagement is not onboarding at all, it is scope. Work that requires deep familiarity with your domain is a poor fit for six weeks, however capable the contractor, because they will spend a third of the time acquiring context that leaves with them.

Better fits: well-specified implementation, a self-contained piece of infrastructure, a migration with clear boundaries, or an audit where the outsider perspective is itself the value. Worse fits: anything requiring negotiation with stakeholders they have not met, or work whose correct shape depends on knowing why five previous decisions were made.

Where the work does touch that history, the cheapest mitigation is making the reasoning retrievable rather than requiring a colleague to narrate it. If the team confirms a brief at the end of each day, the contractor can ask why an approach was chosen and get the answer from whoever chose it, with a source under it, without spending their named contact's slots on it. It never guesses, which matters more for someone who lacks the context to spot a wrong answer. See StandIn for the first 30 days.

Common Questions

How do you onboard a contractor quickly?

Have all access working before day one, name a single contact with protected time, write down the outcome and the decision boundary, and give them something shippable on day two. Access delays are the biggest avoidable cost.

How much onboarding is reasonable for a six-week engagement?

Two days, not a week. Beyond that you are spending a meaningful share of the contract on context that leaves when they do, which is an argument for scoping the work differently rather than onboarding faster.

Should contractors attend team meetings?

Only the ones that affect their work. Full inclusion is a nice gesture and an expensive one on a short engagement, and it is usually the meetings rather than the work that consume their first week.

What should a contractor hand over at the end?

The reasoning behind what they built, what they would do next, and anything they worked around rather than fixed. That last item is the one most often lost and the one that costs the team most after they leave.