Introductory periods are nearly universal and largely ceremonial. Ninety days are written into the handbook, ninety days elapse, nobody says anything, and the employee is confirmed by silence. The employer has learned things during those months but has not recorded or acted on them, and the one moment designed for an honest reckoning passes unused.
That is a shame, because the arrangement is genuinely useful when it is run properly, and it is useful to both sides.
What it is actually for
Hiring is a decision made on very little evidence. An interview samples an hour of somebody's behavior under artificial conditions. References are cautious to the point of uselessness. A skills test shows how someone performs when they know they are being watched.
The introductory period is the first chance to see the real thing: how someone works on an ordinary Wednesday, how they behave when something goes wrong, whether they ask for help before or after the problem becomes expensive, whether coworkers seek them out or route around them.
None of that is visible at interview. All of it is visible by week six.
Why most are wasted
Three failures, in roughly this order of frequency.
Nobody is responsible for the review. It is in the handbook but not in anyone's calendar, so it does not happen.
Nothing was written down during the period. When the date arrives the manager has a general impression rather than instances, and a general impression is not something you can act on or defend.
The standard was never stated. The employee was never told what success at thirty days looks like, so any judgment made at thirty days is against a target only one party could see. That is unfair whichever way the decision goes.
Running one that works
Write down what good looks like at the start. Half a page. What they should be able to do unsupervised by week four, week eight, week twelve. Give it to them on day one. This is the single highest-value part and it takes twenty minutes.
Put three short reviews on the calendar, not one long one. Twenty minutes at weeks four, eight, and twelve beats an hour at the end. Problems surface while there is still time to fix them, which is the entire point. An introductory period that only discovers a problem at the end has failed even if the decision is correct.
Keep contemporaneous notes. Two lines after each review. What was discussed, what was agreed, by when. This is not paperwork for its own sake; it is what makes the final conversation specific rather than vague, and specific is kinder as well as safer.
Make the decision on time. Confirm, extend, or end, and say which, in writing. An extension is legitimate if the person is close and the trajectory is right, but it must come with what specifically needs to change and by when. An open-ended extension is just a longer silence.
The extension, if you use one
An extension is the right call more often than employers think, and it is misused more often still. The distinction is whether you can name what has to change.
"Another month to see how it goes" is not an extension, it is a deferral with a date attached. A proper one says: these two specific things are not yet where they need to be, here is what adequate looks like, we will review on this date, and if they are there you are confirmed. Both parties can act on that. Neither can act on a vague sense that things might improve.
Extend once. A second extension tells the employee, correctly, that the decision is not really being made and that their position is indefinite. At that point you have the worst of both arrangements, none of the security of confirmation, none of the clarity of an ending.
The conversation nobody wants
Ending an introductory period is unpleasant and most managers postpone it, usually by telling themselves the person may yet turn a corner.
Occasionally they do. More often the employer spends another four months confirming what they suspected in week six, during which the employee has also been unhappy, has not developed, and now faces a harder conversation with less runway to find something else. Deciding at the point you know is better for the person than deciding four months later.
What the employee should get out of it
It is easy to write about this entirely from the employer's side, as though the only question is whether to keep someone. The employee is also deciding, and they have even less information than you do.
They took the job on an interview and a posting. They are now finding out what the work actually involves, whether the description was accurate, and whether the people are ones they want to spend their working life among. An introductory period run with real conversations gives them somewhere to raise that while it is still easy to raise, rather than discovering in month five that the job was mis-sold and leaving without a word.
Employers who treat it as a two-way review lose the occasional person at week eight who would otherwise have left at month nine, after you had trained them. That is a good trade, not a failure.
The legal shape of it, briefly
Employment nearly everywhere in the United States is at-will by default, so an introductory period creates no separate legal status. It does not suspend the protections that apply from day one, and it does not lower the bar for behaving reasonably and documenting decisions. Minimum wage, overtime and the rest of the baseline the Department of Labor enforces apply in week one exactly as they do in year three. What the period gives both sides is a structured, expected point to be honest. The label on it changes the conversation, not the law.