[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-zh-\u002Fhow-to-write-meeting-minutes":3},{"page":4,"surround":600},{"id":5,"title":6,"authors":7,"badge":10,"body":11,"date":576,"demo-cta":577,"description":578,"extension":579,"genre":580,"heroOrder":581,"icp":582,"image":585,"meta":586,"navigation":587,"no-translate":577,"path":588,"rank-country":581,"rank-keywords":589,"rank-tag":595,"seo":596,"stem":597,"updated":581,"video":598,"__hash__":599},"blog_zh\u002Fblog\u002Fhow-to-write-meeting-minutes.md","如何撰写会议记录：格式、模板、示例——以及现在由谁来撰写（2026）",[8],{"name":9},"The Mind.com Team","Guide",{"type":12,"value":13,"toc":563},"minimark",[14,19,23,26,31,34,108,116,128,132,135,186,189,193,199,205,211,214,360,363,416,419,423,430,433,437,449,456,459,480,483,488,491,496,505,510,513,518,521,526,532,537,540,545,548,551],[15,16,18],"h1",{"id":17},"如何撰写会议纪要格式模板示例以及如今谁来撰写2026","如何撰写会议纪要：格式、模板、示例——以及如今谁来撰写（2026）",[20,21,22],"p",{},"会议纪要是会议的正式书面记录：谁出席了，讨论了什么，决定了什么，以及谁在何时之前负责什么。与逐字记录不同，纪要不记录每一句话——它们记录的是结果。与随意的总结不同，纪要遵循一种可辨识的格式，在董事会、委员会和协会中，它们通常是组织必须保存的唯一文档。",[20,24,25],{},"本指南先讲手工技巧——格式、可复制的模板、填好的示例、董事会会议有何不同——然后讲格式本身从未涉及的部分：2026 年谁来撰写纪要，以及当与会者不共享同一种语言时，纪要以谁的语言呈现。",[27,28,30],"h2",{"id":29},"会议纪要是什么以及不是什么","会议纪要是什么——以及不是什么",[20,32,33],{},"会议后会产生三种文档，它们回答不同的问题：",[35,36,37,55],"table",{},[38,39,40],"thead",{},[41,42,43,46,49,52],"tr",{},[44,45],"th",{},[44,47,48],{},"记录什么",[44,50,51],{},"典型篇幅",[44,53,54],{},"谁会阅读",[56,57,58,76,92],"tbody",{},[41,59,60,67,70,73],{},[61,62,63],"td",{},[64,65,66],"strong",{},"逐字记录",[61,68,69],{},"每一个词，按顺序",[61,71,72],{},"数页",[61,74,75],{},"几乎没人，偶尔搜索",[41,77,78,83,86,89],{},[61,79,80],{},[64,81,82],{},"纪要",[61,84,85],{},"正式记录：出席情况、议题、决议、表决、行动项",[61,87,88],{},"一到两页",[61,90,91],{},"成员、审计人员、未出席者",[41,93,94,99,102,105],{},[61,95,96],{},[64,97,98],{},"回顾",[61,100,101],{},"决议、行动项和待解问题，按阅读顺序排列",[61,103,104],{},"一屏",[61,106,107],{},"所有受邀者，当天发送",[20,109,110,111,115],{},"纪要居于中间：比",[112,113,98],"a",{"href":114},"\u002Fblog\u002Fmeeting-recap","更完整，比逐字记录短得多，且——在正式场合中——是具有法律效力的版本。如果您的会议是一次工作通话，且没有人会审计它，回顾格式更轻量、阅读率更高；我们为它保留了单独的指南。如果您的会议有主持人、议程和任何类似表决的环节，您需要的是纪要。",[20,117,118,119,123,124,127],{},"纪要不是对时间的记录。这个词来自拉丁语 ",[120,121,122],"em",{},"minuta","——\"小的\"——如 ",[120,125,126],{},"minuta scriptura","，即以小字记录的笔记，事后正式誊写。纪要从来都是关于精简笔记，而非关于时钟。",[27,129,131],{"id":130},"包含哪些内容标准格式","包含哪些内容：标准格式",[20,133,134],{},"一套可用的会议纪要包含八个要素。这是几乎所有模板背后的骨架，从项目同步会到董事会会议册皆然：",[136,137,138,145,151,157,163,169,175,181],"ol",{},[139,140,141,144],"li",{},[64,142,143],{},"会议名称、日期、时间和地点","（或会议链接——\"地点\"现在是一个 URL）。",[139,146,147,150],{},[64,148,149],{},"出席情况","——出席者、请假缺席者，以及任何来宾。在正式会议中，注明是否达到法定人数。",[139,152,153,156],{},[64,154,155],{},"上期纪要的批准","——正式机构以批准上次会议的记录作为开场，并注明修改之处。",[139,158,159,162],{},[64,160,161],{},"议程项，按顺序","——每项一个区块，各附简短中立的讨论摘要。两三句话；记录立场，而非逐句转述。",[139,164,165,168],{},[64,166,167],{},"决议","——每项决议用一句话表述，并注明通过方式（\"协商一致通过\"、\"5票赞成2票反对通过\"）。决议是纪要存在的理由；切勿将它们埋没在讨论文字中。",[139,170,171,174],{},[64,172,173],{},"行动项","——负责人、任务、截止日期。每项一行。没有负责人的行动项只是一个愿望，不是记录。",[139,176,177,180],{},[64,178,179],{},"下次会议","——日期和时间（如已确定）。",[139,182,183],{},[64,184,185],{},"休会时间及纪要记录人。",[20,187,188],{},"不应包含的内容：逐字引用（除非有人要求被记录在案）、语气和情绪、记录人的个人意见，以及任何非正式发言。纪要在构造上是中立的——读者不应能从文本中看出记录人站在哪一边。",[27,190,192],{"id":191},"如何撰写会前会中会后","如何撰写：会前、会中、会后",[20,194,195,198],{},[64,196,197],{},"会前，借用结构。"," 拿到议程并将其转化为纪要骨架：每项一个标题、从邀请函预填出席名单、链接上期纪要。百分之九十的格式化工作在任何人发言之前就已完成。如果没有议程，这是第一个需要提出的问题——没有议程的纪要只会变成谁的嗓门大谁就被记录的时间线。",[20,200,201,204],{},[64,202,203],{},"会中，记录决议而非对话。"," 做纪要的技巧在于实时的高强度筛选：对于每个议程项，您需要记录提出的立场（仅在重要时归属发言者）、决议和行动项。当一项决议产生时，大声宣读——\"我们记录如下：X，全体同意，Anna 于15日前交付\"——让与会者在大家还记得时纠正。仅此一个习惯就能消除纪要传阅后出现的大部分争议。",[20,206,207,210],{},[64,208,209],{},"会后，当天发布。"," 在上下文还清晰时整理笔记，如果您的流程要求，请主持人审阅，然后将纪要发送给所有受邀者——尤其是错过会议的人。然后将它们存放在下次会议能找到的地方：只存在于一个人收件箱里的纪要，等于组织没有这份纪要。",[27,212,213],{"id":213},"会议纪要模板",[215,216,217,280,292,321,347],"blockquote",{},[20,218,219,230,233,234,237,238,233,241,244,245,237,248,233,251,254,233,257,237,260,233,263,237,265,233,268,270,233,273,237,275,233,278],{},[64,220,221,225,226,229],{},[222,223,224],"span",{},"组织 \u002F 团队"," — ",[222,227,228],{},"会议名称"," 纪要",[64,231,232],{},"日期："," ",[222,235,236],{},"日期"," · ",[64,239,240],{},"时间：",[222,242,243],{},"开始","–",[222,246,247],{},"结束",[64,249,250],{},"地点：",[222,252,253],{},"会议室 \u002F 会议链接",[64,255,256],{},"出席：",[222,258,259],{},"姓名",[64,261,262],{},"请假：",[222,264,259],{},[64,266,267],{},"来宾：",[222,269,259],{},[64,271,272],{},"主持人：",[222,274,259],{},[64,276,277],{},"记录人：",[222,279,259],{},[20,281,282,285,287,288,291],{},[64,283,284],{},"1. 上期纪要批准",[222,286,236],{}," 的纪要已获批准 ",[222,289,290],{},"按传阅版本批准 \u002F 作如下修改：……","。",[20,293,294,300,303,233,306,309,310,233,313,225,315,318,319,291],{},[64,295,296,297],{},"2. ",[222,298,299],{},"议程项",[222,301,302],{},"两三句话的中立讨论摘要。",[64,304,305],{},"决议：",[222,307,308],{},"一句话——决定了什么以及如何通过：协商一致 \u002F 表决票数","。\n",[64,311,312],{},"行动：",[222,314,259],{},[222,316,317],{},"任务"," — 截止 ",[222,320,236],{},[20,322,323,328,331,233,333,309,339,233,341,225,343,318,345,291],{},[64,324,325,326],{},"3. ",[222,327,299],{},[222,329,330],{},"摘要。",[64,332,305],{},[222,334,335,336,338],{},"决议，或\"推迟至 ",[222,337,236],{},"\"",[64,340,312],{},[222,342,259],{},[222,344,317],{},[222,346,236],{},[20,348,349,233,352,355,356,359],{},[64,350,351],{},"下次会议：",[222,353,354],{},"日期，时间","。\n会议于 ",[222,357,358],{},"时间"," 休会。",[27,361,362],{"id":362},"填好的示例",[215,364,365,385,390,402,411],{},[20,366,367,370,372,373,375,376,378,379,381,382,384],{},[64,368,369],{},"Aster GmbH — 产品委员会纪要",[64,371,232],{}," 2026年8月28日 · ",[64,374,240],{}," 14:00–14:50 · ",[64,377,250],{}," 会议链接\n",[64,380,256],{}," L. Ortega（主持人）、M. Bauer、K. Sato、P. Nowak（记录人）· ",[64,383,262],{}," J. Lindqvist",[20,386,387,389],{},[64,388,284],{},"\n8月14日的纪要按传阅版本获批准。",[20,391,392,395,396,398,399,401],{},[64,393,394],{},"2. 第四季度定价调整","\nBauer 展示了修订后的分级方案；Sato 提出了对年度续约的影响。委员会同意修订不适用于10月前签署的合同。\n",[64,397,305],{}," 修订后的分级方案自10月1日起适用于新合同——3票赞成0票反对通过。\n",[64,400,312],{}," M. Bauer — 向销售团队提供更新后的价格表 — 截止9月5日。",[20,403,404,407,408,410],{},[64,405,406],{},"3. 日语支持覆盖","\nSato 汇报了当前响应时间。讨论推迟至9月招聘轮次后再议。\n",[64,409,305],{}," 推迟至下次委员会会议。",[20,412,413,415],{},[64,414,351],{}," 2026年9月11日，14:00。\n会议于14:50休会。",[20,417,418],{},"注意示例中没有包含什么：没有人的原话，没有形容词，没有氛围。五十分钟的会议变成了十四行文字，一个未出席的人可以据此行动——这就是纪要的全部职责。",[27,420,422],{"id":421},"董事会纪要正式性增加了什么","董事会纪要：正式性增加了什么",[20,424,425,426,429],{},"对于董事会、委员会或协会，同样的骨架会承担法律职责，具体细节因司法管辖区和您的章程而异——请同时核查两者。各规则手册中一致的增加内容包括：记录通知已妥善送达且达到法定人数；逐字记录",[64,427,428],{},"动议","——谁提出、谁附议，以及表决结果，注明弃权者和任何回避者；当成员要求时记录异议。已批准的纪要通常成为组织对其决议的正式证据，这就是为什么董事会将批准上次会议纪要作为第一项议程——记录本身需要一项决议。",[20,431,432],{},"法律效力带来的纪律性，恰恰也是让日常纪要保持高质量的同一条原则：中立的措辞、决议优先于对话、以及不会写入任何您不想在两年后被重新宣读的内容。",[27,434,436],{"id":435},"如今谁来撰写以及以谁的语言","如今谁来撰写——以及以谁的语言",[20,438,439,440,443,444,448],{},"2026 年，撰写本身越来越多地被自动化：会议被转录，模型草拟摘要，纪要记录者的工作从速记转向编辑。自动化大多未改变的是格式背后的假设——即会议及其记录只发生在一种语言中。用英语开一场会，团队成员的思维语言是葡萄牙语、波兰语和德语，纪要则以英语呈现：准确、正式，但对大多数受其约束的人来说，这是一份第二语言文档。我们在",[112,441,442],{"href":114},"回顾指南","中记录了各主要平台在通话后实际保留了什么，按厂商分类并附来源——各地的模式都一样：一份记录，一种语言——而",[112,445,447],{"href":446},"\u002Fblog\u002Fthe-meeting-a-week-later","一周后您的语言中还有多少会议内容","是一个有可量化答案的问题。",[20,450,451,452,455],{},"我们构建 InterMIND，正是为了让记录不再带有这个假设。它是一个通讯空间，会议以每位参与者自己的语言运行——语音、聊天和笔记——当通话结束时，摘要已经存在：概览、标记为已同意\u002F待定\u002F有争议的要点、带负责人的行动项，每一行都保留时间戳。已登录的成员通过邮件、会议聊天和日历事件获取摘要，每位成员都可以",[64,453,454],{},"以自己的语言","阅读——记录按读者翻译，而非以会议室中最响亮的语言一次性写入。任何成员都可以编辑，每次编辑都保留作者和修订历史，频道保留每次过往会话的记录。（以无账户来宾身份加入的参与者可以获得完整的实时翻译会议，但会后没有记录——账户是免费的，正是它使记录可触达。）摘要模型托管于欧盟，请求级零数据留存。",[20,457,458],{},"纪要作为一种技艺，在自动化中存续——仍然需要有人来判断会议意味着什么。不该存续的是这样一个观念：多语言会议室的正式记录只能以一种语言存在。",[460,461,462,471],"ul",{},[139,463,464,470],{},[64,465,466],{},[112,467,469],{"href":468},"\u002Ffeatures\u002Frecap","查看完整示例","——由撰写您纪要的同一套代码渲染的真实记录，包含时间戳。",[139,472,473,479],{},[64,474,475],{},[112,476,478],{"href":477},"\u002Fdemo","体验实时演示","——无需注册；开口说话，聆听为每位听众翻译的会议室。",[27,481,482],{"id":482},"常见问题",[20,484,485],{},[64,486,487],{},"什么是会议纪要？",[20,489,490],{},"会议纪要是会议的正式书面记录：日期和出席情况、讨论的议题、做出的决议（在有表决时附表决票数），以及带负责人和截止日期的行动项。它们记录结果而非对话——一个错过会议的读者应能在不听任何人发言的情况下据此行动。",[20,492,493],{},[64,494,495],{},"为什么叫\"minutes\"？",[20,497,498,499,501,502,504],{},"源自拉丁语 ",[120,500,122],{},"，\"小的\"——",[120,503,126],{}," 是会议过程中以小字记录的粗略笔记，事后正式誊写。名称指的是精简笔记，而非时间单位。",[20,506,507],{},[64,508,509],{},"会议纪要应包含哪些内容？",[20,511,512],{},"八项内容：会议名称\u002F日期\u002F时间\u002F地点；出席情况（出席者、请假者、来宾、相关时注明法定人数）；上期纪要批准；每个议程项附简短中立摘要；决议，每项用一句话表述并注明通过方式；带负责人和截止日期的行动项；下次会议日期；以及休会时间和纪要记录人。",[20,514,515],{},[64,516,517],{},"会议纪要不应包含哪些内容？",[20,519,520],{},"逐字对话、语气、情绪、记录人的个人意见，以及非正式发言。仅在重要时或成员要求被记录时才归属立场。纪要是中立的：文本不应透露记录人站在哪一边。",[20,522,523],{},[64,524,525],{},"会议纪要和会议回顾有什么区别？",[20,527,528,529,291],{},"纪要是更完整的正式记录——出席情况、议程项、决议、表决、行动项——在正式机构中经批准后具有法律效力。回顾是一屏的工作摘要（决议、行动项、待解问题），当天发送。对于工作通话，回顾的阅读率更高；对于有主持人和表决的场合，请写纪要。我们保留了",[112,530,531],{"href":114},"单独的回顾指南",[20,533,534],{},[64,535,536],{},"会议纪要应该多详细？",[20,538,539],{},"详细到缺席成员可据此行动；简短到能被人读完。工作准则：每个议程项两三句中立讨论，每项决议恰好一句话，每个行动项一行。五十分钟的会议通常应控制在一到两页。",[20,541,542],{},[64,543,544],{},"谁来记录纪要？",[20,546,547],{},"正式机构指定秘书或轮流出任；在工作会议中则是被指派的人——最好不是主持人，因为主持人正忙于主持讨论。2026 年，越来越多的初稿由机器从会议本身生成，人的角色转向编辑：在记录传阅前核实决议、负责人和日期。",[549,550],"hr",{},[20,552,553],{},[120,554,555,556,562],{},"来源：",[112,557,561],{"href":558,"rel":559},"https:\u002F\u002Fwww.merriam-webster.com\u002Fdictionary\u002Fminute",[560],"nofollow","Merriam-Webster — \"minute\"（名词）：\"the official record of the proceedings of a meeting\"，源自拉丁语 minutus，\"small\"","。董事会纪要要求因司法管辖区和章程而异——请核查您的适用规定。核验于2026年9月。",{"title":564,"searchDepth":565,"depth":566,"links":567},"",2,3,[568,569,570,571,572,573,574,575],{"id":29,"depth":565,"text":30},{"id":130,"depth":565,"text":131},{"id":191,"depth":565,"text":192},{"id":213,"depth":565,"text":213},{"id":362,"depth":565,"text":362},{"id":421,"depth":565,"text":422},{"id":435,"depth":565,"text":436},{"id":482,"depth":565,"text":482},"2026-09-02",false,"会议记录是会议的正式书面记录：决定了什么、谁投票、谁在何时之前完成什么。格式、您可以复制的模板、填写完整的示例、董事会会议的附加内容——以及该格式从未提出的问题：记录以谁的语言送达？","md","seo",null,{"role":583,"spend":584},"team-lead","incumbent-subscription","\u002Fblog\u002Fhow-to-write-meeting-minutes.svg",{},true,"\u002Fblog\u002Fhow-to-write-meeting-minutes",[590,591,592,593,594],"how to write meeting minutes","meeting minutes","meeting minutes template","meeting minutes example","what are meeting minutes","wave-space",{"title":6,"description":578},"blog\u002Fhow-to-write-meeting-minutes","howto-minutes","DlDy_V1i8h_riABaC5FPCpSnkgsflxaxwzJLmvnj15Y",[601,606],{"title":602,"path":603,"stem":604,"description":605,"children":-1},"发现电话：它是什么、如何进行，以及如何用潜在客户自己的语言开展 (2026)","\u002Fblog\u002Fdiscovery-call","blog\u002Fdiscovery-call","发现电话是与潜在客户的首次实质性对话：您借此了解他们的问题是否是您能解决的，而他们则借此判断您是否值得进行第二次会议。30 分钟的议程、15 个问题、简短的话术、以及后续步骤——加上为更倾向于用自己思考的语言作答的潜在客户准备的三步设置：日历中的预订页面、一个可重复使用的会议链接，以及一份会自动归档至您 CRM 的会议纪要。",{"title":607,"path":608,"stem":609,"description":610,"children":-1},"销售跟进邮件：通话后的模板，以及如何让总结报告自动发送 (2026)","\u002Fblog\u002Fsales-follow-up-email","blog\u002Fsales-follow-up-email","销售跟进邮件会重述通话内容、所作决定以及带有日期的下一步行动，并在当天发出。本文提供针对实际场景的五个模板、发送时机规则、如何通过 BCC 在 HubSpot、Pipedrive 和 Zoho 中将邮件同步至 CRM（附相关文档化条件），以及一种可为您自动生成通话总结并存入潜在客户记录中而无需任何人手动复制的设置方案。"]