Onboarding a new starter to client work in their first week

A first-week onboarding plan for agency new starters: what to set up before day one, how to hand over client context, and when to let them run a job.

Gareth Thurlow 9 min read

The saved views menu, open under “Viewing: My critical jobs (edited)” with an Update button beside it. It lists My views (My critical jobs, Due this week, shared) and views Shared with project by Leo Ortiz and Priya Shah, options to rename, share or delete the view on screen, and “Save current view…”.

A new starter at an agency usually spends their first week asking where things are. Which client is this for, what did they already say no to, where is the latest file, and who decides?

Most of those answers exist somewhere. They are in a lead's head, an old email thread or a call nobody wrote up. This article is a first-week onboarding plan for client work: what to set up before day one, how to hand over context without a week of meetings, and when to let a new starter run a job on their own.

Why agency onboarding is harder than it looks#

Onboarding at an agency is not just learning the tools. A new designer or account manager has to learn several clients at once, each with its own history, preferences and approver. The tools are the easy part.

The context is what slows people down. A job title like "Homepage hero" tells a new starter nothing about the two rounds the client rejected, the colour they asked for on a call, or the fact that only one person on the client side can say yes. If that history lives in people's heads, the only way to pass it on is to talk, and the people with the history are usually the busiest.

So the aim of the first week is simple: move the new starter from asking for context to reading it, and from reading it to adding to it.

Before day one: set up the place, not just the login#

A login on its own gives someone an empty screen. Spend half an hour the week before they start so the screen has something to say.

  1. Invite them as a team member, to the right projects. An invitation lasts 7 days, with one reminder after 3 days, so send it close to their start date. Add them only to the projects they will work on first. They can join more later, and a short sidebar is easier to learn.
  2. Pick their first two or three jobs. Choose real work that is under way, not a practice task. Add them to each job, so they hear about it, and assign one small job to them outright.
  3. Write a short note on each of those jobs. One comment that says what the job is, where it stands and what to watch out for. This is the single most useful thing you can do.
  4. Check the brief is on the job. If the brief is in an email, paste it into the job's description. A creative brief your team can start from covers what a good one includes.
  5. Make sure the project has shared views. A view such as "Due this week" or "Client review" saves a new starter from building filters on day one.

Day one: let the app teach the app#

You don't need to demo the basics. Skybase gives each person a getting-started checklist for their role, and a team member's has six steps: explore the sample project, add a job with a due date and priority, try the table view, plan in the calendar, save a view and open Reports. If your workspace no longer has the sample project, the first step asks them to open a project instead.

The Help menu has the rest. Take a tour runs short guided tours of the inbox, the board, the table, the calendar and a job in detail. Getting started reopens the checklist if they closed it, and Keyboard shortcuts lists the keys.

Give them the morning for this. Then spend your time on the part the app can't teach: the clients.

Day two: read the history before asking about it#

This is where the work you did before day one pays off. Ask the new starter to open each of their jobs and read it top to bottom before they ask anyone anything.

A job in Skybase keeps its context in one place:

  • Details holds the description, which should hold the brief, plus the job's dates, priority and type.
  • Tasks shows the steps inside the job, each with its owner and due date, and how many are done.
  • Files holds every file on the job, including what is waiting for approval.
  • The thread holds the comments, and its Activity filter shows what changed and who changed it: moves between columns, priority changes, files approved or rejected, and what automations did.

Reading the thread with All selected gives the whole story in order: the conversation and the changes around it. Twenty minutes per job is usually enough to answer most first-week questions.

The Logo lockups, final round job showing its labels (none yet, so Add label), priority, due date, members, the Details, Tasks, Files and Notes tabs, and a checklist of five tasks, three complete. A fourth task is ticked and the progress bar moves to four of five. Beside the tabs is the comments panel with a comment from the client, Tom.

Encourage them to keep their own questions in Notes. Notes on a job are private to the person who writes them, so a new starter can jot down "Why did the client reject round two?" without posting it to the team. At the end of the day, the questions that are still open become one comment or one conversation, not twenty.

Day three: shape the inbox so it doesn't shout#

By midweek a new starter is on several jobs, and the notifications start to arrive. This is the point where people either learn to triage or learn to ignore everything.

Show them the inbox's filters. Assigned to me and Mentions are the two that need an answer. Due soon is the one to read each morning. Anything else can wait, be snoozed until tomorrow or be marked read.

Then let them set their own email: instant, or an hourly, daily or weekly digest, with quiet hours if they want them. The morning roundup at 09:00 covers what is overdue, due today and coming up, and it is on by default for people with email notifications on. For someone new, that one email is often the most useful message of the day. An inbox your team can triage in ten minutes goes through the rest.

Day four: give them views, not instructions#

Instead of explaining how you filter the board, give the new starter the filters already saved.

A saved view keeps a set of filters and a layout: the board, the table or the calendar. A view shared with the project shows up for everyone on it, and "me" in a shared view means whoever opens it. So one "My week" view, made once, works for every new starter after this one.

Three views are worth having before anyone new joins a project:

  • My week: jobs assigned to me, due this week.
  • Overdue: every job past its due day, with completed jobs hidden.
  • Needs a date: jobs with no due date, so nothing waits unplanned.

To save one, filter the board or table, then open Views and choose Save current view…. Saved views: the small habit that keeps a team focused covers when to share a view and how to keep the list short.

The saved views menu, open under “Viewing: My critical jobs (edited)” with an Update button beside it. It lists My views (My critical jobs, Due this week, shared) and views Shared with project by Leo Ortiz and Priya Shah, options to rename, share or delete the view on screen, and “Save current view…”.

Day five: hand over one job completely#

By the end of the week, the new starter should own one job end to end. Pick something with a clear finish and a friendly client: a set of social formats, a landing page section, a copy edit.

"Own" means three things:

  1. They are the assignee, and the job's due date is theirs to keep.
  2. They write the next comment to the client, not you.
  3. They move the job to the next column when it is ready, and say so in the thread.

You stay on the job as a collaborator, so you see everything. The point is that the record of the job now has their name on it, and the next new starter will read their comments the way they read yours.

A worked example: Harbour Studio takes on a designer#

Take a small agency, say Harbour Studio, which is rebranding its client Northwind. This is a made-up example. Imagine Harbour has just hired a designer who starts on Monday.

The Friday before, Maya Chen, the studio lead, invites the new designer as a team member to the Northwind project only. She adds them to two jobs. On "Homepage hero", Priya Shah's hero-direction-b.png is waiting for approval from Tom Becker, Northwind's client contact. On "Brand guidelines v3", Tom has asked for a darker navy.

Maya leaves a comment on each. On the guidelines job it says: "Tom asked for a darker navy on the call on Wednesday. Leo has added Deep Harbour (#0B2545) to the palette. Tom is the only person at Northwind who signs off, and he reviews on Thursdays."

She also assigns the new designer one small job of their own, "Social launch kit", which is still sitting in Unscheduled on the calendar. Part of their week is giving it a date.

On Monday the designer works through the checklist and the tours. On Tuesday they read both jobs, keep their questions in Notes and end up with two left: which file formats Tom prefers, and whether the social kit uses the new navy. Sam Okafor answers both in one comment.

By Friday the designer has dragged "Social launch kit" onto a day in the calendar, posted the first round, and moved the job to Client review. When the "Client review hand-off" automation reassigns the job and tells Tom, nobody had to explain it: the rule did what the board said it would.

A checklist for your next new starter#

  • Invited as a team member, to the first projects only.
  • Two or three real jobs, each with a handover comment.
  • The brief on each job, not in an inbox.
  • Shared views for "My week", "Overdue" and "Needs a date".
  • A morning for the checklist and tours.
  • A day to read job history, with questions kept in Notes.
  • One job of their own by Friday.

The getting started guide walks through the workspace itself, and the saved views guide shows how to build the views above.

Good onboarding at an agency is mostly good record-keeping. If every job carries its brief, its files and its decisions, a new starter can learn a client by reading, and their first week goes on the work.

Written by

Gareth Thurlow

Founder, Skybase

Gareth founded Skybase to give agencies and client teams one place for client work, from the brief to the sign-off.