Essential SOPs Part 5: Rotational Field Audits
Every field in your CRM was added for a reason. The trouble is, nobody remembers most of them. Here's a simple rotation that keeps your fields honest without turning into a six-month project.
This is the fifth post in our Essential SOPs for Salesforce Admins series, based on my session at Texas Dreamin'. Part 1 made the case for routine maintenance, Part 2 covered user management, Part 3 covered backup and recovery, and Part 4 tackled duplicates. This week we wrap up our three weeks on data with the fields themselves.
I was working through a data dictionary with a client when we hit a field called Shipping Date.
Seems clear, right? Except it wasn't. The field was stamped automatically when the opportunity closed, and only then. The integration never came back and updated it with the actual ship date. So it wasn't a shipping date at all. It was an anticipated shipping date.
Meanwhile, someone had been building reports off it as if it were the real thing, and there was a chance commissions were being calculated from it too.
One field. One label that didn't mean what everyone thought it meant. That's why field audits belong on your SOP list.
How Fields Go Sideways
Nobody sets out to build a messy org. Fields pile up one reasonable request at a time:
The quick ask. Someone needs to track something for a project, so a field gets added. The project ends. The field stays.
No owner. When there's no one responsible for the platform, you end up with duplicate fields. Two teams ask for the same thing with different names, and both get built.
Fields to nowhere. The same field lives on more than one object, and neither one is actually being updated.
Lost meaning. One client had Amount and Annual Amount on their opportunities. Nobody knew what Annual Amount meant or when to use it, but it mattered a lot to the CEO, who was thinking of it as the value of the deal in the current year. Reps tabbed past it, or typed in whatever got them to the next screen when it was required.
That last one is the sneaky part. A field can have great adoption and still be full of bad data, because people are filling it in without a shared understanding of what belongs there.
Why "Rotational"?
When I suggest a field audit, I usually get one of two reactions: a laugh, or a look of quiet dread. People picture a giant spreadsheet with every field on every object and a summer spent filling it in.
Do you really need to go through every field at once? No.
A rotational audit means you pick one object (or one slice of an object) each month and give it a proper look. Accounts in one month, contacts the next, then opportunities, then leads, then whatever custom objects matter most to your business. Over the course of a year, you've touched everything that matters, and no single month feels like a burden.
The Monthly Rotation
For the object in this month's spotlight:
Pull the field list. Export the fields for the object, including the description and help text (if they exist, which is its own finding).
Check usage. For each field, look at how often it's actually populated, and where it's referenced. Salesforce's Where is this used? button on custom fields will tell you whether a field is tied to page layouts, automation, or reports.
Spot-check the data. Pull a quick report and eyeball what's in there. If the data doesn't line up with what you'd expect, that's often an enablement issue, not a field issue.
Ask the people who use it. My favorite audit question is simply: "What does this field mean to you?" Sometimes people respond with "Why are you asking me that?" That's fine. It doesn't matter what I think the field means. I need to know what the business thinks it means and what kind of data should be in it.
Decide: keep, fix, or retire. Keep it as is, fix the label, help text, or training, or start the process of retiring it.
Retire Carefully
Deleting a field feels great. It also can't always be undone the way you'd hope. Before you retire anything:
Hide it from page layouts first and see who notices. Silence for a month or two is a pretty good sign.
Confirm it's not feeding an integration, a report the executive team gets every Monday, or a commission calculation.
Make sure your backup (hello, Part 3) has captured the data before it goes.
Capture It in a Data Dictionary
Every rotation should leave something behind: a living data dictionary. People always chuckle when I bring this up, like it's busywork. But the data dictionary is what saved the day with that Shipping Date field. It's also how you'll onboard your next admin, your next sales leader, and, increasingly, your AI tools.
That last point matters more every quarter. AI is only as good as the data and context you ground it in. If your team can't agree on what a field means, your AI won't either. It'll just be confidently wrong, faster.
Where to Start
If field audits are the pillar you're picking up first, here's the single move: pick the five fields your leadership team looks at most (think the fields on the pipeline dashboard) and ask three people what each one means. If you get the same answer three times, great. If you don't, you've found your first audit.
What's Next
That wraps our three blogs on data. Next post, we shift from the data to the people using it with training material audits: why your enablement docs go stale faster than you think, and how to keep them in step with how your org actually works.
