Note-Taking Systems for Administrative Assistants

The meeting minutes templates on this site solve the formatting problem — they give you a place to put attendees, decisions, and action items. They do not solve the harder problem, which is what you actually write down while a meeting is in progress. That depends on the meeting type, and on what someone reading the notes a month later needs to recover.

This page covers four note-taking methods that map cleanly onto the meetings administrative assistants attend most often: the Cornell method, the BIO method, simple outline notes, and the decision log. None of them is universally best. Each is best for a specific situation.

How to Choose

Before picking a method, answer two questions:

• Who is the reader? If it's only your executive, optimize for skim-ability. If it's the whole team or the board, optimize for record-keeping and unambiguous language.
• What is at stake if a detail is missed? A team standup tolerates a missed nuance. A board vote does not.

From those two answers, the right method usually selects itself.

The Cornell Method

How it works

You divide each page into three regions: a wide column for raw notes during the meeting, a narrow margin to the left for cues or questions, and a strip at the bottom for a one-paragraph summary written immediately after.

Best for

One-on-one strategy meetings, training sessions, learning-heavy meetings where your executive will want to review the gist later but probably won't re-read the details. The summary strip is what makes it work — by forcing yourself to compress the meeting into three sentences, you also identify what mattered.

Worked example

Quarterly business review with a department head: in the right-hand main area, capture the headline numbers and the explanations for variance. In the left-hand cue column, write the questions you'd want to follow up on ("why did the renewal rate dip in Q2?"). In the summary strip at the bottom, write what changed since last quarter and what's now expected by next quarter. Your executive opens this once, reads the summary, and only dips into the detail if a question is raised.

Limitations

Cornell is slow if action items pile up. Use a different method for any meeting where the output is mostly tasks.

The BIO Method (Background, Information, Outcomes)

How it works

Every meeting note is structured into three blocks: the Background (one or two lines on why this meeting happened), the Information exchanged, and the Outcomes — decisions made, actions assigned, and follow-ups scheduled.

Best for

Cross-functional meetings, vendor reviews, and any meeting where the people reading the notes weren't in the room. The background block is what saves the reader; without it, "we agreed on Option B" is meaningless three weeks later.

Worked example

Vendor selection meeting for a new conferencing platform:

• Background: Current contract expires in 90 days; IT requested a recommendation by next Friday.
• Information: Three vendors evaluated; pricing, security, and integration notes per vendor.
• Outcomes: Vendor B selected. Procurement to draft contract by [date]. IT to schedule rollout. Communication plan due to leadership next week.

Limitations

BIO works less well for meetings without a clear endpoint, like brainstorming sessions or open Q&A.

Outline Notes

How it works

Hierarchical bullets following the meeting agenda. Each agenda item becomes a top-level bullet; sub-bullets capture detail; action items are flagged inline.

Best for

Standing meetings with a stable agenda — staff meetings, weekly leadership syncs, recurring project check-ins. The structure forces consistency over time, which makes the notes searchable as a body of work.

Worked example

Weekly leadership team meeting follows the same five agenda items every week. Outline notes from the past six weeks become a usable history of what was discussed under "Hiring," what under "Customer escalations," and what under "Budget." Tracking the same agenda item over time exposes drift — a topic that's been "on the agenda" for four weeks without resolution becomes obvious.

Limitations

Outline notes are unwieldy for meetings without a fixed agenda, and they can mislead — neat-looking bullets sometimes hide that no decision was actually reached.

The Decision Log

How it works

Instead of capturing the conversation, you capture only the decisions. Each entry has the date, the decision, the rationale in one sentence, who is accountable, and what would have to change to revisit it.

Best for

Board meetings, executive committee meetings, hiring decisions, and any meeting where the durable artifact is the decision rather than the discussion. A decision log is also the single most useful document to maintain across multiple meetings — it captures the reasoning that emails and minutes routinely lose.

Worked example

Decision log entry from a board meeting:

• Date: April 14, 2026
• Decision: Approve the proposed budget reallocation from marketing to product.
• Rationale: Marketing CAC has plateaued; product engineering capacity is the current growth bottleneck.
• Owner: CFO and Head of Product, jointly.
• Revisit if: Q3 product velocity does not improve, or marketing efficiency falls below the target floor.

Limitations

A decision log on its own is not minutes — for formal meetings you still need a minutes document. Use the log alongside, not instead of, formal minutes.

Paper, Tablet, or Laptop?

The right tool depends less on personal preference than on what the meeting will tolerate. Three considerations dominate:

Eye contact and trust

In small high-trust meetings — a 1:1 with your executive, a sensitive HR conversation, a candidate interview — typing on a laptop creates a barrier that paper or a tablet does not. The other person reads the screen as a wall and adjusts what they say. If the meeting depends on candor, paper or a tablet held flat is a better fit. The trade-off is slower capture, which is usually worth it.

Searchability afterward

Paper notes are gone the moment the meeting ends unless you photograph or transcribe them. If you take notes that need to be referenced months later — vendor decisions, board discussions, anything that might come up in a future audit — type them, or write them on paper and transcribe within twenty-four hours. The transcription step is also useful editorial work; it forces you to drop the noise.

Distraction

Laptops are the easiest place to be obviously distracted. If you are taking notes for someone else's benefit — your executive, the team, the record — being visibly present matters. Close the laptop's other tabs before the meeting starts, or use a tablet in a single-app focus mode. Notetakers who multitask during meetings get noticed faster than they realize, and almost never positively.

The hybrid that works

Many strong notetakers run a deliberate hybrid: a small notebook for the meeting itself, then a thirty-minute block within an hour of the meeting to convert the notes into the right digital format — outline notes for the team's standing recurring meeting, BIO-formatted summary for the cross-functional update, decision log entries where applicable. The notebook becomes the rough capture; the digital file becomes the artifact.

Sharing Notes Without Causing New Problems

The harder half of note-taking is what happens after. Notes that go unsent are only useful to you. Notes that go to the wrong audience cause new problems.

Confirm the audience before you write

The same meeting can produce three different documents depending on who is reading. Internal team notes can be candid; notes that include the board chair or external counsel cannot. Decide before the meeting whether the artifact is private, internal, or external, and write to that audience from the first line.

Send a summary, not the raw notes

For most meetings, the right post-meeting deliverable is a five-line summary email — what was decided, what is owed, by whom, by when, and what the next checkpoint is. The full notes live in your file system as backup. Sending raw notes invites re-litigation of the meeting in reply-all, which is the single most predictable way to undo a decision that was already made.

Confidentiality flags belong in the file name

If a note contains anything that should not be shared casually — names of candidates, salary figures, in-progress legal matters, M&A discussion — flag it in the file name itself, not just inside the document. "Q3-board-CONFIDENTIAL.docx" is harder to forward by accident than "Q3-board.docx." This is the same principle that makes the desk manual reference passwords rather than store them.

Common Mistakes

• Trying to capture everything. Verbatim notes are noise. The brain that reads them later is not your brain.
• Skipping the post-meeting clean-up. Notes are draft material. They should be tidied within an hour, while the meeting is fresh, not three days later when half the context is gone.
• Putting action items in only one place. Actions belong in your task tracker, not just in the meeting notes. If they live only in the notes, they get missed.
• Using one method for every meeting. The whole reason for choosing among methods is that meetings differ. A standing meeting and a vendor selection meeting do not benefit from the same structure.

Putting It Together

If you support an executive who attends ten meetings a week, you are likely to use three of these methods in rotation: outline for the standing rhythm, BIO for the cross-functional and vendor work, and a decision log running across both. Cornell is the one to reach for when the meeting is a strategy or planning session that produces ideas more than tasks.

Whichever method you use, store notes somewhere your future self and your successor can find them. This is one of the small disciplines that turns a competent admin into a person whose absence is felt — and it's one of the things that should live in your desk manual for whoever covers your role on your next vacation. If meeting coordination itself is also part of your remit, the broader playbook is in the scheduling and meeting coordination guide.