Standard Operating Procedure (SOP) Draft

Draft a standard operating procedure (SOP) for the following process: Process name: [name of process, e.g., "Customer Onboarding"] Current state: [brief description of how it works today] Team involved: [list of roles or departments] Frequency: [how often this process runs] Structure the SOP with: 1. Purpose & scope (1 paragraph) 2. Roles & responsibilities (table or bullet list) 3. Step-by-step procedure (numbered steps, each 1–3 sentences) 4. Tools & systems required (list) 5. Common issues & troubleshooting (optional but valuable) 6. Appendix with templates or examples (if applicable) Use clear, action-oriented language. Avoid jargon; define any acronyms.

Process Audit & Improvement Recommendations

Conduct a process audit and generate improvement recommendations for the following operational process. Process name: [e.g., "Monthly Vendor Invoice Reconciliation"] Current process description: [describe each step in sequence — or paste existing SOP/notes] Team involved: [roles/departments] Key problems we're experiencing: [e.g., frequent errors, long cycle time, handoff failures, compliance gaps] Current cycle time: [how long this process takes end-to-end] Volume: [how often this runs / how many items processed] Analyze the process and provide: 1. A process map summary (describe the current flow in 5–8 steps) 2. Top 3–5 inefficiencies or failure points identified 3. Recommended improvements for each (quick win vs. longer-term fix) 4. Estimated impact of each improvement (time saved, error reduction, cost) 5. Implementation priority ranking (High/Medium/Low) 6. Success metrics to track improvement Format as an operations improvement brief for a COO or VP of Operations.

Process Flow Documentation

Document the end-to-end process flow for [process name] at [company name]. Process description (as described verbally or from rough notes): [Paste or describe the process here — it does not need to be formatted] Convert this into a structured process flow document with: 1. Process overview: purpose, scope, frequency, and key stakeholders (1 paragraph) 2. Input triggers: what starts this process 3. Step-by-step flow: each step with responsible role, action taken, and system used 4. Decision points: where choices or approvals are required (describe each decision and the two paths) 5. Handoffs: where work moves from one team or person to another (and how) 6. Output: what is produced at the end of the process 7. Exception handling: what happens when something goes wrong Format suitable for inclusion in a process library or tool like Lucidchart, Notion, or Confluence (text-based flow that can be converted to a diagram).

Bottleneck Analysis

Conduct a bottleneck analysis for the following process at [company name] and identify the primary constraints slowing it down. Process name: [e.g., "Sales Order Fulfillment," "Employee Onboarding," "Monthly Financial Close"] Current end-to-end cycle time: [e.g., "14 days from order to delivery"] Target cycle time: [e.g., "7 days"] Process steps (describe in sequence): 1. [Step 1 — include: who performs it, how long it takes, volume per period] 2. [Step 2 — same format] 3. [Continue for all steps] Known pain points: [list any steps already suspected of being slow, error-prone, or resource-constrained] Handoffs that frequently cause delays: [describe] Analyze and provide: 1. Bottleneck identification: rank each step by its contribution to total cycle time and flag the top 2–3 constraints 2. Root cause for each bottleneck: is it a capacity issue (not enough people/resources), a process issue (steps are inefficient), a dependency issue (waiting on others), or a technology issue? 3. Impact quantification: for the primary bottleneck, estimate how much cycle time would be saved if it were resolved 4. Improvement options for each bottleneck: at least 2 options per bottleneck (quick fix vs. structural change) 5. Recommended sequence: which bottleneck to address first and why Format as an improvement brief for a COO or operations lead.

Project Charter

Draft a project charter for the following initiative at [company name]. Project name: [name] Project sponsor: [executive or leader authorizing this project] Project manager: [name/role] Business problem or opportunity: [1–2 sentences on why this project exists] Proposed solution / scope: [what the project will and will not include] Key deliverables: [list 3–5 concrete outputs] Success criteria: [how will we know the project succeeded? — measurable outcomes] Timeline: [start date, key milestones, target completion] Budget: [approved or estimated budget] Key stakeholders: [list with their role in the project] Known risks: [list 2–3 with likelihood and mitigation] Dependencies: [other projects, teams, or decisions this depends on] Format as a formal project charter suitable for executive sign-off. Include a one-paragraph executive summary at the top.

Project Status Report

Write a project status report for [project name] at [company name] for the period ending [date]. Project overview (1–2 sentences): [brief description of what this project is doing] Overall status: [Green / Yellow / Red — with a one-line reason] This period summary: - Completed milestones: [list] - In-progress work: [list with % complete] - Upcoming milestones (next 2 weeks): [list with target dates] Issues and risks: - Active issues: [list with owner and resolution plan] - New risks identified: [list with likelihood and mitigation] Budget status: [on budget / over budget / under budget — with brief explanation] Schedule status: [on track / ahead / behind — with brief explanation] Decisions needed from leadership: [list any blockers or decisions the project team needs] Next report date: [date] Format as a concise, scannable 1-page status report suitable for a PMO dashboard or leadership briefing.

Project Retrospective Facilitation Guide

Create a project retrospective facilitation guide for [project name] at [company name]. Project context: [brief description — type of project, duration, team size, outcome] Retrospective attendees: [list of roles] Duration of retro session: [e.g., 60 minutes, 90 minutes] Generate: 1. Facilitator opening script (2–3 minutes — set the tone, establish psychological safety) 2. Structured agenda with timing for each section 3. Discussion questions for each retro section: - What went well? (5–6 prompts) - What could have gone better? (5–6 prompts) - What did we learn? (3–4 prompts) - What will we do differently next time? (3–4 prompts) 4. Instructions for a team exercise (e.g., dot voting on themes, silent writing before discussion) 5. Template for capturing action items from the retro 6. Facilitator tips for handling tension or dominant voices Format as a guide the facilitator can use directly.

Vendor Performance Scorecard

Create a vendor performance scorecard for [vendor name], our [category] vendor, covering [time period]. Performance dimensions to evaluate: - Delivery / timeliness: [rating 1–5] — [notes: on-time delivery rate, missed deadlines] - Quality of work / output: [rating 1–5] — [notes: defect rate, rework required] - Responsiveness and communication: [rating 1–5] — [notes: response time, proactiveness] - Contract and SLA compliance: [rating 1–5] — [notes: adherence to terms] - Value for cost: [rating 1–5] — [notes: cost vs. quality vs. market] - Relationship and partnership: [rating 1–5] — [notes: collaborative, easy to work with] Generate: 1. Weighted overall score (suggest weightings if not provided) 2. 2–3 sentence summary per dimension 3. Top 2 strengths with supporting evidence 4. Top 2 improvement areas with specific, actionable asks for the vendor 5. Recommendation at contract renewal: renew as-is / renegotiate / rebid / terminate 6. Suggested agenda for vendor business review meeting Format for use in a quarterly vendor business review.

RFP (Request for Proposal) Template

Draft a Request for Proposal (RFP) for [company name] seeking [product/service category]. Project background: [brief description of what we need and why] Scope of work required: [describe what the vendor will deliver] Contract type anticipated: [e.g., annual SaaS subscription, professional services, managed service] Contract value range: [estimated range] Target go-live or implementation date: [date] RFP sections to include: 1. Company overview and project background 2. Scope of work and deliverables (detailed) 3. Technical and functional requirements (list of must-have and nice-to-have) 4. Vendor qualifications required (experience, certifications, references) 5. Proposal format instructions (what to include, page limits) 6. Pricing requirements (structure, format, what to include) 7. Evaluation criteria and weighting (how we will score responses) 8. Timeline: RFP release, Q&A deadline, proposal due, decision date 9. Terms and conditions for RFP submission Format as a formal RFP document suitable for distribution to potential vendors.

Vendor Contract Review Checklist

Create a vendor contract review checklist for [company name] to use when evaluating [contract type, e.g., SaaS subscription, professional services, facility services] agreements. Contract under review: - Vendor name: [name] - Contract value: [annual or total value] - Contract term: [length] - Renewal type: [auto-renew / manual renewal / evergreen] Review each of the following areas and document findings: 1. Scope of services: Is the scope clearly defined? Are there ambiguities that could lead to disputes? 2. Pricing and payment terms: Are rates locked? What are the escalation clauses? When is payment due? 3. Auto-renewal and termination: What is the notice period to cancel? Can we terminate for convenience? 4. SLAs and remedies: Are service levels defined? What are the penalties or credits if the vendor misses them? 5. Data and confidentiality: Who owns the data? Is there a data processing agreement (DPA)? What are breach notification requirements? 6. Liability and indemnification: Are liability caps reasonable? Is indemnification mutual? 7. Change management: How are scope changes or price changes handled mid-term? 8. Insurance requirements: Does the vendor carry adequate insurance? 9. Dispute resolution: What is the process for resolving disputes? Which jurisdiction governs? For each area: note the contract provision (or flag if missing), assess risk (High/Medium/Low), and state recommended action (accept / negotiate / escalate to legal).

Operational Runbook

Create an operational runbook for [system, service, or process name] at [company name]. Purpose of this runbook: [what this document helps the operator do — e.g., "respond to alerts," "execute the monthly close process," "onboard a new client"] Audience: [who will use this — e.g., "on-call engineers," "operations coordinators," "new team members"] Sections to include: 1. Overview: what this system/process does and why it matters (1 paragraph) 2. Prerequisites: tools, access, and permissions required before starting 3. Common tasks: step-by-step instructions for the 3–5 most frequent tasks operators perform 4. Scheduled tasks: list of recurring tasks with frequency and instructions 5. Alert response: for each common alert or exception, list: what triggers it, what it means, and steps to resolve 6. Escalation path: who to contact when the runbook doesn't cover a scenario 7. Related documentation: links to SOPs, architecture docs, vendor contacts Format for use in Confluence, Notion, or a shared drive. Use numbered steps, not prose paragraphs.

Knowledge Base Article

Write a knowledge base article for [company name]'s internal wiki covering the following topic: Topic: [e.g., "How to submit a vendor payment request," "How to access the VPN," "How to escalate a customer complaint"] Audience: [who will read this — e.g., all employees, new hires, department-specific] Assumed prior knowledge: [what readers already know — e.g., "familiar with our ticketing system," "no technical background assumed"] Article structure: 1. Title: clear, action-oriented (starts with "How to..." or "Understanding...") 2. Summary: 1–2 sentences explaining what this article covers and who should read it 3. Prerequisites (if any): what the reader needs before starting 4. Step-by-step instructions: numbered, each step 1–2 sentences with screenshots described [or noted as needed] 5. Tips or common mistakes: 2–3 practical notes to avoid common errors 6. Related articles: 2–3 links to related topics (suggest titles) 7. Last updated: [date] | Owner: [role] Keep language plain and direct. Write for someone doing this for the first time.

Standard Operating Procedure Review

Review the following Standard Operating Procedure (SOP) and provide a structured assessment with improvement recommendations. SOP to review: [Paste the existing SOP here] SOP metadata: - SOP name: [name] - Process owner: [role] - Last reviewed: [date] - Current version: [version number] - Audience: [who follows this SOP] Evaluate the SOP across these dimensions: 1. Clarity and readability: Are steps written in plain, action-oriented language? Could a new employee follow this without additional guidance? 2. Completeness: Are there missing steps, unstated assumptions, or gaps in the process flow? 3. Accuracy: Based on the process description, are there any steps that appear outdated, incorrect, or inconsistent with how the process likely works today? 4. Roles and accountability: Is it clear who is responsible for each step? Are handoffs explicitly defined? 5. Exception handling: Does the SOP address what to do when something goes wrong or a step cannot be completed as written? 6. Tools and systems: Are all referenced tools or systems up to date? Are links or system names current? 7. Compliance and control requirements: Are any regulatory, audit, or approval steps present where required? Provide: - An overall quality rating (Strong / Adequate / Needs Significant Revision) - Specific edits recommended (cite the section or step number) - Prioritized list of changes (must-fix vs. nice-to-have) - Suggested updated version for any steps that need major rewriting

Meeting Summary → Action Items

Summarize the following meeting notes and extract key action items: [Paste meeting notes or transcript here] For each action item, provide: - Clear action description - Owner (person responsible) - Due date (if mentioned or infer a reasonable timeline) - Priority level (High/Medium/Low) Format as a structured list. At the top, include 1–2 sentences summarizing the overall meeting outcome or decision.

All-Hands Meeting Agenda

Create an all-hands meeting agenda for [company name] for [month/quarter]. Meeting details: - Audience: all employees ([number] people) - Duration: [e.g., 60 minutes] - Format: [in-person / virtual / hybrid] - Host: [CEO / COO / other] Topics to cover this meeting: - Company update / performance: [key message or data point] - Highlight or win to celebrate: [describe] - Product or operations update: [what's new] - Q&A session - Any other agenda items: [list] Generate: 1. A timed agenda (15-min blocks with buffer for questions) 2. Suggested talking points (3–5 bullets) for each agenda item 3. An opening script (60 seconds) to set the tone 4. A closing script (30 seconds) with call to action or next steps 5. 5 suggested questions for the Q&A seed box (in case no one speaks up) Keep the meeting focused and energizing — not a status update dump.

Stakeholder Update Email

Write a stakeholder update email for [project or initiative name] at [company name]. Update frequency: [weekly / bi-weekly / monthly] Audience: [executive team / cross-functional stakeholders / board / external partners] Reporting period: [date range] Content to include: - Progress this period: [describe what was accomplished — be specific] - Current status: [on track / at risk / blocked — with brief explanation] - Key decisions made or needed: [list] - Upcoming milestones: [next 1–2 with dates] - Issues or risks: [any new problems and how they're being handled] - Budget / resource update (if applicable): [on budget / over budget / resource gap] - Action items for stakeholders: [what you need from them, if anything] Format: brief, scannable email (under 250 words). Use short paragraphs or bullets. No narrative fluff — executives should be able to read this in 90 seconds.

Executive Briefing Summary

Write an executive briefing summary for [topic or initiative] to be delivered to [executive audience, e.g., CEO, executive committee, board]. Briefing context: - Topic: [e.g., "Q2 Operations Review," "New Vendor Transition Update," "Process Automation Initiative"] - Audience: [list who will read or hear this] - Purpose: [e.g., "inform and align on status," "seek a decision," "escalate a risk"] - Time available: [e.g., "5-minute read," "10-minute verbal briefing"] Content to incorporate: - Situation overview: [what is happening and why it matters — 2–3 sentences] - Key facts or data points: [list 3–5 numbers, milestones, or findings] - Options or recommendations (if a decision is needed): [describe 2–3 options with pros and cons] - Preferred recommendation (if applicable): [state clearly with rationale] - Risks or concerns: [1–2 most important items executives need to know] - What you need from the executive(s): [e.g., a decision, budget approval, a sponsor introduction, awareness only] - Next steps and timeline: [what happens after this briefing] Format: write the briefing in the BLUF (Bottom Line Up Front) structure — lead with the conclusion, support with facts, close with the ask. Total length: 200–300 words. Executives should finish reading and know exactly what is being asked of them.

Issue Escalation Triage

Triage and categorize the following operational issue(s): Issue(s) to triage: [Describe the issue: what happened, who reported it, when, expected vs. actual outcome] For each issue, provide: - Severity (Critical/High/Medium/Low) - Category (e.g., system outage, process failure, resource constraint, compliance gap, quality issue) - Root cause (best guess based on info provided) - Recommended escalation path (who should be notified, in what order) - Immediate mitigation steps (what to do now while investigating) - Next investigation steps (how to dig deeper) Be concise but thorough. Assume the reader is busy and needs actionable guidance.

Operational Risk Register

Create an operational risk register for [company name / department / project] covering [time period or ongoing]. Context: [brief description of the operation, department, or project being assessed] For each of the following risk categories, identify 2–3 specific risks, assess them, and recommend controls: Risk categories to cover: - Operational (process failures, staffing, supply chain) - Technology (system outages, data loss, cybersecurity) - Compliance and regulatory (legal, audit, reporting) - Financial (budget overruns, fraud, cost overruns) - Reputational (customer-facing failures, public incidents) For each risk, provide: - Risk description (specific and concrete) - Likelihood (High/Medium/Low) - Impact if it occurs (High/Medium/Low) - Risk rating (likelihood × impact: Critical/High/Medium/Low) - Current controls in place - Recommended additional controls or mitigation actions - Risk owner (role) - Review frequency Format as a table suitable for an operations or risk committee review.

Business Continuity Plan Outline

Create a business continuity plan (BCP) outline for [company name / department]. Organization type: [e.g., professional services firm, manufacturer, SaaS company] Critical business functions to protect: [list 3–5 — e.g., customer order processing, payroll, IT systems, client communications] Primary disruption scenarios to plan for: [e.g., natural disaster, cyberattack, key personnel loss, facility loss, supply chain disruption] BCP outline should include: 1. Purpose, scope, and objectives (1 paragraph) 2. Business impact analysis: for each critical function, what is the maximum tolerable downtime and recovery time objective (RTO)? 3. Recovery strategies: for each scenario, what is the response plan? 4. Crisis communication plan: who communicates to whom, through what channels, and what the initial messaging says 5. Key personnel and alternates: who is responsible for each function if primary person is unavailable 6. Technology recovery: data backup procedures, remote work capability, vendor contacts 7. Plan testing schedule: how often the plan will be tested and in what format 8. Plan maintenance: who owns the plan and how often it is updated Format as an outline ready for a full BCP document to be built from.