New Employee Onboarding: A 90-Day Plan and How to Evaluate Results

Why the First Three Months Matter

In the first weeks, a new hire works more slowly than experienced colleagues and relies on their help. Independence grows gradually, and how fast it grows depends largely on how clearly tasks are set and whether the person has access, training, and regular feedback.

When onboarding is left to chance, the story is often the same. The new hire waits for equipment and logins, reads policies, and gets tasks in bits and pieces. Three months later, the manager says “not the right fit” but can’t point to the results that were expected. The employee, for their part, is convinced no one ever explained what was wanted.

Don’t expect full productivity within 90 days. Experience shows that a new employee usually needs around 12 months to reach peak performance in a role. That doesn’t mean they are ineffective for the whole year: this is the time to maximum contribution, not to first value. The goal for the first three months is more practical. The employee should handle the role’s core tasks with confidence, and the company should have enough evidence to tell whether they are heading in the right direction.

Below is the sequence for onboarding new employees, from preparation to the final evaluation. It works both in companies with an HR team and in businesses of 20–50 people where the manager handles onboarding personally.

Onboarding and Probation Are Not the Same Thing

These terms are often confused, although each serves its own purpose.

• Onboarding is an organized process in which the company helps a new person learn the job, the processes, and the team. It isn’t regulated by law; the company itself decides what it includes and how long it lasts.
• Probation (the Labor Code’s term is “preliminary test”; in everyday use, the probationary period) is a legal mechanism. Under the Labor Code, it allows the employer to verify that the employee is suitable for the assigned work, and allows the employee to decide whether to continue.
• Performance evaluation compares what was expected with what was actually done. It is needed both during onboarding and after it.
• The decision to continue employment is a separate HR step, formalized under the rules of labor legislation.

Important: what the law says about probation. Below is only what you need to know to plan onboarding under the Labor Code of the Republic of Uzbekistan, in force since April 30, 2023. Check the procedure for your specific situation with a lawyer or HR administrator.

• Probation must be stipulated in the employment contract. If there is no such clause, the employee is considered hired without probation (Art. 129).
• Probation can be set only at hiring. It cannot be set when an employee is transferred to another position (Art. 129).
• It lasts no more than three months, or no more than six for the head of an organization, their deputies, the chief accountant, and the head of a separate division. Periods of temporary incapacity for work and other periods of actual absence from work do not count toward it (Art. 130).
• Probation is not set for certain categories of employees, for example pregnant women, women with a child under three, people under 18, employees on contracts of up to six months, and some graduates of educational institutions (the full list is in Art. 129). Nor is it set for seasonal workers (Art. 492) or temporary workers hired for up to two months (Arts. 495–496).
• Before probation ends, either party may terminate the contract by giving the other written notice at least three days in advance. The employer may do so if the probation result is unsatisfactory, and must state the reasons (Art. 132).
• If probation has expired, or fewer than three days remain and the other party does not agree to a shorter notice period, the contract stays in force and can then be terminated only on general grounds (Art. 132).

Three practical conclusions follow. First, the end of a 90-day onboarding plan does not automatically mean the end of probation: absences can push back the probation end date, and a shorter probation will end before the plan does. Second, Articles 129–132 do not provide for extending probation at the employer’s discretion, so “extending probation to finish onboarding” is not an option. Finally, the method in this article works well for evaluating an employee on probation: the decision will rest on documented facts rather than a general impression.

Stage 1. Preparing Before the Employee Starts

Most first-month problems are set up before day one. Start preparing as soon as the offer is accepted. For a typical office role, a week is often enough; for a complex position, allow more. The timelines below are guidelines: check them against how long it actually takes your company to issue equipment and access.

Define Expectations for the First 90 Days

This is the manager’s main task, and it can’t be delegated to HR. Write down a few key results (in practice, 3–5 works well) that the employee should deliver by the end of month three. Each result should answer the question: “What will be done, and how will we see it?”

Compare two versions:

• Vague: “get up to speed with client work.”
• Specific: “independently manage 20 active clients, respond to requests within one business day, and prepare a commercial proposal from the standard template without help.”

The numbers in goals like these come not from industry benchmarks but from how your company actually works: how many clients an experienced employee handles, what response time the team expects, how quickly previous new hires got up to speed. If you have nothing to go on, set a qualitative criterion and refine it at the 30-day check-in.

Map the Knowledge and Skills the Role Requires

Split everything the employee needs to learn into three groups:

1. Product and business: what the company sells or produces, who the customers are, how the sales funnel or production chain works.
2. Processes and tools: accounting and business systems (for example, 1C or a CRM), approval workflows, document management, internal rules.
3. Role-specific professional skills: what sets a strong specialist in this position apart in your company specifically.

Next to each item, note who will teach it and when the skill is needed. This turns the map into a training plan rather than a wish list.

Prepare the Workspace and System Access

The test is simple: on day one, the employee should be able to log in to every system they need without calling IT. To get there:

• the manager sends IT, the office administrator, or the responsible manager a list of systems, folders, chats, and equipment well in advance, allowing for your internal turnaround times;
• the person responsible creates accounts before day one and tests the logins, including any permissions the role requires;
• the administrator prepares the desk, building pass, office supplies, and, if needed, a company SIM card;
• HR or whoever handles personnel records prepares the hiring paperwork (see below).

Separately, put together a short starter pack: an org chart with photos and roles, plus 3–5 documents that are genuinely needed in the first week. Forty policies “for reference” don’t belong in it.

Under the Labor Code, before the contract is signed, the employer must familiarize the person with the nature of the work, the working conditions, the internal work regulations, and the company policies related to their job (Art. 123). If probation is planned, it must be stipulated in the employment contract (Art. 129). Hiring is formalized by an order issued on the basis of the contract. The employee must acknowledge the order by signature within three days of actually starting work, and the hiring details are entered into the Unified National Labor System (Arts. 122, 127). Registering the employment contract in this system is a separate employer obligation (Art. 25).

Assign Responsibilities

In a small company, one person often covers both HR and administration, and the mentor is the manager or an experienced colleague. That’s fine. What matters is not how many people are involved but that every task has a specific name attached to it.

Put Meetings in the Calendar in Advance

Before the employee starts, schedule the day-one meeting with the manager, introductions to key colleagues in related departments, and all the check-ins for the 90 days. A meeting that isn’t in the calendar usually doesn’t happen, especially for a busy manager.

Two or three days before the start date, send the employee a short message: what time and where to arrive, whom to ask for, and how the first day will go. It’s convenient to use the channel you already used during hiring, such as Telegram.

Readiness check the day before. If the answer to even one question is “no,” the start isn’t ready yet:

• Are the 90-day expectations written down?
• Have access and equipment been tested?
• Has a mentor been assigned, and do they know it?
• Are tasks for the first week ready?
• Are the day-one meetings and the check-ins in the calendars?

Stage 2. The First Day

By the end of day one, the employee should understand three things: why their role exists, what they’re doing this week, and whom to go to with questions. Everything else (tours, signatures, introductions) serves these three goals.

What the First Day Might Look Like

Morning: paperwork and workspace (up to 1 hour). HR completes the paperwork; the administrator shows the workspace and practical day-to-day details. Documents that can be signed earlier or later shouldn’t be left for the first morning.

Meeting with the manager. This is the central event of the day, and the manager runs it personally, not HR. An hour is usually enough. If there’s a lot to cover, it’s better to split the conversation into two meetings over the first few days than to cut it down to five minutes. Topics to cover:

• why this role is needed and what company problem it solves;
• the 90-day expectations: the 3–5 results prepared in advance;
• scope of responsibility: what the employee decides alone, what needs approval, and what to leave alone for now;
• working norms: which channel to use, how quickly people are expected to respond, whom to escalate urgent issues to;
• the plan for the first week and the first task;
• how feedback will work: when regular meetings happen, how the manager will give comments, how the employee should flag problems.

The last point matters more than it seems. An agreement like “every Friday we spend 30 minutes reviewing the week, and if you’re stuck for more than half a day, message me right away” removes the new hire’s fear of “bothering” people and lets the manager hear about difficulties in time.

Meeting the team and the mentor. A few short meetings with the people the employee will work with every day are better than a tour of every office. On this day, the mentor shows where key materials are and what a normal working day looks like for the team.

Afternoon: checking tools and the first task. The employee logs in to every system and immediately reports anything that doesn’t work. Then they get a small, real task that can be finished in a day or two: sorting through last week’s incoming requests, updating a reference list, or drafting a document from a template.

What to Avoid

• A day spent entirely on paperwork and briefings: the person leaves feeling there’s no real work for them.
• A manager who is “busy today,” with the first meeting postponed indefinitely.
• Overload: ten new names and five systems in one day won’t stick.

How to tell the day went well. At the end of the day, ask the employee to answer in their own words: what task they’re working on tomorrow, what’s expected of them by the end of the quarter, and whom they’ll go to if something is unclear. If the answers are vague, go over the essentials again the next morning.

Stage 3. The First Two Weeks: From Introductions to Real Work

Over these two weeks, the employee moves from learning to doing. A good sign is that by the end of week two, they have completed several real work tasks rather than only reading about how they’re done.

Good Starter Tasks

Choose first tasks that meet four criteria: they are real, mistakes in them are cheap, results are visible quickly, and doing them requires getting to know key processes. For example:

• for an accountant: reconciling balances with a few counterparties, then reviewed by a colleague;
• for a sales manager: calling a list of dormant customers using a ready-made script;
• for a developer: fixing a small bug that takes them through the whole path from ticket to release;
• for a procurement specialist: preparing purchase requests for standard items.

Hand Over Responsibility Gradually

Here is a handy four-step sequence. Its pace depends on how complex the task is, not on the calendar:

1. The mentor does it; the new hire watches and asks questions.
2. The new hire does it; the mentor is right there and corrects on the spot.
3. The new hire does it alone; the mentor reviews the result.
4. The new hire does it alone; reviews are occasional spot checks.

Move to the next step once the work has been done well, not when a date comes around. For simple tasks, a new hire may go through all four steps in a few days; for complex ones, the path can take a month or longer.

Check Understanding, Not Just Attendance at Training

A signature saying “I have read and understood” doesn’t mean the person has actually understood the process. Three simple techniques work:

• explain it back: ask them to explain the process in their own words, as if to a colleague from another department;
• scenario walk-through: “A client asks for a discount above the limit. What do you do?”;
• mini-task: have them carry out one step of the process on a real or practice example.

If the employee struggles at this early stage, check the quality of the explanation first, and only then draw conclusions about them. Explain it differently or give them more practice.

How to Set Up Mentoring

The mentor is responsible for “how to do it”; the manager is responsible for “what to do and why” and for evaluation. Don’t mix these roles: it’s easier for a new hire to ask “silly” questions of someone who isn’t evaluating them.

The meeting rhythm depends on the role. For many office positions, a short daily meeting in the first week and two or three meetings in the second week work well. Where the mentor and the new hire work side by side, separate meetings may not be needed. The mentor needs time set aside for this within their own workload; otherwise mentoring quickly becomes a formality.

Spot Gaps Early

Ask the same question at every meeting: “What took longer than you expected these past few days?” The answers usually fall into one of three groups:

• missing information: they don’t know where a document is or who makes a decision;
• missing skills: they know what to do but are still slow or make mistakes;
• missing resources: no access, no system permissions, no necessary equipment.

The company can resolve the first and third groups within a day. The second requires training and practice.

New to the Field vs. Experienced Specialist: Different Paths

What’s reasonable to expect by the end of week two: the employee works in all the necessary systems, has completed several real tasks, knows the key people in internal processes, and can state their 90-day goals. Expecting independence on complex tasks at this point is usually premature.

Stage 4. The First Month: First Independent Results

By the end of month one, the conversation shifts from “what have you learned” to “what have you done.” This is the first point where you can rely on work results, not just impressions.

What the Employee Does Alone and What They Do With Support

Split the role’s tasks into three lists and agree on them with the employee:

• does independently: routine tasks for which they have gone through all the handover steps;
• does with limited support: does the work alone but gets key decisions approved or submits the result for review;
• doesn’t do yet: complex or high-risk tasks they will move on to in month two or three.

These lists are a simple, visual way to show progress. At each subsequent meeting, tasks should move up the list.

How to Check Quality, Deadlines, and Grasp of Priorities

Quality. Take 3–5 completed pieces of work and review them with the employee: what was done well, where there were mistakes, and whether those mistakes recur. A recurring mistake matters more than a one-off.

Deadlines. Compare how many tasks were completed on time and why the rest slipped. “I was waiting for data from another department” and “I didn’t get to it” call for different solutions.

Priorities. Give the employee a list of five current tasks and ask them to rank them and explain the order. This quickly shows whether they understand what matters to the company or simply take tasks as they come in.

How to Assess Working Relationships

Ask two or three colleagues who work with the employee most often. “How’s the new hire doing?” gets you opinions, not facts, so ask specific questions:

• Do you get what you need from them, on time and in the right form?
• Were there situations where they didn’t ask for help when they should have?
• What should they do differently when working with your department?

Where to Look for Training Gaps

Compare the knowledge and skills map you drew up before the start date with reality. Items that should have been mastered by now but haven’t been are your gaps. For each one, decide who will close it and how over the next two to three weeks.

What to Record by the End of the Month

Briefly, on one page:

• which tasks the employee performs independently;
• which of the expected 90-day results are already in progress and how they’re advancing;
• the gaps identified and the plan to close them;
• what the company needs to do on its side (access, training, clarifying tasks).

There are no universal benchmarks for every position. For a contact center agent, the volume and quality of handled inquiries are already visible by the end of the month. A B2B sales manager with a sales cycle of several months may not have closed any deals yet, and that’s normal: assess their activity and the quality of their work at the early stages of the funnel. The criteria depend on the role, task complexity, length of the work cycle, the employee’s level, and the resources they were given.

Stage 5. Check-Ins and the 90-Day Onboarding Calendar

A check-in is not a report for HR or an exam set by the manager. It’s a conversation that compares expectations, actual results, obstacles, and the support needed, and then agrees on next steps.

Onboarding Calendar: Template

Use this table as a starting point and adjust it for the specific position. For simple roles, the stages compress; for complex ones, they stretch out.

Between the main checkpoints, short weekly one-on-ones between the manager and the employee are useful, for example 20–30 minutes. In a small company, these are often enough to make the interim check-ins in week 2 and on day 60 simply a slightly more detailed version of the usual conversation.

End of Week One

Participants: the employee and the mentor; ideally the manager too, even for 15 minutes.

What to discuss: whether all the tools work, whether tasks are clear, whether there’s enough information.

What to prepare: a list of completed tasks and questions that are still unanswered.

Decisions: fix any access issues; adjust tasks for week two.

End of Week Two

Participants: the employee, the manager, the mentor.

What to discuss: the first real tasks and their quality, knowledge gaps, the pace of handing over responsibility.

What to prepare: 2–3 pieces of completed work to review; the mentor prepares a brief assessment of what the employee already does alone.

Decisions: which tasks to move to independent work, what to add to training.

Day 30

Participants: the employee, the manager; HR if possible, to gather the employee’s feedback separately.

What to discuss: progress toward the 90-day goals, the three task lists (alone / with support / not yet), working relationships with colleagues.

What to prepare: the one-page month summary (see the previous section), feedback from 2–3 colleagues.

Decisions: confirm or refine the 90-day expectations; launch an improvement plan if needed.

Day 60

Participants: the employee, the manager.

What to discuss: independence on routine tasks, first results on more complex ones, follow-through on the agreements made on day 30.

What to prepare: data on the agreed results, work samples, status of the training plan.

Decisions: what needs to be done before day 90. If results are noticeably behind, discuss it honestly now rather than at the final meeting: by day 90 there may be no time left to course-correct, especially if probation applies.

Day 90

Participants: the employee, the manager, HR.

What to discuss: the final evaluation against the agreed criteria (covered in detail in the next section), plans for the next 3–6 months.

What to prepare: the completed evaluation form with examples; the employee’s self-assessment using the same form.

Decisions: confirm that onboarding is complete and set a development plan, launch a time-bound improvement plan, or consider an employment decision. If probation applies, the decision on it is made and formalized separately, under the rules of the Labor Code. If the probation outcome needs to be taken into account, it makes sense to hold the final evaluation in advance, for example 1–2 weeks before probation ends. This is an organizational recommendation, not a legal requirement. What the law does require is different: written notice of termination during probation must be given at least three days in advance (Art. 132 of the Labor Code). Confirm the probation end date with your HR administrator, since periods of absence from work don’t count toward it.

Questions to Ask the Employee

At each meeting, three or four questions from this list are enough:

• What went better than you expected? What turned out to be harder?
• What takes up most of your time?
• What do you need to work faster: information, access, training, decisions from others?
• How closely does the job match what we discussed at the interview?
• How can I, as your manager, help you?
• What task would you like to take on next month?

Stage 6. Evaluating Results: How to Tell Onboarding Has Worked

Successful onboarding isn’t completed training or a good impression on the manager. It’s evidence-backed results against expectations agreed in advance. If expectations weren’t written down at the start, an honest evaluation at the end is nearly impossible.

Four Questions Instead of One

“Is the employee coping?” is too general. Break it into four questions:

1. Results: what has the employee actually done? Tasks completed, interim results achieved, volume of work.
2. Competence: how well do they do it? Quality of work, soundness of decisions, how they handle non-standard situations.
3. Integration into the work environment: have they settled in? Do they understand processes and priorities, work well with colleagues, know whom to turn to?
4. Working conditions: has the company provided everything needed? Resources, training, access, clear tasks, regular feedback.

The fourth question is often skipped, and it shouldn’t be. Weak results may stem from unrealistic expectations, poor training, a lack of resources, or mistakes in how the work is organized. All of this needs to be ruled out before drawing conclusions about the person.

Choose Criteria and Expected Levels in Advance

Not every area is equally important for every position. Before the employee starts, choose 4–6 criteria and, for each, write down what result and what level on the scale below you expect by day 90:

• mastery of the role’s professional tasks;
• quality and timeliness of work;
• degree of independence;
• understanding of processes and priorities;
• working relationships;
• achievement of agreed interim results.

The expected level depends on the role, task complexity, and resources. For an accountant, it’s reasonable to expect independent handling of routine transactions by day 90. For complex negotiations or large projects, “performs with support” may be perfectly normal at that point. There is no single standard for every position.

Rating Scale

The key question that separates level 2 from level 3: was help needed at key steps of the task, and how substantially did the reviewer have to correct the result?

Level 4 is given only for exceeding expectations on the criterion itself. Helping colleagues or working beyond the role is valuable, but it counts toward the rating only if it was part of the agreed expectations.

The main rule of the scale: no supporting example, no rating. If the manager can’t back up a level with work output, data, or specific feedback, the criterion gets “N/A,” not an “average” score.

Onboarding Evaluation Form: How to Record It All

One table is enough. The manager sets it up before the start date and adds to it at each check-in. The first four columns are filled in advance; the rest are filled in as you go. Here is a sample row for an accountant:

Add a separate row for working conditions: “provided,” “partially provided,” or “not provided,” with an explanation. Before the final meeting, the employee fills in the results columns themselves: any differences from the manager’s assessment make the best talking points.

Example: A Procurement Manager at a Distribution Company

A company in Tashkent with about 60 employees and no dedicated HR team. A new procurement manager joins from a retail chain, with experience working with suppliers. This is a hypothetical example: the numbers and circumstances are invented to show the reasoning.

Where the expectations came from. The manager wrote them down before the employee started. The target volume of 15 suppliers is the category that one experienced buyer handles in the department. By internal rule, negotiations on large contracts involve the manager, so level 2 was expected on this criterion by day 90. Suppliers were handed over in stages: 5 by day 30 and all 15 by day 60.

What held the employee back. Permissions to approve payments in the accounting system were granted only in week six. Until then, he couldn’t process supplier payments himself, and some results simply couldn’t be demonstrated. So the criteria that depended on these permissions were assessed using data from after they were granted.

What’s confirmed. On all key operational tasks, the employee is working at the expected level. The early delays with the finance department are explained by permissions granted late, not by his work.

What remains open. How he handles the full volume during a peak period and how he negotiates without the manager. There isn’t enough data to draw conclusions yet, and it’s too early to rate these.

The logical decision. Consider onboarding successful for the core tasks and draw up a development plan for the next two to three months: independent negotiations and a check during the peak period. If the contract includes probation, this data gives no grounds to consider the probation result unsatisfactory, but the decision itself is made and formalized separately, under the rules of the Labor Code.

Note what this evaluation doesn’t include: “fit in well with the team” and “comes across as capable,” without a single example. Statements like these may reflect reality, but you can’t base a decision on them.

Stage 7. Course Correction: What to Do If a New Hire Falls Behind

Falling behind, spotted on day 30 or day 60, is a normal working situation, not a failure. The mistake is either to stay silent until the final meeting or to conclude straight away that the person isn’t right for the job. First identify the cause: what you do depends on it.

How to Document the Agreements

An improvement plan fits on half a page and answers five questions:

1. What needs to change: a specific result or action, not “do better.”
2. By when. The deadline depends on the skill and the work cycle. For routine operations, two to four weeks is often enough; skills with a long cycle need more time, with an interim checkpoint.
3. What support the company provides: training, a mentor, the manager’s time, access.
4. What signs will show progress: exactly what the manager will look at in the next meeting.
5. When the review takes place: a date in the calendar, not “we’ll see.”

Both parties agree on the plan and confirm it in writing. This gives the employee clarity and gives the company a clear record of how decisions were made.

Two Rules That Protect Against Mistakes

An improvement plan is always time-bound. It has a deadline, criteria, company support, and a review date set in advance. A new cycle makes sense if the previous one showed measurable progress or if the company has just removed an obstacle that was getting in the way. If there’s no progress and the conditions are in place, extending the plan won’t change anything by itself. If probation applies and you want the plan’s outcome to inform the probation decision, the plan has to fit within the probation period: Articles 129–132 of the Labor Code don’t provide for extending probation at the employer’s discretion.

Don’t make an employment decision based on a single episode. A failed assignment or an unpleasant conversation is a reason to look into things, not grounds for a conclusion. The decision should rest on several confirmed facts across different periods.

If things are still heading toward a parting of ways, consider other options too: a transfer to a role where the employee’s strengths are more needed, or a revised scope of responsibility. The legal rules here depend on the situation. During probation, the procedure in Article 132 of the Labor Code applies: written notice at least three days in advance and, for the employer, only if the probation result is unsatisfactory and with the reasons stated. After probation ends, or if there was no probation, the contract can be terminated only on the grounds and following the procedure the Code sets for termination at the employer’s initiative. Check decisions like these with a lawyer in advance.

In Short: Your Employee Onboarding Plan in Five Steps

1. Before the start date, write down the key results for the 90 days with the expected level for each, set up access, and assign owners by name. If you need probation, stipulate it in the employment contract.
2. On day one, the manager personally explains the role, the goals, and how feedback will work, and the employee gets their first real task.
3. In the first weeks, hand over responsibility step by step and check understanding through practice.
4. Hold check-ins at the end of weeks one and two and on days 30, 60, and 90, and bring examples of work to them. If probation applies, align the final meeting with its end date.
5. Evaluate using four questions (results, competence, integration into the work environment, and working conditions), and if the employee falls behind, look for the cause first and the solution second.

Systematic onboarding doesn’t require a dedicated department or complex programs. It requires expectations written down in advance, meetings in the calendar, and an evaluation based on facts. Start with the calendar template and the onboarding form from this article, and use them to draw up a plan for one specific vacancy. The next ones will go faster.