You can do a lot in Salesforce without writing Apex. Two of the sharpest tools are formula fields and validation rules. Used well, they make pages cleaner, data smarter, and processes safer—without slowing admins down or confusing users. This guide is written for intermediate builders who know the basics and want practical patterns, gotchas, and copy-paste snippets.

If you need official references, start with formula fields and validation rules. For a quick operational tune-up alongside these changes, see our checklist 10 High-Impact Updates Every Salesforce Admin Should Make.

How to think about formulas vs. validations

• Formulas compute a value at view time. Great for scorecards, derived dates, “smart” labels, rollups you can’t get otherwise, and helper fields for reports.
• Validations prevent a save when data doesn’t meet your rules. Use them to enforce process, guard compliance, and stop garbage at the door.

Pro tip: Design the smallest rule that gets the behavior you want. Overly strict logic drives users to spreadsheets.

Recipe 1 — “Next Step can’t go stale” (Opportunity)

Goal: keep pipeline review honest by requiring a fresh Next Step in later stages.

Validation Rule (Opportunity)

AND(
  ISPICKVAL(StageName, "Proposal/Price Quote"),
  OR(
    ISBLANK( NextStep ),
    TODAY() - DATEVALUE(LastModifiedDate) > 14,
    NOT(ISCHANGED(NextStep))
  )
)

Why it works: enforces that a human updated Next Step within 14 days when the deal is serious. Pair with a list view “Needs Update.”

Recipe 2 — “Auto-name Opportunities” (consistent, report-friendly)

Formula (Text)

Account.Name & " — " &
TEXT( StageName ) & " — " &
TEXT( CloseDate )

Use it for: a read-only display name or a helper field for exports.
Gotcha: if you actually rename the standard Name field, make sure downstream integrations aren’t expecting user-entered names.

Recipe 3 — “Discount needs a reason” (soft control)

Validation Rule (Opportunity)

AND(
  Discount__c > 0,
  ISBLANK( Discount_Reason__c ),
  ISCHANGED(Discount__c)
)

Pattern: allow flexibility but capture intent when it matters.

Recipe 4 — Phone and email sanity checks (REGEX)

Validation Rule (Lead – simple US phone)

AND(
  NOT( ISBLANK( Phone ) ),
  NOT( REGEX( Phone, "^(\\+1)?\\s*\\(?\\d{3}\\)?[-\\.\\s]?\\d{3}[-\\.\\s]?\\d{4}$" ) )
)

Validation Rule (Contact – email format)

AND(
  NOT( ISBLANK( Email ) ),
  NOT( REGEX( Email,
    "^[A-Z0-9._%+-]+@[A-Z0-9.-]+\\.[A-Z]{2,}$"
  ))
)

Tip: keep formats forgiving; your goal is “less junk,” not perfection.

Recipe 5 — “Close Date can’t be in the past” (with exceptions)

Validation Rule (Opportunity)

AND(
  ISCHANGED(CloseDate),
  CloseDate < TODAY(),
  NOT($Profile.Name = "System Administrator")
)

Pattern: allow admins/batch users to fix bad imports; everyone else follows the rule.

Recipe 6 — KPI helper: “Win probability from stage and signal”

Formula (Percent, 0–1)

/* Base from stage */
CASE(
  TEXT(StageName),
  "Qualification", 0.1,
  "Proposal/Price Quote", 0.5,
  "Negotiation/Review", 0.7,
  "Closed Won", 1,
  0.05
)
/* Nudge up if executive engaged */
+ IF( Executive_Sponsor__c = TRUE, 0.1, 0 )
/* Nudge down if open P1 case */
- IF( Has_Open_P1_Case__c = TRUE, 0.15, 0 )

Use it for: scoring and coaching dashboards without building a model.
Gotcha: cap results with MIN(1, MAX(0, <expr>)).

Recipe 7 — Stage-dependent field requirements (no more blanket required fields)

Validation Rule (Opportunity)

AND(
  ISPICKVAL(StageName, "Negotiation/Review"),
  ISBLANK( Primary_Stakeholder__c )
)

Pattern: require only what’s needed at this stage. Pair with Dynamic Forms to hide later-stage fields earlier in the cycle.

Recipe 8 — Lock fields after approval (immutability)

Validation Rule (Custom Object)

AND(
  PRIORVALUE(Status__c) = "Approved",
  ISCHANGED( Price__c ),
  NOT( $Permission.Approval_Override__c )
)

Pattern: once a record is “approved,” disallow changes to money fields unless a named permission is on (create a Permission Set with the Approval_Override__c permission and grant sparingly).

Recipe 9 — Cross-object formulas for coaching

Formula (Text on Opportunity): summarize account health)

/* Show an at-a-glance read for reps and managers */
"Health: " &
CASE(Account.Health_Score__c, 3, "Strong", 2, "Watch", 1, "Risk", "Unknown") &
" — Open P1s: " & TEXT(Account.Open_P1_Cases__c)

Why: put the most important account signals where decisions happen (on the deal).
Gotcha: formula fields display even if the referenced fields are FLS-hidden; avoid exposing PII indirectly.

Recipe 10 — Helpful links right on the record (HYPERLINK)

Formula (Text on Account): jump to external system)

HYPERLINK(
  "https://billing.example.com/customer?id=" & CASESAFEID(Id),
  "Open in Billing",
  "_blank"
)

Pattern: create fast paths to docs, billing, or internal tools.
Tip: use CASESAFEID() to guarantee a 18-char ID for systems that care.

Testing & performance notes (worth your time)

• Order of execution: validations run before flows and before write to DB. Formulas render at view time, so they’re always “fresh.”
• Null math: use BLANKVALUE() and VALUE() to avoid #Error! when numbers/text collide.
• Compile size: super long formulas can hit limits; break them into multiple fields or use CASE() instead of deep IF() ladders.
• Profiles vs Permission Sets: aim for least privilege; validations can reference $Permission.X to allow controlled bypasses.
• Reports & exports: a hidden field on the layout can still leak via reports if FLS grants Read. Check both UI and report builder.

If you’re tightening security while you build, our deep dive Salesforce Security Review: Field-Level Security & Auditing covers FLS checks, history, and export monitoring.

Naming, comments, and governance

• Name rules for humans: opp_require_next_step_at_proposal beats VR_001.
• Comment formulas: inline comments help future you (and auditors).
• Bundle work: ship related formulas/validations with DevOps Center so history and approvals are clear.
• Sandbox first: test with representative data and multiple profiles.

For broader operating hygiene (page speed, backup, access), this companion post helps: Top 10 Tips for Salesforce Administrators.

When to reach for something else

• Rollup logic across large hierarchies → use Declarative Lookup Rollup Summaries (AppExchange) or Flow + scheduled paths.
• Complex date math with business hours → consider Flow or Apex for accuracy.
• Heavily dynamic rules (thresholds change often) → store values in Custom Metadata Types and reference with $CustomMetadata in formulas/validations.

Bottom line

Formulas make your data smarter; validations keep it honest. Start with one friction point—stale next steps, missing stakeholders, sloppy discounts—and apply the smallest rule that nudges behavior. Measure the impact, iterate, and keep your rules readable. If you want a quick review of your org’s formulas and validations, Revenue Ops can run a focused audit and leave you with a clear backlog.