Philippines staffing guide · Published
On this page
Write a meeting-notes quality bar for client calls
A practical quality bar for client-call notes: the decisions, the owners, the dates, and the plain-language summary that keeps a distributed team aligned.
Client-call notes are often judged by how complete they look rather than by whether they help someone act. A polished page can still omit the one decision the client made or the person who agreed to send the file. A written quality bar gives the assistant a specific target and gives the reviewer something concrete to check. It also protects the client from being surprised by an action nobody recorded.
The bar should be short enough to apply during a busy week. It should define what must appear, what may be summarized, and what must never be included. Apply it to a sample of calls each month instead of every note. That keeps the review useful without turning it into a bottleneck.
Define the decisions the notes must capture
Every client call should produce a short list of decisions, even when the decision is to wait. A decision states what will happen, what will not happen, and who agreed. If the call only shared information, say that explicitly so a reader does not invent a decision. A note without this section is a transcript summary, not a record.
Use the client's own words for a decision when the wording matters. For example, record that the client approved the revised scope rather than that the call went well. If the decision was conditional, write the condition beside it. The next reader should not have to guess what would make the decision change.
Separate what was said from what was agreed
Discussion and agreement are different, and mixing them creates disputes. Put background comments, options, and concerns in one part of the note and confirmed items in another. Label the confirmed part clearly so it can be forwarded to the client without extra editing. This separation also shows when a topic was raised but not resolved.
When a participant floats an idea, record it as an option rather than a plan. Name who raised it and whether anyone responded. That prevents an exploratory comment from becoming an accidental commitment. If the client later asks why something was not done, the note shows the idea was never approved.
Name owners and dates for every action
Each action needs one owner and one due date, even when the date is approximate. Use a person's name or role, not the word team, because shared ownership usually means no ownership. If the client owns the action, say so and note the expected response date. The assistant should not leave the call without knowing who does what next.
For actions that depend on someone else, record the dependency beside the date. A filing that waits on a client signature is different from a filing the assistant can complete today. Add the channel where the action will happen, such as email or the shared portal. The next reader should be able to start the action without opening the recording.
Standardize the note's shape without scripting it
Use the same section order for every client call: attendees, purpose, decisions, actions, and open questions. A consistent shape lets a reader find the important part in seconds. It also makes gaps visible when a section is empty. Keep the headings plain and avoid clever labels that change from call to call.
Do not force the assistant to write the same sentences every time. The structure is fixed, but the language should reflect the actual conversation. Provide one strong example and one weak example so the difference is concrete. Reviewers should comment on missing substance, not on stylistic preference.
Review a sample against the bar each month
Choose five calls from the month, including one difficult or unusual conversation. Check each note for decisions, owners, dates, and a clear open-question list. Mark the first place a reader would have to ask a follow-up question. That mark is more useful than a general score because it points to a specific gap.
Share the findings as a short list of patterns, not a ranking of assistants. If three notes miss the same field, fix the template or the call handoff rather than coaching each person separately. Update the example note with a better version of the weakest section. Repeat the sample next month to see whether the change held.
Close the loop after the call
A note is not finished when it is sent. The assistant should check that each action reached the task queue and that the owner saw it. Record the queue reference beside the action so the link is visible. If an action cannot be added to the queue, say why and who is tracking it elsewhere.
Send the client a short summary within the agreed window, even when the note is internal. The summary should repeat the decisions and the client's own actions, not the full discussion. Ask for a correction if anything is wrong. That small step catches a misunderstanding before it becomes a missed deadline.
Handle sensitive calls with a tighter rule
Some calls involve personal, financial, or legal details that should not sit in a general notes folder. Define which topics require a restricted note, who may read it, and how long it is kept. Record only what the follow-up work needs, not the full conversation. When in doubt, ask the client before writing sensitive detail.
Store restricted notes in the approved location and link to them from the main record without copying the content. Do not paste sensitive details into chat or email summaries. Review access when a team member leaves the account. A tight rule protects the client and gives the assistant a clear boundary.
Questions and operating boundary
Do we need to record every call?
Record calls that produce a decision, an action, or a client commitment. Routine internal updates can be summarized in the queue instead.
Should notes quote the client directly?
Quote only when the exact wording matters, such as a scope boundary or an approval. Otherwise paraphrase accurately and keep the quote short.
Who reviews the notes?
The account lead or a senior assistant reviews a monthly sample. The reviewer checks substance and completeness, not writing style.
Source
ftc.gov provides authoritative background and does not endorse this service.