Set a weekly check-in that reviews work, not activity

A weekly check-in should review the work the assistant produced, not the hours spent. Choose a small sample, the open questions, and the next decision. A check-in that reads a task list becomes a status report. Use the same format for every handover so the next reader can scan it. The assistant should record the owner and the date before the next shift. A short note with the requester and the next action is easier to use.

Keep the meeting short and prepare the sample in advance. The manager should see the work before the meeting, not during it. Record the date and the source so the next reviewer can repeat the check. Write the deadline as a date and a local time. The handoff should say what the next person may decide without asking. A short note with the requester and the next action is easier to use.

Pick one routine task, one exception, and one task the client challenged. The mix shows whether the standard holds under pressure. A sample of only easy tasks hides the problem. Use the same format for every handover so the next reader can scan it. The assistant should record the owner and the date before the next shift. Test the brief on one real task before applying it to the whole role.

Send the sample with a short note on what to look for. The assistant should know the criteria before the meeting. Test the rule on one real task before applying it to the queue. Name the owner in the same line as the action. Keep the source link with the task so the next reviewer can check it. Test the brief on one real task before applying it to the whole role.

List the questions the assistant could not answer with the brief. A repeated question is a brief problem, not a performance problem. Update the brief or the source. Name the owner in the same line as the action. The assistant should record the owner and the date before the next shift. The client should know who is handling the question and when to expect an answer.

Record the owner and the date for each open question. A question without an owner will return. Separate what was observed from what was assumed. Keep the boundary visible in the place where the work is assigned. The assistant should record the owner and the date before the next shift.

End the check-in with one decision: continue, adjust, or escalate. Record the decision and the next review date. A check-in without a decision is a conversation. Separate what was observed from what was assumed. Test the brief on one real task before applying it to the whole role. A short note with the requester and the next action is easier to use.

Keep the decision with the work sample. A later review may need to see what was agreed. Use the same format for every handover so the next reader can scan it. Name the owner in the same line as the action. A short note with the requester and the next action is easier to use.

Ask the assistant and the manager whether the check-in helped. A check-in that produces no change is not working. Change the sample or the cadence. Review the first few notes together before the process expands. The handoff should say what the next person may decide without asking. Test the brief on one real task before applying it to the whole role.

For the support model, review the [services page](/services) and the scope it describes. Use the [contact page](/contact-us) when the decision needs a written boundary. The [U.S. Small Business Administration](https://www.sba.gov/business-guide/manage-your-business/manage-your-finances) publishes public guidance on documenting recurring work. Keep the note with the task so the next reviewer can find it. Keep the source link with the task so the next reviewer can check it. Test the brief on one real task before applying it to the whole role.