What an onboarding pack is for
New starters in marketing tend to learn the team's ways of working from whoever sits nearest. They pick up the naming convention from the last campaign they see, the approval route from the first person who signs something off and the location of the current logo from a colleague's desktop. Some of what they learn is wrong, and some of it is risky: a list exported without its suppression entries, a claim published without review, an ad live under an invented name that breaks every report it touches.
A pack fixes that by giving every joiner the same, current account of how the team works, at the moment they need it. It also saves the team time, because the questions every new person asks are answered once, in writing, rather than by interruption each time. And it exposes gaps: a rule nobody can find written down, an access request nobody knows how to make, a procedure that turns out not to exist.
It complements two existing pages rather than replacing them. The guide to hiring and developing marketers treats onboarding as a plan with an owner: access arranged before day one, the business and the plan in the first week, a small real piece of work and a buddy. A colleague asked to act as that buddy or coach can follow the tutorial on coaching a newer marketer before you manage, which keeps pay, probation and performance with the manager. The guide to a first digital marketing role covers the same weeks from the starter's side. The pack is the operations artefact both of them draw on. An experienced joiner who writes their own plan for those weeks, as the tutorial on planning your first months in a new marketing role describes, uses the pack as the source for its learning list.
| Part of onboarding | Who owns it | Where it is covered |
|---|---|---|
| Goals, reviews, introductions and a buddy | The hiring manager | The hiring guide |
| The starter's own learning and work log | The new starter | The first-role guide |
| Access, workflow, rules, procedures, first task | Operations, section by section | This tutorial |
| Bringing an agency into live accounts | The agency's client lead | Agency onboarding checklist |
| Bringing a new tool into the team | The tool's owner | Marketing tool onboarding SOP |
Before you start
- Have the access register. The tutorial on reviewing access to marketing tools builds a register of tools, owners, deputies and roles, with joiner triggers. The pack's access section is drawn from it.
- Have the workflow written down. The campaign workflow guide is the route the pack explains, including the fast lane for low-risk work.
- Have some procedures. The SOP tutorial writes them. The pack points to procedures; it does not contain them.
- Ask the last few joiners. What did they need and not find, what did they get wrong early on, and whom did they have to ask? Their answers are the best specification for the pack.
- Agree where it lives. The same shared space as the procedures and the work system, linked from the place new starters will look first. A pack sent as an attachment is out of date by the next joiner.
The steps
List the roles the pack must serve
List the roles that join the team, such as channel specialist, content writer, designer, campaign manager, regional marketer or contractor. Most of the pack is common to all of them, but access, procedures and first tasks differ by role, so the pack needs a common core and a short section per role. Include people who join for a while, such as contractors, interns and secondees, because they often get the least onboarding and the broadest access. Agencies coming into live accounts follow the agency onboarding checklist instead, though they may need the rules section too.
Write the access each role needs and who grants it
For each role, list the tools and accounts it needs, the role or permission level in each and who grants it, taken from the access register. Keep each to the narrowest role the work needs, as the access review tutorial recommends, and write when each should be requested so it is ready on the first day rather than in the third week. Give each person their own account; never hand a joiner a shared login. Note which access comes later, once the first weeks are done, so the newcomer is not given admin rights to accounts they will not use yet. Each grant itself then runs through the marketing tool access request SOP, which records it in the register with an end or review date. Each later access reviewA periodic check of who can use each marketing tool: every account matched to a current person, supplier or integration, with owners, deputies and narrow roles. checks that what a joiner was given still matches the work they do.
Explain how work reaches the team and where it lives
Describe the route work takes: where requests come in, how triage works, what a brief is and who signs it, how work moves through stages in the work system, which reviews it passes and what the launch check involves. Link the campaign workflow guide rather than restating it, and add only what is specific to your team: the name of the request form, the board or project where work lives, the meeting where triage happens. Say where things are kept, including the calendar, the asset library with its approved files and the shared folders, and where they are not kept, such as personal drives and chat threads.
Write the rules a newcomer can break on day one
List the rules a newcomer could break before anyone thinks to mention them, and keep the list short. Name campaigns and assets to the team's Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably., and build every UTMURL tags identifying traffic source. to it, as naming conventions and UTMs sets out. Send work for the reviews the approval matrix requires, which the approvals and compliance guide explains. Never send to a list that has not been checked against the suppression list: the UK regulator's direct marketing guidance describes honouring opt-outs, and as the suppression list entry and the data operations guide put it, opt-outs are kept on a suppression list rather than deleted and applied across every channel they cover. Link each rule to its owner's page and say what to do when unsure.
Choose the procedures to read, in order
From the team's procedure library, choose the few each role needs first, and put them in the order the newcomer will meet the work. A channel specialist might read how to set up a campaign in their channel, then how to add tracking, then the launch check. Mark which procedures they should read before their first task and which can wait. Link each procedure rather than copying it, so the pack never holds an out-of-date version. If a procedure the newcomer needs does not exist, note it as a gap and pass it to whoever owns the procedure library.
Pick a safe first task from low-risk work
Choose a first task that is real, small and low-risk, and that passes through the whole route: intake, the work system, review and the launch check. Work that qualifies for the fast lane the campaign workflow defines is usually right, such as a social post from approved assets or an email from an approved template. Avoid tasks involving new claims, personal data, live budget changes or a list nobody has checked. Have the newcomer run the campaign launch QA checklist on it with someone who has done it before, and record what was unclear.
List who to ask for what
Write a short directory by topic rather than by person: who to ask about access, about the brand, about an approval, about tracking, about a supplier, about the calendar. Name the role first and the current person second, so the list survives staff changes. Include people outside marketing the newcomer will need, such as the person who owns data protection and the web team's contact. Use a RACI matrix to set who owns each section of the pack itself, so every part has one accountable role responsible for keeping it accurate.
Test the pack with the next person who joins
Give the pack to the next joiner and ask them to note, as they go, anything missing, wrong, unclear or out of date. Do not explain it first; the test is whether it works without help, in the same spirit as the new-starter test the SOP tutorial applies to a procedure. Watch for the questions they still have to ask, because each one is a missing line. Check that their access arrived on time and at the right level. Review the notes with them once their first task is done.
Update it after every joiner and every process change
Make the corrections from each joiner's notes before the next one arrives. Then link the pack to the things it describes, so that when a rule, a tool, a procedure or the workflow changes, the owner of that change updates the pack too. Put a last-reviewed date on the pack and on each section. A pack that is updated only when someone notices it is wrong will be wrong for the joiner who notices it.
What goes in the pack
The pack works best as a short index page with links, one section per heading below, and a role section for each role. Most of its content lives elsewhere and is linked, so that the pack stays accurate as the things it describes change.
| Section | What it holds | Usually owned by |
|---|---|---|
| Welcome and how to use the pack | What it covers, what the manager's plan covers, who to ask | Operations |
| Access by role | Tools, role levels, who grants each and when to request | The access register's coordinator |
| How work flows | The request route, the work system, triage, reviews and launch check | The workflow owner |
| Where things live | Calendar, asset library, shared folders, procedures | Operations |
| Rules that matter on day one | Naming, approvals, suppression and consent, brand basics | The owner of each rule |
| Procedures to read, in order | Links by role, marked before or after the first task | The procedure owners |
| First task | A fast-lane task by role, with the launch check | The hiring manager with operations |
| Who to ask for what | A directory by topic, role first | Operations |
| Change log | What changed, when and after which joiner | Operations |
An accountancy firm's marketing team builds its pack (illustrative)
Plovarin Accountancy builds an onboarding pack
Plovarin Accountancy, an invented accountancy firm with 7 offices and a marketing team of 8, hired a new marketing executive. In her second week she sent the firm's tax-deadline newsletter to a list exported from the practice management system, which did not carry the email platform's suppression entries. 46 people who had unsubscribed received it, and several complained.
The marketing manager reported it to the partner who owned data protection, and the operations coordinator built an onboarding pack. She asked the last 3 joiners what they had needed. All 3 said the same things: they had not known how campaigns were named, who approved anything mentioning tax rules and that lists had to come from the email platform rather than from exports.
The pack had a common core and 3 role sections, for the marketing executive, the designer and the events coordinator. The rules section was 5 lines long: name campaigns to the convention, build links to the naming convention, send anything mentioning tax rules for technical review, send only to lists held in the email platform and checked against the suppression list, and ask the coordinator before using any export. The first task for the executive role was a scheduled social post from the approved asset library, checked against the launch checklist.
The next joiner, a designer, used the pack 2 months later. Her notes found 4 gaps, including a missing access request for the asset library, and the pack was corrected before the following joiner started. No list has been sent outside the email platform since.
Common mistakes
- Treating the pack as the manager's plan. Goals, reviews and introductions belong to the hiring manager. The pack is the reusable part operations keeps.
- Copying procedures into the pack. Copies go out of date. Link the procedures and keep the pack as an index.
- Access arranged after the starter arrives. Write when each access request should be made, so it is ready on day one.
- Broad access from the start. Give the narrowest role the work needs and add more later. Admin rights are not a welcome gift.
- A long rules section. Newcomers remember a handful of rules. Keep the list to the ones that cause real harm when broken.
- A risky first task. New claims, live budgets and personal data are not for the first week. Choose fast-lane work and pair it.
- Never testing it. The only test that counts is a new joiner using it without help.
- Updating it only when someone complains. Link it to what it describes and update it after every joiner and every change.
