Prepare for the first-90-day conversation with evidence, not a performance speech

The first months of a new state job can pass quickly enough that progress feels obvious in the moment and hard to describe later. You know more names, need fewer explanations, and can complete tasks that once seemed opaque. An early review is a chance to connect that progress to the work expected of you. It is not a reason to produce an inflated account of everything you have touched since arriving.

Tennessee HR Support says your supervisor will complete an interim review within the first 90 days of onboarding. Ask your supervisor about the actual timing and preparation for your role. The approach below is an editorial preparation method, not the state’s rating system, a guarantee of a particular outcome, or advice about employment rights.

Ask what the conversation needs to cover

Before collecting evidence, find out what your supervisor wants to discuss. The meeting may focus on assigned work, learning progress, expectations, or obstacles. Knowing the purpose prevents you from spending hours on a presentation when a short set of examples would be more useful. If a formal document is involved, ask where the current version is and what you are expected to contribute.

Clarify the period being reviewed and the responsibilities that were actually assigned. A task you observed is different from one you performed independently. A temporary arrangement may not represent the long-term role. Explain those distinctions plainly so that the conversation evaluates the work you did rather than a job description imagined after the fact.

If you have not received clear expectations, raise that early. Ask what satisfactory work looks like and which priorities should guide the next weeks. Waiting until the review to reveal a major misunderstanding makes it harder for both people to use the meeting constructively.

Choose a few examples with a clear result

Select examples that show learning or a completed contribution. For each one, describe the assignment, your part, the result, and what you learned. Keep the account proportional. Supporting someone else’s task is valuable, but should not be presented as sole ownership of the whole outcome.

Use approved records or general descriptions rather than exporting sensitive work to prove your point. You can explain that you completed a defined type of task under review without attaching a real person’s record. Ask what evidence may be included if the formal process requires documentation. The agency’s information-handling rules still apply to review preparation.

Include an example of feedback you acted on. A correction followed by improved work often tells the supervisor more than a list of activities. Describe the change specifically: what you misunderstood, what guidance you received, and how you adjusted. You do not need to dramatize a routine learning moment or turn it into a claim that no further support is needed.

Identify the work that still needs supervision

Be clear about what you can do independently and where you still need a check. New employees can feel pressure to describe all assistance as a thing of the past. That is risky when a task has consequences and you are not yet confident about exceptions. Accurate limits let the supervisor plan support and assign work appropriately.

Distinguish a knowledge gap from an access or process dependency. You may understand the task but lack a permission. You may have the permission but not yet know the approval route. Those situations require different responses. Naming the actual barrier makes the next step more concrete than saying you need more training in general.

Bring unresolved administrative issues only where they affect the conversation. A missing onboarding item or unanswered support request may be relevant, but the review should not become a substitute help-desk ticket. Explain the impact, the contact already made, and the decision or assistance you need from the supervisor.

Ask questions that shape the next month

Useful review questions look forward. Which task should I be able to handle with less review next? Where should I improve accuracy before increasing speed? Which exception should I escalate rather than decide myself? These questions turn general feedback into something you can practice.

If feedback is broad, ask for a concrete example. “Be more proactive” might mean flagging a dependency earlier, preparing information before a meeting, or checking an unresolved item without another reminder. The expected behavior matters. Do not guess at it and then judge yourself against a standard the supervisor did not intend.

When priorities conflict, ask which takes precedence and why. A new employee may be trying to satisfy several reasonable requests at once. The review offers a place to make that workload visible and agree on an order, rather than quietly choosing the most recent request and leaving another commitment unmet.

Leave with an agreed next step

At the end, summarize the main expectations in your own words and invite correction. A short recap can reveal a misunderstanding while both people are present. Record the agreed actions in the appropriate place and distinguish formal requirements from your personal planning notes. Do not treat an informal conversation as a substitute for a required official record.

Set a practical follow-up point where your supervisor’s process allows it. The goal is to check whether the requested improvement or support has occurred, not to create another meeting without a purpose. If the action depends on another office, identify who will contact it and what outcome you need.

An early review is most useful when it produces a clearer next month. You do not need a flawless story about the first ninety days. You need a fair description of the work, evidence of learning, and an honest account of what remains difficult. That combination gives both you and your supervisor something concrete to build on.