Your 30-Day Review at a New Job: How to Prepare and What to Say

A 30-day review is an early check-in between you and your manager, usually held at the end of your first month. It covers how you are settling in, what you have learned, and whether the role matches what you both expected. It is rarely a pass-or-fail test, but it is one of the best chances you will get to ask questions, raise problems while they are small, and agree on what success looks like for the next few months. This guide explains what to expect, what to prepare, and what to say, with a worked example from a fictional new analyst.

What a 30-day review usually covers

Most 30-day reviews have two halves. In one half, your manager asks how the job is going for you. In the other, they share early observations about your work. Some companies use a formal form, while others treat it as a longer one-on-one.

Duke University Health System's 30-day review form is a useful public example. It begins with the new employee's feedback, asking what part of the job they find most rewarding, whether the job meets their initial expectations, and whether they feel supported by their team. Only then does the manager review expected behaviors. The form lets the manager mark a behavior “not observed” and notes that it should be observed before the end of the 90-day period.

That detail is worth remembering. At 30 days, your manager has not seen everything you can do, and they know it. The review is mostly about direction: are you learning the right things, getting what you need, and heading toward the expectations for the role?

Questions you may be asked

You do not need scripted answers, but thinking about these questions in advance makes the conversation easier. Most of them appear in some form on public 30-day review templates.

• What part of the job have you enjoyed most so far?
• Is the role what you expected when you accepted the offer?
• What has been the most challenging part?
• Are you getting the information, access, and training you need?
• Who has been especially helpful?
• What could we do to help you settle in faster?
• What do you want to focus on in the next 30 or 60 days?

Answer honestly and briefly, with one example for each answer. “The most challenging part has been finding where decisions are recorded; I spent most of week two looking for the pricing history” is more useful than “everything is new.”

Keep a short record from week one

The easiest way to prepare for a 30-day review is to keep a few lines of notes as you go. New jobs are full of small firsts: your first completed task, the first question you answered for someone else, the first problem you noticed. By week four, most of them have blurred together.

A useful daily or every-other-day note has three parts: what you did or learned, what confused you or got in the way, and anyone who helped. It takes two minutes. Over a month, it gives you specific examples of progress and a clear list of the things you still need.

Those notes also help much later. Your first annual review will ask about the whole year, including the months when you were still finding your way. A record from the start makes it easy to show how quickly you became effective.

Prepare five things before the meeting

Spend 20 minutes before the meeting turning your notes into a short page. You do not need to share it, but bring it so you can refer to it.

• Two or three things you have completed or learned that show progress, each with a specific example.
• One or two things that are harder or slower than you expected, and what would help.
• Your understanding of your main goals for the next 60 days, written in one or two sentences.
• Questions about how your work will be judged, such as what good looks like at 90 days and at your first review.
• One piece of feedback you want to ask for, about something specific you have done.

If your role came with a job description or a 30-60-90 day plan, put it next to your notes. Check where you are ahead, where you are on track, and where the plan no longer matches the work. That comparison is often the most useful part of the meeting.

What to say when you are still learning

At 30 days, you will not know everything, and you should not pretend to. Managers usually worry more about new hires who seem certain about everything than about those who are honest about what they are still learning.

A good pattern is to name what you have learned, then what you are working on next. “I can now run the weekly report on my own. I'm still slow with the forecast model, so I've booked time with Marcus to go through it this week.” This shows progress and a plan in two sentences.

When you are asked whether the role matches your expectations, be honest but specific. If something is different, say what it is and whether it matters to you. “I expected more customer contact; so far it has been mostly internal reporting. Is that likely to change?” gives your manager a chance to explain or adjust.

Raise problems early and specifically

The first month is the best time to fix practical problems. Missing system access, unclear ownership, a broken tool, or meetings that make it hard to focus all become harder to raise the longer you wait, because they start to feel like part of the job.

Describe the problem, its effect, and what would help. “I still don't have edit access to the finance dashboard, so I'm sending changes to Sam to make for me, which adds about a day. Could you help me get access?” is easy to act on.

If you are worried about something larger, such as workload, a conflict, or a gap between the job and what you were told, raise it now as a question rather than a complaint. Early problems are usually easier to fix than ones that have been building for six months.

Ask for the expectations you will be measured on

The most valuable thing to leave the meeting with is a clear picture of what success looks like. Ask what your manager expects you to be doing independently by 90 days, and what will matter most in your first performance review.

Write down the answers and confirm them in a short message afterward. “Thanks for today. My understanding is that by the end of January I should own the weekly and monthly reports and have a first version of the regional forecast. Let me know if I've missed anything.” This gives you both a shared reference.

If your manager is unsure, suggest a draft. “Would it help if I wrote down what I think my 90-day goals are, and you can correct them?” Many managers appreciate this, especially if they are busy.

Worked example: a 30-day check-in for a new analyst

In this fictional scenario, Alex joined a finance team as an analyst four weeks ago. Alex's notes from the month include the following.

• Week 1: Shadowed the weekly sales report. Didn't have access to the data warehouse until Thursday.
• Week 2: Ran the report with help. Spent a long time finding the source of the regional revenue figures.
• Week 3: Ran the report alone. Noticed one region's numbers looked high; Priya confirmed a formula error.
• Week 4: Started learning the forecast model. Still slow. Marcus has been very helpful.

From those notes, Alex prepares a short summary to bring to the meeting. “In the first month I've taken over the weekly sales report, and since week three I've run it on my own. I found a formula error that was overstating one region, which Priya has now fixed. The forecast model is my next focus; I'm slower than I'd like and have time booked with Marcus. The main thing that slowed me down was data access, which took four days. Could we agree on what I should own by the end of my third month?”

That summary takes under a minute to say. It shows progress, a contribution beyond the basic task, honesty about a gap, a practical problem, and a clear question about expectations.

After the meeting

Within a day, send the short confirmation message about your goals. Add the feedback you received to your notes, together with anything you agreed to do. If your manager mentioned a skill to develop, note when you work on it, so you can show progress at 60 or 90 days.

Keep the habit of short notes going. Bloomly lets you capture a work note in a few seconds by typing or speaking, organized under the Role you are in. When your 90-day check-in or first annual review arrives, you can look back at what you learned and contributed from day one.

A 30-day review goes best when you bring specific examples, an honest view of what is still hard, and a clear question about what success looks like next. Start a simple record of what you learn and do each day, raise practical problems early, and leave the meeting with expectations you both agree on. The habit you build in the first month will also make every later review easier, because the evidence will already be there.