Office Of Siridantamahapalaka

Anekajātisaṃsāraṃ sandhāvissaṃ anibbisaṃ gahakāraṃ gavesanto dukkhā jāti punappunaṃ Gahakāraka diṭṭho'si puna gehaṃ na kāhasi sabbā te phāsukā bhaggā gahakūṭaṃ visaṅkhataṃ visaṅkhāragataṃ cittaṃ taṇhānaṃ khayamajjhagā (The Dhammapada, verses 153-154) (Vandāmi cetiyaṃ sabbaṃ, sabbaṭṭhānesu patiṭṭhitaṃ. Ye ca dantā atītā ca, ye ca dantā anāgatā, paccuppannā ca ye dantā, sabbe vandāmi te ahaṃ.)

Showing posts with label Cluster-E Template. Show all posts

Saturday, December 13, 2025

Template No.: T225 Template Title: External Expert Peer Review Request Form

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T225

Template Title: External Expert Peer Review Request Form

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (add C for partnerships/MoUs; add H for ethics model)

Linked Templates / Policies: T218 (Partner Reputation & COI Check), T216 (Ethics & Consent Review), T217 (Data Storage & Access Register), T214 (Risk Assessment for Testing Proposal), T173 (Records Classification), Communication Policy / T190 (Media Approval if public mention)

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 (why we use this form)

This form requests a peer review from an external expert.
It records who we asked, what question we asked, what documents we sent, the deadline, and the reply.

2) Request summary (basic details)

Request ID / code: ______________________________
Date sent: ____ / ____ / ______
Requested by (HSWAGATA name/role): ______________________________
Project / dossier title (if any): ____________________________________
Project / dossier ID (if any): _____________________________________
Related item/object ID (internal, if any): ___________________________

Reason for peer review (tick):
Science accuracy [ ] Conservation advice [ ] Risk review [ ] Report clarity [ ] Misinformation risk [ ] Ethics/faith-sensitive wording [ ] Other: ____

3) External expert details (expert name)

Expert full name: ________________________________________________
Title / position: ________________________________________________
Institution / organisation: _______________________________________
Field of expertise (tick): Conservation [ ] Materials science [ ] Chemistry [ ] Forensics [ ] Museum studies [ ] Buddhist studies [ ] Other: ____
Country/city: _________________________________________________
Email: __________________________ Phone (optional): _______________

How we found the expert (tick): Recommendation [ ] Publication [ ] Partner list [ ] Conference [ ] Other: ____

4) Ethics and conflict-of-interest check (quick)

COI (conflict of interest) asked? Yes [ ] No [ ]
COI declared? None [ ] Yes (details below) [ ] Pending [ ]

COI details (short):

Expert agrees to confidentiality? Yes [ ] No [ ] Pending [ ]
Method (tick): Email confirmation [ ] Signed NDA/MoU clause [ ] Other: ____

Classification of what we will share (T173): Internal [ ] Restricted [ ] Sacred-Restricted [ ]

5) Review question (question)

Write the exact question(s) for the expert. Keep it clear and limited.

Main question (1–3 lines):

Sub-questions (optional):

Scope boundaries (must tick):

No Sacred-Restricted security/access details will be shared. [ ]
No “how-to” instructions requested for harmful use. [ ]
Expert should note limits/uncertainty clearly. [ ]

6) Documents sent (documents sent)

List every document/file shared.

Document 1

Title/file name: ______________________________________________
Version/date: ____________________
File code / location (internal): _________________________________
Classification (T173): Internal [ ] Restricted [ ] Sacred-Restricted [ ]

Document 2

Title/file name: ______________________________________________
Version/date: ____________________
File code / location: __________________________________________

Document 3 (optional)

Title/file name: ______________________________________________
Version/date: ____________________

How documents were sent (tick): Secure email [ ] Secure link/folder [ ] Printed copy [ ] Other: ____

Access end date (if temporary): ____ / ____ / ______
(If shared via folder access, update T217.)

7) Deadline and reply method (deadline)

Reply deadline requested: ____ / ____ / ______
Time zone (if needed): ____________________
Preferred reply method (tick): Email [ ] Signed letter [ ] Review form [ ] Marked-up document [ ] Call/meeting summary [ ] Other: ____

Expected length (tick): Short notes [ ] 1–2 pages [ ] Detailed review [ ]

8) What we asked the expert to include (simple checklist)

Tick what we want back.

Main findings (what is correct / not correct) [ ]
Any unclear wording or misleading claims [ ]
Limits and uncertainty (what we cannot say) [ ]
Risks (faith/heritage/peace) and mitigation ideas [ ]
Suggested improved wording (simple, respectful) [ ]
References (optional) [ ]

9) Reply received (reply)

(Complete when a reply arrives.)

Reply received? Yes [ ] No [ ] Pending [ ]
Date received: ____ / ____ / ______
Received by (name/role): ________________________________________

Summary of expert reply (5–10 lines):

Expert recommendation (tick):
Approve as is [ ] Approve with edits [ ] Do not approve [ ] Needs more tests/info [ ] Other: ____

Key required changes (list):

Attachments received (tick): Marked-up document [ ] Notes [ ] Call minutes [ ] Other: ____
File location/path: ________________________________________________

10) HSWAGATA follow-up actions

Action 1: _________________________________________________
Owner: __________________________ Deadline: //____

Action 2: _________________________________________________
Owner: __________________________ Deadline: //____

Update needed (tick): T212 FAQ [ ] T223 display text [ ] T214 risk assessment [ ] T216 consent notes [ ] Staff training (T222) [ ] Other: ____

11) Sign-off and filing

Prepared by (name/role): _______________________ Signature: __________ Date: //____
Reviewed by (Science/Verification lead): ________ Signature: __________ Date: //____
Reviewed by (Doctrinal/Ethics, if needed): ______ Signature: __________ Date: //____
Approved by (Director/Authority, if needed): ____ Signature: __________ Date: //____

File code / reference ID: ____________________
Classification recommended (T173): Internal [ ] Restricted [ ] Sacred-Restricted [ ]
File location (cabinet/folder + digital path): __________________________
Retention period: 3 years [ ] 5 years [ ] 10 years [ ] Other: ____

Template No.: T224 Template Title: Post-Testing Reflection & Lessons-Learned Sheet

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T224

Template Title: Post-Testing Reflection & Lessons-Learned Sheet

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link H for normative learning; F if conflict risk occurred)

Linked Templates / Policies: T214 (Risk Assessment for Testing Proposal), T216 (Ethics & Consent Review), T215 (Multi-Lab Dossier Summary), T217 (Data Storage & Access Register), T220 (Incident Report: Breach of Testing Protocol), T223 (Cross-Check Lab Reports vs Public Displays), T212 (Visitor FAQ Planning), T213 (Media Interview Prep), T190 (Media Approval), T169 (Learning Workshop Note), T163 (Risk Register Entry), T173 (Records Classification)

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 (why we use this sheet)

This sheet reflects on each testing project after it ends.
It records what worked, what did not work, and lessons learned.
It also checks impact on faith, heritage, and peace.

Important: Do not write exact security routines or other Sacred-Restricted details here.

2) Project identification (basic info)

Project / dossier title: __________________________________________
Project ID / code: _______________________________________________
Related object/item ID (internal): _________________________________
Testing period (from/to): ____ / ____ / ______ to ____ / ____ / ______
Lead unit/department: ____________________________________________
Project lead (name/role): ________________________________________

Linked records (write IDs):

T214 Risk Assessment ID: ____________________
T216 Ethics & Consent ID: ____________________
T215 Multi-lab dossier ID (if any): ____________________
T217 Data register file code(s): ____________________
T220 Incident report ID(s) (if any): ____________________
T223 Display cross-check ID(s) (if any): ____________________

3) Project aim and expected value

Main aim (1–2 sentences):

What we hoped to improve (tick):
Conservation care [ ] Truthful education [ ] Rumour response [ ] Better records [ ] Staff skills [ ] Partnership learning [ ] Other: ____

Was the aim reached? Yes [ ] Partly [ ] No [ ]
Short reason: _________________________________________________

4) Summary of what was done (high level only)

Write 3–6 lines. Keep it general and safe (no “how-to”).

5) What worked well (what worked)

Write 5–10 clear points.

Top success factor (one main reason):

6) What did not work well (what did not)

Write 5–10 clear points (facts, not blame).

Main cause (tick):
Planning gap [ ] Time pressure [ ] Training gap [ ] Partner gap [ ] Data control gap [ ] Communication gap [ ] Equipment issue [ ] Other: ____
Notes: ____________________________________________________________

7) Impact review (faith / heritage / peace)

Rate each area and explain briefly.

A) Faith impact (impact on trust and respect)

Faith impact level: Positive [ ] Neutral [ ] Negative [ ]
Why (2–5 lines):

Did any group feel disrespected or worried? Yes [ ] No [ ]
If Yes, what was the issue (short): _________________________________

B) Heritage impact (physical care and safety)

Heritage impact level: Improved care [ ] No change [ ] Increased risk [ ]
Why (2–5 lines):

Any damage suspected? Yes [ ] No [ ] Not sure [ ]
If Yes/Not sure: conservation follow-up needed. Yes [ ] No [ ] Ref: ____

C) Peace and harmony impact (community relations)

Peace impact level: Positive [ ] Neutral [ ] Negative [ ]
Why (2–5 lines):

Any conflict signs or tension? Yes [ ] No [ ]
If Yes: was it managed calmly? Yes [ ] No [ ] Notes: ________________

D) Misinformation impact (rumours and public understanding)

Rumour situation after project: Reduced [ ] Same [ ] Increased [ ]
Evidence (questions, posts, complaints) (short): ______________________

FAQ update needed (T212)? Yes [ ] No [ ]
Public display update needed (T223)? Yes [ ] No [ ]

8) Stakeholder feedback (what people said)

Tick and summarise.

Feedback sources used:
Staff [ ] Monastics/custodians [ ] Local community [ ] Donors [ ] Lab partners [ ] Visitors [ ] Media (approved) [ ]

Top 3 positive comments:

Top 3 concerns / complaints:

Complaint form (T183) linked? Yes [ ] No [ ] Ref: ____________________

9) Ethics, consent, and respect check (quick)

Consent was clear and respected (T216). Yes [ ] No [ ] Partly [ ]
Community consultation was adequate (if needed). Yes [ ] No [ ] Partly [ ]
No pressure from outside groups to “prove” things. Yes [ ] No [ ]
Public wording stayed respectful and truthful. Yes [ ] No [ ]

Notes (short):

10) Data and records check

All files stored in approved locations (T217). Yes [ ] No [ ] Partly [ ]
Access list is correct and updated. Yes [ ] No [ ]
Backups completed. Yes [ ] No [ ]
Any data incident/leak risk? Yes [ ] No [ ]
If Yes: link to T220/T163. Ref: _________________________________

Records to archive now (list file codes):

11) Lessons learned (lessons)

Write 5–10 lessons. Make them practical.

One key lesson to remember (1 sentence):

Learning workshop needed (T169)? Yes [ ] No [ ]
If Yes, date: //____ Facilitator: __________________________

12) Improvements and action plan (next steps)

List actions with owner and deadline.

Action 1: _________________________________________________

Owner: __________________________ Deadline: //____
Type (tick): SOP update [ ] Training [ ] Partnership rule [ ] Data control [ ] Display text [ ] Other: ____

Action 2: _________________________________________________

Owner: __________________________ Deadline: //____

Action 3: _________________________________________________

Owner: __________________________ Deadline: //____

Risk register entry needed (T163)? Yes [ ] No [ ] Risk ID: _____________

13) Communication follow-up (if public-facing)

Was any public message released? Yes [ ] No [ ]
If Yes:

Approved by T190? Yes [ ] No [ ] Ref: __________________________
Spokesperson prep used (T213)? Yes [ ] No [ ]
Any correction needed? Yes [ ] No [ ]

Notes (short):

14) Sign-off and approvals

Prepared by (name/role): _______________________ Signature: __________ Date: //____

Reviewed by (Science/Verification lead): ________ Signature: __________ Date: //____
Reviewed by (Conservation): ____________________ Signature: __________ Date: //____
Reviewed by (Doctrinal/Ethics): ________________ Signature: __________ Date: //____
Reviewed by (Security/Data custodian): __________ Signature: __________ Date: //____

Approved by (Director/Authority/Board if needed): _____________________
Signature: __________ Date: //____

15) Filing

Template No.: T223 Template Title: Cross-Check Form: Lab Reports vs Public Displays

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T223

Template Title: Cross-Check Form: Lab Reports vs Public Displays

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link H for ethical truthfulness)

Linked Templates / Policies: T212 (Visitor FAQ Planning), T190 (Media & Social Media Approval), T213 (Media Interview Preparation), T217 (Data Storage & Access Register), Scientific Verification SOP, Display Text / Interpretation Policy, T173 (Records Classification)

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 (why we use this form)

This form checks that public display text matches lab reports and approved findings.
It helps us keep displays truthful, respectful, and not exaggerated.

2) Documents being compared (what we are checking)

A) Lab report / technical source

Lab report title: ______________________________________________
Lab/institution name: ___________________________________________
Report date: ____ / ____ / ______
Report ID / file code: __________________________________________
Storage reference (T217 file code/path): ___________________________
Summary of key finding(s) (1–3 lines):

B) Public display / public text

Display type (tick): Wall label [ ] Panel [ ] Exhibit booklet [ ] Website page [ ] Audio guide [ ] Tour script [ ] Other: ____
Display location (gallery/area): _________________________________
Display item code / label ID: ____________________________________
Current display version number/date: _____________________________
Photo of panel/label stored? Yes [ ] No [ ] File ref: _____________

3) Cross-check rules (must follow)

Tick to confirm:

We do not claim “100% proof” if the lab report does not say it. [ ]
We state limits and uncertainty in simple words when needed. [ ]
We do not share restricted methods, security details, or private data. [ ]
We use respectful words about faith and sacred heritage. [ ]

4) Cross-check entries (main section)

(Use one entry per finding. Add pages as needed.)

Entry No.: ______

A) Finding (from lab report) (finding)

Finding title (short): ____________________________________________
Exact lab finding (short summary, 1–3 lines):
Confidence/limits stated by lab (tick): Clear limits [ ] Some limits [ ] Not stated [ ]
Notes on uncertainty (simple): ____________________________________

B) Current public display text (copy exact words) (current display text)
Paste the current text here (or attach and write “See attachment”):

C) Gap check (what is wrong, if anything)
Tick all that apply:

Display matches lab finding. [ ]
Display is too strong / exaggerated. [ ]
Display is unclear / confusing. [ ]
Display uses wrong term or wrong number. [ ]
Display misses the limits/uncertainty. [ ]
Display may cause faith harm or conflict. [ ]
Display may spread misinformation. [ ]
Other: __________________________ [ ]

Explain the gap (1–3 lines):

D) Needed change (new wording) (needed change)
Write the needed change in simple public language (2–6 lines).
(Keep it calm. Keep it truthful. Add limits if needed.)

E) Risk level if not changed
Low [ ] Medium [ ] High [ ]
Reason (short): _________________________________________________

F) Who will update

Assigned to (name/role): _______________________________________
Deadline: ____ / ____ / ______

G) Update record (complete after change) (date updated)

Was the display updated? Yes [ ] No [ ] In progress [ ]
Date updated: ____ / ____ / ______
New display version number/date: ________________________________
Photo/screenshot of updated text stored? Yes [ ] No [ ] File ref: ____
Old version removed/archived? Yes [ ] No [ ] Where archived: ______

5) Review and approvals (before public release)

Doctrinal/ethics check needed? Yes [ ] No [ ]
If Yes: reviewer name/role: _____________________ Date: //____

Science accuracy check needed? Yes [ ] No [ ]
If Yes: reviewer name/role/lab: __________________ Date: //____

Communications approval needed? Yes [ ] No [ ]
If Yes: use T190 for public text update. Ref ID: ______________________

Approved by (name/role): _______________________ Signature: __________ Date: //____

6) Notes and lessons (optional)

What did we learn (1–5 points)?

FAQ update needed (T212)? Yes [ ] No [ ] Note: ______________________
Staff training needed (T222)? Yes [ ] No [ ] Topic: _________________

7) Filing

File code / reference ID: ____________________
Classification recommended (T173): Internal [ ] Restricted [ ]
File location (cabinet/folder + digital path): __________________________

Template No.: T222 Template Title: Staff Training Log: Science & Misinformation

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T222

Template Title: Staff Training Log: Science & Misinformation

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link H for ethics; C for systems)

Linked Templates / Policies: Scientific Verification SOP, Communication Policy, T213 (Media Interview Prep), T212 (Visitor FAQ Planning), T190 (Media Approval), T169 (Learning Workshop Note), T163 (Risk Register Entry), T166 (Induction Checklist), T173 (Records Classification)

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 (why we use this log)

This log records all staff training on science topics and misinformation control.
It shows who was trained, what was taught, and how well it worked.

2) Training programme details (for the log period)

Log period (month/quarter/year): ______________________________
Department/unit running training: ______________________________
Training coordinator (name/role): ______________________________
Review frequency (tick): Monthly [ ] Quarterly [ ] Yearly [ ]

3) Quick rules (must follow)

Tick to confirm:

Training uses simple, truthful language (no exaggerated claims). [ ]
No sharing of Sacred-Restricted details in training notes. [ ]
Attendance and evaluation records are stored safely (privacy). [ ]
If a gap is found, we plan a follow-up training. [ ]

4) Training session register (summary table)

(Use one line per session. Add pages as needed.)

Columns to fill (one row per session):

Session ID
Date
Topic/title
Trainer (name/role/organisation)
Duration
Audience (staff/volunteers/guards/guides)
Number planned / number attended
Location (room/online)
Evaluation method (quiz/feedback/observation)
Result summary (pass rate / key issues)
Follow-up needed (Y/N)
File location / reference ID

Register entries

(Add more entries as needed.)

5) Training session record (full details)

(Complete this section for each session. Copy this section as needed.)

A) Session identification

Session ID / code: ______________________________
Session date: ____ / ____ / ______
Time: __________ to __________ (Total minutes: ________)
Location (room/online platform): ______________________________
Training type (tick): Induction [ ] Refresher [ ] New policy/SOP [ ] Incident response [ ] Media readiness [ ] Other: ____

B) Topic and purpose

Training topic/title (topic): _____________________________________
Why this training (purpose, 1–2 lines):

C) Trainer details (trainer)

Trainer 1

Name/role/organisation: _________________________________________
Contact (internal use): __________________________________________
Trainer 2 (optional) _______________________________________________

D) Content outline (what was covered)

Tick and add notes.

Basic museum science (simple explanation) [ ] Notes: ________________
Limits of science (uncertainty, careful claims) [ ] Notes: ____________
How misinformation spreads (rumours, social media) [ ] Notes: ________
How staff should answer visitor questions (calm, truthful) [ ] Notes: __
“Red lines” (no security details, no “how-to testing”) [ ] Notes: ______
Using approved messages (FAQ / key lines) [ ] Notes: ________________
When to refer questions to the science/comms team [ ] Notes: _________
Case example used (non-sensitive) [ ] Notes: _______________________
Other content: __________________________ [ ] Notes: _______________

E) Participants (participants)

Audience group (tick): Front desk [ ] Guides [ ] Security [ ] Conservation [ ] Admin [ ] Volunteers [ ] Mixed [ ]
Attendance list attached? Yes [ ] No [ ]
If Yes, where filed (path/ref): ______________________________________

Participant list (optional small group):

Name/role: __________________________ Signature: __________
Name/role: __________________________ Signature: __________
Name/role: __________________________ Signature: __________
(Add more as needed.)

F) Learning goals (simple)

By the end, participants can:

6) Evaluation (evaluation)

A) Evaluation method (tick)

Quick quiz [ ] Short written test [ ] Verbal Q&A [ ] Observation in real work [ ] Role-play practice [ ] Feedback form [ ] Other: ____

B) Results (write numbers if possible)

Number evaluated: ________
Pass/meet standard: ________
Need support / re-train: ________

Common mistakes seen (short):

What went well (short):

C) Trainer and participant feedback

Trainer comment (2–5 lines):

Participant feedback summary (2–5 lines):

7) Corrective actions and follow-up

Follow-up needed? Yes [ ] No [ ]

If Yes, list actions:
Action 1: __________________________________ Owner: __________ Date: //____
Action 2: __________________________________ Owner: __________ Date: //____

Update needed (tick):
Visitor FAQ (T212) [ ] Media prep lines (T213) [ ] SOP/training materials [ ] Other: ____

Risk register entry needed (T163)? Yes [ ] No [ ] Risk ID: __________
Learning note needed (T169)? Yes [ ] No [ ] Reference: _____________

8) Attachments (optional)

Tick what is filed with this session:
Slides/handouts [ ] Quiz sheet [ ] Answer key [ ] Attendance sheet [ ] Photos (non-sensitive) [ ] Trainer CV/credentials [ ] Other: ____

File path / reference ID: ____________________________________________

9) Sign-off and filing

Prepared by / coordinator (name/role): __________________ Signature: __________ Date: //____
Trainer (name/role): _________________________________ Signature: __________ Date: //____
Reviewed by (Unit Head / Science lead): ________________ Signature: __________ Date: //____

File code / reference ID: ____________________
Classification recommended (T173): Internal [ ] Restricted [ ]
File location (cabinet/folder + digital path): __________________________
Retention period: 1 year [ ] 3 years [ ] 5 years [ ] Other: ____

Template No.: T221 Template Title: Annual Science & Education Programme Plan (Outreach)

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T221

Template Title: Annual Science & Education Programme Plan (Outreach)

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link D for community engagement; H for long-term ethics planning)

Linked Templates / Policies: T211 (Science–Faith Dialogue Event Plan), T212 (Visitor FAQ Planning), T213 (Media Interview Prep), T190 (Media Content Approval), T185 (School Visit Planning), T197 (Youth Engagement Activity Plan), T180 (Community Event Proposal), T163 (Risk Register Entry), T173 (Records Classification), Visitor Safety Plan, Relic Respect & Safeguarding Rules

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 (why we use this plan)

This plan lists the science and education programme for one year.
It helps HSWAGATA teach carefully, reduce rumours, and protect faith, heritage, and peace.

2) Plan identity (basic details)

Programme year: ________
Plan period: ____ / ____ / ______ to ____ / ____ / ______
Programme lead (name/role): ____________________________________
Science/verification support (name/role): _________________________
Doctrinal/ethics support (name/role): ____________________________
Communications support (name/role): _____________________________

Short programme theme (1 line):

3) Main objectives (5–7)

Tick or write simple objectives.

Teach visitors what museum science is (in simple words). [ ]
Reduce misinformation and rumours about relics. [ ]
Build respectful science–faith dialogue. [ ]
Support schools and youth learning safely. [ ]
Train staff/volunteers to speak truthfully and calmly. [ ]
Build partnerships with credible labs and educators. [ ]
Share public-safe care practices (no sensitive details). [ ]

Other objective: ________________________________________________ [ ]

4) Target groups (who we serve)

Tick all that apply and estimate numbers.

General visitors: ________ / year
Pilgrims: ________ / year
School groups (teachers + students): ________ / year
Youth groups (clubs, scouts, etc.): ________ / year
Community leaders/elders: ________ / year
Donors/supporters: ________ / year
Media (approved only): ________ / year
University/research visitors: ________ / year
Other: ____________________ Estimated: ________ / year

5) Key partners (partners)

List planned partners and what they do.

Partner 1: ______________________________________________

Type: Lab [ ] University [ ] School [ ] Temple [ ] NGO [ ] Government [ ] Other: ____
Planned role: Speaker [ ] Review content [ ] Host visit [ ] Provide materials [ ] Other: ____

Partner 2: ______________________________________________

Planned role: ______________________________________________

Partner 3: ______________________________________________

Planned role: ______________________________________________

Partner checks needed (T218 / T157)? Yes [ ] No [ ] Ref: __________

6) Programme activities (annual activity list)

(Use one line per activity. Add rows as needed.)

Columns to fill: Activity name • Format • Target group • Quarter/month • Lead • Partners • Estimated participants • Cost estimate • Risk level • Approval needs

Activity 1

Activity name: _________________________________________________
Format (tick): Talk [ ] Workshop [ ] Tour [ ] School visit [ ] Dialogue [ ] Exhibit panel [ ] Online post [ ] Training [ ] Other: ____
Target group: _________________________________________________
Time (quarter/month/date): _______________________________________
Lead (name/role): ______________________________________________
Partners: ______________________________________________________
Estimated participants: ________
Estimated cost: ____________________ (currency: ________)
Risk level: Low [ ] Medium [ ] High [ ]
Needed templates/approvals: T211 [ ] T190 [ ] T185 [ ] T197 [ ] Other: ____

Activity 2

Activity name: _________________________________________________
Format: _________________________________________________
Target group: _________________________________________________
Time: _______________________________________
Lead: _______________________________________
Partners: ____________________________________
Estimated participants: ________
Estimated cost: ____________________
Risk level: Low [ ] Medium [ ] High [ ]
Approvals needed: _____________________________

Activity 3

(Repeat as needed)

7) Content plan (what we will teach)

Tick key content themes for the year.

“What science can do” (careful, limited claims) [ ]
“What science cannot prove” (limits and uncertainty) [ ]
Basic conservation care (safe, public-safe information) [ ]
How to check rumours and misinformation [ ]
Respectful language for sacred heritage [ ]
Peace and harmony in public communication [ ]
Visitor FAQ updates (T212) [ ]
Other theme: ________________________________ [ ]

Doctrinal/ethics check needed for content? Yes [ ] No [ ]
Reviewer (name/role): _____________________________________________

Lab/science review needed for content? Yes [ ] No [ ]
Reviewer/lab: _________________________________________________

8) Communications and media plan (public-facing)

Public announcements needed? Yes [ ] No [ ]
If Yes: use T190 for each post. Yes [ ]
Will any media interviews happen? Yes [ ] No [ ]
If Yes: use T213 for preparation. Yes [ ]

Key public message (1–2 lines):

Red lines (must follow):

No Sacred-Restricted details. [ ]
No “how-to testing” instructions. [ ]
No exaggerated claims. [ ]

9) Budget plan (annual)

Currency: ________

A) Budget lines (fill amounts)

Speakers/transport/hospitality: ____________________
Printing (posters, leaflets, panels): ____________________
Education materials (worksheets, kits): ____________________
Interpretation/language support: ____________________
Audio/visual (mic, projector, rental): ____________________
Staff/volunteer support (meals, local travel): ____________________
Partner/lab review costs (approved): ____________________
Accessibility support (ramps/signs/seating as needed): ____________________
Safety/first aid/event needs: ____________________
Other: ____________________ Amount: ____________________

Total planned budget: ____________________

B) Funding sources

Museum budget [ ] Donors (approved) [ ] Grants [ ] Partner support [ ] Other: ____
Notes (no donor control of results): ___________________________________

10) Risks and safeguards (required)

Tick main risks for the programme.

Misinformation/rumours risk [ ]
Community tension risk [ ]
Media sensational risk [ ]
Safety/crowd risk [ ]
Reputational risk [ ]
Data/privacy risk [ ]

Main mitigations (short):

Risk register entry needed (T163)? Yes [ ] No [ ] Risk ID: _____________

11) Monitoring and evaluation (how we know it worked)

A) Indicators (tick and fill)

Number of events delivered: target ________
Number of people reached: target ________
Number of school/youth activities: target ________
Visitor FAQ produced/updated (T212): Yes [ ] No [ ]
Staff/volunteer training sessions: target ________
Reduction of repeated rumours (tracked by questions/complaints): Yes [ ] No [ ]

B) Feedback tools

Use: T183 [ ] Short paper form [ ] Teacher feedback [ ] Online survey [ ] Other: ____

Monthly/quarter review dates: Q1 //____ Q2 //____ Q3 //____ Q4 //____

12) Approvals and sign-off

Prepared by (name/role): _______________________ Signature: __________ Date: //____

Reviewed by (Science/Verification): _____________ Signature: __________ Date: //____
Reviewed by (Doctrinal/Ethics): ________________ Signature: __________ Date: //____
Reviewed by (Communications): _________________ Signature: __________ Date: //____
Reviewed by (Safety/Security): ________________ Signature: __________ Date: //____

Approved by (Director/Authority): ______________ Signature: __________ Date: //____

13) Filing

File code / reference ID: ____________________
Classification recommended (T173): Internal [ ] Restricted [ ]
File location (cabinet/folder + digital path): __________________________

Template No.: T220 Template Title: Incident Report: Breach of Testing Protocol

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T220

Template Title: Incident Report: Breach of Testing Protocol

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (add F if conflict risk; add G if loss/neglect risk)

Linked Templates / Policies: Scientific Verification SOP, Chain-of-Custody SOP, T214 (Testing Risk Assessment), T216 (Ethics & Consent Review), T217 (Data Storage & Access Register), T218 (Partner Reputation & COI Check), T219 (Equipment Loan/Borrow), T213 (Media Interview Prep), T190 (Media Approval), T169 (Learning Workshop Note), T163 (Risk Register Entry), T173 (Records Classification), T183 (Feedback/Complaint)

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 (why we use this form)

This form records any breach of testing protocol (a mistake or rule break).
It helps protect faith, heritage, and peace. It also helps learning and prevention.

Important: Do not write exact security routines, exact storage locations, or other Sacred-Restricted details here.

2) Incident identification (basic details)

Incident ID / code: ______________________________
Date discovered: ____ / ____ / ______
Time discovered: __________
Date incident happened (if known): ____ / ____ / ______
Time incident happened (if known): __________
Location (general): On-site lab area [ ] Storage support area [ ] Display area [ ] Offsite lab [ ] Transport [ ] Digital system [ ] Other: ______
Reported by (name/role): _______________________________________
Incident owner (name/role): _____________________________________

Related project/dossier: ______________________________ (T215 ID if any: __________)
Related object/item case (internal ID): ___________________________

3) What happened (summary)

Write 3–8 lines. Use facts only.

4) What protocol was breached? (tick all that apply)

Testing process

Unapproved method used [ ]
Steps not followed / missing checklist [ ]
Sampling attempted without approval [ ]
Equipment not calibrated / wrong settings [ ]
Wrong labeling / mix-up risk [ ]
Poor environment control (heat/light/humidity) [ ]
Other: __________________________ [ ]

Chain-of-custody / access

Unauthorised person handled item [ ]
Access rules not followed [ ]
Transport/handling log incomplete [ ]
Item left unattended [ ]
Other: __________________________ [ ]

Data and confidentiality

File shared to wrong person [ ]
File stored in wrong place (personal device/USB) [ ]
Missing encryption/password [ ]
Public statement made too early [ ]
Other: __________________________ [ ]

Which SOP/policy section was breached (if known): _____________________________

5) People and organisations involved (roles only if sensitive)

HSWAGATA staff involved (name/role):

External lab/partner involved? Yes [ ] No [ ]
If Yes, organisation name: __________________________________________
Main contact (role/name): __________________________________________

Witnesses (optional): ______________________________________________

6) Immediate containment actions (what we did right away)

Tick what was done.

Work stopped immediately [ ] Time: ________
Item secured (authorised storage only) [ ]
Area secured / access limited [ ]
Supervisor informed [ ]
Security informed (if needed) [ ]
Conservation informed [ ]
Data access removed/locked [ ]
Incorrect file deleted/moved to correct secure folder [ ]
Equipment taken out of use [ ]
Other immediate action: __________________________ [ ]

Immediate actions details (short):

7) Impact assessment (impact)

A) Impact type (tick all that apply)

Faith/trust impact (community upset, disrespect concern) [ ]
Heritage impact (damage risk, contamination, loss) [ ]
Peace impact (conflict/rumours/media risk) [ ]
Legal/compliance impact [ ]
Data/privacy impact [ ]
Safety impact (people injured or near-miss) [ ]

B) Severity rating

Likelihood: 1 Rare [ ] 2 Unlikely [ ] 3 Possible [ ] 4 Likely [ ] 5 Almost certain [ ]
Impact: 1 Minor [ ] 2 Low [ ] 3 Medium [ ] 4 High [ ] 5 Severe [ ]

Overall severity (tick): Low [ ] Medium [ ] High [ ] Critical [ ]

C) Impact notes (facts only)

What was affected (item/data/people): _______________________________
Any physical damage suspected? Yes [ ] No [ ] Not sure [ ]
If Yes/Not sure, conservation check required.

Notes:

8) Notifications and escalation (who was informed)

Tick and fill dates.

Unit Head informed [ ] Date: //____
Director informed [ ] Date: //____
Board informed (if needed) [ ] Date: //____
Conservation lead informed [ ] Date: //____
Doctrinal/Ethics advisor informed [ ] Date: //____
Security lead informed [ ] Date: //____
IT/Data custodian informed [ ] Date: //____
Partner lab informed [ ] Date: //____
Government/authority informed (if required) [ ] Date: //____

Any public/media risk? Yes [ ] No [ ]
If Yes: use T213 for messages and T190 for approvals. No public talk until approved.

9) Root cause review (why it happened)

Tick main cause(s). Add short notes.

Lack of training/induction [ ]
Poor supervision / unclear roles [ ]
Time pressure / rushed work [ ]
Checklist not used [ ]
Wrong equipment / equipment failure [ ]
Poor communication with partner [ ]
Poor data control / wrong folder access [ ]
Human error (mistake) [ ]
Unclear consent/permission limits [ ]
Other cause: __________________________ [ ]

Root cause notes (2–6 lines):

10) Corrective actions (fix now)

List actions that correct the problem. Include owner and deadline.

Corrective action 1: _______________________________________________

Owner: __________________________ Deadline: //____
Status: Open [ ] In progress [ ] Done [ ]

Corrective action 2: _______________________________________________

Owner: __________________________ Deadline: //____
Status: Open [ ] In progress [ ] Done [ ]

Corrective action 3: _______________________________________________

Owner: __________________________ Deadline: //____
Status: Open [ ] In progress [ ] Done [ ]

If data was involved: update T217 entry? Yes [ ] No [ ] File code: __________
If equipment was involved: update T219? Yes [ ] No [ ] Loan ref: __________

11) Preventive actions (stop it happening again)

Tick and plan.

Update SOP/checklist [ ] Link to T162 (SOP cover) if needed: ________
New training for staff/partners [ ]
Stronger access controls (roles/permissions) [ ]
Two-person verification for key steps [ ]
Better labeling and documentation rules [ ]
Better pre-brief with partner labs [ ]
Update risk assessment (T214) [ ]
Other prevention: __________________________ [ ]

Prevention action plan (owner + deadline):

12) Learning and reflection (learning)

Write 3–7 lessons. Keep them practical and simple.

Learning workshop needed (T169)? Yes [ ] No [ ]
If Yes, planned date: //____ Facilitator: _____________________

Risk register entry needed (T163)? Yes [ ] No [ ] Risk ID: _____________

13) Closure (when the case is finished)

Case closed? Yes [ ] No [ ]
Closure date: ____ / ____ / ______
Closed by (name/role): ____________________________________________

Evidence attached (tick):
Photos (safe) [ ] Logs [ ] Email trail [ ] Lab note [ ] Data access log [ ] Training record [ ] Other: ____

14) Signatures and approvals

Prepared by (name/role): _______________________ Signature: __________ Date: //____

Reviewed by (Science/Verification lead): ________ Signature: __________ Date: //____
Reviewed by (Conservation, if item risk): _______ Signature: __________ Date: //____
Reviewed by (Security/Data, if needed): _________ Signature: __________ Date: //____
Reviewed by (Doctrinal/Ethics, if faith impact): _ Signature: __________ Date: //____

Approved by (Director/Authority/Board if needed): _____________________
Signature: __________ Date: //____

15) Filing

Template No.: T219 Template Title: Scientific Equipment Loan / Borrow Form

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T219

Template Title: Scientific Equipment Loan / Borrow Form

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link C for partnerships; G for maintenance care)

Linked Templates / Policies: Asset Management Policy, Lab Safety SOP, Chain-of-Custody SOP (for sensitive tools), T218 (Partner Reputation & COI Check), T163 (Risk Register Entry), T173 (Records Classification)

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 (why we use this form)

This form records any scientific equipment that is borrowed or loaned.
It tracks the item, condition, who has it, dates, and return condition.

2) Loan type and reference

Loan type (tick):
HSWAGATA borrows from partner [ ]
HSWAGATA loans to partner [ ]
Internal loan (between departments) [ ]

Loan reference / ID: _______________________________
Related project/dossier ID (if any): _______________________________
Related partner check (T218 ID, if external): _______________________

3) Item details (item)

Item name: _______________________________________________
Item category (tick): Measuring device [ ] Imaging tool [ ] Storage/packing tool [ ] PPE/safety [ ] Computer/drive [ ] Other: ____
Brand/model (if any): ______________________________________
Serial number / asset tag: _________________________________
Quantity: ________

Accessories included (tick): Case [ ] Charger [ ] Cable [ ] Batteries [ ] Manual [ ] Calibration certificate [ ] Other: ____
List accessories (if needed): _______________________________________

4) Condition at handover (condition)

Date checked: ____ / ____ / ______
Checked by (name/role): __________________________________________

Condition (tick): New [ ] Good [ ] Fair [ ] Poor [ ] Not working [ ]

Condition notes (write clearly):

Photos taken at handover? Yes [ ] No [ ]
If Yes, photo file/path: ____________________________________________

Calibration status (if relevant)

Calibration needed? Yes [ ] No [ ]
Last calibration date (if known): ____ / ____ / ______
Calibration proof attached? Yes [ ] No [ ] NA [ ]

5) From / To (from/to)

A) Lender (from)

Organisation/unit: ________________________________________________
Person name/role: ________________________________________________
Phone/email: _________________________________________________
Address/location (optional): ______________________________________

B) Borrower (to)

Organisation/unit: ________________________________________________
Person name/role: ________________________________________________
Phone/email: _________________________________________________
Use location (general): ____________________________________________

6) Loan dates and return plan (dates)

Date issued / handed over: ____ / ____ / ______
Time issued: ________
Expected return date: ____ / ____ / ______
Expected return time (optional): ________
Actual return date (complete later): ____ / ____ / ______
Actual return time (complete later): ________

Reason for loan (short):

Approved use only (tick):
Conservation care [ ] Documentation [ ] Education demo (approved) [ ] Lab testing support (approved) [ ] Other: ____

7) Handling and safety rules (must tick)

Borrower received basic use instructions. Yes [ ] No [ ]
Borrower will use PPE if needed. Yes [ ] No [ ] NA [ ]
Item will be kept dry, clean, and secure. Yes [ ] No [ ]
Item will not be shared to another person without approval. Yes [ ] No [ ]
No use in restricted/sacred areas unless authorised. Yes [ ] No [ ]
Data devices (USB/drives/laptops) follow data security rules. Yes [ ] No [ ] NA [ ]

Special handling notes (if fragile/sensitive):

8) Responsibility and liability (simple)

Responsible borrower (name/role): _________________________________
If lost/damaged, borrower must report within: 24 hours [ ] 48 hours [ ] Other: ____
Repair/replacement rule (tick): Borrower pays [ ] Shared cost [ ] Case-by-case [ ] Not stated [ ]

Insurance / liability document attached (if external loan)? Yes [ ] No [ ] NA [ ]

9) Return condition check (return condition)

(Complete when item is returned.)

Returned to (name/role): _________________________________________
Return condition (tick): Same as issued [ ] Minor wear [ ] Damaged [ ] Missing parts [ ] Not working [ ]
Condition notes: _________________________________________________
Accessories returned fully? Yes [ ] No [ ] List missing: _______________

Photos taken at return? Yes [ ] No [ ]
If Yes, photo file/path: ____________________________________________

Action needed (tick):
Clean [ ] Repair [ ] Re-calibrate [ ] Replace [ ] No action [ ]
Work order / maintenance note (if any): ______________________________

10) Signatures (handover and return)

Handover signatures

Lender name/role: __________________________ Signature: __________ Date: //____
Borrower name/role: ________________________ Signature: __________ Date: //____
HSWAGATA witness (if needed): ______________ Signature: __________ Date: //____

Return signatures (complete later)

Returned by (name/role): ____________________ Signature: __________ Date: //____
Received by (name/role): ____________________ Signature: __________ Date: //____

11) Filing

Template No.: T218 Template Title: Partner Reputation & Conflict-of-Interest Check Form

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T218

Template Title: Partner Reputation & Conflict-of-Interest Check Form

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link C for partnerships/MoUs; F for conflict risk; H for ethics model)

Linked Templates / Policies: T157 (Partnership Proposal Evaluation), T156 / T24 (MoU templates), T214 (Risk Assessment for Testing Proposal), T216 (Ethics & Consent Review), T213 (Media Interview Prep), T190 (Media Approval), T163 (Risk Register Entry), T173 (Records Classification)

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 (why we use this form)

This form checks a partner’s reputation and conflict of interest (COI) before cooperation.
It helps protect faith, heritage, public trust, and peace.

2) Partner identity (partner details)

Partner organisation name: ________________________________________
Type (tick): Lab [ ] University [ ] Museum [ ] NGO [ ] Company [ ] Temple [ ] Government office [ ] Other: ______
Country/city: _________________________________________________
Website (optional): _____________________________________________

Main contact person

Name/title: _________________________________________________
Email/phone: _________________________________________________

HSWAGATA link

Proposed project / reason for partnership: __________________________
Related dossier/proposal ID (if any): _______________________________
Related templates (tick): T157 [ ] T214 [ ] T215 [ ] T216 [ ] Other: ____

3) Quick screening (stop/hold triggers)

Tick if any apply. If “Yes”, consider Hold and escalate.

Partner refuses to share basic legal identity/registration. Yes [ ] No [ ]
Partner demands secrecy that breaks museum policy. Yes [ ] No [ ]
Partner asks for special access to restricted relic areas. Yes [ ] No [ ]
Partner promises “guaranteed proof” or “miracle verification.” Yes [ ] No [ ]
Partner wants media publicity before ethics approval. Yes [ ] No [ ]
Partner has active legal case that may affect trust. Yes [ ] No [ ]

Notes: ____________________________________________________________

4) Reputation check (known controversies)

A) Known controversies (write facts only)

Controversy 1 (what is known): ______________________________________

Source type (tick): News [ ] Official report [ ] Court record [ ] Community report [ ] Online claim [ ] Other: ____
Year/date (if known): ___________________________________________
Status (tick): Confirmed [ ] Not confirmed [ ] Mixed/unclear [ ]
Risk to HSWAGATA (tick): Low [ ] Medium [ ] High [ ]
Notes: ____________________________________________________________

Controversy 2: _________________________________________________

Status: Confirmed [ ] Unclear [ ]
Risk level: Low [ ] Medium [ ] High [ ]
Notes: ____________________________________________________________

B) Public trust signals (positive/negative)

Tick and note evidence.

Good reputation in heritage/science community [ ] Notes: _____________
Strong ethics policy published [ ] Notes: ___________________________
Past partnerships with credible institutions [ ] Notes: _______________
Complaints from communities about disrespect [ ] Notes: _____________
Accusations of “fake relic testing” or scams [ ] Notes: _______________
Other signal: __________________________ [ ] Notes: ________________

5) Funding sources and independence (funding sources)

List what is known. If unknown, mark “unknown” and request info.

Main funding sources (tick): Government [ ] University [ ] Private donors [ ] Corporate [ ] Service fees [ ] Grants [ ] Unknown [ ]
Details: __________________________________________________________
Any funding linked to political parties or conflict groups? Yes [ ] No [ ] Not sure [ ]
If Yes/Not sure, explain carefully: __________________________________
Any funding linked to heritage trade / collectors market? Yes [ ] No [ ] Not sure [ ]
Notes: ____________________________________________________________

6) Conflict-of-interest (COI) check (links to conflicts)

COI means: a personal or organisational interest that may bias decisions.

A) Organisational COI

Partner sells paid “authentication certificates” to the public. Yes [ ] No [ ] Not sure [ ]
Partner earns money based on a “positive result.” Yes [ ] No [ ] Not sure [ ]
Partner wants exclusive rights to publish first. Yes [ ] No [ ] Not sure [ ]
Partner requests ownership/control of data. Yes [ ] No [ ] Not sure [ ]
Partner has a commercial product linked to this project. Yes [ ] No [ ] Not sure [ ]

Notes: ____________________________________________________________

B) Individual COI (key persons)

For each key person, record declared interests.

Person 1 name/title: _______________________________________________

Declared COI? Yes [ ] No [ ] Not asked [ ]
COI details (short): ______________________________________________

Person 2 name/title: _______________________________________________

Declared COI? Yes [ ] No [ ] Not asked [ ]
COI details (short): ______________________________________________

COI declaration form attached? Yes [ ] No [ ]

7) Links to conflicts or sensitive disputes (peace risk)

Tick if any link exists.

Partner linked to past heritage disputes (ownership/return cases). Yes [ ] No [ ] Not sure [ ]
Partner linked to theft, illicit trade, or handling unproven objects. Yes [ ] No [ ] Not sure [ ]
Partner linked to community tensions (religious/ethnic/political). Yes [ ] No [ ] Not sure [ ]
Partner linked to misinformation campaigns. Yes [ ] No [ ] Not sure [ ]

Notes (facts only, no rumours): ______________________________________

If peace risk seems medium/high, consider: T214 [ ] T163 [ ] and senior review.

8) Due diligence documents requested (what we asked for)

Tick and record what is received.

Legal registration documents [ ] Received [ ] Date: //____
Ethics policy / code of conduct [ ] Received [ ] Date: //____
List of board/owners (if relevant) [ ] Received [ ] Date: //____
Lab accreditation / credentials [ ] Received [ ] Date: //____
Past project references (2–3) [ ] Received [ ] Date: //____
Data security policy [ ] Received [ ] Date: //____
COI declarations (key staff) [ ] Received [ ] Date: //____
Insurance / liability coverage (if needed) [ ] Received [ ] Date: //____
Other: __________________________ [ ] Received [ ] Date: //____

Missing items (list): _______________________________________________

9) Risk rating and mitigation (decision support)

A) Risk ratings (tick)

Reputation risk: Low [ ] Medium [ ] High [ ]
COI risk: Low [ ] Medium [ ] High [ ]
Peace/conflict risk: Low [ ] Medium [ ] High [ ]
Data/security risk: Low [ ] Medium [ ] High [ ]

Overall risk (tick): Low [ ] Medium [ ] High [ ] Critical [ ]

B) Mitigation options (tick and note)

Require written COI declarations and publish limits [ ] Notes: _________
Use independent second lab review [ ] Notes: _______________________
Use strong MoU clauses (data, publication, confidentiality) [ ] Notes: __
Limit access to files/objects (need-to-know) [ ] Notes: ______________
Use neutral language in all public text [ ] Notes: ___________________
Hold/stop partnership until missing docs arrive [ ] Notes: ____________
Other mitigation: __________________________ [ ] Notes: ____________

10) Decision and approvals

Decision (tick one):
Approve partner (low risk) [ ]
Approve with conditions/mitigation [ ]
Hold for more checks / documents [ ]
Do not approve partner [ ]

Reasons (short, factual):

If approved with conditions, list conditions:

Risk register entry needed (T163)? Yes [ ] No [ ] Risk ID: _____________

11) Signatures and filing

Prepared by (name/role): _______________________ Signature: __________ Date: //____

Reviewed by (Science/Verification lead): ________ Signature: __________ Date: //____
Reviewed by (Doctrinal/Ethics): ________________ Signature: __________ Date: //____
Reviewed by (Security/Data): ___________________ Signature: __________ Date: //____

Approved by (Director/Authority/Board): _________ Signature: __________ Date: //____

Template No.: T217 Template Title: Data Storage & Access Register (Testing Files)

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T217

Template Title: Data Storage & Access Register (Testing Files)

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65

Linked Templates / Policies: T173 (Archive & Records Classification), Scientific Verification SOP, Chain-of-Custody SOP, T215 (Multi-Lab Dossier Summary), T216 (Ethics & Consent Review), T213 (Media Interview Prep), T190 (Media Approval), Data/Privacy Rules

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 (why we use this register)

This register tracks testing files (photos, lab data, reports).
It shows where files are stored, who can access them, and how backups are done.

2) Register control (who manages this register)

Register owner (name/role): ______________________________________
Backup owner (name/role): ________________________________________
Register location (folder/cabinet/path): ____________________________
Review cycle (tick): Monthly [ ] Quarterly [ ] After each project [ ] Yearly [ ]
Last review date: ____ / ____ / ______
Next review date: ____ / ____ / ______

3) Simple rules (must follow)

Tick to confirm these rules are applied:

Files are not stored on personal phones/laptops/USB. [ ]
Files are shared only with approved people and approved labs. [ ]
Sacred-Restricted files are stored in the highest security storage. [ ]
Access is “need-to-know” only. [ ]
Public posts or media sharing need separate approval (T190/T213). [ ]

4) Access levels (choose one per file)

Use the same words in each entry:

Public (rare for testing files): can be shared openly.
Internal: staff use only.
Restricted: limited staff + named roles only.
Sacred-Restricted / Sensitive: very limited access; extra control.

5) Data storage & access entries (main table)

(Use one entry per file set. Add pages as needed.)

Entry 1

File code / ID: ______________________________________________
File title (short): ___________________________________________
File type (tick): Photo [ ] Video [ ] Audio [ ] Notes [ ] Raw lab data [ ] Report [ ] Consent proof [ ] Chain-of-custody record [ ] Other: ____
Related project/dossier ID (T215 if any): ________________________
Related consent/risk refs (T216/T214 IDs): ________________________
Date created/received: ____ / ____ / ______
Created by / source (role or lab name): ___________________________

Storage location (where it is kept)

Primary location (system + path/cabinet): __________________________
Physical copy exists? Yes [ ] No [ ]
If Yes, physical location: ______________________________________

Classification and access

Classification (T173): Public [ ] Internal [ ] Restricted [ ] Sacred-Restricted [ ]
Access level (must match above): _________________________________
People allowed (names or roles):
1. __________________________ 2) __________________________
2. __________________________ 4) __________________________
External lab access allowed? Yes [ ] No [ ]
If Yes, lab name + scope (what they can see): ______________________
Access approval required from (tick): Unit Head [ ] Director [ ] Board [ ] Security lead [ ] Other: ____

Controls

Password/encryption used? Yes [ ] No [ ]
Two-factor login used (if available)? Yes [ ] No [ ]
Download/print allowed? Yes [ ] No [ ]
If Yes, limits: _________________________________________________

Backup

Backup exists? Yes [ ] No [ ]
Backup location: _______________________________________________
Backup method (tick): Automatic [ ] Manual [ ]
Backup frequency: Daily [ ] Weekly [ ] Monthly [ ] Other: ____
Last backup date: ____ / ____ / ______

Retention

Retention period (tick): 1 year [ ] 3 years [ ] 5 years [ ] 10 years [ ] Permanent [ ]
Planned archive/secure delete date (if not permanent): ____ / ____ / ______

Notes (short):

Entry 2

File code / ID: ______________________________________________
File title: _________________________________________________
File type: Photo [ ] Video [ ] Notes [ ] Raw lab data [ ] Report [ ] Other: ____
Primary location: ____________________________________________
Classification (T173): Internal [ ] Restricted [ ] Sacred-Restricted [ ]
People allowed (names/roles): ____________________________________
Backup location + last backup date: ________________________________
Notes: ______________________________________________________

(Add more entries as needed.)

6) Access change record (when people are added/removed)

Use this section when access permissions change.

Change #1

Date: ____ / ____ / ______
File code/ID: ______________________________________________
Change (tick): Add access [ ] Remove access [ ] Change level [ ] Move file [ ]
Person/role affected: ________________________________________
Reason (short): _____________________________________________
Approved by (name/role): __________________ Signature: ________

Change #2

Date: ____ / ____ / ______
File code/ID: ______________________________________________
Change: Add [ ] Remove [ ] Change level [ ] Move [ ]
Approved by: ___________________________ Signature: ________

7) Incident note (if data is lost, leaked, or wrongly shared)

Tick if any incident happened: Yes [ ] No [ ]
If Yes:

Date: ____ / ____ / ______
What happened (short, factual): ___________________________________
Immediate action taken: __________________________________________
Who was informed (roles): ________________________________________
Risk register entry made (T163)? Yes [ ] No [ ] Risk ID: _____________

8) Sign-off and filing

Prepared by (name/role): _______________________ Signature: __________ Date: //____
Reviewed by (Science/Verification lead): ________ Signature: __________ Date: //____
Reviewed by (Security/Data custodian): __________ Signature: __________ Date: //____
Approved by (Director/Authority, if needed): ____ Signature: __________ Date: //____

Template No.: T216 Template Title: Ethics & Consent Review Form for Testing (Custodians / Owners / Community)

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T216

Template Title: Ethics & Consent Review Form for Testing (Custodians / Owners / Community)

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link F if conflict risk; H for ethics model)

Linked Templates / Policies: T214 (Risk Assessment for Testing Proposal), Scientific Verification SOP, Relic Respect & Safeguarding Rules, T215 (Multi-Lab Dossier Summary), T156 / T24 (MoU templates), T190 (Media Approval), T183 (Feedback/Complaint), T163 (Risk Register), T173 (Records Classification)

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 (why we use this form)

This form checks ethics and consent before any testing of a relic or sacred object.
It confirms consent from custodians, legal owners, and community, and records any conditions.

2) Testing proposal link (reference)

Proposal title / ID: ____________________________________________
Link to T214 risk assessment ID: _________________________________
Dossier ID (if multi-lab, T215): _________________________________
Reason for testing (tick): Conservation care [ ] Rumour response [ ] Education [ ] Research [ ] Other: ____

Short summary (2–4 lines, non-sensitive):

3) Object / relic details (non-sensitive)

Item name / museum ID: __________________________________________
Item type (tick): Relic-related [ ] Sacred object [ ] Reliquary/container [ ] Other: ____
Current status (tick): On display [ ] In storage [ ] Offsite (approved) [ ]
Sensitivity level (tick): Low [ ] Medium [ ] High [ ] Sacred-Restricted [ ]

Important note: Do not write security routines or exact storage locations here.

4) Stakeholder map (who must be respected)

Tick all groups that may be affected.

Primary custodian(s) / monastic authority [ ]
Legal owner(s) / trustee(s) [ ]
Local temple / sangha community [ ]
Lay community near the site [ ]
Donors connected to the object/site [ ]
Government heritage office (if required) [ ]
Partner labs/institutions (if any) [ ]
Other: __________________________ [ ]

Stakeholder notes (short): ___________________________________________

5) Consent checklist (who agreed, and how)

A) Custodian consent (custodians)

Custodian/monastic authority name/role: ______________________________
Consent given? Yes [ ] No [ ] Pending [ ] Not applicable [ ]
Type of consent (tick): Written [ ] Recorded meeting minutes [ ] Email [ ] Other: ____
Date of consent: ____ / ____ / ______
Proof filed (path / ref): ____________________________________________

Custodian notes / limits (short):

B) Legal owner consent (legal owners)

Legal owner/trustee name/role: ______________________________________
Consent given? Yes [ ] No [ ] Pending [ ] Not applicable [ ]
Proof of ownership checked? Yes [ ] No [ ] Pending [ ]
Type of consent (tick): Written [ ] Contract/MoU [ ] Email [ ] Other: ____
Date: ____ / ____ / ______
Proof filed (path / ref): ____________________________________________

Owner notes / limits (short):

C) Community consent (community)

Community consulted? Yes [ ] No [ ] Pending [ ] Not applicable [ ]
Method (tick): Elder/leader consultation (T188) [ ] Community meeting [ ] Temple committee [ ] Survey (T189) [ ] Other: ____
Date(s): ____ / ____ / ______
Who was consulted (roles/groups only): _______________________________

Community main view (short):
Support [ ] Mixed [ ] Concern [ ] Strong objection [ ]
Notes: _____________________________________________________________

D) Government/authority consent (if required)

Permission required by law/policy? Yes [ ] No [ ] Not sure [ ]
If Yes: authority name: _____________________________________________
Permission received? Yes [ ] No [ ] Pending [ ]
Reference number (if any): _________________________________________

6) Conditions and “strings attached” (conditions)

Any conditions placed by any party? Yes [ ] No [ ]

If Yes, list them clearly:
Condition 1: _______________________________________________________
Condition 2: _______________________________________________________
Condition 3: _______________________________________________________

Are any conditions not acceptable (control, special access, public claims)?
Yes [ ] No [ ] Not sure [ ]
If Yes, explain and propose changes: _________________________________

If conditions are risky, link to: T179 (Gift with Conditions Risk Review) or internal ethics note.

7) Ethics check (faith, heritage, peace)

Tick Yes/No and add short notes.

A) Faith and respect

The purpose is respectful and not insulting to faith. Yes [ ] No [ ]
Notes: _____________________________________________________________
Words like “prove/disprove” will be avoided in public talk. Yes [ ] No [ ]
Notes: _____________________________________________________________

B) Heritage care (non-harm)

The plan uses minimal handling and avoids harm. Yes [ ] No [ ]
Notes: _____________________________________________________________
No sampling/destructive action is planned (unless separately approved). Yes [ ] No [ ]
If No: sampling approval attached? Yes [ ] No [ ] Ref: ________________

C) Peace and harmony

Testing will not increase conflict in the community. Yes [ ] No [ ] Not sure [ ]
Notes: _____________________________________________________________
A calm communication plan exists for rumours or disagreement. Yes [ ] No [ ]
Link (T212/T213/T190 as needed): ___________________________________

8) Consent quality check (is it informed and free?)

Tick Yes/No.

Consent was informed (people understood purpose and limits). Yes [ ] No [ ]
Consent was voluntary (no pressure, no fear, no payment for consent). Yes [ ] No [ ]
Consent scope matches the plan (site/lab/time). Yes [ ] No [ ]
People understand that results may be uncertain. Yes [ ] No [ ]
People understand we may not publish details publicly. Yes [ ] No [ ]

If any “No”, explain what must be fixed: _______________________________

9) Confidentiality and data rules

Classification (T173) for this case: Internal [ ] Restricted [ ] Sacred-Restricted [ ]
Who may access the dossier (roles): ________________________________
Any photos/data shared with labs? Yes [ ] No [ ]
If Yes: data-sharing rule agreed (MoU/T24)? Yes [ ] No [ ] Ref: _________

Media rule: No media statement without T190 and approved spokespeople.

10) Decision (proceed, hold, or refuse)

Decision (tick one):
Proceed (consent complete) [ ]
Proceed with conditions/changes [ ]
Hold (needs more consent/info) [ ]
Do not proceed (ethics/consent not acceptable) [ ]

Reasons (short, factual):

Actions needed if “Hold” or “Do not proceed”:
Action 1: ______________________________ Owner: __________ Date: //____
Action 2: ______________________________ Owner: __________ Date: //____

11) Signatures and approvals

Prepared by (name/role): _______________________ Signature: __________ Date: //____

Reviewed by (Science/Verification): _____________ Signature: __________ Date: //____
Reviewed by (Conservation): ____________________ Signature: __________ Date: //____
Reviewed by (Doctrinal/Ethics): ________________ Signature: __________ Date: //____
Reviewed by (Security/Chain-of-custody): _______ Signature: __________ Date: //____

Approved by (Director/Authority/Board): _________ Signature: __________ Date: //____

12) Attachments and filing

Attachments (tick):
T214 risk assessment [ ] Custodian consent proof [ ] Owner consent proof [ ] Community notes [ ] Government permit [ ] Draft public FAQ line (T212) [ ] MoU/T24 [ ] Other: ____

File code / reference ID: ____________________
File location (cabinet/folder + digital path): __________________________
Retention period: 3 years [ ] 5 years [ ] 10 years [ ] Permanent [ ] Other: ____

Template No.: T215 Template Title: Multi-Lab Cooperation Dossier Summary Sheet

THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T215

Template Title: Multi-Lab Cooperation Dossier Summary Sheet

Related Research Case IDs / Cluster: Cluster E (Science, Testing, Misinformation), Cases 46–65 (also link C for MoUs; F if disputes; H for governance model)

Linked Templates / Policies: T214 (Risk Assessment for Testing Proposal), Scientific Verification SOP, T156 (MoU Concept Note) / T24 (Full MoU), T168 (Steering Committee Minutes), T163 (Risk Register Entry), T213 (Media Interview Prep), T190 (Media Approval), T173 (Records Classification), Chain-of-Custody SOP

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 (why we use this sheet)

This sheet gives a clear overview of a multi-lab cooperation for testing or study.
It lists the labs, roles, timeline, and shared rules. It supports truth, respect, and safety.

2) Dossier identity (basic details)

Dossier title / short name: ________________________________________
Dossier ID / code: _______________________________________________
Related object/relic case ID (internal): _____________________________
Testing purpose (tick): Conservation care [ ] Material ID [ ] Authentication concern [ ] Rumour response [ ] Research [ ] Other: ____
Link to risk assessment (T214 ID): _________________________________
Start date planned: ____ / ____ / ______
End date planned: ____ / ____ / ______

Short summary (2–4 lines, non-sensitive):

3) Labs involved (labs list)

(Use one row per lab. Add pages if needed.)

Lab 1

Lab/institution name: _____________________________________________
Country/city: _________________________________________________
Main contact (name/title): ________________________________________
Email/phone: _________________________________________________
Lab role (tick): Lead lab [ ] Support lab [ ] Independent review [ ] QA/check [ ] Other: ____
Main method area (high level): ____________________________________
Legal status/credential (short): ___________________________________
Conflict-of-interest check done? Yes [ ] No [ ] Notes: _______________

Lab 2

Lab/institution name: _____________________________________________
Contact: ________________________________________________________
Role: ___________________________________________________________
Method area: _________________________________________________
COI check done? Yes [ ] No [ ] Notes: ______________________________

Lab 3 (optional)

Lab/institution name: _____________________________________________
Contact: ________________________________________________________
Role: ___________________________________________________________

4) Roles and responsibilities (who does what)

HSWAGATA roles

Dossier owner (name/role): _______________________________________
Science/verification lead: ________________________________________
Conservation lead: ______________________________________________
Doctrinal/ethics advisor: _________________________________________
Security/chain-of-custody lead: ___________________________________
Communications lead (if needed): _________________________________

Lab roles (summary)

Lead lab duties (tick): Plan test steps [ ] Set QA rules [ ] Collect results [ ] Draft joint report [ ] Other: ____
Support lab duties: _______________________________________________
Independent reviewer duties: ______________________________________

Decision authority for key changes (tick):
Director [ ] Board [ ] Abbot/Sangha authority [ ] Joint Steering Committee [ ] Other: ____

5) Timeline (key dates and milestones)

Milestone 1: ______________________________ Date: //____ Owner: __________
Milestone 2: ______________________________ Date: //____ Owner: __________
Milestone 3: ______________________________ Date: //____ Owner: __________
Milestone 4: ______________________________ Date: //____ Owner: __________
Milestone 5 (final report): ________________ Date: //____ Owner: __________

Meetings planned (tick): Weekly [ ] Monthly [ ] At milestones [ ] Other: ____
Minutes template to use: T168 [ ] / T153 [ ]

6) Shared rules (must agree before work starts)

Tick and add notes. These rules protect faith, heritage, and peace.

A) Respect and boundaries

No disrespectful handling or language. Yes [ ]
No Sacred-Restricted security details shared. Yes [ ]
No public “prove/disprove faith” framing. Yes [ ]

B) Testing limits

Non-destructive first (if possible). Yes [ ]
No sampling/destructive testing unless top approval is recorded. Yes [ ]
Approval reference (if ever): ______________________________________

C) Chain-of-custody and access

One clear chain-of-custody record used for all moves. Yes [ ]
Only named authorised persons may handle/transport. Yes [ ]
Transport rules agreed (secure packing, logs). Yes [ ]

D) Data and reporting rules

Shared file system agreed (location/path): __________________________
File naming rule agreed: __________________________________________
Raw data access limited to approved team. Yes [ ]
All changes tracked (version control). Yes [ ]

E) Confidentiality and classification

Classification (T173) for this dossier: Internal [ ] Restricted [ ] Sacred-Restricted [ ]
Labs agree not to share without written approval. Yes [ ]

F) Publication and media rules

No media interviews without comms approval (T213). Yes [ ]
No posts without content approval (T190). Yes [ ]
Publication plan agreed (tick): No publication [ ] Joint paper [ ] Public summary only [ ] Other: ____

G) Disagreement rule

If labs disagree, we record differences calmly and do not hide them. Yes [ ]
Final report will show limits and uncertainty clearly. Yes [ ]

7) Coordination and governance (how we manage the cooperation)

Steering group name: _____________________________________________
Members (roles only): ____________________________________________
Meeting schedule: _______________________________________________
Decision method (tick): Consensus [ ] Vote [ ] Lead lab decides [ ] HSWAGATA decides [ ] Other: ____
Escalation path (if serious issue): _________________________________

8) Risks and controls (summary)

(Use T214 for full assessment; summarise here.)

Risk 1: ______________________________ Level: Low [ ] Med [ ] High [ ]
Control: ___________________________________________________________
Link to T163 risk entry? Yes [ ] No [ ] Risk ID: _______________________

Risk 2: ______________________________ Level: Low [ ] Med [ ] High [ ]
Control: ___________________________________________________________

9) Outputs and deliverables (what we expect)

Tick and describe.

Joint test plan (high level) [ ] Due: //____
Condition/conservation note [ ] Due: //____
Lab reports (per lab) [ ] Due: //____
Joint summary report (public-safe version) [ ] Due: //____
Data package (restricted) [ ] Due: //____
FAQ updates needed (T212) [ ] Yes [ ] No [ ]

Where final outputs will be stored (path): __________________________

10) Approvals (sign-off)

Prepared by (name/role): _______________________ Signature: __________ Date: //____

Approved by (Director/Authority/Board): _________ Signature: __________ Date: //____

11) Filing

သာဓိကာရ ပဋိဝေဒနာ

သာဓိကာရ ပဋိဝေဒနာ © ၂၀၂၁ ဘိက္ခု ဓမ္မသမိ (ဣန္ဒသောမ) သိရိဒန္တမဟာပါလက-ကာယာလယ. သဗ္ဗေ အဓိကာရာ ရက္ခိတာ. ဣဒံ သာသနံ တဿ အတ္ထဉ္စ အာယသ္မတော ဓမ္မသာမိဿ ဉာဏသမ္ပတ္တိ ဟောန္တိ၊ ယေန ကေနစိ ပုဗ္ဗာနုညာတံ လိခိတ-အနုမတိံ ဝိနာ န ပုန-ပ္ပကာသေတဗ္ဗံ န ဝိတ္ထာရေတဗ္ဗံ ဝါ.

Content Source Declaration

All content published on this website, www.siridantamahapalaka.com, including but not limited to articles, Dharma talks, research findings, and educational resources, is intended solely for the purpose of Dhamma dissemination, study, and public benefit. Some images and visual content used throughout this website are sourced from public domains, Google searches, and social media platforms. These are used in good faith for non-commercial and educational purposes. If any copyright holder has concerns regarding the usage of their content, please feel free to contact us for proper acknowledgment or removal. A portion of the Dharma talks, especially those categorized under "Dharma Talk" and "Dependent Origination – Questions and Answers", have been translated from the teachings of respected Venerable Sayadaws. Proper reverence is maintained in delivering these teachings with accuracy and sincerity for the benefit of Dhamma practitioners. We deeply respect the intellectual and spiritual contributions of all teachers and content creators. Our aim is to preserve, promote, and respectfully share the teachings of the Buddha.

🔸 Disclaimer on Translations and Content Accuracy

While great care has been taken in translating Dhamma talks and related materials, any errors, inaccuracies, or interpretative issues that may be found within this blog are solely the responsibility of the author. This website and its content are not affiliated with or officially represent any individual, group, institution, or monastery/temple or Musuem. All translations, interpretations, and editorial decisions have been made independently by the author with sincere intention for Dhamma sharing. We humbly request the understanding and forgiveness of readers and the venerable teachers, should any shortcomings or misinterpretations arise.

ဝန္ဒာမိ

Total Pageviews

ဝန္ဒာမိ

ဝန္ဒာမိ စေတိယံ

Saturday, December 13, 2025

1) Purpose (why we use this form)

2) Request summary (basic details)

3) External expert details (expert name)

4) Ethics and conflict-of-interest check (quick)

5) Review question (question)

6) Documents sent (documents sent)

7) Deadline and reply method (deadline)

8) What we asked the expert to include (simple checklist)

9) Reply received (reply)

10) HSWAGATA follow-up actions

11) Sign-off and filing

1) Purpose (why we use this sheet)

2) Project identification (basic info)

3) Project aim and expected value

4) Summary of what was done (high level only)

5) What worked well (what worked)

6) What did not work well (what did not)

7) Impact review (faith / heritage / peace)

A) Faith impact (impact on trust and respect)

B) Heritage impact (physical care and safety)

C) Peace and harmony impact (community relations)

D) Misinformation impact (rumours and public understanding)

8) Stakeholder feedback (what people said)

9) Ethics, consent, and respect check (quick)

10) Data and records check

11) Lessons learned (lessons)

12) Improvements and action plan (next steps)

13) Communication follow-up (if public-facing)

14) Sign-off and approvals

15) Filing

1) Purpose (why we use this form)

2) Documents being compared (what we are checking)

3) Cross-check rules (must follow)

4) Cross-check entries (main section)

Entry No.: ______

5) Review and approvals (before public release)

6) Notes and lessons (optional)

7) Filing

1) Purpose (why we use this log)

2) Training programme details (for the log period)

3) Quick rules (must follow)

4) Training session register (summary table)

Register entries

5) Training session record (full details)

A) Session identification

B) Topic and purpose

C) Trainer details (trainer)

D) Content outline (what was covered)

E) Participants (participants)

F) Learning goals (simple)

6) Evaluation (evaluation)

A) Evaluation method (tick)

B) Results (write numbers if possible)

C) Trainer and participant feedback

7) Corrective actions and follow-up

8) Attachments (optional)

9) Sign-off and filing

1) Purpose (why we use this plan)

2) Plan identity (basic details)

3) Main objectives (5–7)

4) Target groups (who we serve)

5) Key partners (partners)

6) Programme activities (annual activity list)

Activity 1

Activity 2

Activity 3

7) Content plan (what we will teach)

8) Communications and media plan (public-facing)

9) Budget plan (annual)

A) Budget lines (fill amounts)

B) Funding sources

10) Risks and safeguards (required)

11) Monitoring and evaluation (how we know it worked)

A) Indicators (tick and fill)

B) Feedback tools