Operations
SOPs, meeting follow-through, vendor and project communication.
Process owners running the day-to-day operation.
Project ManagersProject-specific coordination and delivery.
Admin / Executive AssistantsScheduling, correspondence, and office admin.
All Operations prompts
SOP from a workflow description
Turn an informal workflow description into a proper, followable SOP.
SOP gap review
Audit an existing SOP for ambiguity or missing steps and propose specific fixes.
Meeting prep agenda
Build a time-budgeted agenda ordered by priority and marked for decision vs. info items.
Meeting notes to follow-up summary
Turn raw meeting notes into decisions, owned action items, and open questions.
Vendor status request
Request a status update from a vendor with a specific, professional ask.
Vendor issue internal escalation
Escalate a vendor problem internally, leading with business impact.
Operational incident report
Write a blameless, factual incident report with a clear timeline.
Incident prevention recommendations
Propose preventive measures that trace directly to the incident’s root cause, ranked by effort vs. impact.
Multi-process audit summary
Turn audit findings across several processes into a single prioritized improvement list.
Stakeholder status update
Turn raw progress notes into a status-led update with a clear decision-needed flag.
3-sentence executive summary
Condense a detailed status into exactly 3 sentences that never hide a risk.
Leadership-ready risk summary
State a project risk plainly with mitigation trade-offs and one clear recommendation.
Blocker escalation
Escalate a blocker with a specific ask and deadline stated up front.
Requirements draft from conversation notes
Turn stakeholder conversation notes into scoped must-haves and nice-to-haves.
Scope change summary
Document a scope change with impact and required approval, even if impact is unconfirmed.
Retrospective summary from raw notes
Structure retro notes into what went well, what to fix, and top takeaways.
Lessons-learned document
Turn a retrospective into forward-looking, actionable guidance for future projects.
RAID log entries
Categorize mixed project notes strictly into Risks, Assumptions, Issues, or Dependencies.
Meeting scheduling request
Draft a scheduling email that offers specific time options instead of an open-ended ask.
Reschedule notification
Notify attendees of a reschedule clearly, without over-apologizing.
Travel itinerary summary
Turn raw booking confirmations into a chronological itinerary with flagged risks.
Travel request summary
Turn trip details into an approval-ready travel request with an honest cost estimate.
Report formatting cleanup
Clean up and structure a raw report for distribution without altering its substance.
Expense summary from raw receipts
Categorize and total a raw expense list, flagging anything that does not fit a category.
Correspondence in the executive’s voice
Draft a message matching a described executive tone and covering every key point given.
Thank-you / acknowledgment note
Draft a brief, specific acknowledgment note tied to the actual thing being thanked for.
Office logistical announcement
Announce a logistical change with practical impact and dates stated up front.
