AI-Assisted SOP Generator
Procedures written in a minute and approved from the inbox
Personal IP, built independently.
The problem
Every operations manager knows the procedures should be written down. Very few of them are, because writing a clean, consistent document takes an hour that nobody has, and the person who knows the process best is usually the one least likely to sit down and type it. So the knowledge stays in someone’s head, and the day they’re off sick the warehouse finds out what that costs.
What I built
A workflow where the person who does the job answers a short form, in their own words, and a formatted procedure appears a minute later. The answers are sent to a language model with a strict structure to fill in, so the result comes back as seven clean fields rather than a wall of prose. Those fields are written into a branded Google Doc with real headings, a PDF copy is saved to Drive, and the manager gets an email with Approve and Deny buttons.
Make has no built-in way to pause and wait for a person, so the approval is a second scenario. The buttons in the email point at a webhook that carries the document’s ID and the decision; a router files the document into the Approved or Rejected folder and shows the manager a confirmation page. Nothing gets filed as official until someone has said yes.
The stack
Make.com for both scenarios, the Claude API for the drafting, Google Forms, Docs, Drive and Gmail for the documents and the approval email, and webhooks to close the loop. Two scenarios, fourteen modules.
What changed
A one-minute form becomes a formatted, branded SOP that a manager approves from their inbox, and it files itself in the right folder. The same webhook-and-router gate drops into any workflow that needs a person to sign off before something becomes official: expense approvals, published content, client deliverables.
Proof
