THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM
FOR INTERNAL USE ONLY
Template No.: T227
Template Title: Conflict Chronology Log (Timeline) + Event Notes
Related Research Case IDs / Cluster: Cluster F – HGT Conflicts & Security (Cases 66–85)
Linked Templates / Policies: T226 (Overview), T228 (Stakeholder Map), T229 (Document Index), T232 (Risk Sheet), T236 (Security Incident), Confidentiality & Access 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 [ ]
A) Purpose and rules (read first)
Purpose: to keep one clear timeline for a conflict case. It supports calm decisions, safety actions, and fair review.
Rules (tick when applied):
Use neutral words (facts, not blame). [ ]
Use 24-hour time and full date (DD/MM/YYYY). [ ]
Do not delete old entries. If a mistake happens, add a new line marked “Correction”. [ ]
Use codes/roles instead of full names (for privacy). [ ]
Link every entry to source + evidence ID when possible. [ ]
Case ID: ___________________________ Related Case ID(s): ______________________
Chronology owner (role): ___________________________ Start date: //______
B) Timeline table (Chronology Log)
(One line per event. Attach “Event Notes” for important events.)
| No. | Date | Time | Event type (tick) | Location | People/units involved (codes) | Short event description (1–3 lines) | Source (who/what) | Evidence ID(s) | Verification (tick) | Impact level | Immediate action taken | Next step / owner / due date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | //____ | ____ | Report [ ] Meeting [ ] Message [ ] Security [ ] Relic move [ ] Media [ ] Legal [ ] Other:____ | __________ | __________ | ________________________________ | __________ | __________ | Unverified [ ] Partial [ ] Verified [ ] | Low [ ] Med [ ] High [ ] | __________________ | __________________ |
| 2 | //____ | ____ | Report [ ] Meeting [ ] Message [ ] Security [ ] Relic move [ ] Media [ ] Legal [ ] Other:____ | __________ | __________ | ________________________________ | __________ | __________ | Unverified [ ] Partial [ ] Verified [ ] | Low [ ] Med [ ] High [ ] | __________________ | __________________ |
| 3 | //____ | ____ | Report [ ] Meeting [ ] Message [ ] Security [ ] Relic move [ ] Media [ ] Legal [ ] Other:____ | __________ | __________ | ________________________________ | __________ | __________ | Unverified [ ] Partial [ ] Verified [ ] | Low [ ] Med [ ] High [ ] | __________________ | __________________ |
Event type guide (simple):
Report: someone tells staff about a conflict issue
Message: key chat/email/letter appears
Security: access issue, threat, crowd risk, theft risk
Relic move: any movement, packing, storage change (must be authorised)
Legal: police, court, lawyer, official order, MoU dispute
Media: news post, rumour, public statement
C) Event Notes (T67-style) – use 1 sheet per important event
Event Note ID: EN-____ (match Timeline No. ____)
C1) Event basics
Related Case ID: _______________________ Timeline No.: ______
Date: //______ Time: ________ Time zone: __________
Location: _________________________________________________
Event type: Report [ ] Meeting [ ] Message [ ] Security [ ] Relic move [ ] Media [ ] Legal [ ] Other: ______
C2) Who was involved (codes/roles)
Primary parties present: __________________________________________
Witnesses / observers (codes): ___________________________________
HSWAGATA staff roles present: ____________________________________
C3) What happened (facts only)
Write clearly, 8–15 lines:
C4) What was seen vs reported
What staff saw directly (if any):
What others said/reported (mark as “reported”):
C5) Messages / claims (if any)
If there was a claim (letter, screenshot, voice note), record it briefly:
Claim summary (1–3 lines): ___________________________________________
Channel: Email [ ] Letter [ ] Chat app [ ] Phone [ ] Social media [ ] Other: ____
Note: do not act on screenshots alone; verify through official channels.
C6) Evidence link (do not attach originals here; index them)
Evidence included in this event (tick):
Photo [ ] Video [ ] Screenshot [ ] Letter [ ] Email [ ] Audio [ ] CCTV note [ ] Other: ____
Evidence ID(s) (from T229): __________________________________________
Stored at (file path / cabinet): ______________________________________
C7) Verification status
Verification: Unverified [ ] Partial [ ] Verified [ ]
How verified (1–2 lines): ____________________________________________
Verified by (role): __________________________ Date: //______
C8) Risk and safety note (short)
Any risk to people? Yes [ ] No [ ] Unsure [ ]
Any risk to relic safety? Yes [ ] No [ ] Unsure [ ]
If Yes/Unsure, what protection step was taken now:
C9) Decisions and actions from this event
Decision made (if any): ______________________________________________
Actions (owner + due date):
_______________________ Owner: __________ Due: //____
_______________________ Owner: __________ Due: //____
_______________________ Owner: __________ Due: //____
C10) Communication control
Internal update sent? Yes [ ] No [ ] To whom (roles): ________________
External communication allowed? Yes [ ] No [ ] Board only [ ]
If Yes, approved spokesperson (role): _________________________________
C11) Sign-off
Logged by (Name): __________________ Role: __________________
Signature: _________________________ Date: //______
Reviewed by (Supervisor/Head): ______________________________
Signature: _________________________ Date: //______
D) Corrections / addendum (if needed)
Addendum No.: ____ Related Timeline No.: ____
Reason for correction (1–3 lines): ____________________________________
Corrected information (facts):
Logged by: _______________________ Date: //______
