# Team Wiki & SOP Template

## 1️⃣ Overview & Quick Start  
A single source of truth for all standard operating procedures (SOPs), team knowledge, and cross‑functional documentation. This template is built around three core pillars:

1. **SOP Library** – Structured, version‑controlled procedures.  
2. **Team Directory** – Who owns what, with contact details.  
3. **Knowledge Base** – FAQs, guides, and reference material.

> 💡 Tip: Pin the **SOP Dashboard** view to the top of your Notion sidebar for instant access by the whole team.

---

## 2️⃣ SOP Library (Database)  
| SOP ID | Title | Owner | Department | Status | Last Updated | Link |
|--------|---------------------------|----------------|------------|----------|--------------|------|
| SOP‑001 | New Hire Onboarding | Alice Chen | People Ops | ✅ Published | 2024‑06‑15 | [[SOP‑001]] |
| SOP‑002 | Incident Response (Critical) | Marco Ruiz | IT Security | 🛠️ Draft | 2024‑05‑28 | [[SOP‑002]] |
| SOP‑003 | Quarterly Financial Close | Priya Patel | Finance | ✅ Published | 2024‑04‑30 | [[SOP‑003]] |
| SOP‑004 | Content Publishing Workflow | Jamal Lee | Marketing | ✅ Published | 2024‑06‑01 | [[SOP‑004]] |
| SOP‑005 | Customer Support Escalation | Nina Gomez | Support | 🛠️ Review | 2024‑06‑20 | [[SOP‑005]] |

> 💡 Tip: Use the **Status** property to trigger automated reminders (e.g., a weekly reminder for SOPs in “Draft” or “Review”).  

### SOP Dashboard Views  
- **All SOPs** – Table view with filters for every department.  
- **Pending Review** – Board view grouped by **Status** (Draft → Review → Published).  
- **Recently Updated** – Calendar view showing the **Last Updated** date.

---

## 3️⃣ Team Directory (Database)  
| Name | Role | Department | Primary SOPs | Email | Slack |
|------|------|------------|--------------|-------|-------|
| Alice Chen | HR Manager | People Ops | SOP‑001 | alice@company.com | @alice |
| Marco Ruiz | Security Lead | IT Security | SOP‑002 | marco@company.com | @marco |
| Priya Patel | Finance Analyst | Finance | SOP‑003 | priya@company.com | @priya |
| Jamal Lee | Content Strategist | Marketing | SOP‑004 | jamal@company.com | @jamal |
| Nina Gomez | Support Supervisor | Support | SOP‑005 | nina@company.com | @nina |

> 💡 Tip: Link each team member’s **Primary SOPs** to the SOP Library so owners can quickly jump to the procedures they maintain.

---

## 4️⃣ Knowledge Base  
A flexible page hierarchy for quick reference material. Suggested top‑level pages:

- **Company Policies** – HR, compliance, security.  
- **Tool Guides** – Slack, CRM, analytics dashboards.  
- **FAQs** – Common questions by department.  
- **Glossary** – Acronyms and terminology.

Each page should include a **Table of Contents** block and a **Last Reviewed** date property to keep content fresh.

> 💡 Tip: Enable the **“Sync to Google Drive”** integration for large PDFs (e.g., policy manuals) and embed them directly in the Knowledge Base pages.

---

## 5️⃣ SOP Creation & Review Workflow  
1. **Create SOP** – Duplicate the **SOP Template** page (provided in the SOP Library).  
2. **Draft** – Fill in the procedure, attach files, and set **Status** to “Draft”.  
3. **Peer Review** – Assign reviewers via the **Owner** property; Notion will send a reminder.  
4. **Publish** – Change **Status** to “Published”; the **Last Updated** field auto‑updates.  
5. **Version Log** – Each publish creates a new entry in the **SOP History** linked database (auto‑generated by a roll‑up of the **Version** number).

> 💡 Tip: Use the **“@mention”** feature to tag the responsible owner directly in the SOP body; this creates a backlink in the owner’s profile page.

---

## 6️⃣ Permissions & Governance  
- **View‑Only** for all staff on the Knowledge Base (prevents accidental edits).  
- **Edit** rights for SOP owners and their department leads.  
- **Admin** rights for the **Wiki Admin** role (typically People Ops).  

Set up a **Notion Group** called “SOP Editors” and assign the appropriate page permissions in the **Share** menu.

> 💡 Tip: Enable **“Allow duplicate”** for the SOP Library database so other teams can fork SOPs while preserving the original source.

---

## How to import into Notion  
1. **Create a new page** in your Notion workspace where you want the template to live.  
2. Click the three‑dot menu → **“Import”** → select **“Markdown & CSV”**.  
3. Upload this `.md` file. Notion will create the headings, text, and tables automatically.  
4. For each markdown table (SOP Library, Team Directory, etc.), click **“Turn into database”** → choose **Table**.  
5. Adjust property types:  
   - **Date** for “Last Updated”.  
   - **Person** for “Owner”.  
   - **Select** for “Status”.  
   - **URL** for “Link”.  
6. Add the **views** (Table, Board, Calendar) as described in the sections above.  
7. Set **page permissions** according to the “Permissions & Governance” section.  
8. (Optional) Duplicate the **SOP Template** page from the SOP Library and start populating your first SOP.

Your Team Wiki & SOP system is now live—ready for the whole organization to create, maintain, and reference standard procedures with confidence.