Operations work is text-heavy: SOPs, status reports, vendor evaluations, risk registers, meeting agendas. AI is uniquely good at this category — but only with the right prompt structure. Below: 8 production prompts for ops teams, copy-paste ready.
I need to document a process the team has been doing informally. The process is: [DESCRIBE]. Write a complete SOP with: - Title (action-oriented, "How to..." or "Process for...") - Purpose (1-2 sentences: when does someone use this) - Owner and stakeholders - Prerequisites (what needs to be true before starting) - Step-by-step procedure (numbered, specific, no ambiguity) - Exception handling (when to deviate, who to escalate to) - Success criteria (how do you know the process was completed correctly) - Related docs / links Match the structure of the example SOPs in the knowledge base.
Here is a process we currently follow: [PASTE] Here are recent issues with how it's working: [PASTE] Audit: - Where does this process create friction? - Where is human judgment required vs. where could it be automated? - What's the typical cycle time vs. theoretical minimum? - Where do handoffs fail? - 3 specific changes that would most improve it, ranked by ROI - Whether this process should be eliminated entirely (worth asking)
We're evaluating these vendors for [USE CASE]: [LIST] Build an evaluation matrix: - Define 6-8 evaluation criteria specific to our use case (not generic "ease of use") - Weight each criterion 1-10 based on importance to us - Score each vendor on each criterion with reasoning - Calculate weighted total - Identify the criterion where the choice actually depends (where vendors differ most) - Recommend the top choice with 2 specific reasons Format: clean table.
Project: [NAME] This week's progress: [PASTE notes] Blockers: [PASTE] Next week's priorities: [PASTE] Risks: [PASTE] Write a clean stakeholder update: - 1-sentence headline (status: on track / at risk / blocked) - This week's wins (3-5 bullets, specific) - This week's blockers (named, with action and owner) - Next week's plan (3-5 bullets) - Risks worth flagging (with proposed mitigations) Length: under 350 words. Voice: direct, no marketing language, no "we're excited to share."
Last 30 days of operational metrics: [PASTE] Key incidents: [PASTE] Queue / backlog state: [PASTE] Team capacity: [PASTE] Draft the ops review brief: - What's working well (specifics, not platitudes) - What's degrading (with the data behind it) - The 3 things requiring decision this month - Resource asks (be specific — what, why, ROI) - Process changes I'm recommending Goal: leadership reads this in 5 minutes and can make decisions. No padding.
Role: [NAME] Reports to: [WHO] Reason for opening: [BACKFILL / GROWTH / NEW FUNCTION] Key responsibilities (rough): [PASTE] Draft the internal job posting: - Role and team - Why this role exists now (specific business reason) - What success looks like in first 90 days (concrete projects) - Required vs. nice-to-have qualifications (be honest) - Comp range - How to apply / next steps Voice: candid, not corporate. Internal team should feel they understand both the opportunity and the realistic challenges.
Risk I've identified: [DESCRIBE] What triggered me to notice: [CONTEXT] Write the risk register entry: - Risk title (clear, specific) - Description (1-2 sentences) - Likelihood (1-5 with reasoning) - Impact if realized (1-5 with reasoning) - Combined score and tier (Critical / High / Medium / Low) - Owner - Current mitigations in place - Proposed additional mitigations - Review date (when do we re-evaluate) Be specific. "Cyber risk" is not a useful entry. "Risk that our HubSpot integration breaks if [vendor] sunsets their v2 API" is useful.
Meeting: [Weekly leadership sync / Monthly all-hands / Quarterly business review] Last meeting's notes: [PASTE] Things I want to cover this meeting: [LIST] Time available: [60 / 45 / 30 mins] Build the agenda: - Open (review of action items from last meeting) - 3-4 substantive discussion topics, each with: topic, decision needed, time allocated, who leads - Quick updates (round-robin, time-boxed) - Action items capture Allocate time realistically. Most meetings fail because they pack 90 minutes of content into 60. Tell me what to cut.
These prompts work 5x better inside a properly configured Claude Project loaded with your context. See our full function guide for the setup walkthrough, or have Treetop build the Project for your team.