A new employee should not have to discover the job through scattered messages, old documents and whoever happens to be available. Yet many onboarding plans focus on forms and introductions, then leave the person to “settle in”.
A useful first month answers four questions: What am I here to achieve? How does work move through this organisation? Who can help me? How will I know whether I am progressing? Build the plan around those answers and administration becomes one part of onboarding, not the whole experience.
Define the first-month destination
Before choosing activities, write three to five outcomes the employee should reach by day 30. These should be early indicators of readiness, not a compressed version of the annual performance plan.
For a customer-service employee, outcomes might include using core systems safely, resolving a set of common queries with support and knowing when to escalate. For a team leader, they might include meeting each direct report, understanding current commitments and proposing priorities for the next month.
Describe observable evidence for every outcome. “Understand the business” is too vague. “Can explain how a customer request moves from sales to delivery” gives the employee and manager something concrete to discuss.
Prepare before the start date
Send a concise welcome note confirming the start time, location or joining link, dress expectations, transport or parking details, contact person and what to bring. Avoid sending a thick pack of reading with no guidance about what matters.
Make sure access, equipment and the workspace are ready. Test logins rather than assuming an account has been created correctly. Tell reception, security and the immediate team when the person will arrive.
Prepare a written first-week schedule, a role summary and the employment information the employee should receive. Assign one person to own the plan. When ownership is unclear, the new hire spends the first days chasing basic answers.
Make day one feel navigable
The purpose of day one is orientation, safety and connection, not maximum information transfer. Start with the role’s purpose and the needs it serves. Then show how the team works, where essential information lives and whom to contact for urgent help.
Complete necessary administration in a calm, private setting. Explain policies in practical terms rather than asking the employee to acknowledge a folder they have not absorbed.
Introduce a small number of relevant people and explain why each relationship matters. A list of names is less useful than: “Nomsa approves customer refunds; speak to her before promising an exception.”
End the day with a short manager check-in. Ask what is clear, what remains confusing and whether any access problem could block the next morning.
Build week one around guided practice
Combine explanation, observation and practice. A useful sequence is: see a task done, discuss why it is done that way, try a low-risk version, receive feedback and repeat.
Give the employee real but controlled work as soon as reasonably possible. Completing a meaningful task creates context for later training and helps the manager see where support is needed.
Use a checklist, but do not confuse attendance with learning. Instead of recording that a system demonstration happened, confirm that the employee can complete a relevant action safely. Leave unscheduled time for questions and reflection; an hour-by-hour calendar for five days can become exhausting.
Increase ownership across weeks two to four
In week two, let the employee handle recurring tasks with a clear escalation route. In week three, add variation or a more complex case. By week four, ask the employee to complete an agreed piece of work with less supervision and explain their reasoning.
Keep the workload realistic. A new hire is learning terminology, relationships and unwritten rules at the same time as the technical work. Progress should be visible without manufacturing a test designed to catch them out.
Introduce objectives in stages. Separate “must know now” from “useful later”. If everything is presented as urgent, the employee cannot prioritise and the manager cannot diagnose the source of a mistake.
Create a manager feedback rhythm
Schedule check-ins at the end of day one, during the first week and at least weekly for the rest of the month. Use the same four prompts:
- What has gone well?
- Where are you blocked?
- What feedback do you need?
- What will you practise or deliver next?
Managers should provide specific examples promptly. “Be more proactive” offers little direction. “Before Thursday’s meeting, review the open cases and flag any that need another team” identifies a behaviour and a deadline.
Document agreed expectations, support and follow-up dates. If concerns arise during probation, address them early and give the employee a fair opportunity to improve. Do not save a month of vague dissatisfaction for one dramatic conversation.
Sources and limits
The framework is informed by the CCMA’s official probation information sheet and its guidance on written particulars of employment.
The appropriate onboarding and probation process depends on the role, employment terms, workplace rules, collective agreements and current law. This article is practical guidance rather than legal advice. Employers should seek qualified assistance when managing performance concerns or possible termination.