ate No.: T-TK019 Template Title: Rumor Response Plan (Online Rumor Wave After Event)
THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM
FOR INTERNAL USE ONLY
Template No.: T-TK019
Template Title: Rumor Response Plan (Online Rumor Wave After Event)
Related Research Case IDs / Cluster: TK-019 / Cluster E (Science, Testing, Misinformation) + Cluster F (Conflict, Security, Reputation Risk)
Linked Templates / Policies: T-TK005 Public Correction Procedure; T-TK006 Publication Approval Workflow; T-TK008 Authority-Name Use Policy; T-TK009 Evidence Integrity Checklist; T-TK017 Response Tracking Form; Incident Reporting Form; Data Protection & Confidentiality Policy; Conflict Resolution & Security SOP; Access Control Policy
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 [ ]
1) Purpose
This plan is used when a rumor wave starts online after an event (festival, donation, relic viewing, testing talk, conflict news).
Goals:
Protect truth and public trust.
Reduce conflict and panic.
Protect relic security and staff safety.
Respond with calm “Right Speech”.
Core rule: We respond with facts we can verify. We do not fight people online.
2) Trigger (activate if any are true)
Rumor spreads fast (many shares/comments) [ ]
Rumor includes relic authenticity/testing claims [ ]
Rumor claims theft/loss/movement [ ]
Rumor uses an authority name without consent [ ]
Rumor targets staff with harassment [ ]
Rumor reveals restricted locations or sacred images [ ]
Media contacts HSWAGATA for comment [ ]
Other: ______________________________________ [ ]
Activation date/time: ____ / ____ / ______ _______
3) Rumor incident record (basic)
Rumor Incident ID: TK019--
Event name/date (if related): _______________________________
Main rumor topic (tick):
Authenticity/testing [ ] Theft/loss [ ] Custody dispute [ ] Donor scandal [ ] Authority endorsement [ ] Other: ______
Short rumor summary (1–2 lines, copy exact key claim words):
Risk level (choose one):
Low [ ] Medium [ ] High [ ] Critical [ ]
4) Roles and responsibilities
Rumor Lead (Comms): ______________________________
Fact-Check Lead (Verification): ___________________
Security Lead (if needed): ________________________
Board Delegate (High/Critical): ___________________
Moderator (social media): _________________________
Two-person rule: All decisions must be checked by at least 2 staff.
5) Step 1 — Capture evidence (do immediately)
Tick completed:
Screenshots saved (show account name + date/time) [ ]
URLs/links saved [ ]
Video saved (if any) [ ]
Main platforms: Facebook [ ] TikTok [ ] YouTube [ ] X [ ] News site [ ] Other: ____
Accounts/pages/groups involved (list 3–10):
__________________ 2) __________________ 3) __________________
Key comments showing harm/threats saved (if any) [ ]
Impersonation signs saved (if any) [ ]
File naming standard: TK019_YYYYMMDD_Platform_RumorTopic
Stored at secure location: _________________________________
Access level: Internal [ ] Restricted [ ] Sacred-Restricted [ ]
6) Step 2 — Build the rumor timeline (simple)
Fill in the timeline (facts only):
| Time/Date | What appeared | Where (platform/account) | Evidence saved? |
|---|---|---|---|
| First post | Y/N | ||
| First share wave | Y/N | ||
| New version/mutation | Y/N | ||
| Media asked | Y/N | ||
| After correction (if any) | Y/N |
7) Step 3 — Quick harm check (security + privacy)
Tick any urgent risks:
Reveals storage location / security details [ ]
Shows sacred-restricted photos/videos [ ]
Calls people to “come take action” [ ]
Targets staff with harassment [ ]
False testing claim may cause conflict [ ]
Other: ____________________________________ [ ]
If urgent risk exists:
Notify Security Lead now [ ]
Limit public comments (moderation) [ ]
Do not share more details in replies [ ]
File Incident Report (if needed) [ ]
8) Step 4 — Fact-check (truth check)
Choose the rumor type and required verification:
A) Testing/authenticity rumor
Use T-TK005 + T-TK015 (if real testing request exists) [ ]
Verify with lab/hospital using official contact [ ]
B) “Official letter” rumor
Use T-TK004 External-Claim Verification SOP [ ]
C) Authority name used
Use T-TK008 Authority-Name Use Policy [ ]
D) Private messages used as proof
Use T-TK009 Evidence Integrity Checklist [ ]
Verification status (choose one):
Unverified (no proof) [ ]
False (confirmed wrong/fake) [ ]
Misleading (partial truth used wrongly) [ ]
True (verified) [ ]
Ongoing inquiry [ ]
Short verification note (1–2 lines):
9) Step 5 — Choose response level (do not overreact)
Decision made by: __________________________ Date: ____ / ____ / ______
Level A — Monitor only (low spread, low harm)
No public reply [ ]
Save evidence + monitor 7 days [ ]
Level B — Quiet correction (medium spread)
One calm reply + one private request to correct/remove [ ]
Use short message only [ ]
Level C — Official public correction (high spread / harmful)
Official post on HSWAGATA channels [ ]
Pin post / share once [ ]
Request platform takedown (fake docs / impersonation) [ ]
Level D — Board + Security escalation (critical)
Board statement (approved) [ ]
Legal/security referral (if needed) [ ]
Staff safety plan [ ]
Any public statement must follow T-TK006.
10) Step 6 — Message rules (Right Speech for rumors)
The response must be:
True [ ] Calm [ ] Clear [ ] Respectful [ ] Short [ ]
Avoid:
Blame/shame [ ] Long debates [ ] Personal data [ ] Sacred details [ ] Security details [ ]
One-message rule: Post one clear message. Do not argue in 50 comments.
11) Standard message templates (copy and fill)
Template 1 — Unverified rumor (no proof)
“HSWAGATA has seen a public claim about: ____________________.
At this time, we have no verified record to confirm this claim.
We ask the public to wait for confirmed information from our official channels.
Thank you for supporting peace and careful speech.”
Template 2 — Confirmed false / fake document
“HSWAGATA has verified that a claim about: ____________________ is not correct.
We request people not to share unverified information.
If any official update is needed, we will publish it through our official channels.”
Template 3 — Authority name misused
“HSWAGATA respects all respected teachers and institutions.
A rumor uses the name of ____________________.
HSWAGATA has no verified consent for this name to support this claim.
Please rely on official channels for confirmed information.”
Approved by (Comms Lead + Board delegate if Level C/D):
Name: __________________ Signature: __________ Date: //______
12) Step 7 — Platform actions (optional but useful)
Tick what you did:
Report impersonation account [ ]
Report fake document/media [ ]
Request takedown (platform form) [ ]
Turn on comment moderation (if policy allows) [ ]
Hide/remove abusive comments (per policy) [ ]
Block accounts only if harassment is repeated [ ]
Record ticket/case number (if any): _________________________
13) Step 8 — Follow-up monitoring and closing
Monitoring period: ___ days (default 7–14)
Track:
Rumor stopped [ ]
Rumor reduced [ ]
Rumor changed into new version [ ]
Rumor increased again [ ]
Media follow-up requests [ ]
If rumor increases:
Escalate response level [ ]
Board notified [ ]
Security actions updated [ ]
Closure note (1–2 lines):
14) Archive checklist
Evidence screenshots + links saved [ ]
Timeline table complete [ ]
Verification notes saved [ ]
Final message text saved [ ]
Approval record saved (T-TK006 if public) [ ]
Incident report linked (if any) [ ]
Filed by: _______________________ Date: ____ / ____ / ______
Reviewed by (Head/Board delegate): ______________ Date: ____ / ____ / ______