Turn rough notes into a clear SOP Starter · Any AI assistant
A step-by-step SOP with roles, checkpoints, problem handling and a version table, ready for review.
You are an operations specialist who writes SOPs that frontline staff can follow.
Process: [name, for example, receiving goods at the warehouse]
Who does it: [roles]
Tools and systems: [list]
My rough notes: [paste notes, a voice memo transcript or the old SOP]
Common mistakes today: [list]
Write the SOP:
1. Purpose and scope in two sentences.
2. Roles and responsibilities.
3. Numbered steps, one action per step, each starting with a verb. Mark checkpoints where the person must verify something before moving on.
4. What to do when something goes wrong, for the three most likely problems.
5. Safety: for any step with a hazard, the PPE and controls from our risk assessment (HIRARC), marked for our safety officer to confirm.
6. Records to keep.
7. A version control table: version, date, author, changes, approver.
Write at a level a new staff member can follow on day one. If my notes skip a step or leave a decision unclear, list it as a question at the end instead of guessing.
Optional: add a Bahasa Malaysia version of the steps. Tip: Ask someone who does the job to walk through the draft and correct it. Add photos or screenshots to the steps once the text is agreed. Steps that involve machinery, chemicals or work at height need sign-off from your safety and health officer before use.
Map a process and find the bottlenecks Starter · Any AI assistant
A process map, the main bottlenecks and improvement ideas ranked by impact and effort.
You are a lean process improvement consultant.
Process: [name, start point, end point]
How it works today: [describe the steps, who does each, systems used, handovers and approvals]
Volume and timing: [for example, 200 orders a week, 5 days end to end]
Complaints or problems: [list]
Ask me up to three questions first if the description has gaps. Then:
1. Write the current process as a table: step, role, action, system, typical work time and wait time before the next step.
2. Mark each step as Value-adding, Necessary (required but adds no value for the customer) or Waste.
3. Identify the three biggest bottlenecks or delays and explain why they happen.
4. Suggest improvements for each, such as removing an approval, combining steps, standard templates or automation.
5. Rank the ideas in a table by impact and effort (High, Medium or Low).
6. Draw the improved process as a Mermaid flowchart I can paste into a diagram tool. Tip: Time a few actual cases before you run the prompt, since estimated wait times are often wrong. Check the map with the people who do each step.
Compare vendor quotations side by side Advanced · ChatGPT, Claude, Copilot
A like-for-like comparison of quotations with scope gaps, weighted scores and questions for each vendor.
You are a procurement analyst. I have attached [number] vendor quotations as PDF files for [what we are buying].
Our requirements: [paste the specification or must-haves]
Evaluation weightings: [for example, price 40%, quality and specification 30%, delivery 15%, support 15%]
Do the following:
1. Extract each quotation into a table: vendor, items, quantities, unit prices, total in RM, SST or other charges as shown, delivery time, payment terms, warranty, validity and exclusions.
2. Normalise the quotes so they compare like for like. Flag items one vendor included and another left out, and estimate the cost of closing each gap, labelled as an estimate.
3. Check each quote against our requirements and mark Met, Not met or Unclear.
4. Score the vendors using the weightings, showing your scoring.
5. Recommend a vendor for the evaluation committee to decide on, and list questions to ask each vendor.
6. List what we must verify before award, such as company registration, licences, certificates (for example ISO or halal) and references.
Give the PDF page for every figure you extract. Then check your own extraction: recalculate each quotation total and flag any that do not add up. Tip: Check extracted prices against the PDFs before you share the comparison. The recommendation is input for the people who approve; follow your company's procurement policy on approvals and the number of quotations required, and keep vendor pricing in a company-approved AI tool.
Write a blameless incident review Starter · Any AI assistant
An incident review with timeline, root causes, actions and owners, focused on systems over individuals.
You are a facilitator for blameless post-incident reviews.
Incident: [what happened, for example, a delivery sent to the wrong customer, a system outage or a near miss on the production floor]
When and where: [date, time, site]
Impact: [customers affected, cost in RM, safety, downtime]
What we know: [paste notes, chat logs or statements, with names replaced by roles]
Write an incident review:
1. A summary in three sentences.
2. A timeline of events with times.
3. What went well in the response.
4. Contributing factors across people, process, systems and environment. Use the five whys to reach root causes for the two most important factors.
5. Actions, each with an owner role, a due date and how we will know it worked. Favour actions that change systems and processes over reminders to be careful.
6. Open questions to investigate.
7. If this was a workplace accident, dangerous occurrence or near miss: what may need to be recorded or notified to DOSH, marked for our safety and health officer to confirm.
Describe what people did and why it made sense to them at the time, without blaming individuals. Tip: Replace names with roles before pasting logs or statements. Keep this review separate from any disciplinary process. For safety incidents, your safety and health officer decides what must be notified to DOSH and by when; check the current rules under OSHA 1994 as amended.
Stress-test an operations plan before you commit Advanced · Claude, ChatGPT, Gemini
A critical review of your plan that exposes weak assumptions, likely failure points and missing steps.
You are a sceptical, experienced chief operating officer reviewing my plan before I present it.
The plan: [paste or attach, for example, a system rollout, a new shift pattern or a site move]
Goal: [what success looks like]
Constraints: [budget in RM, timeline, people, systems]
Review it in three passes:
1. Assumptions: list every assumption the plan depends on, stated or hidden, and rate each as Solid, Uncertain or Risky, with your reason.
2. Pre-mortem: imagine it is six months later and the plan has failed. Give the five most likely reasons, each with an early warning sign.
3. Gaps: missing steps, owners, dependencies, approvals, communication or training.
Then give:
- The three changes that would most improve the plan.
- Questions a steering committee is likely to ask, with what I need to answer them.
Be direct. Critique the plan and leave the rewriting to me. Tip: Run it, revise the plan, then run it again on the new version. Ask a colleague to challenge the same points in person.
Write a weekly project status update (Starter · Copilot, ChatGPT, Claude) Build a project risk register through guided questions (Advanced · Claude, ChatGPT, Copilot) Design a KPI dashboard for your operation (Advanced · Copilot, ChatGPT, Claude) Find stock risks and slow movers in inventory data (Advanced · ChatGPT, Claude, Copilot) Plan a response to a supplier delay (Starter · Any AI assistant) Draft a HIRARC risk assessment for a task (Advanced · Claude, ChatGPT, Copilot) Set up an SOP assistant for frontline staff (Advanced · NotebookLM, ChatGPT, Gemini) Prepare a checklist for a halal audit (Starter · Any AI assistant) Cut patient waiting times at a clinic (Starter · Any AI assistant) Plan logistics for an exam week or school event (Starter · Any AI assistant) Organise a defect list for property handover (Starter · ChatGPT, Claude, Copilot) Improve a public service counter process (Starter · Any AI assistant) Streamline the steps in claims processing (Starter · Claude, ChatGPT, Copilot)