A 30-day employee performance review should answer four practical questions: what the new employee was expected to learn, what work they actually completed, what remains untested, and what support is needed next. It is not a license to assume that every employee is fully productive after one calendar month. Use the real role description, agreed training schedule, and observed work rather than an arbitrary rating or someone else’s ramp-up speed.
This guide is for a supervisor documenting an early check-in, not for deciding legal probation rights or employment status. The sample employee, tasks, and statements below are hypothetical. Adapt them to the actual role, local policy, accessible work conditions, and requirements that the employee has been told about.
Start With Agreed First-Month Expectations
Before writing a comment, open the job description, the onboarding plan, and the actual assignments for the first month. Sort each item into completed, in progress, not yet scheduled, and blocked by missing access or instruction. A new employee who has not been trained on a restricted workflow should not be rated as having failed that workflow. If responsibilities changed after hiring, document the change rather than treating the original plan as an unalterable contract.
For a hypothetical operations coordinator, early expectations might include learning the scheduling system, recording handoffs with supervision, and identifying the person who approves a revised schedule. They would not automatically include independent authorization of payroll or staffing decisions. Ask the employee which instructions were unclear; that answer often reveals a solvable process issue rather than a personal weakness.
Gather Work Samples Instead of First Impressions
Look for actual deliverables: a completed checklist, a carefully corrected record, supervisor observation of a task, or notes from a guided practice session. Write down the date or context of a representative example without exposing personal customer information. A manager’s general impression that someone is “friendly” or “not proactive” does not show whether the employee met the agreed responsibility.
The UC Berkeley HR guidance recommends agreeing on how performance will be verified using work products, reports, observable criteria, and similar evidence. In a first-month check-in, the important distinction is between the ability demonstrated during permitted work and assumptions about work that has not happened. Include one genuine positive example and one verifiable learning need if the evidence supports them.
Use a Four-Part Early Check-In Record
A short review can have four fields: expected task, observed evidence, current support or constraint, and next checkpoint. For instance, a hypothetical note could say: “Entered assigned schedule changes accurately during guided practice; still needs access to the final approval queue; schedule a supervised approval demonstration before independent routing.” This separates a demonstrated ability from a missing permission and gives the next supervisor a useful action.
Avoid copying a generic one-to-five score unless the employer has defined what every level means for that role and review period. If a score is required, connect it to the applicable standard and specific examples. “Not yet observed” is often more accurate than “below expectations” for a task withheld until a later training stage.
Prepare Questions for a Two-Way Conversation
Invite the employee to bring one task that became easier, one point where they needed help, and one question about what comes next. Ask whether directions, tools, safety training, and access matched the plan. Listen before labeling a delay as a performance problem. Write a concise summary of what each side agreed to do, and distinguish a request for help from an agreement that a new result is guaranteed.
The MIT HR performance review guidance frames reviews as shared conversations grounded in prior notes and ongoing coaching. A first-month check-in works best when it extends that conversation instead of appearing as a surprise final judgment. Give the employee a chance to correct factual mistakes in the record through the employer’s established process.
Document a Fair Hypothetical Manager Comment
Hypothetical example: “During guided inventory updates, Morgan checked product identifiers against the source list and flagged two ambiguous descriptions for supervisor review. Independent exception handling has not yet been assigned. Over the next month, we will practice approved exception routes and confirm when system access is ready.” The example is illustrative; it does not report a real employee or a measured company outcome.
The comment avoids declaring that Morgan “mastered inventory” after an incomplete training window. It identifies observable behavior, preserves the manager’s approval boundary, and provides a specific action. Substitute actual dates, tasks, and evidence. If no issue was observed, do not invent a problem merely to balance positive and critical feedback. Conversely, do not omit a documented issue just to create a cheerful review.
Set the Next Checkpoint Without Inventing a Policy
Choose one or two achievable next actions whose owner and timing are clear: for example, the manager arranges system training, the employee practices a standard work sample, and both review the resulting record. Record how progress will be verified. If an obstacle belongs to another team, name the needed coordination instead of attributing it automatically to the new hire.
A 30-day conversation is not necessarily the end of probation, the beginning of benefits, or a binding promise of continued employment. Those matters depend on employment terms and applicable policies. The OPM performance management cycle distinguishes the ongoing monitoring and development of work from single review events; use that general principle without importing federal-specific employment rules into a private workplace.
Review the Record for Fairness and Privacy
Check that the examples cover the appropriate observation window and avoid private health, family, or protected personal information. Do not reveal another employee’s confidential evaluation to explain a comparison. Where work was unavailable, instructions conflicted, or equipment was missing, note the limitation. Avoid rating a person’s attitude based solely on a video-call expression or one unconfirmed comment from a coworker.
Before completing the record, verify role requirements, the review date, the name of the reviewer, and what the employee may add or correct under company policy. The record should support a fair conversation and a later follow-up, not an unsupported verdict about what the employee will accomplish.
Turn the Conversation Into a Concrete Follow-Up
At the end of the conversation, read back the decisions in ordinary language. For example, confirm which training session the manager will arrange, which routine task the employee may practice with supervision, and which assignment must wait for additional access. A useful record has an owner for each action. The manager should not write “employee will improve immediately” when the missing system permissions or training schedule are outside the employee’s control.
Give the employee a way to ask follow-up questions and agree on a date to review the plan. Keep the written summary factual, including any disagreement that the employer’s process permits employees to record. Where standards are not yet clear, the next action should be to clarify them rather than invent a rating. The check-in has value when both sides can act on what it says.
How We Research First-Month Reviews
We checked MIT HR on evidence-based performance conversations, UC Berkeley HR on verifiable expectations, and OPM on the performance cycle. These are guidance sources, not a universal 30-day rating law. JobAsk uses hypothetical examples and does not guarantee employee outcomes.
For commercial relationship transparency, see our affiliate disclosure. This article recommends no paid review tool and makes no assumptions about an employer’s rating system.
Explore Related Career Guides
- Employee Performance Evaluation Form: A Practical Manager Template
- How to Respond When You Disagree With a Performance Review
- Annual Performance Review Questions: Ask About Evidence and Priorities
- Career Aspirations in a Performance Review: Ask for the Next Step
- Performance Review Goals: Set Measurable Priorities for the Next Cycle
Not unless the employer’s actual review process requires one. Observable tasks and training status may be more informative than an unexplained number.
Record it as not yet assessed and explain the missing training or access; do not treat it automatically as a performance failure.
Expected first-month work, verified examples, constraints, employee input, and a clear next checkpoint.
Use the organization’s stated response or correction process and distinguish disagreement from a documented factual error.
No. The check-in documents observed progress, not an employment or benefit guarantee.