Why should you document a meeting? Options for documenting a meeting When should you document or record a meeting? Who should document the meeting? How do you document meetings effectively? Following up: What to do with the record A useful meeting may produce decisions, ideas, assignments, questions, commitments, and information that need to be remembered after the conversation ends. If those outcomes exist only in people's memories, they can easily be misunderstood, forgotten, or reopened later because participants remember the discussion differently. Meeting documentation creates an appropriate organizational record of what needs to be remembered and acted upon. The form of that record should match the purpose of the meeting. A project team may need a short decision and action log. A Board may need formal minutes. A planning session may benefit from visible working notes. In some limited situations, an audio or video recording or transcript may be appropriate. These forms of documentation are not interchangeable. They create different privacy, security, accessibility, legal, governance, and retention considerations. Why should the meeting be documented? Appropriate documentation can help an organization in several ways. It preserves decisions. People can verify what was actually decided rather than relying on memory. It supports follow-through. Action items can identify responsible people, deadlines, and next steps. It creates organizational memory. Future staff, volunteers, Board members, or project participants can understand important previous actions. It supports accountability. A record can show who had decision authority and what commitments were made. It can help people who were unable to attend. An appropriate summary may give them the information they need without requiring them to reconstruct the meeting from other participants' memories. It can support governance, compliance, evaluation, or audit responsibilities. Some meetings and decisions require documentation because of organizational policy, governing rules, contracts, or law. It can support learning. Notes from planning, evaluation, or problem-solving sessions can preserve important questions, alternatives, assumptions, and lessons. Documentation does not need to reproduce everything that happened. More detail is not always better. A good record captures the information the organization has a legitimate reason to preserve while avoiding unnecessary personal, confidential, speculative, or irrelevant detail. Documentation can affect participation People may communicate differently when they know their words are being preserved. This is especially important when: Participants have unequal power The discussion involves personnel or sensitive community information People may face consequences for disagreeing Participants do not know one another well The issue is controversial Comments may become public Before the meeting, be clear about what will be documented, whether comments will be attributed to individuals, who will receive the record, and how the information may be used. Do not use an icebreaker or another social technique as a substitute for addressing legitimate privacy or confidentiality concerns. Options for documenting a meeting Choose the least intrusive form of documentation that meets the legitimate need. No formal record Some informal conversations may not require an organizational record. Even then, an important decision or commitment that emerges may need to be documented elsewhere. Personal or working notes Participants may take notes for their own work. Personal notes are not automatically the official organizational record. Be careful about including confidential, speculative, or unnecessary personal information, particularly when notes are stored in organizational systems or may be subject to retention or disclosure requirements. Decision and action log Many operational meetings need only a concise record of: Decisions Action items Responsible people Deadlines Significant unresolved issues Next review date where appropriate A decision and action log can be more useful for day-to-day project management than lengthy narrative minutes. Formal minutes Boards, governing committees, public bodies, and some formal organizational groups may need official minutes. Requirements may come from bylaws, organizational policy, contracts, funding arrangements, law, or governance practice. Formal minutes generally focus on what the body did rather than attempting to reproduce everything participants said. Visible working notes During planning, brainstorming, or problem-solving, it can be useful for participants to see ideas and questions as they are captured. Tools may include: Whiteboards Large paper Shared documents Digital whiteboards Project-management tools Other accessible collaborative systems Visible working notes can help participants correct misunderstandings while the discussion is still happening. They are not automatically the final or official record. Audio or video recordings Audio and video create substantially more sensitive records than ordinary minutes. Before recording, ask: Is a recording actually necessary? What legitimate purpose will it serve? Is recording lawful and permitted by organizational policy? Have participants received appropriate notice or provided consent where required? Who will be able to access it? Where will it be stored? How will it be protected? How long will it be retained? Is there a less intrusive way to meet the same need? Sensitive personnel, legal, clinical, participant, security, or other confidential meetings may be inappropriate to record even when the technology makes recording easy. Transcripts and automated meeting notes Virtual meeting platforms and other tools may create live transcripts, summaries, action items, or searchable meeting notes. Treat these tools as information systems, not simply convenient note-taking features. Before using them, determine: Whether the tool is approved by the organization What audio, text, or other data are sent to the service Where the information is stored Who can access it Whether the information is retained by the provider Whether confidential information may be included Whether the generated output will become an organizational record Automated transcripts and summaries should be reviewed by a responsible person before they are treated as accurate or official. Automated systems may misidentify speakers, omit qualifications, misunderstand technical terms, or describe a discussion as a decision when no decision was actually made. Accessibility tools and retained transcripts are not the same thing Captioning or other communication technology may be necessary to provide effective access during a meeting. Using an accessibility feature does not necessarily mean that the resulting text should be permanently retained as a meeting transcript. Decide separately what the organization actually needs to preserve. When should you document or record a meeting? The answer depends on the meeting's purpose, authority, risk, and applicable requirements. Documentation may be limited when: The conversation is informal No organizational decision or commitment is being made No later follow-up depends on the discussion No policy, governance, contractual, or legal requirement calls for a record If an important decision emerges unexpectedly, document the decision appropriately even if the meeting was originally informal. Formal minutes may be appropriate or required when: A governing Board is meeting A committee has authority to act for a governing body Formal motions or votes occur Organizational governance rules require minutes Law, regulation, contract, or policy requires a formal record Visible working notes may be useful when: Participants are brainstorming The group is comparing alternatives The problem is complex Several concerns or criteria need to remain visible Participants need to confirm that the facilitator or recorder has captured their ideas accurately Decide whether those working notes will be retained after the meeting or used only to create a more focused final record. Detailed documentation may be appropriate when: A high-impact decision requires a clear rationale Significant risks or alternatives need to be documented A funding or contractual requirement calls for it An evaluation or planning process requires a record of major themes Audio or video recording may be appropriate when: Exact language has a legitimate and important purpose The recording is required or specifically authorized Participants have received appropriate notice or consented where required Secure storage, access, and retention procedures are available Recording should not be the default merely because a virtual meeting platform includes a Record button. Different meetings need different records Do not use one recording practice for every type of meeting. Consider separate approaches for: Board and governance meetings Staff meetings Project meetings Community consultations Public meetings Personnel meetings Clinical or confidential service discussions Investigation or legal matters Who should document the meeting? Assign responsibility before the meeting when documentation is important. The appropriate recorder should be able to: Listen accurately Distinguish decisions from discussion Summarize without changing meaning Recognize what information belongs in the record Use the organization's approved documentation system Protect confidential information Ask for clarification when necessary Separate facilitation and documentation when the process is complicated One person can sometimes facilitate and take notes during a short or straightforward meeting. Separate the roles when: The discussion is complex Many participants are involved The facilitator needs to manage conflict or unequal participation Formal minutes are required Detailed visible recording is part of the process This allows the facilitator to focus on the group process and the recorder to focus on accuracy. Formal governance responsibility In a Board setting, a secretary, staff liaison, or another designated person may prepare the minutes according to the organization's governance arrangements. The governing body remains responsible for making sure its official record is accurate and appropriately approved. How do you document meetings effectively? Effective documentation begins with agreement about what kind of record is being created. Clarify the purpose before the meeting Ask: Who needs this record? What will they use it for? Is it a working record or an official record? Will individual comments be attributed? Will it be public, internal, confidential, or restricted? How long should it be retained? Use an approved format A meeting template can improve consistency. Depending on the meeting, fields might include: Meeting name Date and time Location or meeting platform Participants or required attendance information Purpose Agenda items Decisions Action items Responsible people Deadlines Unresolved issues Record what matters Focus on information the organization needs to preserve. Depending on the meeting, that may include: Decisions Significant options considered Important criteria or evidence Material concerns or risks Assignments Deadlines Questions requiring follow-up Do not record a statement merely because it was emotional, provocative, or memorable. Distinguish discussion from decisions A participant proposing something does not mean the group adopted it. Use language such as: Proposal discussed: Extend evening service hours. Decision: Pilot extended hours on Tuesdays for eight weeks. This distinction reduces later confusion. Distinguish paraphrases from quotations Most meeting records should summarize rather than reproduce comments word for word. If exact wording is important: Verify the wording Make clear that it is a quotation Attribute it only where attribution is appropriate Do not place a recorder's paraphrase in quotation marks or make it appear that someone used words they did not use. Ask for clarification If the recorder is uncertain, ask. For example: I have the decision as: "The program will begin in January, subject to final budget approval." Is that accurate? This is especially useful when displaying working notes during the meeting. Use accessible formatting Meeting records should be readable and usable by the people who need them. Use: Clear headings Plain language Descriptive links where relevant Accessible electronic formats Tables or structured fields where they improve clarity Do not rely on color alone to communicate meaning. Protect confidential information Avoid unnecessary detail involving: Personnel Participants or clients Health or disability information Legal advice Investigations Security information Other restricted matters The official record should contain enough information to document the action without creating unnecessary exposure of sensitive information. Document conflicts of interest where relevant Formal governance records may need to identify: A disclosed conflict Whether the person left or abstained from deliberation or voting The resulting action Follow applicable governance policies and requirements. Handle executive or confidential sessions separately Sensitive portions of formal meetings may require a restricted record. Document enough information to preserve required actions and decisions while limiting distribution to authorized people. Do not automatically place confidential discussion into broadly distributed minutes. Create a clear source of truth Modern meetings may produce several artifacts: Collaborative notes Chat messages Whiteboard content A transcript An audio or video recording Automated summaries Formal minutes Identify which one is the official record. The existence of multiple digital artifacts should not create several conflicting versions of what the organization decided. Formal meeting minutes Formal minutes should follow the organization's governing requirements. Depending on the organization, minutes may include: Name of the organization or body Date and time Location or meeting method Members present, absent, or excused where required Whether a quorum was present Motions or formal proposals where applicable Decisions and vote results Abstentions, recusals, or dissents where required or appropriate Significant documents or reports introduced Action items or follow-up responsibilities Adjournment or ending time The level of discussion detail should fit the organization's legal and governance needs. Minutes generally do not need to function as a transcript. Review and approval Draft formal minutes should be reviewed for accuracy according to the organization's process. Once approved, preserve the approved version as the official record. If a later correction is necessary, document the correction according to the organization's procedure rather than silently rewriting historical records. Following up: What to do with the record Distribute it to the right people Different meeting records may have different audiences. A project action log may go to the project team. Board minutes may go to Board members and other authorized people. A public body may have disclosure requirements. A confidential session may require tightly restricted distribution. Do not assume every person who attended should automatically receive every underlying recording, transcript, or confidential attachment. Send useful records promptly People need decisions and assignments while there is still time to act on them. Operational meeting notes may be shared soon after the meeting. Formal governing minutes should be prepared and reviewed according to the organization's governance requirements and timeline. Separate minutes from action tracking where useful Minutes preserve what happened. An action tracker helps manage what needs to happen next. An action tracker might include: Task Responsible person Due date Status Dependencies Escalation if overdue Keeping this information in a project or task-management system may make follow-up easier than repeatedly searching meeting minutes. Store records securely Store organizational records in approved locations rather than leaving the only copy in one person's email, notebook, desktop, or personal cloud account. Apply appropriate: Access controls Backup procedures Security protections Version control Records-retention rules Retain records according to policy and requirements Establish how long different meeting records should be kept. The answer may differ for: Approved Board minutes Project notes Working drafts Audio or video recordings Transcripts Chat logs Confidential records Follow applicable law, governance requirements, contracts, and the organization's document-retention and destruction policy. Do not retain sensitive recordings indefinitely merely because digital storage is inexpensive. Suspend ordinary destruction when preservation is required If a record becomes relevant to litigation, an investigation, an audit, a regulatory matter, or another formal preservation requirement, follow appropriate legal or organizational instructions before destroying it. Control access to recordings and transcripts Audio, video, and transcripts can reveal substantially more information than ordinary minutes. If they are retained: Limit access to authorized people Use appropriate security controls Do not publish them merely because they exist Delete them when the legitimate retention period ends, unless preservation is required Use the record Documentation has little value if nobody uses it. Before the next relevant meeting or review: Check action-item status Bring unresolved issues forward Confirm whether earlier decisions have been implemented Use prior decisions to avoid reopening settled questions without a reason Close the loop with participants If a meeting gathered recommendations or community input but another person or body made the final decision, communicate what happened afterward. Explain: What was heard What was decided What input influenced the result What did not change Why Recording people's ideas without ever explaining what happened to them does not create meaningful participation. In Summary Meeting documentation helps organizations preserve decisions, maintain institutional memory, assign responsibility, and follow through. The goal is not to create the most detailed possible record of everything that was said. Different meetings require different records. A project team may need a decision and action log. A governing body may need formal minutes. A planning process may benefit from visible working notes. Audio, video, transcripts, and automated meeting summaries should be used only when their additional detail serves a legitimate purpose and the organization can manage the resulting privacy, security, access, and retention responsibilities. Good documentation distinguishes discussion from decisions, paraphrases from quotations, working notes from official records, and broadly available information from confidential material. Formal meeting records should follow applicable governance and legal requirements and should be reviewed, approved, stored, and retained according to established procedures. Digital tools can make documentation faster, but they do not eliminate the need for human judgment. Automated transcripts and summaries should be checked before they are relied upon as the official account of what happened. Finally, a meeting record should support action. Decisions should be clear, responsibilities should have owners and deadlines, and important records should remain available to the people who legitimately need them. Contributor Jenette Nagy Bill Berkowitz Resources Print Resources Burleson, C. (1990). Effective meetings: The complete guide. New York, NY: John Wiley. Dashiell, K. (1990). Managing meetings for collaboration and consensus. Honolulu, HI: Neighborhood Justice Center of Honolulu, Inc. Doyle, M. & Straus, D. (1976). How to make meetings work: The new interaction method. New York, NY: Wyden Books. Interaction Associates, Inc. (1987). Facilitator institute. San Francisco, CA: Author. Morrison, E. (1994). Leadership skills: Developing volunteers for organizational success. Tucson, AZ: Fisher Books. Quinlivan, D., & Renner, P. (1994). In search of solutions: 60 ways to guide your problem-solving group. San Diego, CA: Pfieffer and Company.
