Choose three fields and keep them fixed
A daily note works when the reader knows where to look. Use three fields: what moved, what is blocked, and what needs a decision. Add a fourth field only when the role has a recurring risk that the first three cannot capture. A fixed format lets the manager scan the note in under a minute.
Write the note at the same time each day so the manager can plan around it. Send it in the same channel, not sometimes in chat and sometimes in email. If the day has no movement, say so rather than skipping the note. A missing note is indistinguishable from a missed day.
Set a rule for days when the assistant is out of the office. The covering person should send the same note under their own name or mark it as a cover note. Do not let the regular assistant write retrospectively for a day they did not work. The record should show who actually observed the work.
Report movement as a result, not an activity
I worked on the report is an activity. The report is ready for review is a result. Ask for the result and the next step. If the task is not finished, state what remains and when the next check will happen. A result-based note tells the manager whether to act.
Link the result to the file or message where it can be seen. A short link saves a search and makes the note verifiable. If the result is a decision, name the person who made it. Do not describe a decision as movement unless it is actually settled.
Ask for the one thing the manager should look at first if they have only a minute. That line forces the assistant to prioritize and gives the manager a fast entry point. It is not a substitute for the fields. It is a reading aid for a busy morning.
Make blockers specific and owned
A blocker is something the assistant cannot resolve without another person. Name the person and the exact question. Waiting on the client is too vague. Waiting on the client's finance lead to approve the revised invoice is specific enough to act on.
Record how long the item has been blocked and what happens if it stays blocked. A blocker that is three days old needs an escalation, not another day of waiting. The note should show the owner and the next follow-up date. The manager can then decide whether to intervene.
Ask for the next action even when the task is complete. A completed task may need a review, a filing, or a client message before it is truly closed. The next action keeps the note connected to the work that follows. It also stops a task from being marked done when only the draft is finished.
Separate a decision request from a question
A question can be answered from the reference library or by a quick reply. A decision changes what the team will do and needs the person with authority. Label the two differently so the manager does not treat every question as a decision. The assistant should not wait for a decision when a lookup would answer the question.
For each decision request, state the options and the recommended option. Give the manager enough context to decide without reopening the whole task. Record the decision and the date it was made. The next note should show the action that followed.
Record the decision request even when the manager answers in a chat message. A verbal or chat approval can be missed by the next shift. Copy the decision into the note with the time and the person. That small step turns a conversation into a record.
Keep the note short enough to survive a busy day
A stand-up note is not a daily report. Keep it to a few lines per field and link to the detail. If the note takes more than ten minutes to write, the format is too heavy. A short note written every day is more useful than a thorough note written once a week.
Use plain language and avoid internal shorthand that a new reader would not know. The note may be read by a backup manager or a client owner. A short glossary at the top of the channel can help. Review the glossary when a new term appears.
Keep the last five notes in a thread rather than deleting them each day. The thread shows how a blocker developed and whether the same issue returns. A manager who reads only today's note may miss a pattern. The thread is also useful when the role is handed to a new manager.
Review the note format after two weeks
After two weeks, ask the manager whether the note changed any decision. If the answer is no, the fields may be reporting activity rather than supporting action. Remove a field that nobody uses and add one that answers the missing question. Keep the change small and test it for another two weeks.
Ask the assistant whether the note created work or reduced it. A format that forces a daily hunt for something to say will produce filler. A format that captures real blockers will save messages. Record the answer with the format version so the next manager can see why it changed.
Review the note with a backup manager who has not seen the role before. If they cannot tell what needs attention, the fields are not doing their job. Ask them which line they would act on first. Their answer shows whether the note is written for the reader or for the writer.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration — Hire and manage employees guidance on clear expectations and regular communication with a new team member.
Related reading
Write a first-week decision log for a new virtual assistant
A first-week decision log that records what the assistant decided, what was escalated, and which instruction needs to change before the second week.
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.
