How to Create an SOP in Salesforce
Salesforce admins change field logic every sprint. An SOP that took a day to write is wrong by Friday. Here is how to build one that survives - and how to re-record it in minutes when it does not.
- Free plan — no card
- Works on any web app
- Share with one link
- Blur sensitive data
What does “Create an SOP in Salesforce” mean?
An SOP for Salesforce is a written procedure that defines exactly how a specific record-level task is performed - which object to start from, which fields are mandatory, which validation rules apply, and what the record should look like when the task is complete. It exists so that two reps performing the same task produce the same data.
Why this matters
Salesforce data quality is a documentation problem long before it is a reporting problem. When reps guess at stage definitions or skip required fields, pipeline forecasts drift and nobody can point at the moment it broke.
Where it goes wrong today
Stage definitions live in someone's head
Ask five reps what Negotiation means and you get five answers. The report built on top of that is fiction.
Screenshots go stale every release
Salesforce ships three seasonal releases a year plus your own admin changes. A screenshot-heavy Google Doc is out of date within a quarter.
Nobody can find the doc
The SOP is in a Drive folder the new hire was never shared on, so they ask in Slack instead and get a half-remembered answer.
Writing it is a full day of work
Capture, crop, annotate, caption, repeat. For a twenty-step Lightning flow that is most of a working day for the one admin you cannot spare.
The fix
How Michii handles it
Capture the real workflow, do not describe it
Record yourself performing the task in Salesforce once. Every click, field entry and page transition is captured with a screenshot, in order.
Re-record instead of re-writing
When Spring release moves a button, redo the affected steps in under a minute rather than patching images by hand.
Share as a link, not a file
Paste one URL into the Chatter post, the onboarding checklist, or the Salesforce help text itself. It never gets a stale copy.
Blur what should not be captured
Redact customer names, emails and revenue figures on the captured screenshot before publishing.
How to create an sop in Salesforce
Work through this once for a single, high-frequency task - converting a lead, or moving an opportunity to Closed Won. Get that one right before documenting the rest.
Pick one task with a clear start and end
Not Manage the pipeline. Something like Convert a qualified lead into an opportunity and contact. If you cannot name the finished record, the scope is too wide.
Write the prerequisites first
Which profile or permission set, which record type, which Salesforce org. A guide that assumes the reader already has access will fail on step one for half its audience.
Record yourself doing it in Salesforce
Start the capture, then perform the task at normal speed in a sandbox or with test data. Do not narrate or slow down - the tool captures each click regardless.
Fix the wording on the generated steps
Auto-generated captions say what was clicked. Replace the ones that need the why - especially validation rules, required fields, and anything with a business rule behind it.
Redact anything customer-identifying
Blur account names, contact emails, deal values and any PII on the captured screenshots before you publish.
Define what done looks like
End with the record state a reader can check themselves - stage set, close date populated, contact role assigned.
Link it where the work happens
Put the URL in the Salesforce help text for that page layout, in the onboarding checklist, and in the team Slack channel topic. A wiki nobody opens is not documentation.
By hand vs. with Michii
| Doing it by hand | With Michii | |
|---|---|---|
| Time to first draft | Most of a day for a 20-step flow | About as long as performing the task once |
| Keeping up with releases | Re-screenshot and re-caption by hand | Re-record the changed steps in a minute |
| Reader experience | Match the doc against your screen and hope | Replay the steps on the live Salesforce org |
| Distribution | A PDF in a Drive folder | One link that always shows the current version |
| Sensitive data | Manually crop or blur each image | Redact on the capture before publishing |
What teams use this for
Checklist
- Name the exact starting object and record type
- List the required profile or permission set
- One action per step - split any step containing the word and
- Screenshot every validation rule the reader will hit
- Redact all account names contact emails and revenue figures
- State the finished record state so the reader can self-check
- Assign an owner and a review date at the top
Frequently asked questions
How long does it take to write a Salesforce SOP?
Written by hand with screenshots, budget five to ten minutes per step - most of a day for a twenty-step flow. Recorded automatically, it takes about as long as performing the task once, plus editing time for wording and redaction.
How do I keep a Salesforce SOP current across seasonal releases?
Re-record the affected steps rather than editing screenshots. Because capture takes a minute, re-recording after Spring, Summer and Winter releases actually gets done, where patching images does not.
Can I document Salesforce workflows without an admin licence?
Yes. Capture happens in the browser on the screens you can already reach, so any user can document their own workflow at their own permission level.
How do I stop customer data ending up in the SOP?
Record in a sandbox with test data where you can, and blur account names, contact details and deal values on the captured screenshots before publishing.
Where should the finished SOP live?
Link it from the place the work happens - the Salesforce help text on that page layout, the onboarding checklist, and the team Slack topic. Central wikis are where documentation goes to be forgotten.
Document your Salesforce workflow in one pass
Record the task once. Michii writes the numbered steps, captures each screen, and gives you a link your team can replay against the live org.
Create an SOP in other tools
Related