Onboarding
Set probation expectations through clear work agreements
Set early-employment expectations by agreeing role outcomes, observable work standards, support, review cadence, and who makes decisions. Explain the organisation's approved process and route formal policy or legal questions to qualified owners. Provide timely evidence-based feedback and document material changes, so the employee is not asked to infer success from silence.
On this page
Separate policy from the work plan
Share the approved employment policy and contacts responsible for explaining it. The manager's job is to translate the role into early outcomes, behaviours tied to work, and available support. Do not improvise legal interpretations, guarantees, or consequences in an onboarding conversation. If policy and manager practice appear inconsistent, pause and ask the appropriate people to clarify before making commitments.
Define staged expectations
Set what the person should learn, practise, and own over meaningful work cycles. Include quality, collaboration, and decision expectations with examples relevant to the role. Adjust for access and onboarding dependencies. A list of final job outcomes from day one provides little guidance; equally, vague advice to settle in gives no basis for useful coaching.
Agree evidence and feedback cadence
Name the work artifacts, observations, stakeholder inputs, or service results that will inform discussions. Schedule frequent early check-ins and more formal review points under company practice. Managers should raise concerns when evidence appears, explain the effect, hear context, and agree next actions. Avoid collecting undisclosed opinions or waiting until the end to reveal a pattern.
- Early outcomes and why they matter
- Observable evidence for each outcome
- Access, training, and manager support
- Check-in and review dates
- Official contact for policy questions
Adjust fairly when inputs fail
Illustrative example: a new implementation consultant is expected to lead a customer session in week six, but required product access arrives in week four. The manager records the dependency, provides a shadow session, and revises the practice sequence. They still discuss preparation quality promptly. The missing access is not ignored, and it is not mislabelled as an individual performance failure.
Document the shared understanding
After each review, record outcomes discussed, supporting examples, employee context, support promised, changes, and next dates in the approved place. Give the employee appropriate visibility into the working agreement. Seek qualified HR or legal guidance for formal decisions. Clear documentation should improve the next conversation, not replace direct, respectful management with a paper trail. Calibrate managers on examples of role-related evidence and supportive responses before they run reviews. Different teams should not invent incompatible meanings for the same company process. When a manager is unsure, they should seek help early rather than delay feedback or improvise a formal interpretation with the employee. Check that the manager's promised support actually appears in calendars, access requests, or assigned teaching, because an expectation without its enabling condition is incomplete.
Next step
Write staged early outcomes with evidence and support, schedule the review cadence, and confirm the official route for policy questions before the employee starts.