The Field That Should Be Required but Is Not
One optional CRM field is quietly breaking your forecasts, your attribution, and your strategic decisions. The fix takes 15 minutes.
Somewhere in your CRM there is a field that is marked optional. It should be required. And the fact that it is optional is quietly breaking something downstream that you have been trying to fix for months.
It might be the lead source field. Every new contact enters the system without anyone noting where they came from. Six months later, the CEO asks which channel is producing the most revenue and nobody can answer because the data was never captured. The sales team says referrals. Marketing says the website. Finance says they do not know. Everyone is guessing because one field was left optional at the start.
It might be the close date on opportunities. Sales reps leave it blank because they do not want to commit to a number. The forecast depends on close dates. The forecast is wrong every quarter. Leadership stops trusting the forecast and starts running the business on gut feel. The root cause is not a forecasting problem. It is a field that should be required.
It might be the industry field on accounts. Without it, you cannot segment your pipeline by vertical. Without segmentation, you cannot measure which verticals are converting. Without that data, every decision about where to focus rests on opinion. One empty field, six months of unclear strategy.
The pattern is always the same. Someone set up the CRM during the early days when the team was small and everyone knew everything. Making fields optional felt reasonable because the three people using the system already had the context. Then the company grew. New people joined who did not have that context. The optional fields stayed optional. And the downstream effects compounded.
The fix takes 15 minutes. Open the CRM. Look at every field on the lead and opportunity objects. Ask one question for each: if this field is blank, does it break a report, a forecast, or a decision? If yes, make it required. Add a validation rule. The system enforces what the process could not.
It is not glamorous work. Nobody gets excited about making a field required. Six months from now, when the CEO asks where revenue is coming from and you can answer with data, the 15 minutes will have been the highest-leverage work anyone did all quarter.
Which fields in your CRM are optional right now that should be required?

Shannon Maguire
Principal System Architect, CWT Studio
Finds where your operations are breaking and installs enforcement so they cannot break again.
Engagements where this pattern showed up are documented in the case studies.
Continue Reading
The $130K Job Title Everyone Is Arguing About
Notes Not Working in Salesforce Starter? It's Chatter, and There's No Switch
Salesforce Is Retiring Your Edition. Here's What the Forced Move Actually Involves.
If this matches what's happening in your stack, 30 minutes is enough to place it.