docs/Chemical-Standard-Operating-Protocols.md changed. Please check whether the formal
SOP set in lab_safety_docs/standard-operating-procedures/ needs a corresponding update.
These two documents are not mirrors — read this before editing:
- The quick-reference doc is informal, one entry per chemical.
- The formal SOPs (SOP-01..15,
.docx, UW EH&S template) are grouped by hazard class and
are signed, approved documents. Use
lab_safety_docs/standard-operating-procedures/SOP-Coverage-Crosswalk.csv to find which
SOP number covers the chemical that changed.
- Do not edit the
.docx/.pdf files directly — a scripted edit will likely break
the approval signatures and EH&S formatting. Instead:
- Identify the affected SOP-NN via the crosswalk.
- Add or update a short redline note at
lab_safety_docs/standard-operating-procedures/pending-redlines/SOP-NN.md
describing exactly what text should change and why, citing the relevant section
number (Sections 1-12 per the UW blank SOP template).
- Leave the
.docx/.pdf themselves untouched — a human applies the redline in Word
and routes it through the normal approval / re-training process described in the SOP
README's "Review cadence" section.
- If the quick-reference change doesn't affect any chemical the SOP set covers (e.g. a
wording/typo fix, or a chemical outside the FTR 209/213 inventory), close this issue with
a comment explaining why — no redline needed.
- Title any resulting PR starting with
[sop-sync] so the merge doesn't immediately
re-trigger a follow-up sync issue on the other side.
diff --git a/docs/Chemical-Standard-Operating-Protocols.md b/docs/Chemical-Standard-Operating-Protocols.md
index cdfa269..587ac23 100644
--- a/docs/Chemical-Standard-Operating-Protocols.md
+++ b/docs/Chemical-Standard-Operating-Protocols.md
@@ -10,6 +10,8 @@
Full, per-hazard-class UW EH&S-format SOPs (SOP-01 through SOP-15, Rev. 0, September 1, 2026) covering every chemical in the FTR 209/213 MyChem inventory. Each SOP documents engineering controls, PPE, storage, spill response, and waste disposal in more detail than the summaries below; consult it for chemicals flagged as Particularly Hazardous Substances (PHS).
+This quick-reference doc and that SOP set are not mirrors of each other — they're kept loosely in sync by [`.github/workflows/sop-sync.yml`](../.github/workflows/sop-sync.yml), which opens a GitHub issue (assigned to Copilot) whenever either side changes, asking for the other to be reviewed.
+
---
### [RNAzol RT](#rnazol_rt)
docs/Chemical-Standard-Operating-Protocols.mdchanged. Please check whether the formalSOP set in
lab_safety_docs/standard-operating-procedures/needs a corresponding update.These two documents are not mirrors — read this before editing:
.docx, UW EH&S template) are grouped by hazard class andare signed, approved documents. Use
lab_safety_docs/standard-operating-procedures/SOP-Coverage-Crosswalk.csvto find whichSOP number covers the chemical that changed.
.docx/.pdffiles directly — a scripted edit will likely breakthe approval signatures and EH&S formatting. Instead:
lab_safety_docs/standard-operating-procedures/pending-redlines/SOP-NN.mddescribing exactly what text should change and why, citing the relevant section
number (Sections 1-12 per the UW blank SOP template).
.docx/.pdfthemselves untouched — a human applies the redline in Wordand routes it through the normal approval / re-training process described in the SOP
README's "Review cadence" section.
wording/typo fix, or a chemical outside the FTR 209/213 inventory), close this issue with
a comment explaining why — no redline needed.
[sop-sync]so the merge doesn't immediatelyre-trigger a follow-up sync issue on the other side.