Start the log on day one
A first-week decision log records the choices the assistant makes while the role is still new. Start it on the first morning, before the first real task lands. The log is not a performance review and not a task list. Its purpose is to show which decisions were clear, which needed a question, and which instruction was missing.
Ask the assistant to add one line whenever a task required a judgment that the written instructions did not cover. Include the task, the decision, the reason, and the person who confirmed it. A short line written at the moment is more reliable than a Friday reconstruction. The log should take seconds, not minutes, or it will be abandoned during a busy day.
The log should name the source the assistant used to make the decision, such as a template, a previous message, or a named person. That field explains the basis of the choice without requiring a long narrative. It also shows which sources are actually trusted in daily work. A source that nobody cites may be a document that needs replacing.
Separate routine choices from escalations
Most first-week decisions are routine, such as choosing a file name or ordering a reply. Record those only when the choice could set a precedent. Escalations deserve a separate row because they show where the role boundary sits. A request to approve a refund, contact a client directly, or change a deadline is an escalation, not a routine choice.
For each escalation, record the question, the person who answered, and how long the answer took. A slow answer may mean the escalation route is wrong, not that the assistant is slow. If the same question is escalated twice, the instruction needs to change. The log turns repeated questions into a repair list.
Record the time between the request and the decision, not only the decision itself. A fast answer may show a clear route, while a slow answer may reveal a missing owner. Use the timing to start a conversation about the route rather than to score the assistant. A pattern of slow answers is a process signal.
Record the instruction that was missing
When a decision required a guess, write the guess and the gap it exposed. A missing rule about which folder to use is a documentation problem. A missing rule about who may approve a client-facing change is a boundary problem. Label the gap so the reviewer can route it to the right owner.
Do not rewrite the whole instruction set on day two. Choose the gap that caused the most rework or the most waiting and fix that one. Record the change and the date. The next log entry should show whether the fix worked. A small, tested change is more useful than a large document written after one week.
Ask the reviewer to confirm the gap rather than only the decision. A manager may see a missing rule that the reviewer would have answered from habit. Comparing the two views shows whether the instruction is missing or merely hard to find. That distinction decides whether to write a new rule or reorganize the existing one.
Keep the client out of the raw log
The raw log may contain client names, message details, or account information. Keep it in the approved workspace and limit access to the manager and the reviewer. When the log is shared more widely, remove client identifiers and keep the decision pattern. The pattern is what teaches the next role, not the name on the file.
If a client asks how the assistant is being supervised, describe the decision categories rather than the log itself. The client does not need to read individual entries to understand the control. Ask the client-side owner whether their policy requires a different record. Adapt the log rather than keeping a parallel private version.
Ask the client-side owner which entries can be shared in a monthly summary. A client may want to see the categories without seeing individual messages. Agree the summary format before the first review so nobody has to redact a document under pressure. That agreement also sets the boundary for future logs.
Review the log at the end of week one
Set a review at the end of the first week with the assistant, the manager, and the reviewer. Read the log in order and mark each entry as clear, clarified, or still open. Count the entries by type. A cluster of escalations in one category points to a boundary that needs a written answer.
Ask the assistant which decision felt risky and which instruction was hardest to find. The answer may not match the manager's view, and that difference is useful. Record the agreed changes and the date they take effect. Do not close the review without at least one concrete change to the instructions or the route.
Invite the assistant to propose one change to the instructions. A person who has just used the material often sees the confusing step that the author stopped noticing. The manager decides whether to adopt it, but the proposal should be recorded either way. That habit builds ownership without giving away the approval boundary.
Carry the log into the second week
Keep the log for the second week but reduce the required detail. The goal is to move from capturing every decision to capturing only exceptions. If the same category stays quiet, the instruction is probably working. If a new category appears, add it to the review.
At the end of the month, compare the first-week entries with the current ones. A drop in routine questions suggests the reference material is improving. A rise in escalations may mean the role is taking on more judgment, which needs a different review. Record the interpretation so the next manager does not read the numbers as a simple score.
Keep a short list of recurring decisions beside the log, not inside it. The list can become a quick reference for the next assistant without exposing the week's details. Update the list only when a decision is confirmed by the owner. A reference built from unconfirmed guesses will spread the wrong answer.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration — Hire and manage employees guidance on setting expectations and managing a new working relationship.
Related reading
Define a daily stand-up note that replaces status chasing
A daily stand-up note with three fixed fields that gives the manager the decisions, blockers, and next actions without a round of status messages.
Build a reference library a virtual assistant can search in one pass
A small reference library with stable names, a visible owner, and a search rule that lets a virtual assistant find the current answer without asking twice.
