Skip to content
EMPOBase
en

An onboarding checklist for new NGO staff

By the EMPOBase team · · 4 min read

Short answer

A good onboarding checklist covers three periods: before day one, the first week and the first 90 days. It names an owner for each task, such as HR, the line manager or IT. It includes contracts, access, safeguarding and code-of-conduct sign-off, a role briefing, and a probation review. Tick items off in one shared record so nothing is missed.

Key points

  • Split onboarding into before day one, week one and the first 90 days.
  • Give every task an owner: HR, the line manager, IT or finance.
  • Get the code of conduct and safeguarding declarations signed in week one.
  • Set the probation review date at the start, not when it is due.

Why onboarding needs a checklist

New staff form a view of an organization in the first days. If their laptop is not ready, nobody has explained the reporting line, and the code of conduct arrives three months late, they notice. A checklist is not paperwork for its own sake. It is how a busy team makes sure the same good start happens for every person, in every office.

What should happen before day one?

Most gaps appear here, because the offer is signed and the team relaxes.

  1. Contract and terms. Send the contract, job description and any country-specific documents. Check that the contract type and end date are right.
  2. Identity and right to work. Collect the documents your law requires, and note any expiry dates, such as a visa or work permit.
  3. Safeguarding checks. Complete the checks your policy requires before the person starts work.
  4. Equipment and access. IT prepares the account, email and equipment. Give access only to what the role needs.
  5. Welcome note. The line manager sends a short plan for the first week and names a buddy.

What should happen in week one?

  1. Welcome and introductions. Meet the team, the buddy and the key colleagues in finance, logistics and programs.
  2. Policies and sign-off. Walk through the code of conduct and the safeguarding and PSEA (protection from sexual exploitation and abuse) policy. Get the declarations signed. Add the data protection and security rules.
  3. Role briefing. Explain the job, the projects the person supports, the budget lines they may touch and the approval limits that apply to them.
  4. Emergency details. Record the emergency contact and, for field staff, the security briefing and communication tree.
  5. Set goals. Agree two or three goals for the first 90 days in writing.

What should happen in the first 90 days?

WhenTaskOwner
Day 30Check-in on workload, questions and early concernsLine manager
Day 30Required training startedHR
Day 60Review progress against the three goalsLine manager
Day 90Probation review, or earlier if the contract sets a shorter periodLine manager and HR
End of probationWritten decision: confirm, extend or endHR and line manager

Set these dates when the person starts. A review that is not in the calendar tends to be missed, and a missed review can leave you without a clean record if there is a problem later.

Who owns each task?

Give every line a name. A checklist without owners is a wish list. The usual split:

  • HR: contract, documents, policies, records, probation dates.
  • Line manager: welcome, role briefing, goals, check-ins.
  • IT: accounts, equipment, access.
  • Finance: payroll set-up and expense rules, within your national law.

If the new person is also taking over from someone, link this list to the offboarding checklist so the handover is complete.

How do you keep the record?

Keep one onboarding record per person with the date each task was done and who did it. Review overdue items weekly in the first month. When the same task is late for several hires, fix the process, not the person.

Employment rules on probation, notice and documents differ by country. Check yours before you set the dates.

Common onboarding mistakes

Four mistakes appear again and again:

  • Treating week one as a pile of reading. People forget most of it. Spread policies across the first month, and put safeguarding and the code of conduct first.
  • Leaving the new person alone. A buddy who answers small questions, such as where the forms are, saves the manager many interruptions.
  • Skipping the budget and approval rules. A new officer who does not know the approval limits may either wait too long or act without approval. Explain the rules for their level in the first week.
  • Forgetting the manager. A first-time manager needs a short briefing on leave, reviews and conduct, too.

Ask each new starter, at 30 days, what was missing from their first weeks. Use the answers to improve the list for the next person. After two or three hires, the checklist usually settles into a form that fits your organization.

Where EMPOBase fits

EMPOBase has an Onboarding workflow in the People & HR module. Onboarding, probation-review and contract-decision events use the dates on the staff profile, so you review the checklist, owners and dates rather than build them each time. Signed PSEA and code-of-conduct declarations are kept as a renewable record with an expiry. Role changes are started by hand, and the checklists are only as good as the profile dates, so keep those current. See the platform overview.

Questions people ask

Who is responsible for onboarding?

The line manager owns the new person's experience, and HR owns the process and records. IT and finance own their own tasks. Name each owner on the checklist.

Should onboarding be different for field staff?

The core steps stay the same, but add local items: travel and security briefing, emergency contacts and site access. Do these before the person reaches the site.

How long should onboarding last?

Plan for the probation period, often three to six months, and check in formally at 30, 60 and 90 days. Your contract and local law set the actual probation length.