报告修订与换版的规范做法

结论：更正是可以的，但原版不能消失，修订要留痕

报告发出后，有时需要修改：

发现错误。 笔误、计算错误、数据录入错误。

信息变更。 委托方名称、地址的更正。

补充内容。 增加原委托范围内遗漏的项目。

核查后的更正。 因异议核查发现的问题。

处理这些情形的原则是：可以修订，但要留痕。

留痕意味着：原报告不能当作从未存在过，修订的内容和原因要可追溯，修订后的报告要能与原报告区分。

这个原则的原因是：报告可能已经被使用、被引用、被归档在别处，如果原版凭空消失而新版悄悄替换，就产生了不可追溯的风险。

修订的方式

「更正件」适合改动小的情形 ——比如委托方名称写错一个字，发一份更正说明附在原报告后面即可。

「换发报告」适合改动大的情形 ——数据错误、结论变化，需要重新出具完整报告。

更正件的做法

明确关联。 写明所更正的原报告编号和日期。

明确内容。 原内容是什么、更正为什么。

说明原因。 简要说明为什么更正。

编号与签发。 更正件有自己的编号，按报告的程序签发。

与原报告的关系。 说明更正件与原报告一并有效。

「一并有效」是更正件的关键表述 ——更正件本身不完整，必须与原报告一起使用才有意义。

换发报告的做法

新编号。 换发的报告用新编号，版本标识不能重复。

标注替代关系。 写明本报告替代哪份报告。

原报告作废。 明确原报告作废。

修改内容的说明。 说明相对原报告修改了什么。

回收原报告。 尽可能回收已发的原件。

通知使用方。 通知已知的报告使用方。

「版本标识不能重复」是基本要求 ——如果新旧报告用同一个编号，在别人的档案里就无法区分哪份是有效的。

已发副本的处理

这是实务中较难的部分：

登记发放情况。 报告发给了谁、几份，应当有记录。

通知已知的接收方。 告知报告已修订。

尽力回收。 要求退回或销毁原件。

记录处理情况。 哪些回收了、哪些没有。

无法回收时的说明。 在修订记录中说明。

「发放登记」是能否有效通知的前提 ——如果不知道报告发给了谁，修订后就无法通知，风险就留在外面。

电子报告的处理

电子版的替换。 系统中的电子版要同步更新。

下载记录。 已下载的副本无法收回，需通过通知处理。

在线核验。 如果有在线核验功能，核验结果应当反映最新状态。

作废的标识。 作废的报告在核验时应当能查到作废状态。

「在线核验反映最新状态」是电子报告的优势 ——即使旧副本在外流传，核验时能发现它已被替代。

记录的要求

修订的记录。 什么时候、因为什么、改了什么、谁批准的。

原报告的留存。 原报告的存档件保留，标注作废。

原始记录的关联。 修订依据的原始记录。

通知的记录。 通知了谁、什么时候、对方的回应。

回收的记录。 回收情况。

记录的目的是可追溯 ——事后能还原整个过程。

不规范做法的风险

悄悄替换。 用同编号的新版替换旧版而不作说明，造成同一编号两个版本在外，无法区分。

不通知使用方。 使用方继续用错误的报告做决策。

不留存原版。 无法追溯原来发生了什么。

口头更正。 没有书面依据。

修改存档件。 直接改档案中的报告，破坏了记录的完整性。

「修改存档件」问题最大 ——它让记录变得不可信，而记录的可信是整个体系的基础。

常见的准备不足

信息不全。 材料、工艺、使用环境的信息缺失，导致方案设计缺乏依据。

样品不具代表性。 试制样品或挑选样品，与量产状态有差距。

条件未明确。 测试条件没说清楚，数据的适用范围就不明确。

只看初始值。 忽略了环境和时间作用后的性能变化。

项目不完整。 遗漏了必要的项目，提交时才发现。

这五项在实际委托中出现频率较高，建议在项目启动时逐项确认，因为它们造成的返工成本远高于事前确认所花的时间。

数据的组织与保存

记录的完整性。 条件、方法、设备、样品状态、实测值。

可追溯性。 数据与样品批次、生产批次的关联。

保存期限。 覆盖产品的生命周期。

检索的便利。 需要时能快速定位。

版本的管理。 数据更新时的版本控制。

建议建立统一的数据台账，记录每组数据的来源、条件、适用范围和有效期。数据积累起来之后，后续的产品开发和变更评估都能受益。

与整体工作的衔接

这部分工作不是孤立的，它与几项内容相关：

与设计的衔接。 数据是设计决策的依据，也是设计验证的证据。

与风险管理的衔接。 识别出的风险点应当有对应的验证。

与变更管理的衔接。 变更时判断是否需要重新验证。

与生产控制的衔接。 关键参数的控制限值来自验证数据。

与售后的衔接。 失效分析需要原始数据作为对照。

建议在项目规划时就把这些衔接关系理清楚，避免各环节各做各的、数据无法互相支撑。

我们的做法

发现报告需要更正时，我们按改动的大小选择更正件或换发报告，并在文件中明确与原报告的关系。

换发时我们用新编号并标注替代关系，原报告标注作废，不使用同编号覆盖的做法。

我们保留报告的发放记录，修订后通知已知的接收方，并记录通知和回收的情况。

原报告的存档件我们保留并标注作废，不做删改，因为记录的完整性比档案的整洁重要。

如果你收到的报告有需要更正的内容，可以直接联系我们说明：132 4819 8029。流程见检测流程，其他问题见常见问题，更多内容见知识库。

English version

Conclusion. Reports sometimes need amending after issue. Errors are found, whether typographical, computational or data entry. Information changes, such as corrections to the client's name or address. Content is added, covering items within the original commission that were omitted. Or a review following an objection finds something. The principle for handling these is that amendment is permissible but must leave a trail. Leaving a trail means the original report cannot be treated as though it never existed, the amended content and its reason must be traceable, and the amended report must be distinguishable from the original. The reason is that the report may already have been used, cited or filed elsewhere, and if the original vanishes while a new version quietly replaces it, an untraceable risk is created.

Forms of amendment. A correction notice suits a small number of definite errors, attaching to the original without replacing it. A replacement report suits more extensive changes, taking a new number while the original is withdrawn. And a supplementary report suits added items, coexisting with the original. A correction notice suits minor changes such as a mis-typed character in the client's name, where a correction statement attached to the original suffices. A replacement report suits substantial changes such as data errors or altered conclusions, where a complete report must be reissued.

Preparing a correction notice. State the relationship clearly, identifying the original report's number and date. State the content clearly, covering what was there and what it becomes. Explain the reason briefly. Number and authorise it, giving it its own number and issuing it through the report procedure. And state its relationship with the original, namely that the two are valid together. Validity together is the key statement: a correction notice is incomplete in itself and is meaningful only when used with the original.

Preparing a replacement report. Give it a new number, since version identifiers must not repeat. State what it supersedes. Withdraw the original explicitly. Explain what changed relative to the original. Recover issued originals so far as possible. And notify known users of the report. Non-repeating version identifiers are a basic requirement: if old and new reports carry the same number, no one else's files can distinguish which is current.

Handling issued copies. This is the harder part in practice. Keep a distribution record of who received the report and how many copies. Notify known recipients that the report has been amended. Make every effort to recover copies, asking for return or destruction. Record the outcome, covering what was recovered and what was not. And explain in the amendment record where recovery was impossible. The distribution record determines whether effective notification is possible: without knowing who received the report, no one can be notified after amendment and the risk remains outstanding.

Handling electronic reports. Replace the electronic version in the system so that it stays synchronised. Recognise that downloaded copies cannot be recalled and must be handled by notification. Ensure online verification reflects the current state where such a facility exists. And make withdrawal visible, so that verification of a withdrawn report shows its withdrawn status. Online verification reflecting the current state is the advantage of electronic reports: even where an old copy circulates, verification reveals that it has been superseded.

Record requirements. Record the amendment covering when, why, what changed and who approved. Retain the original report in the archive, marked as withdrawn. Link to the raw records that the amendment rests on. Record notifications covering who was notified, when and how they responded. And record recovery outcomes. The purpose of records is traceability, allowing the whole process to be reconstructed afterwards.

Risks of poor practice. Quiet replacement, substituting a new version under the same number without explanation, leaves two versions of one number circulating and no way to tell them apart. Not notifying users leaves them making decisions on an erroneous report. Not retaining the original makes it impossible to trace what happened. Verbal correction leaves no documentary basis. And altering the archived copy destroys the integrity of the record. Altering the archive is the worst of these: it makes records untrustworthy, and trustworthy records are the foundation of the whole system.

How we handle it. Where a report needs correcting we choose between a correction notice and a replacement according to the extent of the change, and state the relationship with the original in the document. On replacement we use a new number and state what is superseded, marking the original withdrawn, rather than overwriting under the same number. We keep distribution records, notify known recipients after amendment and record both the notification and the recovery outcome. And we retain the archived original marked as withdrawn without alteration, since the integrity of records matters more than the tidiness of the file.

If a report you have received needs correcting, get in touch and tell us: +86 132 4819 8029.