How Consistent Are Meeting Notes Across Offshore Executive Assistants?

Research question and decision supported

The question is how consistently offshore executive assistants capture decisions and actions from comparable meetings. The decision supported is whether the note template, the meeting format, or the assistant's instruction needs repair. A note can be well written and still omit the decision that the executive needed to see. The method measures the presence and accuracy of decisions and actions, not the length or style of the prose.

State whether the comparison covers the same meeting type, the same executive, or the same assistant group. Notes for a project update and notes for a personnel discussion have different privacy and detail requirements. Report the scope beside the consistency rate. The decision should follow the scope that produced the finding.

Define the scoring unit

Score the decision and the action as separate units. A decision record should identify the question, the outcome, the decision owner, and the date. An action record should identify the task, the owner, and the due point. Do not score a note as complete because it mentions the topic without recording the outcome. Use a short coding sheet with examples of a complete and an incomplete entry.

Write the definition with the executive's own examples where possible. An executive may treat a directional comment as a decision, while the assistant treats it as discussion. Clarifying that boundary before scoring prevents the review from measuring two different standards. Keep the examples with the coding sheet and review them when a new assistant joins.

Draw comparable meetings

Select meetings of the same type and similar length. Include meetings with a clear decision and meetings where the outcome was deferred. Include recurring and one-off meetings so the sample is not dominated by a familiar format. Exclude meetings with no note or with a note that is explicitly marked as incomplete. Record the meeting type, assistant, date, and number of decisions and actions.

Check that the sample includes each assistant who documents the meeting type. If one assistant is missing, the result cannot describe that assistant. Compare the meeting agendas and the follow-up messages to establish what actually happened. The agenda and follow-up are not the note, but they provide a reference for the decisions and actions that should appear.

Measure missing and incorrect entries

Count decisions and actions that are missing, incomplete, or wrong. Missing means the note does not mention the item. Incomplete means the note mentions it without the owner or due point. Wrong means the note records a different decision or owner than the meeting record supports. Report each category separately. A note with one wrong owner is more dangerous than a note with one missing low-priority action.

Use the follow-up message and the task system to confirm the owner where available. Do not assume that the note is wrong because the follow-up changed the decision later. Record the date of the change and treat it as a separate event. The scoring should reflect what was known at the time of the meeting.

Compare by assistant, meeting type, and template

Group the results by assistant, meeting type, and template version. Look for a template that produces missing actions or a meeting type that produces missing decisions. Compare assistants only after checking the meeting mix and the executive's instructions. A new assistant may document harder meetings or receive less context. Do not rank people from a small sample without reading the cases.

Ask two reviewers to score an overlapping sample and discuss the differences. A disagreement often reveals a vague decision definition or an action that was implied but never stated. Revise the coding sheet before changing the training. Record the calibration result and the version of the definition used.

Test the note template

Take a small set of meetings and rewrite the notes using the proposed template. Ask the executive to find the decisions and actions without reading the full note. Measure the time and the number of misses. If the template adds sections without improving retrieval, remove them. A good template makes the important items easy to find, not the document longer.

Test the template on a recurring meeting and on a one-off meeting with an unusual decision. Check that sensitive material still has a place to be omitted or restricted. Confirm that the action owner and due point are visible without opening another system. The template should support the assistant's judgment rather than replace it.

Use the result to change one instruction

Choose the most common gap and change one instruction or template field. If decisions are missing, add a decision prompt to the meeting agenda and the note template. If actions lack owners, require an owner field before distribution. If an assistant is unsure about authority, add a short decision guide with examples. Assign an owner and a review date, then repeat the review with the same meeting types.

Confirm that the change was delivered. Check the template version, the agenda, and the assistant's guide. A note standard that lives only in a training session will fade. Ask the executive whether the change improved the note they actually use, not just the note's completeness score.

What the result does not tell you

The review measures whether the written note contains the decision and the action, not whether the meeting itself was well run. A meeting with no clear decision will produce an incomplete note even when the assistant performs well. Read the agenda and the follow-up before blaming the template for a missing outcome. The result also does not show whether the executive used the note after it was distributed.

A note can be complete and still arrive too late to be useful. Record the distribution time and ask the executive whether the note reached them before the next decision point. A timely note with one missing action may be more valuable than a perfect note delivered the next day. The review should include timeliness when the meeting drives same-day work. The same principle applies to corrections: an updated note that nobody sees does not fix the record. Add the correction time and the recipients to the record so a later review can confirm that the change reached the people who relied on the original note.

One short reporting note should accompany the result. State the meeting types, the number of notes, the template version, and the categories that were scored. List the two most common omissions and the owner who will correct them. Avoid a single headline score that hides the difference between a missing decision and a missing action. A reader should be able to see which part of the note system failed and what change will be tested next.

Limitations

The method depends on a reference record for what happened in the meeting. The agenda and follow-up messages may themselves be incomplete, and a decision may have been made in a side conversation. Reviewers may disagree about whether a statement was a decision. Small samples and different meeting types make the consistency rate unstable, and a change in the template can create apparent improvement before behavior changes.

A missing entry is not proof that the assistant was careless. It may mean the meeting had no clear decision or the executive asked for a different format. Use the result to improve the note system, not to judge an individual from one sample. Report the meeting types, the definitions, and any template change so the next review is comparable.

Sources

1. U.S. Small Business Administration, Manage your business
2. NIST Cybersecurity Framework 2.0
3. U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics
4. Federal Trade Commission, Data Security
5. U.S. Department of Labor, Employer Responsibilities
6. NIST Privacy Framework
7. U.S. Department of Labor, Recordkeeping
8. NIST SP 800-53, Security and Privacy Controls
9. Internal Revenue Service, Recordkeeping
10. U.S. Small Business Administration, Manage your finances