Skip to content

Workli

First Week With a New Freelancer: A Day-by-Day Onboarding List

You've hired someone good. Now the clock is running, and the most common way to waste their first week is to leave them waiting: for access, for files, for an answer to "where do I start?"

Below is the onboarding plan I use, split by day. It assumes a small team or a solo founder hiring one freelancer for a project of a few weeks or more. Shrink it for smaller jobs.

Before day one

Do these before the start date. They cost you an hour and save the freelancer a day.

  1. Send a short welcome message with the start date, main contact and preferred channel.
  2. Create accounts or invites for every tool they'll need: repo, design files, project board, staging server, analytics.
  3. Use individual logins, not a shared password. You'll thank yourself at the end.
  4. Write a one-page brief: goal, current state, first milestone, known problems.
  5. Gather existing material in one folder: brand files, past specs, screenshots, recordings.
  6. Block 45 minutes in your calendar for a kickoff call.

If any access needs approval from someone else, chase it now, not on Monday morning.

Day one: kickoff and access

The goal of day one is simple: the freelancer can open everything and knows what the first deliverable is.

  • Kickoff call (30–45 minutes):
  • Walk through the brief.
  • Confirm the first milestone and its date.
  • Agree on how and when updates happen.
  • Name the person who answers questions and the person who approves work.
  • Access check: ask them to log into each tool during or right after the call. Fix gaps the same day.
  • Questions list: invite them to keep a running list of questions and send it at the end of the day.

Don't expect output on day one. Expect a working setup and a sharper set of questions.

Days two and three: first small deliverable

Give them something small and real to finish early. It builds momentum and tests the working relationship on both sides.

Good first tasks:

  • A small bug fix or a single screen in a design.
  • A written review of the current state with recommendations.
  • A short spike or prototype on the riskiest part of the project.

During these days:

  1. Answer questions within the response time you agreed.
  2. Review the first deliverable quickly, ideally within a day.
  3. Give specific feedback: what works, what to change, what doesn't matter.
  4. Note any process friction (slow approvals, missing info) and fix it.

Days four and five: settle the rhythm

By now you'll know how this person works. Use the end of the week to lock in habits for the rest of the project.

  • Update format: a short written update works well. What was done, what's next, what's blocked.
  • Review cadence: decide when you'll look at work, so they're not waiting on random check-ins.
  • Decision log: start a simple document listing decisions and who made them.
  • Milestone check: is the first milestone still on track? Adjust now if it isn't.
  • Feedback both ways: ask what's slowing them down. Freelancers who work with many clients often spot process problems fast.

A short end-of-week checklist

Tick these off on Friday:


  • Freelancer has every access they need, and nothing they don't.

  • First small deliverable is reviewed and accepted (or revised).

  • Next milestone and date are confirmed in writing.

  • Update and review rhythm is agreed.

  • Payment terms for the first milestone are clear: amount, method, due date.

  • Both of you know who to contact if something goes wrong.

On payment: if you met through a marketplace, check whether it handles payments at all. Some do; others, like the one at https://workli.tech/, leave payment to the client and freelancer directly, so the terms you wrote down are what everyone works to.

Common onboarding mistakes.

A few that come up again and again:

  • Sharing one admin login with everyone.
  • Handing over a huge backlog instead of a single first task.
  • Going silent for days after the kickoff.
  • Changing the scope during week one before the freelancer has finished anything.
  • Treating the freelancer as an outsider who doesn't need context.

A good first week doesn't need to be elaborate. Clear access, one small win, and a settled rhythm are enough. Get those three right and the rest of the project usually runs on its own.

Writer

Workli

@workli

Working checklists for hiring freelancers, agreeing milestones and closing contracts cleanly.

Comments 0

Replies to this note, oldest first.

No replies yet. Found it useful? Say so below.

Write a reply

A moderator reads each reply before it goes up. A name will do; there is nothing to sign up for.

Plain text, up to 2,000 characters.

More from Workli