\n| Broken link \/ reference<\/td>\n | URL + broken destination + suggested replacement link<\/td>\n | Replace link; confirm it supports the same claim<\/td>\n | Page updated; change log if meaning changes<\/td>\n<\/tr>\n |
\n| Outdated guidance<\/td>\n | What changed + effective date (if known) + source<\/td>\n | Rewrite section; align with current workflow<\/td>\n | Page updated; last reviewed refreshed; change log entry<\/td>\n<\/tr>\n |
\n| AI-assistance disclosure question (transparency hook)<\/td>\n | Which page + what you want clarified<\/td>\n | Confirm whether AI-assisted drafting was used and ensure the human review checklist and citation rules were applied<\/td>\n | Trust notes \/ editorial note updated as needed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Required visual notes (implementation guidance):<\/strong> Add a simple \u201cReview checklist\u201d visual note near the trust notes section, and include an \u201cAI-assistance disclosure\u201d callout note when applicable.<\/p>\n<\/span>Weighted Checklist:<\/span><\/h2>\nWhen we review a correction request, we score it for speed and risk. Use the same checklist to submit higher-signal requests.<\/strong><\/p>\n\n- 40% \u2014 Specificity:<\/strong> Did you include the exact quote and location (heading\/paragraph)?<\/li>\n
- 25% \u2014 Evidence quality:<\/strong> Is the source primary\/official and directly relevant?<\/li>\n
- 15% \u2014 Proposed replacement:<\/strong> Did you provide corrected wording we can paste with minimal edits?<\/li>\n
- 10% \u2014 Impact:<\/strong> Does the issue affect decisions, compliance, or workflow outcomes?<\/li>\n
- 10% \u2014 Scope clarity:<\/strong> Is it one claim, or does it require a broader rewrite?<\/li>\n<\/ul>\n
We apply this to corrections<\/strong> and updates<\/strong> so we can prioritize what matters operationally, not what\u2019s loudest.<\/p>\n<\/span>Outreach Templates:<\/span><\/h2>\nCopy\/paste templates for submitting corrections.<\/strong><\/p>\n<\/span>Template 1: Factual correction<\/span><\/h3>\nSubject:<\/strong> Correction request \u2014 [Page URL]<\/p>\nMessage:<\/strong> I\u2019m requesting a correction on this page: [URL]. The sentence \u201c[quote]\u201d appears under [heading]. Proposed replacement: \u201c[replacement]\u201d. Source: [link]. Reason: [1\u20132 lines]. If this is substantive, please update the change log and last reviewed date.<\/p>\n<\/span>Template 2: Outdated process update<\/span><\/h3>\nSubject:<\/strong> Update request \u2014 process changed \u2014 [Page URL]<\/p>\nMessage:<\/strong> This section looks outdated: [URL + heading]. What changed: [describe]. Effective date (if known): [date]. Supporting reference: [link]. Suggested new steps: [bullets].<\/p>\n<\/span>Template 3: AI-assistance disclosure clarification (transparency hook)<\/span><\/h3>\nSubject:<\/strong> Trust note clarification \u2014 AI-assisted drafting disclosure \u2014 [Page URL]<\/p>\nMessage:<\/strong> On [URL], can you confirm whether AI-assisted drafting was used and whether a human review checklist was applied? If yes, please add\/confirm the disclosure and citation rules in the trust notes.<\/p>\n<\/span>Common pitfalls<\/span><\/h2>\n\n- Vague reports:<\/strong> \u201cThis seems wrong\u201d without the exact quote slows everything down.<\/li>\n
- Screenshots without text:<\/strong> Images are hard to verify and copy. Paste the exact sentence and the URL so we can act quickly.<\/li>\n
- No source:<\/strong> If there\u2019s no supporting reference, we can\u2019t responsibly change factual claims.<\/li>\n
- Conflating preference with error:<\/strong> If you want different framing, label it as clarity\/editing feedback, not a factual correction.<\/li>\n
- Assuming silent edits:<\/strong> We aim to document meaningful changes via a change log so readers can track what moved.<\/li>\n<\/ul>\n
<\/span>How to improve results<\/span><\/h2>\nIf you want your correction handled quickly, optimize for reviewer time:<\/p>\n \n- Pinpoint the claim:<\/strong> Quote it and name the heading.<\/li>\n
- Provide paste-ready replacement text:<\/strong> One clean paragraph beats a long explanation.<\/li>\n
- Use a primary source when possible:<\/strong> Official docs beat commentary.<\/li>\n
- State the impact:<\/strong> Tell us what decision the error could affect (workflow, compliance, or operational guidance).<\/li>\n
|
![\"54140\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/corrections-update-policy-757580d2.png.webp\")
<\/p>\n