How to Onboard New Employees: A Guide to the First 90 Days
The new hire signed the contract, arrived on the first day, and received the institutional material. Two weeks later, they’re still “observing,” waiting for someone to have the time to explain how things really work. A month later, the manager realizes they never quite understood what was expected of them.
That script is the most common onboarding at Brazilian companies: let each manager improvise and hope their instincts are good. Unclear expectations and a lack of follow-up can undermine integration from the first few weeks.
This guide shows how to structure the first 90 days without depending on anyone’s memory, goodwill, or free time — with a flow in which every conversation and every training session becomes ready-made reference material.
What onboarding is (and what it isn’t)
Onboarding is the structured process of integrating a new employee into the company: role, team, systems, and culture. It starts before the first day and ends when the person operates on their own — depending on the complexity of the role. Here, 90 days is a planning horizon, not a mandatory onboarding duration.
Onboarding is not:
- The first day of introductions — it’s the least important event of the 90. The decision to stay takes shape in the weeks that follow.
- An email with system links — access is a prerequisite, not integration.
- Admission paperwork — that’s the personnel department’s job. Onboarding is about productivity and retention.
- HR’s responsibility alone — HR coordinates; the manager and the team are the ones who truly integrate the person.
If your company has a “one-day onboarding,” what you actually have is a reception. The process that affects retention lasts weeks — it’s in those weeks that the new hire compares what was promised in the interview with what they find in front of them.
Why the first 90 days are a risk zone
The first weeks help people understand the role and build connections. There is no universal deadline for reaching autonomy.
What market research shows consistently:
- In a historical BambooHR survey of over 1,000 US workers, 31% of employees have left a job within the first 6 months — and two-thirds of those departures happen in the first 3 months.
- Reported reasons included changed expectations about the work and difficulties with managers. These findings are not a current turnover rate for Brazil.
The central detail: nobody quits over a missing institutional PDF. Early departures come from misaligned expectations, a lack of clarity about the role, and isolation — the person doesn’t know what’s expected of them, doesn’t know whether they’re doing well, and has no one to ask.
The guide: the 90 days in three phases
A simple structure that works in companies of any size. The principle: in every phase, there is an intentional conversation, a written expectation, and someone named as responsible.
| Phase | Period | Focus | Exit milestone |
|---|---|---|---|
| 1. Immersion | Day 1 to week 2 | Welcome them, introduce the role, assign the first deliverables | The person knows what’s expected and has already delivered something |
| 2. Operation | Weeks 3 to 6 | Train on the real process, buddy, weekly check-ins | The person handles the core of the role with light supervision |
| 3. Autonomy | Weeks 7 to 12 | Their own goals, 30-60-90 feedback, fine-tuning | The person operates on their own and has a plan for what comes next |
Phase 1 — Immersion (day 1 to week 2)
The goal isn’t to “present everything” — it’s to reduce anxiety and produce a quick first deliverable. Checklist:
- Before the first day (pre-boarding): a welcome email with what to expect on day 1, working hours, dress code, and who will greet them. Zero cost, big effect: the person arrives less anxious.
- First day: a named person responsible for receiving them, plus a tour with real introductions (not just “this is John,” but “this is Jane, who takes care of X — she’s the person you’ll talk to the most”).
- First week: an expectations conversation with the manager — in writing. What the person should deliver within 30 days, how success is measured, and who they go to for each type of question.
- A small first deliverable: something useful, delivered in the first week. Nothing accelerates the sense of belonging like having done something that mattered.
Phase 2 — Operation (weeks 3 to 6)
This is where technical training lives — and companies’ biggest bottleneck: the knowledge sits in the heads of the people who already work there.
- A named buddy: a colleague (not the manager) responsible for the silly questions during the first 30 days. The questions a person is embarrassed to take to the boss need somewhere to go.
- Training in a consultable format: every session with an experienced person becomes material the new hire can reread later — not a conversation that evaporates.
- The manager’s weekly check-in: 15 to 30 minutes. It isn’t pressure — it’s “what got stuck this week?”
Phase 3 — Autonomy (weeks 7 to 12)
- 30-, 60-, and 90-day meetings: structured questions (“What was better than you expected? What was different? What’s missing for you to operate on your own?”).
- Their own goals: from this point on, the person has outcome goals, not just learning goals.
- A conscious decision: at 90 days, both the company and the employee know whether the hire worked — based on data, not on gut feeling.
The real bottleneck: training takes time from people whose plates are already full
Every manager agrees that structured onboarding is a good thing. The problem is practical: phase 2 requires an experienced person to stop producing in order to train. On small teams, it’s the manager themselves — plate already full — who has to explain the process for the umpteenth time. When the schedule gets tight, training becomes “message me with any questions,” which is the same as having no training at all.
That’s where improvisation sends the bill: each new hire receives a different version of the process, the material doesn’t really exist (only conversations), and three months later nobody remembers what was promised on day 1.
The way out isn’t to stop training — it’s to make the training yield more than the conversation:
- Record the training. The handover meeting, the process explanation, the team introduction: everything that’s already being said can be captured.
- Turn talk into structure. One hour of explanation becomes a summary, a mind map, and a checklist — the reference material phase 2 requires.
- Reuse it. The next hire starts with the material ready; the conversation becomes space for what’s specific, not for repeating the basics.
How to do this with Sintesy
Sintesy turns voice and video into structured material — exactly the format onboarding needs to produce. The practical flow:
Before recording, inform participants and confirm authorization and applicable company policies. Keep reusable training separate from individual performance conversations; restrict access and define retention. Do not record passwords or customer data.
1. Capture the training without changing the routine
The training that already happens becomes material. The options cover the formats a company uses day to day:
| Situation | How to capture | What to use |
|---|---|---|
| Remote onboarding meeting (Meet, Teams, Zoom) | Invite the bot to record and transcribe | New → Record meeting |
| In-person handover conversation | Record with your phone on the table | New → Record audio |
| Training recorded as video (Loom, phone) | Upload the file | New → Upload file |
| Institutional video or training on YouTube | Paste the link | New → Summarize YouTube videos |
2. Have the material ready for the next hire
Depending on the content and processing, a synthesis can include: the full transcript (to search for any detail), the structured summary (the reference guide), the mind map (the view of how the process connects), and the checklist (the operational steps as checkable items). Review names, technical terms, and instructions before distributing the material. Full content, export, and sharing options depend on the plan; a folder is not necessarily a collaborative workspace.
The result is exactly what phase 2 of the guide calls for: training in a consultable format, which the person rereads whenever they need it, instead of asking again.
3. Bring it all together in a folder per hire
Create a folder per employee (or per role) and gather there: the day-1 expectations conversation, the process trainings, the handover from each area. When the next hire arrives, the material is already structured and organized — and the buddy spends their energy on what’s unique about that person.
4. Close the loop on days 30, 60, and 90
Record the check-in meetings the same way. Two immediate advantages: you can compare what was said at each milestone (what was promised on day 1 is documented), and if the hire doesn’t work out, you have the material to understand what went wrong — up front, not after the termination.
What to measure in the first 90 days
Onboarding without metrics is just a feeling. Four indicators are enough:
- Early turnover: % of departures within the first 90 days. Compare roles and hiring cohorts, and investigate departure reasons.
- First-year retention: how many hires are still with the company after 12 months. Compare against company history rather than a universal target.
- Time to productivity: how many weeks until the person operates without supervision.
- Newcomer eNPS: the score from people who joined less than 6 months ago, compared to the company average. A significant difference warrants investigation; it does not prove a single cause.
If you don’t have historical data, start by measuring just the first two. They already reveal whether the process is working.
Remote onboarding: the same structure, with an aggravating factor
On remote teams, the casual interactions that integrate people naturally don’t exist. There’s no question in the hallway, no discovering how things work by osmosis. Everything that happens on its own in person has to be deliberate: the conversations need to be on the calendar, the material needs to actually exist (nobody will “ask over chat” with the same ease), and the weekly check-in is mandatory, not something you can cut.
The good news: well-structured remote onboarding tends to produce better material than the in-person kind, because there’s no way to improvise — the same recording and structuring of trainings makes up for the distance.
Recap
- This guide plans onboarding over 90 days, not a single day; adapt the duration to the role.
- The decision to stay takes shape in the first few weeks; most early departures are avoidable with clarity, follow-up, and real material.
- The bottleneck is the time of whoever does the training — capturing and structuring the training that already happens makes the process cheaper and more consistent.
- Measure early turnover and first-year retention; the rest is fine-tuning.
Start with your next hire: set up the folder, record the first expectations conversation, and turn the first training into a guide. The 90 days that follow will thank you — and so will the hire who comes after.
Try building your onboarding material with Sintesy: create your account, record the first-day expectations conversation, and watch the training turn into a summary, a mind map, and a checklist. To round out your management routine, see how to turn internal training into a reference guide, how to turn in-person meetings into documentation, and how to record remote meetings with a bot that transcribes on its own.


