Key takeaways
- Count only actions that name a change, an owner, and a review date.
- Separate a decision-only check-in from one with no recorded outcome.
- Track whether actions are completed by the next check-in.
- Keep the meeting short by removing questions that no longer produce a decision.
Question and scope
This study asks what share of first-month check-ins end with a documented action that names an owner and a date. It treats the check-in as the unit and the written note as the evidence. The scope is one virtual assistant role and a fixed first-month window. The result describes that role and should not be read as a standard for other teams.
A check-in is eligible when it is a scheduled conversation between the assistant and the manager or reviewer about the role. Informal messages and task-specific clarifications are excluded. A documented action is eligible when the note names what will change, who owns it, and when it will be reviewed. The definitions should be recorded before the notes are coded.
The study also records whether the action belonged to the manager or the assistant. A check-in that only produces actions for the assistant is a performance review in disguise. A balanced record is more likely to show a working conversation. Report the owner mix beside the action rate.
| Outcome | Evidence | Follow-up |
|---|---|---|
| Documented action | Named change, owner, date | Check completion next week |
| Decision only | Choice recorded with reason | Confirm the rule still fits |
| No outcome | Note has no action or decision | Ask what blocked the close |
Definitions and evidence standard
Define a documented action as a specific change with an owner and a review date. A statement such as improve communication is not an action because it cannot be checked. A statement such as add a backup approver to the intake form by Friday is an action. The note should contain enough detail for a reader who was not in the meeting.
Use the check-in note, the role card, and the task record as the evidence. Do not count an action that was discussed but never written down. A later message that confirms the action can be used if it names the owner and the date. Memory is not evidence, even when both people agree on what happened.
Separate an action from a decision. A decision records a choice, such as keeping the current review route, while an action records a change. A check-in may end with a decision and no action, which is a valid outcome. Code the two categories separately so the result does not treat every quiet week as a failure.
Sampling and measurement
Collect every scheduled check-in in the first month and freeze the list before coding. If the role started midweek, include the partial week and note it. Read the note in full rather than searching for action words. A note may describe an action without using the word action.
Measure the number of check-ins, the number with at least one documented action, the number with a decision only, and the number with no recorded outcome. Add the number of actions that were completed by the next check-in. Report the counts by week and by action owner. A high action count with low completion is a different problem from a low action count.
If a check-in produced several actions, count the check-in once but record the number of actions. A long list can look productive while nothing is completed. Report the list length beside the completion count. That combination shows whether the meeting is generating realistic commitments.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of decision-only check-ins may mean the role is stable and the conversation is working. A cluster of no-outcome check-ins may mean the notes are not being written or the meeting lacks a closing step. Read the actual notes behind the largest group before naming a reason.
Compare the action rate with the number of open items from the previous week. A week with many open items may produce fewer new actions because the team is still finishing old ones. Report the open-item count with the result. The ratio is more informative than the action count alone.
Check whether the actions were completed by the next check-in. An action that rolls forward repeatedly may be too large or may lack an owner with time. Report the rolled-forward count separately. A pattern of rollover is a stronger signal than a single unfinished item.
Limitations
The note reflects what was recorded, not everything that was agreed. A useful conversation may leave no written trace, and a thin conversation may produce a polished note. The study measures documentation and follow-through, not the quality of the relationship. It also cannot show whether the action improved the work.
The first month may contain unusual setup tasks that produce more actions than a steady month. A later month may look quieter without being less effective. The sample also depends on the manager's note-taking habit, which may change during the period. These limits should be stated with the result.
Coding an action requires a judgment about whether the statement is specific enough to check. Two reviewers may disagree at the margin. Record the disagreements and resolve them with examples before reporting. A short calibration set improves consistency more than a longer definition.
Practical next step
Add a closing line to the check-in template that asks for one action, one owner, and one date. The line should be completed before the meeting ends. A template that leaves the action for later usually produces a summary instead of a commitment. The manager should read the line back to confirm it.
Review the actions from the previous week at the start of the next check-in. A short status for each action takes less time than reconstructing the history. If an action rolled forward, ask whether it should be split or dropped. The review should change the list rather than simply report it.
Test the template for three weeks and compare the action completion rate with the baseline. Keep the change if it produces clearer commitments without lengthening the meeting. If the meeting grows, remove a question that no longer earns its place. The goal is a short conversation with a visible result.
Comparing manager-owned and assistant-owned actions
Compare actions owned by the manager with actions owned by the assistant. A manager action often changes a rule, a permission, or a review route, while an assistant action often changes a habit or a checklist. Both are useful, but they need different follow-up. Reporting them together can make the assistant's workload look larger than it is.
Look at the completion rate for each owner. Manager actions may stall because the manager has competing priorities, while assistant actions may stall because the instruction was unclear. The pattern points to different repairs. A low manager completion rate may mean the check-in is creating work the manager cannot absorb.
Ask whether the assistant had the authority to complete their actions without another approval. An action that depends on an unstated approval is not really owned by the assistant. Record the dependency when it exists. The action list should reflect the real route, not an idealized one.
What the evidence does not show
The study does not prove that a check-in with an action is better than one without. Some weeks need a decision or a listening conversation rather than a new task. It also does not measure whether the action addressed the most important issue. A well-documented action can still be the wrong response.
It does not show that the manager is responsible for every missing action. The assistant may not have raised a blocker, or the note may have been lost. The result describes the recorded outcome, not the intention. A review should ask what prevented the action from being written.
It cannot be used to compare assistants or managers across teams. The role, the client, and the note format differ too much for a fair comparison. The local result is a prompt for a better process, not a ranking. A different team should repeat the method with its own definitions.
Using the result in a manager conversation
Share the distribution and ask the manager which kind of check-in they expected. The answer may reveal that the meeting was designed for status rather than decisions. A status meeting can be useful, but it should not be judged by an action count. The team should agree on the purpose before changing the template.
Ask the assistant which action was easiest to complete and which one was unclear. The answer often identifies a missing owner or an unrealistic date. Use one example to revise the closing line rather than rewriting the whole template. A concrete example is easier to act on than a general discussion.
Close with a small experiment for the next month and a date to review it. The experiment might be one action per check-in or a five-minute review of the previous list. Record the baseline so the result can be compared. The review should keep the change only if it improves the conversation.
Sources and methodology
The study reads each first-month check-in note and codes the outcome as a documented action, a decision only, or no recorded outcome, with owner and completion data.
- U.S. Small Business Administration — Hire and manage employees current.
- U.S. Office of Personnel Management — Training and development current.
- U.S. Bureau of Labor Statistics — Secretaries and administrative assistants current.
- U.S. Cybersecurity and Infrastructure Security Agency — Secure Our World current.
Source count: 4. Last verification date: November 9, 2026.
Questions about the findings
Is a decision-only check-in a failure?
No. A stable week may need a confirmation rather than a new task. The important point is that the decision is recorded.
Should every check-in produce an action?
No. Forcing an action can create busywork. The template should ask for one only when a change is needed.
How do we know an action was useful?
Check whether it was completed and whether the problem it addressed returned. Completion alone is not proof of value.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.
