Write a first-week scorecard for a new outsourced coordinator

What a first-week scorecard is for

A first-week scorecard is not a performance review. It is a short record of whether the role brief, the training, and the access were good enough for real work. Use it to find gaps in the setup before they become habits.

The coordinator should see the same scorecard you use, with the same definitions and the same examples. That transparency turns a judgment into a shared diagnosis.

Keep the scope to work the coordinator actually touched. Do not score attitude, potential, or cultural fit, because those judgments are unreliable after five days. Score whether the assigned queue moved, whether the records are usable, and whether questions reached the right person.

Add one note about the setup, such as a missing example or a late login. That keeps the conversation factual and gives the coordinator something to act on.

Pick five measures you can observe

Choose measures a reviewer can confirm from the work itself. A useful five are items completed, items returned for correction, items waiting on the owner, stop-rule calls made correctly, and handoff notes written. Each one should point to a specific record rather than a general impression.

If two reviewers cannot agree on what counts, rewrite the measure before the first week ends. A measure that needs a debate is not ready for a scorecard.

Avoid measures you cannot observe without extra work. Hours online, message count, and typing speed rarely show whether the output is usable. If a measure needs a new dashboard before the first week, it is probably not a first-week measure.

Start with what the queue already records and add one manual count only when it answers a real question. The scorecard should take less time to prepare than the review meeting.

Calibrate the reviewer before scoring the coordinator. Have two reviewers independently grade the same five items and compare the result. Resolve differences with the written rule rather than seniority.

A reviewer who cannot reproduce the score will produce a scorecard the coordinator cannot trust. Keep the calibration note with the first week's record.

Separate speed from judgment

A new coordinator may be fast because the work is easy or because the work is being skipped. Check a sample of completed items before praising throughput. Look for missing sources, copied answers, and requests closed without a destination record.

Compare the sample with the examples used in training, because a mismatch usually points to a gap in the brief. Speed without a usable record is not progress.

Judgment shows up in the stops. Count the items the coordinator paused and the reason given for each pause. A correct stop with a clear note is a strong signal, even when it slows the queue.

Reward the stop, then teach the coordinator how to resolve the next one. Track whether the same stop recurs, because a repeated stop may mean the rule is wrong rather than the person.

Review the scorecard in a short conversation

Book twenty minutes at the end of the first week and share the numbers before the call. Ask the coordinator which task was hardest and which instruction was unclear. Listen for setup problems: missing examples, conflicting rules, or access that arrived late.

Take notes in the same document as the scorecard so the context stays together. The conversation should produce a change, not a verdict.

End with one written improvement, not a list of ten. Name the change, the owner, and the date it will be checked. If the problem is training, fix the guide.

If the problem is authority, fix the boundary. Do not ask the coordinator to compensate for a broken process, because that turns a setup defect into a personal failing.

Handle a weak first week without panic

A weak first week can come from a poor match, a rushed brief, or an unrealistic queue. Separate those causes before deciding what to do. Look at the training record, the first reviewed items, and the questions the coordinator asked.

The pattern usually points to one cause, and the fix is different for each. Write down the evidence before you speak to the provider.

If the work is consistently unusable and the guide was clear, escalate to the provider with examples. If the guide was thin, repair it and give the coordinator a second measured week.

Replacing a person before fixing the setup repeats the same failure with a new hire. Set a review date for the second week and use the same measures so the comparison is fair.

Retire measures that stop being useful

After a month, some first-week measures become noise. Items completed may matter less than rework rate, and handoff notes may matter less than the number of owner waits. Retire a measure when nobody changes a decision because of it.

Keep a short note about why it was retired so the next manager does not reintroduce it. A scorecard that grows every month becomes a report nobody reads.

Replace it with a measure tied to the next risk, such as access changes, exception aging, or customer follow-ups. Keep the scorecard short enough to read in one sitting.

The point is a shared view of the work, not a permanent reporting system. Review the set at each role change and remove anything the coordinator cannot influence.