Why Every Salesforce Admin Needs SOPs (And Why "I'll Get to It" Isn't a Strategy)
This is the first post in our Essential SOPs for Salesforce Admins series, based on the session I recently presented at Texas Dreamin’. Over the next several weeks, we'll walk through the six pillars of a healthy maintenance routine and help you pick the one to start with.
Quick question: When was the last time you audited your inactive users?
If you had to think about it, or if the honest answer is "when something broke," you're not alone. Many Salesforce admins or platform owners live in reactive mode. The ticket queue is full, sales needs a report by Friday, and someone just asked why their dashboard looks different. Routine maintenance is the thing you'll get to next month. And next month. And the month after that. We’ve all been there.
Here's the problem: next month never comes on its own. You have to put it on the calendar.
What Is an SOP, Really?
A Standard Operating Procedure sounds bureaucratic, but in the Salesforce world it's simple: the routine tasks you perform on a schedule to maintain a healthy instance. It’s not the backlog that you are working through or the project you are focused on for the quarter.
Think of it like the difference between going to the dentist twice a year and only going when a tooth hurts. Both approaches involve a dentist. Only one of them prevents the root canal.
Why This Matters More Now Than Ever
If SOPs have always been a good idea, why am I making the case for them now?
Because the cost of skipping them keeps going up.
Your org is more connected than it used to be. The average Salesforce instance now touches marketing automation, data enrichment tools, billing systems, and integration platforms. A stale user or an unreviewed permission doesn't stay contained anymore. It ripples across every connected system.
Budgets are under a microscope. When renewal season comes, "we think we're using most of our licenses" doesn't hold up. Admins who run regular license and usage reviews walk into those negotiations prepared and with numbers.
Trust erodes quietly. Nobody announces that they've stopped believing the dashboards. They just start exporting to Excel. By the time leadership notices, you're not doing maintenance anymore, you’re probably in a fire drill to figure out what happened.
And yes, the new AI features raise the stakes too. Anything you layer on top of your org (automation, agents, analytics) inherits your data quality and your permission structure. Clean foundations were always the goal and now more tools than ever depend on them.
The admins who look effortless aren't smarter. They just have routines.
The Six Pillars of Salesforce SOPs
Over this series, we'll break down the essential SOPs into six areas:
User Management: The monthly, quarterly, and annual routines that keep licenses optimized and access clean, including the shift from Profiles to Permission Set Groups.
Data Management & Governance: Backup strategy, rotational field audits, and deduplication. This is where "grounding your AI" gets practical.
System Customization, Architecture & Change Management: Intake frameworks that end "Slack drive-by requests," plus sandbox and release management cadences.
Security, Access & AI Trust Boundaries: Health checks, permissions audits, and the newer work of making sure sensitive data is masked before it ever reaches an LLM.
System Performance, Optimization & Automation: Org Check, integration audits, and how to break the big annual work into manageable chunks.
Stakeholders & Documentation: The human side: persona reviews, decision-maker check-ins, and keeping your documentation a living thing instead of a time capsule.
Each post will give you the specific tasks, the cadence for each one, and a practical way to get started.
The Only Rule of This Series: Pick One
Here's what I told the room at Texas Dreamin', and it's the advice I'll repeat at the end of every post in this series:
Pick one to start.
Don't try to implement all six pillars this quarter. Don't build a 40-row spreadsheet of maintenance tasks that collapses under its own weight by March. Choose the one area where your org feels the most pain (licenses you can't account for, data nobody trusts, a release that surprised you) and build the routine for that one thing.
An SOP you actually run monthly beats a comprehensive framework you abandoned in week three.
What's Next
In the next post, we'll dig into User Management: the monthly license and MFA checks, the quarterly stale-user sweeps, and the annual audits that keep your org clean and your renewal negotiations honest.
Until then, here's your homework: look at those six pillars and ask yourself which one would embarrass you in an audit. That's probably your starting point.
