THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION PRIVATE MUSEUM
FOR INTERNAL USE ONLY
Template No.: TK-060 (F/E)
Template Title: Misinformation Correction Triggers Backlash — Backlash Logs & Backlash Safety Plan
Related Research Case IDs / Cluster: Cluster F (Conflicts / HGT Disputes) + Cluster E (Science/Testing/Misinformation)
Linked Templates / Policies:
TK-046 Lab Method Misunderstood — Public FAQ Sheet
TK-047 “Inconclusive” Result Anger — De-escalation Script
TK-050 Testing Results Leaked Early — Confidentiality Control
TK-051 No-Fast-Claims Policy
TK-055 Social Media Impersonation SOP
TK-056 Right-Speech Communications Guide
Institutional Policies for Relic Stewardship (HSWAGATA)
Date of form: ____ / ____ / ______
Prepared by / Role: _______________________
Office / Unit: ____________________________
Country / Location: _______________________
Confidentiality Level:
Internal only [ ] Restricted [ ] Sacred-Restricted / Sensitive [ ]
Use of this form (tick):
New case / action [ ] Follow-up [ ] Annual review [ ] Archive only [ ]
TK-060 — Purpose
Use this template when correcting misinformation (online or offline) causes:
anger, insults, threats, or harassment,
organised backlash, boycotts, or protests,
pressure on staff, donors, monks, or partners,
safety risks to people, relics, or facilities.
This template provides:
Backlash logs (what happened, who is affected), and
a Backlash Safety Plan (how to protect people, relics, and calm speech).
A. Correction Event (What Triggered the Backlash)
Date/time correction was issued: ____ / ____ / ______ ________
Where correction appeared (tick):
☐ Website ☐ Social media ☐ Press statement ☐ Public talk ☐ Poster ☐ Other: _______Correction topic (short):
☐ Testing method limits ☐ “Inconclusive” result ☐ Fake document/image
☐ No-fast-claims clarification ☐ Impersonation warning ☐ Other: _______Exact correction wording used (copy):
Who approved the wording? __________________________ Date: //____
Assigned lead officer: ____________________ Date: //____
B. Backlash Log (Record Facts, Not Opinions)
B1. Timeline
First backlash seen (date/time): //_____ ______
Peak activity (if known): //_____ ______
Current status: ☐ Ongoing ☐ Slowing ☐ Stopped
B2. Channels where backlash appears
Tick all that apply:
☐ Social media comments
☐ Direct messages / emails
☐ Phone calls
☐ In-person complaints
☐ Media articles/videos
☐ Organised group messages
☐ Threats or doxxing attempts
B3. Nature of backlash
Tick all that apply:
☐ Anger / insults
☐ Accusations of lying / cover-up
☐ Religious offence claims
☐ Calls for boycott
☐ Demands to reverse correction
☐ Threats to staff / property
☐ Fundraising misuse continues
B4. Evidence
☐ Screenshots saved
☐ URLs recorded
☐ Call logs saved
☐ Witness notes taken
Evidence storage location / code: _______________________________
C. Impact & Risk Assessment
C1. Who is affected?
☐ Frontline staff
☐ Communications staff
☐ Custodians / monks
☐ Donors
☐ Visitors / public
☐ Relic security
C2. Risk level (current)
☐ Low — verbal criticism only
☐ Medium — sustained harassment or pressure
☐ High — threats, crowd risk, property risk, or targeting individuals
Reason (short):
D. Immediate Safety Actions (Do First)
Tick what has been done:
☐ Pause non-essential public replies
☐ Switch to spokesperson-only responses
☐ Remove staff names from public pages
☐ Increase moderation (hide/report abusive posts)
☐ Advise staff not to engage from personal accounts
☐ Notify Security / Compliance lead
☐ Adjust visitor flow or close affected area (if needed)
Notes:
E. Backlash Safety Plan (Choose and Apply)
E1. Communications control
☐ One approved spokesperson only
☐ Use short, calm statements (no debate)
☐ Repeat the same safe wording (do not improvise)
☐ Do not delete factual corrections unless legally required
☐ Do not argue with abusive accounts
E2. Safe wording (copy-paste)
“We shared a correction to prevent misunderstanding. This is not an attack on faith or people. We will not engage in insults or pressure. Verified information is shared through official channels only.”
E3. Staff protection
☐ Shift changes / buddy system
☐ Front-desk script distributed
☐ Hotline/contact point for staff stress
☐ Temporary removal of personal photos/bios online
E4. Donor & stakeholder calming
☐ Direct message to key donors/leaders
☐ Offer private briefing with senior staff
☐ Share Public FAQ (no new details)
E5. Platform actions
☐ Report threats/impersonation to platforms
☐ Block or mute abusive accounts (documented)
☐ Preserve evidence before reporting
F. Escalation Triggers (Immediate)
Escalate to Security / Board if any apply:
☐ Threats of violence or vandalism
☐ Doxxing of staff or custodians
☐ Crowd mobilisation calls
☐ Targeted harassment campaigns
☐ Attempts to access relic areas
Escalated to: ☐ Security ☐ Compliance ☐ Board ☐ Authorities (if required)
Date/time escalated: ____ / ____ / ______ ________
G. Review of the Original Correction (After Calm)
(Do after safety is stable.)
G1. Was the correction accurate and necessary?
☐ Yes ☐ Needs minor wording change ☐ No (note why)
G2. Did wording escalate emotions?
☐ Tone too strong
☐ Too technical
☐ Misread culturally
☐ Fine as written
G3. Improvements for next time
☐ Simpler language
☐ Earlier stakeholder briefing
☐ Pre-release test with panel
☐ Add Q&A at same time
Notes:
H. Closure
Outcome:
☐ Backlash resolved
☐ Ongoing monitoring
☐ Escalated and managed by Security/Board
Final summary (2–4 lines):
Archive code / file location: ______________________________________
I. Sign-off
Prepared by: __________________________ Signature: ________________
Reviewed by (Comms/Compliance/Security): ______________ Signature: ____
Date: ____ / ____ / ______
End of Template TK-060
