Most contractors waste their first month. Not because they are bad at their job, but because nobody set them up to be good at it. They sit in meetings they do not understand, wait for access that never comes, and produce their first useful work sometime around week five.
Onboarding a contractor means giving them everything they need to do useful work in their first week. Access, context, people, and a clear first task. It is a checklist, not a vibe, and it takes about two hours of your time to get right.
Why do contractors take so long to become useful?
Because they are missing the invisible stuff. Not the brief, the context around the brief. Who the client really is, what has already been tried, which stakeholder is difficult, what done looks like here.
Employees absorb this over months. Contractors do not have months. Every day they spend confused is a day you are paying for, so the economics of onboarding a contractor are brutal. A slow start does not just delay the work, it burns the budget. I have seen this dynamic from both sides, and I wrote about the briefing half of it in how to brief a contractor for a brand project.
What should be ready before day one?
Access to everything, granted in advance. Email, chat, project tools, file storage, client systems. All of it, working, before they start.
This sounds obvious and almost never happens. The contractor arrives, and someone says IT needs three days to set up the accounts. Those three days are the most expensive of the engagement, because first impressions cut both ways. The contractor is forming a view of how your team operates, and right now the view is that nobody was ready for them.
What context do they actually need?
Three documents: the brief, the recent history, and the people map. The brief says what you are making. The recent history says what has already happened. The people map says who decides what.
The people map matters most and gets written least. A contractor who does not know who approves things will either ask everyone, which is slow, or guess, which is dangerous. Write down the names. It takes ten minutes and saves ten days.
What should their first week look like?
One small, real task that ships by Friday. Not reading. Not shadowing. A piece of actual work with a clear definition of done.
This does two things. It forces you to have the access and context ready, because the task cannot happen without them. And it gives the contractor a win in week one, which changes the entire dynamic. They stop being the new person who is still settling in and start being a contributor. Pair this with a proper brief and the difference is night and day. There is more on the delivery side of starting well in the first 30 days what I do when I join.
What is the biggest onboarding mistake?
Treating the contractor like a guest instead of a team member. Guests get shown around and left alone. Team members get put to work.
Invite them to the meetings that matter, including the awkward ones. Give them the client context, including the political bits. The instinct to protect contractors from the messy reality just means they make decisions without it, and then you get to explain the mess anyway, except now it is attached to rework.
Working with Avy
When I join a team, I run my own version of this checklist in reverse. I ask for the access, the history, and the people map in my first conversation, because I know the engagement lives or dies on how fast I become useful.
If you are about to bring in a contractor, or a fractional lead, send them this article before day one. Or book a call and I will walk you through the checklist for your specific situation. The first week is too expensive to waste.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.