Philippines staffing guide · Published

On this page

Set a monthly performance review for an overseas assistant

A monthly review built on agreed outputs, contemporaneous evidence, and two written changes, with compensation kept in a separate conversation.

Set a monthly performance review for an overseas assistant

A monthly review gives an overseas assistant a predictable moment to hear how the work is landing. It also gives the client a structured way to raise a problem before it becomes a resignation or a missed deadline. The meeting should be short enough to hold every month and specific enough to change something. A review that only says the work is fine trains nobody.

Build the review around evidence the team already collects: completed tasks, client feedback, and the exceptions logged during the month. Do not create a separate reporting burden just for the meeting. The assistant should be able to prepare in twenty minutes. The client should arrive with examples, not adjectives. Use the same evidence pack for the review and the client update.

Anchor the review to agreed outputs

Start from the outputs named in the role brief, such as a weekly report or a clean inbox at the end of each shift. Ask whether each output arrived on time and at the agreed quality. Use the task record rather than memory, because memory favors the most recent problem. A review that drifts into unrelated tasks makes the standard feel arbitrary.

If the role has changed, update the output list before the review. An assistant cannot be measured against a brief that no longer matches the work. Note which outputs were added, removed, or renegotiated during the month. The review then compares like with like. Record the change and its date so the next review begins from the current scope rather than the old one.

Collect evidence during the month

Keep a small file of client praise, corrections, and missed deadlines as they happen. A one-line note with the date and the task is enough. Do not wait until the review to reconstruct the month from chat history. Contemporaneous notes are more accurate and less likely to reflect the reviewer's mood. Store it where the assistant can add a note without asking permission.

Ask the client to send one specific example of good work and one of a problem before the meeting. Two examples are enough to start a useful conversation. If the client cannot name one, the review should focus on defining what good looks like. Evidence-free praise and evidence-free criticism are equally hard to act on. If the client sends a general comment, ask for the task and the date behind it.

Separate quality from availability

Quality is whether the work met the standard; availability is whether the assistant was reachable in the agreed window. These are different problems with different fixes. A missed deadline may be a quality issue, a capacity issue, or a schedule mismatch. Name which one before proposing a change. Write the distinction in the review template so it survives a change of reviewer.

Do not use response speed as a proxy for commitment. An assistant who answers every message instantly but delivers weak work is not outperforming one who batches messages and delivers well. Measure the outputs and the response window separately. That separation keeps the review fair and the coaching precise. The review should reward the output that the client actually receives.

Ask the assistant to self-review first

Send three questions before the meeting: what went well, what was hard, and what would make the work easier. Ask for examples, not a rating. The answers show where the assistant needs context, access, or a clearer decision rule. They also surface problems the client has not noticed. Give the assistant the questions at least two days before the meeting.

Listen to the self-review before presenting the client's view. If the two accounts differ, compare them against the task record rather than arguing. A disagreement about facts is easy to resolve with evidence; a disagreement about standards needs a new example. Give the assistant time to respond without interrupting. End the discussion with a shared version of the facts, even if the standard stays open.

Write two changes, not ten

End the review with no more than two changes for the next month. One should address a quality gap and one should remove a friction point. Write each change as a specific action with an owner and a date. A long improvement list signals that the review was a complaint session, not a plan. Name the date when the team will check whether each change held.

Put the changes in the shared workspace where the assistant works every day. Review them at the start of the next meeting before adding anything new. If a change did not work, say so and replace it. Two tested changes a month produce more progress than a page of intentions. Remove a change that creates more work than it saves.

Keep compensation talk separate

A performance review and a pay conversation should not share the same hour unless the policy is already clear. Mixing them makes the assistant hear every comment as a signal about money. Hold the review first and schedule a separate conversation for rate or scope. That separation keeps the feedback honest. Tell the assistant which meeting is which before the calendar invite goes out.

If a raise is tied to a review cycle, state the rule before the meeting and show how it was applied. If the answer is no, give the reason and the date when it can be revisited. Do not promise a future increase to soften a critique. A clear policy is easier to trust than a warm maybe. Put the rule in the role brief so it does not depend on memory.

Questions and operating boundary

Should the review be weekly for a new assistant?

Use a short weekly check-in for the first month, then move to the monthly review once the workflow is stable.

Who should run the review?

The account lead or the person who sees the work daily. The client may join quarterly rather than every month.

What if the assistant disagrees with the feedback?

Compare the feedback with the task record and the agreed standard. If the standard is unclear, write an example and review it again next month.

Source

sba.gov provides authoritative background and does not endorse this service.

Explore services · Browse guides · Plan a controlled lane

Philippines staffing

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. Those details help shape a practical Philippines staffing request.

Contact Us