Practical guide
Create a first-week scorecard for a newly outsourced admin role
A short scorecard that judges a new admin role on observable first-week work instead of personality.
Published

Table of contents
Define first-week outcomes, not personality traits
A first-week scorecard should describe work that can be observed, not impressions that cannot be checked. Useful items include access working on day one, the first task completed against a sample, questions recorded in the right place, and the handoff understood. Each item needs evidence and a reviewer. A trait such as proactive is too vague to score fairly.
Limit the scorecard to six or eight items so the reviewer can actually complete it. Give every item a plain description, the evidence to look for, and the person who will review it. Separate learning goals from production goals. A new hire who is still learning the system should not be judged on volume alone.
Write the scorecard before the person starts, not after the first week. That timing forces the team to agree on what success looks like and prevents the score from drifting toward whatever happened. Share the scorecard with the new hire on day one so the expectations are visible. The document is a planning tool, not a secret test.
Use the same scorecard for every new hire in the same role so the comparison is fair. If the role differs by location or shift, note the difference instead of changing the items silently. A scorecard that changes per person cannot show whether the onboarding is working. Keep the role version with the job description. Review it when the role's tools or outputs change.
Set the baseline before day one
Confirm accounts, tools, reference material, sample work, and a named buddy before the start date. Record what was ready and what was missing on the first morning. A missing login is a preparation failure, not a performance problem. The baseline protects the new hire from being blamed for the team's unfinished setup.
Explain how the scorecard will be used and who will review it. Make clear that the first review is a working conversation, not a final judgment. Give the new hire a way to add items they found confusing. A scorecard that only flows downward misses the information the new person can see most clearly.
Choose a sample task that represents the real work but can be completed in the first week. Use the same reference material a new employee would receive, and keep the sample short enough to finish without cutting corners. The point is to see how the person uses the source, not to test memorization. A realistic sample produces a more useful conversation than a quiz.
Ask the buddy to record the questions the new hire asks during the first week. Those questions are evidence about the reference material. Review them at the day-five check. A question that appears in every onboarding is a missing instruction, not a personal gap. Add the most common question to the quick-start guide.
Review at day three and day five
The day-three check should answer three questions. Can the new hire find the approved source, complete the basic task, and ask for help before making a guess. Fix any blocker immediately, especially access or missing documentation. A small delay on day three can turn into a lost week if nobody acts.
At day five, review each scorecard item with the evidence and write a short note. Distinguish a skill gap from a missing reference or a broken tool. If the new hire did not know where to look, check whether the guide actually contains the answer. If the answer was there and the person missed it, plan a coaching step.
Ask the new hire what was confusing during the week and record the answer. Their view is part of the quality review, not a courtesy. A repeated confusion across two hires usually points to the onboarding material rather than the person. Use that signal to improve the next start.
If an item cannot be observed in the first week, move it to the 30-day plan instead of guessing. A scorecard should not force a judgment without evidence. Mark the item as deferred and explain why. That honesty makes the rest of the review more credible. Tell the new hire which items were deferred and when they will be reviewed.
Turn the scorecard into a 30-day plan
Use the first-week results to set the next month's goals and add complexity gradually. Keep the same evidence standard so progress can be compared. A new goal might be handling a second task type, taking a full queue for one shift, or writing a clearer exception note. Each goal should have a reviewer and a date.
Review progress weekly rather than waiting for a single 30-day meeting. Short reviews catch a misunderstanding before it becomes a habit. Keep the notes in the same place as the scorecard so the next reviewer can see the pattern. The new hire should know what will be reviewed next.
Update the scorecard for the next hire and remove items that did not predict useful performance. Keep a version date so the team can tell which scorecard was used. The final measure is not a perfect first week. It is a new role that becomes productive without hiding problems in guesswork.
Share the updated scorecard with the next reviewer before the next start date. A short handover note explaining what changed is enough. Keep the old versions so the team can see why an item was removed. The scorecard should improve with each hire, not grow without limit. Review the whole scorecard once a year against the role description.
Sources
References supplied with this guide.
| Source | Publisher | Context |
|---|---|---|
| U.S. Small Business Administration, Hire and manage employees | sba.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, Employment Law Guide | dol.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Cybersecurity Framework 2.0 | nist.gov | Primary reference supplied with this article. |