Run a monthly one-on-one with a remote assistant using queue evidence

Pick the evidence before the meeting

A useful one-on-one starts with a small evidence pack rather than a blank conversation. Choose two completed tasks, one correction, one capacity note, and one question the assistant raised during the month. Keep the pack to a single page so the meeting has room for discussion. Evidence without context turns the check-in into a performance review.

Ask the assistant to add one item they want to discuss before the meeting. Their item may be a blocked tool, an unclear brief, or a schedule conflict that the manager never sees. Put both lists side by side and agree on the order. A shared agenda signals that the meeting belongs to both people.

Open with the assistant's own review

Begin by asking the assistant what went well and what felt harder than it should have. Let them describe the work before you offer a judgment. Their account often reveals a source problem behind a quality problem. The manager's first job is to understand the week the assistant actually had.

Listen for the tasks that took longer than expected and ask what caused the extra time. A slow approval, a missing file, or a tool that logged them out can explain a delay that looks like poor time management. Write the cause beside the task. The note becomes the input for the next process change.

Discuss quality without turning it into a score

Use the sampled tasks to discuss accuracy, source use, and judgment rather than a single rating. Ask the assistant to explain the choice behind one correct output and one correction. That explanation shows whether the standard is understood or only followed once. Keep the conversation specific to the work.

Separate a skill gap from a brief gap before agreeing on training. If the assistant knew the right action but the instruction was unclear, fix the instruction first. If the assistant did not know, add a short practice set and a reviewer. Naming the cause prevents a generic coaching plan that solves nothing.

Recognize the work that went right, not only the correction. Name a task where the assistant protected the client from a bad outcome and explain why it mattered. Specific recognition is more credible than a general compliment. It also shows the team which behavior the manager wants repeated.

Cover workload and capacity honestly

Review the number of tasks completed, the hours available, and the work that was pushed to the next day. Ask whether the volume felt sustainable or whether the assistant was absorbing hidden work. A remote assistant may protect the manager from seeing the strain until quality drops. The check-in is the place to surface it early.

Look for recurring work that has no owner and keeps landing on the assistant by default. Decide whether to formalize it, automate it, or return it to the client. A role that grows through unspoken additions becomes impossible to price or back up. Capacity decisions belong in the meeting, not in a hallway request.

Address attendance and schedule reliability

Review start times, breaks, and any missed coverage against the agreed schedule. Ask about the cause before treating a late start as a discipline issue. Power cuts, transport, and family emergencies are common in remote locations and need a practical response. The manager should know which causes are recurring and which are one-off.

Confirm the plan for the next month's known absences and holidays. Check that the backup named in the coverage plan still knows the current tasks. Update the calendar and the task queue in the same conversation. A schedule that is only discussed verbally tends to fail during the first busy week.

Agree on one change and one support request

End the meeting with one change the assistant will make and one support the manager will provide. A change might be a new checklist step, while support might be a faster approval or a clearer example. Write both with a date and an owner. One concrete pair is more useful than a long list of intentions.

Ask the assistant what would make the next month easier and record the answer even if it cannot be granted now. A request that stays visible can shape the next capacity or tool decision. Review the previous month's pair at the start of the next meeting. The follow-through is what makes the check-in credible.

Close the meeting by confirming the date of the next one and the items each person will bring. A standing slot reduces the chance that the check-in is skipped during a busy month. Send a short written recap within the day. The recap gives the assistant a chance to correct anything that was misheard.

Keep a running record between meetings

Keep a short log of decisions, requests, and follow-ups in one place the assistant can read. Add items as they happen rather than reconstructing the month from memory. The log protects both people when a decision is questioned later. It also gives a new manager a quick history of the role.

Set a fixed time each month and protect it from routine meetings. A check-in that moves whenever the calendar fills will disappear during the busiest periods. Send the agenda and the evidence pack one day ahead so the assistant can prepare. A predictable meeting gives the relationship a rhythm that survives a heavy month.

Review the log before each meeting and remove items that are complete. Leave the open items visible with their owner and date. Share the updated log after the meeting so the assistant has the same record. A running record turns a monthly conversation into a continuous working relationship.