Meeting minutes on a resume: show decisions and follow-up

Decide whether meeting minutes are relevant

Meeting minutes can demonstrate more than fast typing. For administrative, project support, operations, and committee roles, the useful work is capturing decisions accurately, identifying owners, and making the next step findable. Read the job posting first. If it asks for meeting coordination, documentation, records, or action tracking, your notes may be worth a bullet.

If you only attended meetings, do not claim that you prepared minutes. If note-taking was a small part of a broader role, place it within the relevant experience entry rather than creating a separate section. A resume should show the value of the work, not list every meeting you joined.

• Who asked you to record the meeting, and how often did you do it?
• What did the notes contain: decisions, owners, deadlines, open questions, or only a transcript?
• Who reviewed or used the record afterward?

Describe the workflow you actually owned

Think through your work before, during, and after the meeting. You might have prepared an agenda template, captured decisions, checked names and dates, circulated a draft for corrections, or updated an action log. Name only the stages you handled. Writing the notes is different from chairing the meeting or approving its decisions.

For example, an assistant who drafted notes and sent them for approval can write that they prepared and circulated minutes for review. They should not say they finalized board decisions if another person approved the record. The same distinction applies to tracking tasks: recording an owner is not the same as managing that owner or guaranteeing completion.

Turn the work into a specific resume bullet

Use a simple pattern: action + meeting context + useful output or follow-up. A bullet might read, if true: “Prepared weekly project meeting minutes, confirmed action owners with the facilitator, and updated the shared action log after review.” The context and the output make the task more concrete than “Took meeting notes.”

Another example for a committee secretary might be: “Drafted committee minutes from agenda items and recorded approved motions, owners, and due dates in the official template.” Adapt the wording to the process you actually used. Do not add “approved” if you recorded proposed actions before the committee confirmed them.

• Too vague: Took notes during meetings.
• More useful, if accurate: Summarized weekly service review decisions and circulated action items to assigned owners after manager review.
• If your role ended at the draft: Prepared minutes for the chair to correct and approve; avoid claiming ownership of the final record.

Show follow-up without inventing outcomes

Follow-up can be a strong part of this example, but be precise. Perhaps you maintained an open-items list, sent reminders under an agreed process, or flagged an unresolved decision before the next meeting. Say what you did and where you handed off the issue. Do not claim that your minutes reduced delays or improved productivity unless you have evidence for that result.

A verified output can be enough: a reviewed record, an updated tracker, or an agenda that identifies unfinished items. If you know a reliable volume, such as the number of recurring meetings you supported, use it only when it adds context. Avoid counting attendees or decisions just to make a routine task sound larger.

Tailor the detail to the role

For an executive assistant role, accuracy, discretion, and clear distribution may matter most. For project coordination, highlight action owners and the next review date. For a records-focused role, emphasize the template, review, and storage process. Use the terminology in the posting only when it accurately describes your work; do not call informal team notes formal minutes.

Mention tools only when they clarify the workflow. A shared document or action tracker may be useful context, but a list of software names is not a substitute for explaining what you recorded. If the posting asks for confidential records, keep any resume example general and do not publish internal decisions, names, or restricted attachments.

• Administrative support: Emphasize accurate records and review before distribution.
• Project support: Emphasize owners, deadlines, and open-item tracking.
• Committee support: Emphasize the approved template and the boundary between drafting and approval.

Check the final claim and layout

Read the bullet as someone outside your organization. Can they tell what kind of meetings you supported and what record you produced? Remove internal acronyms and sensitive details. Check that verbs such as drafted, reviewed, circulated, and maintained match your actual responsibility. Keep the example to one or two lines if other accomplishments need room.

Compare the bullet with the rest of your application so your title, dates, and level of ownership remain consistent. CreateResume can help you revise a structured experience entry and preview the PDF-ready resume. Open the exported PDF and verify that the bullet stays legible and the document contains no private meeting details.