Skip to content
Suggest a correction

Account Check Builder Guide: configuration and results

Example42 min read

The Example: Account Check Builder Guide Check Set installs with Record Health Check and contains 25 Account Checks that teach every Evaluation Type: three formula Checks, ten query Checks, eleven Compare two queries Checks, and one Apex Check. This page lists every Setup value of each Check exactly as installed, and its result on the Acme Corporation demo Account, so you can study a working Check before you build your own.

  • Find a Check on the card by its title. Several Record Health Check Name values were kept from earlier releases and do not describe what the Check does now, such as Example_Website_URL_Valid for Account Type is set.
  • In an org where the package is installed, every name has the rhc__ prefix, such as rhc__Example_Website_URL_Valid.
  • The tables show the values that differ from the defaults. Every Check is active, belongs to the Example_Account_Check_Builder_Guide Check Set, and has Publish User Result Event cleared.
  • Each result names the label the card shows on Acme Corporation, the Account that the demo scratch org creates. In your own org the results depend on your data.
  • To change a Check, clone it into a Check Set your organization owns. A package upgrade can replace changes made to the installed record.

The Check Set waits for Run, reveals one row at a time, shows passed and skipped rows, shows Found and Expected on demand, and places one summary below the rows; none of these Checks has a Category. On Acme Corporation the summary reads 7 Passed, 5 Failed, 9 Warnings, 3 Info, and 1 Unable.

These Checks read fields on the Account and its parent Account.

Label: Example: Account Type is set. Record Health Check Name: Example_Website_URL_Valid. Result on Acme Corporation: Pass. Acme’s Type is Customer.

FieldValue
Evaluation TypeVerify with a formula
Check DescriptionThe formula checks the standard Account Type picklist. It passes when Type has a value and fails when Type is blank.
Applies ToAll records
Pass ConditionNOT(ISBLANK(TEXT(Type)))
Display: Found FormulaIF(ISBLANK(TEXT(Type)), "Not set", TEXT(Type))
Display: Expected Formula"An Account Type is selected"
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatText
Formula Result TypeText
Failure SeverityWarning
Message When Failed{!record.Name fallback="This Account"} has no Account Type selected.
Fix MessageFor {!record.Name fallback="this Account"}, select the Type that describes its relationship to your business.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelSet Account Type for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/edit

Check 20: Account has a phone number or website

Section titled “Check 20: Account has a phone number or website”

Label: Example: Account Phone or Website. Record Health Check Name: Example_Segregation_Of_Duties. Result on Acme Corporation: Pass. Acme has a Phone and a Website.

FieldValue
Evaluation TypeVerify with a formula
Check DescriptionThe formula checks the standard Account Phone and Website fields. It passes when either field has a value and fails when both are blank. This checks completeness, not whether the number or website is valid.
Applies ToAll records
Pass ConditionOR(NOT(ISBLANK(Phone)), NOT(ISBLANK(Website)))
Display: Found Formula"Phone: " & BLANKVALUE(Phone, "Not set") & "; Website: " & BLANKVALUE(Website, "Not set")
Display: Expected Formula"A phone number or website is provided"
Display: Value FormatText
Formula Result TypeText
Failure SeverityWarning
Message When Failed{!record.Name fallback="This Account"} has neither a phone number nor a website.
Fix MessageFor {!record.Name fallback="this Account"}, add a business phone number or website so users can contact or research the business.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelAdd Phone or Website for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/edit

Check 30: Billing address matches the parent bill-to account

Section titled “Check 30: Billing address matches the parent bill-to account”

Label: Example: Parent bill-to alignment. Record Health Check Name: Example_Guide_Industry_Manufacturing. Result on Acme Corporation: Pass. Acme’s billing address matches its parent Account’s.

FieldValue
Evaluation TypeVerify with a formula
Check DescriptionThe formula passes only when all five billing-address components match the parent; any difference fails and no parent skips. Clone only when centralized parent billing is policy, with rules for normalization and legal-entity exceptions.
Applies ToWhen a formula is true
Applies When (Formula)NOT(ISBLANK(ParentId))
Message When Not Applicable{!record.Name fallback="This Account"} has no parent bill-to account to compare.
Pass ConditionAND(BillingStreet = Parent.BillingStreet, BillingCity = Parent.BillingCity, BillingState = Parent.BillingState, BillingPostalCode = Parent.BillingPostalCode, BillingCountry = Parent.BillingCountry)
Display: Found FormulaBillingStreet & ", " & BillingCity & ", " & BillingState & " " & BillingPostalCode & ", " & BillingCountry
Display: Expected FormulaParent.BillingStreet & ", " & Parent.BillingCity & ", " & Parent.BillingState & " " & Parent.BillingPostalCode & ", " & Parent.BillingCountry
Display: Value FormatText
Formula Result TypeText
Failure SeverityInfo
Message When Failed{!record.Name fallback="This Account"} does not match the parent Account’s complete bill-to address.
Fix MessageFor {!record.Name fallback="this Account"}, compare the complete child and parent addresses shown in Found and Expected. Confirm the legal bill-to location with finance before correcting either record.
Message When Unable To EvaluateThe billing addresses for {!record.Name fallback="this Account"} and its parent could not be compared. Verify hierarchy and billing-field access, then retry.
Action LabelReview bill-to address for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/edit

These Checks progress from a count compared with a fixed number (40, 50), to tests of every returned row (60 to 90), Contact Roles (100, 110), a value found in a list (120), and an expected value from a second query (130).

Check 40: High-priority open Cases stay within the limit

Section titled “Check 40: High-priority open Cases stay within the limit”

Label: Example: High-priority Case count. Record Health Check Name: Example_Fewer_Than_Ten_Open_Cases. Result on Acme Corporation: Failed. Acme has 4 open High-priority Cases; the limit is 1.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check counts open Cases with Priority High. It passes when no more than one high-priority Case requires Account-level escalation at the same time.
Applies ToAll records
Source QuerySELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND Priority = 'High'
How To Read Query ResultsOne row or aggregate
Comparison OperatorAt most
Expected Value Comes FromFixed value
Expected Value (Fixed)1
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityCritical
Message When Failed{!record.Name fallback="This Account"} has more than one high-priority open Case, exceeding the example escalation capacity.
Fix MessageFor {!record.Name fallback="this Account"}, review ownership, customer impact, and recovery plans. Escalate excess workload according to the support model; do not lower priority merely to clear the check.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview Cases for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Cases/view

Check 50: At least one open Opportunity is Commit

Section titled “Check 50: At least one open Opportunity is Commit”

Label: Example: Commit Opportunity count. Record Health Check Name: Example_Significant_Open_Opp. Result on Acme Corporation: Info. No open Opportunity is in the Commit forecast category.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check counts open Opportunities with Forecast Category Commit. It passes when at least one open deal is included in the committed forecast.
Applies ToAll records
Source QuerySELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false AND ForecastCategoryName = 'Commit'
How To Read Query ResultsOne row or aggregate
Comparison OperatorAt least
Expected Value Comes FromFixed value
Expected Value (Fixed)1
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityInfo
Message When Failed{!record.Name fallback="This Account"} has no open Opportunity in Forecast Category Commit.
Fix MessageFor {!record.Name fallback="this Account"}, review the forecast with Opportunity owners. Update Forecast Category only when the deal meets the organization's Commit criteria.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview pipeline for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Label: Example: Open Case Contacts. Record Health Check Name: Example_Open_Cases_Have_Contacts. Result on Acme Corporation: Failed. 6 of the 12 open Cases have no Contact.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check reads Contact on each open Case. It passes only when every returned Case has a Contact. With no open Cases, it passes.
Applies ToAll records
Source QuerySELECT ContactId FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false
Source Query FieldContactId
How To Read Query ResultsEvery record passes
Comparison OperatorIs not empty
If Query Finds No RecordsPass
If Field Value Is EmptyTreat as not matching
Display: Found Text{!rhcResult.failedRecordCount} of {!rhcResult.totalRecordCount} missing
Display: Expected TextNone missing
Display: Value FormatText
Failure SeverityCritical
Message When FailedOne or more open Cases for {!record.Name fallback="this Account"} have no Contact.
Fix MessageAssign the correct customer Contact to each open Case on {!record.Name fallback="this Account"}. Close any Case that no longer needs work.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview open Cases for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Cases/view

Check 70: Every escalated open Case has a Description

Section titled “Check 70: Every escalated open Case has a Description”

Label: Example: Escalated Case descriptions. Record Health Check Name: Example_Guide_Contacts_Have_Email. Result on Acme Corporation: Warning. The escalated open Case has no Description.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check reads Description on each escalated open Case. It passes only when every Description has a value. No escalated open Cases skips the check. It does not assess the quality of the text.
Applies ToAll records
Source QuerySELECT Description FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND IsEscalated = true
Source Query FieldDescription
How To Read Query ResultsEvery record passes
Comparison OperatorIs not empty
If Query Finds No RecordsSkip
If Field Value Is EmptyTreat as not matching
Display: Found Text{!rhcResult.failedRecordCount} of {!rhcResult.totalRecordCount} missing
Display: Expected TextNone missing
Display: Value FormatText
Failure SeverityWarning
Message When FailedOne or more escalated open Cases for {!record.Name fallback="this Account"} do not document customer impact.
Fix MessageFor {!record.Name fallback="this Account"}, review the escalated Case with the Case owner and add a factual Description of customer impact. Do not add placeholder text.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview escalated Cases for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Cases/view

Check 80: Every open Opportunity has an active owner

Section titled “Check 80: Every open Opportunity has an active owner”

Label: Example: Active Opportunity owners. Record Health Check Name: Example_High_Value_Open_Opp. Result on Acme Corporation: Pass. Both open Opportunities have active owners.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check verifies Active on the owner of every open Opportunity. It passes only when every Opportunity owner is an active Salesforce user.
Applies ToAll records
Source QuerySELECT Owner.IsActive FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Source Query FieldOwner.IsActive
How To Read Query ResultsEvery record passes
Comparison OperatorEqual to
Expected Value Comes FromFixed value
Expected Value (Fixed)true
If Query Finds No RecordsPass
If Field Value Is EmptyTreat as not matching
Display: Found Text{!rhcResult.failedRecordCount} of {!rhcResult.totalRecordCount} inactive
Display: Expected TextNone inactive
Display: Value FormatText
Failure SeverityWarning
Message When FailedOne or more open Opportunities for {!record.Name fallback="this Account"} are assigned to inactive users.
Fix MessageFor {!record.Name fallback="this Account"}, confirm the correct active sales owner, then transfer each open Opportunity through the approved ownership process.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview pipeline for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 90: No proposal has a missing or low Amount

Section titled “Check 90: No proposal has a missing or low Amount”

Label: Example: Proposal Amount exceptions. Record Health Check Name: Example_Open_Opps_Have_Amount. Result on Acme Corporation: Pass. The proposal’s Amount is $600,000, above the $25,000 minimum.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check returns only proposal-stage Opportunities whose Amount is blank or below $25,000. It passes when the query returns no Opportunity names.
Applies ToAll records
Source QuerySELECT Name FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote' AND (Amount = null OR Amount < 25000)
Source Query FieldName
How To Read Query ResultsEvery record passes
Comparison OperatorIs empty
If Query Finds No RecordsPass
If Field Value Is EmptyTreat as not matching
Display: Found TextProposal opportunities needing review: {!rhcResult.totalRecordCount}
Display: Expected TextNo exceptions
Display: Value FormatText
Failure SeverityWarning
Message When FailedOne or more proposal-stage Opportunities for {!record.Name fallback="this Account"} have a blank Amount or fall below $25,000.
Fix MessageFor {!record.Name fallback="this Account"}, validate scope, pricing, and commercial fit before advancing the deal. Requalify or return undersized deals to an earlier stage; do not inflate Amount to clear the check.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview Opportunities for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 100: Open Opportunities include a Decision Maker

Section titled “Check 100: Open Opportunities include a Decision Maker”

Label: Example: Decision Maker roles. Record Health Check Name: Example_Has_At_Least_One_Contact. Result on Acme Corporation: Pass. One Decision Maker Contact Role is on an open Opportunity.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check counts Decision Maker Contact Roles across open Opportunities. It passes when at least one role exists. This checks the recorded role, not whether the person has verified buying authority.
Applies ToAll records
Source QuerySELECT COUNT() FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false AND Role = 'Decision Maker'
How To Read Query ResultsOne row or aggregate
Comparison OperatorAt least
Expected Value Comes FromFixed value
Expected Value (Fixed)1
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityWarning
Message When FailedNo decision-maker Contact Role is identified across the open pipeline for {!record.Name fallback="this Account"}.
Fix MessageFor {!record.Name fallback="this Account"}, confirm final buying authority, then add the verified Contact as a Decision Maker on the appropriate open Opportunity. Do not infer authority from title alone.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview buying roles for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 110: Contacts on open deals have Email or Phone

Section titled “Check 110: Contacts on open deals have Email or Phone”

Label: Example: Contact details on open deals. Record Health Check Name: Example_Contact_States_Match_Billing. Result on Acme Corporation: Warning. One Contact Role’s Contact has neither Email nor Phone.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check counts Contact Roles on open Opportunities whose Contact has neither Email nor Phone. It passes when the count is zero. It checks presence, not whether the contact details are valid.
Applies ToAll records
Source QuerySELECT COUNT() unreachableStakeholders FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false AND ContactId != null AND Contact.Email = null AND Contact.Phone = null
Source Query FieldunreachableStakeholders
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Expected Value Comes FromFixed value
Expected Value (Fixed)0
If Query Finds No RecordsPass
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue} missing both
Display: Expected TextNone missing both
Display: Value FormatNumber
Failure SeverityWarning
Message When FailedOne or more open-deal stakeholders for {!record.Name fallback="this Account"} have neither email nor phone.
Fix MessageFor {!record.Name fallback="this Account"}, confirm a permitted email address or phone number directly with the stakeholder or an authorized source. Never add fabricated contact data.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview buying contacts for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 120: Open-deal Contact Roles include Technical Buyer

Section titled “Check 120: Open-deal Contact Roles include Technical Buyer”

Label: Example: Find a Technical Buyer role. Record Health Check Name: Example_Billing_State_In_Contacts. Result on Acme Corporation: Info. No open-deal Contact Role is Technical Buyer.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check searches the Role values on open Opportunities for Technical Buyer. It passes when the role appears. Found shows the value being sought; Expected shows the returned list to search.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no Contact Roles on open Opportunities, so buying-committee breadth cannot be measured.
How To Read Query ResultsCompare as lists
Value to find in the list (formula)"Technical Buyer"
Comparison OperatorList contains any
Comparison QuerySELECT Role FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false AND Role != null
Comparison Query FieldRole
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatText
Failure SeverityInfo
Message When FailedNo Technical Buyer is identified across the open-deal buying committee for {!record.Name fallback="this Account"}.
Fix MessageValidate the buying process for {!record.Name fallback="this Account"} and classify a Technical Buyer only when the customer's evaluation responsibility is confirmed.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview buying committee for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 130: Cases closed keep pace with Cases created

Section titled “Check 130: Cases closed keep pace with Cases created”

Label: Example: Cases closed vs created. Record Health Check Name: Example_Contacts_Cover_Open_Cases. Result on Acme Corporation: Warning. 4 Cases closed and 16 were created in the last 30 days.

FieldValue
Evaluation TypeVerify with a query
Check DescriptionThe Query check compares 30-day Case resolution throughput with intake and passes when closures meet or exceed new demand, making backlog direction visible at the Account level.
Applies ToAll records
Source QuerySELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND IsClosed = true AND ClosedDate = LAST_N_DAYS:30
How To Read Query ResultsOne row or aggregate
Comparison OperatorAt least
Expected Value Comes FromComparison query
Comparison QuerySELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND CreatedDate = LAST_N_DAYS:30
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityWarning
Message When FailedFewer Cases were closed than created for {!record.Name fallback="this Account"} during the last 30 days, which can indicate a growing service backlog.
Fix MessageFor {!record.Name fallback="this Account"}, review Case demand, ownership, and aging. Address the backlog; do not close Cases merely to pass.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview Cases for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Cases/view

These Checks compare two counts (140 to 200), two totals (210), or two lists (220 to 240).

Check 140: Every won Opportunity has an Amount

Section titled “Check 140: Every won Opportunity has an Amount”

Label: Example: Won Opportunity Amounts. Record Health Check Name: Example_Parent_Cities_Require_Data. Result on Acme Corporation: Warning. The won Opportunity has no Amount.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check compares won Opportunities with won Opportunities whose Amount is not blank. It passes when both counts match.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsWon = true
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no won Opportunity to review.
Source QuerySELECT COUNT() valuedDeals FROM Opportunity WHERE AccountId = {!record.Id} AND IsWon = true AND Amount != null
Source Query FieldvaluedDeals
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT COUNT() allDeals FROM Opportunity WHERE AccountId = {!record.Id} AND IsWon = true
Comparison Query FieldallDeals
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityWarning
Message When FailedOne or more won Opportunities for {!record.Name fallback="this Account"} have no Amount.
Fix MessageFor {!record.Name fallback="this Account"}, confirm the final booked value from the approved sales record, then update Amount. Do not estimate or invent a value.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview historical deals for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Label: Example: Proposal Next Steps. Record Health Check Name: Example_Contact_Vs_Open_Opp_Count. Result on Acme Corporation: Warning. The proposal has no Next Step.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check counts proposals with Next Step and all proposals. It passes when the counts match. This checks that Next Step has text, not whether the action has been agreed.
Applies ToAll records
Source QuerySELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote' AND NextStep != null
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote'
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityWarning
Message When FailedOne or more proposals for {!record.Name fallback="this Account"} have no Next Step.
Fix MessageFor {!record.Name fallback="this Account"}, confirm the next customer-owned or seller-owned action, accountable party, and timing before updating Next Step. Do not enter generic filler text.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview next steps for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 160: Every proposal has a Primary Campaign Source

Section titled “Check 160: Every proposal has a Primary Campaign Source”

Label: Example: Proposal Campaigns. Record Health Check Name: Example_Guide_Open_Deals_Have_Contacts. Result on Acme Corporation: Failed. The proposal has no Primary Campaign Source.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check counts proposals with a Primary Campaign Source and all proposals. It passes when the counts match. This checks the Campaign link, not the accuracy of attribution.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no open Opportunities, so campaign attribution does not apply.
Source QuerySELECT COUNT() coveredDeals FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote' AND CampaignId != null
Source Query FieldcoveredDeals
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote'
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityCritical
Message When FailedOne or more proposal-stage Opportunities for {!record.Name fallback="this Account"} have lost acquisition attribution.
Fix MessageFor {!record.Name fallback="this Account"}, verify marketing attribution and add the legitimate Primary Campaign Source. Do not invent a Campaign association.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview campaign sources for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 170: Open Opportunity Close Dates are in range

Section titled “Check 170: Open Opportunity Close Dates are in range”

Label: Example: Open Opportunity Close Dates. Record Health Check Name: Example_Distinct_Cities_Vs_Contacts. Result on Acme Corporation: Info. Only 1 of the 2 open Opportunities closes within the next 180 days.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check passes when every open Opportunity has a Close Date from today through the next 180 days, detecting both stale dates and dates outside the operating forecast horizon.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no open Opportunities, so close-date coverage does not apply.
Source QuerySELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false AND CloseDate = NEXT_N_DAYS:180
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityInfo
Message When FailedOne or more open Opportunities for {!record.Name fallback="this Account"} have a past Close Date or sit beyond the 180-day planning horizon.
Fix MessageFor {!record.Name fallback="this Account"}, reconfirm customer timing and update only Close Dates supported by the current plan.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview Close Dates for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 180: Every open Opportunity has a Contact Role

Section titled “Check 180: Every open Opportunity has a Contact Role”

Label: Example: Open Opportunity Contact Roles. Record Health Check Name: Example_Oldest_Contact_City_Matches. Result on Acme Corporation: Failed. Only 1 of the 2 open Opportunities has a Contact Role.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check compares open Opportunities with open Opportunities represented by at least one Opportunity Contact Role. It passes when both counts match.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no open Opportunity to review.
Source QuerySELECT COUNT_DISTINCT(OpportunityId) coveredDeals FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false
Source Query FieldcoveredDeals
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT COUNT() allDeals FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Comparison Query FieldallDeals
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityCritical
Message When FailedOne or more open Opportunities for {!record.Name fallback="this Account"} have no Opportunity Contact Role.
Fix MessageFor {!record.Name fallback="this Account"}, confirm the customer participants for each open Opportunity and add the correct Opportunity Contact Roles. Do not add placeholder Contacts.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview Contact Roles for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 190: Every won Opportunity has a primary Contact

Section titled “Check 190: Every won Opportunity has a primary Contact”

Label: Example: Won Opportunity primary roles. Record Health Check Name: Example_Earliest_Vs_Latest_Close. Result on Acme Corporation: Warning. The won Opportunity has no primary Contact Role.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check passes when every won Opportunity retains a primary Contact Role, preserving buyer history for implementation handoff, renewal planning, and expansion.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsWon = true
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no won Opportunities, so historical buyer attribution does not apply.
Source QuerySELECT COUNT_DISTINCT(OpportunityId) coveredDeals FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsWon = true AND IsPrimary = true
Source Query FieldcoveredDeals
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT COUNT() allDeals FROM Opportunity WHERE AccountId = {!record.Id} AND IsWon = true
Comparison Query FieldallDeals
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatNumber
Failure SeverityWarning
Message When FailedOne or more won Opportunities for {!record.Name fallback="this Account"} have no retained primary customer Contact.
Fix MessageFor {!record.Name fallback="this Account"}, identify the buyer who played the primary role and mark that Contact Role as primary. Do not add a placeholder Contact.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview won deals for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 200: New pipeline value covers recently lost value

Section titled “Check 200: New pipeline value covers recently lost value”

Label: Example: New pipeline vs lost value. Record Health Check Name: Example_Open_Pipeline_Covers_Revenue. Result on Acme Corporation: Failed. New open pipeline is $600,000; value lost in the last 90 days is $760,000.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check compares Amount from open Opportunities created in the last 90 days with Amount from Opportunities closed lost in the same period. It passes when new pipeline value equals or exceeds lost value.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = true AND IsWon = false AND CloseDate = LAST_N_DAYS:90 AND Amount != null
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no closed-lost Opportunity in the last 90 days, so replenishment pressure does not apply.
Source QuerySELECT SUM(Amount) newPipeline FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false AND CreatedDate = LAST_N_DAYS:90 AND Amount != null
Source Query FieldnewPipeline
How To Read Query ResultsOne row or aggregate
Comparison OperatorAt least
Comparison QuerySELECT SUM(Amount) recentLosses FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = true AND IsWon = false AND CloseDate = LAST_N_DAYS:90 AND Amount != null
Comparison Query FieldrecentLosses
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatCurrency
Failure SeverityCritical
Message When FailedNew open pipeline value has not replaced recently lost Opportunity value for {!record.Name fallback="this Account"}.
Fix MessageFor {!record.Name fallback="this Account"}, inspect loss reasons and the account plan, then create only qualified replacement Opportunities supported by a real customer initiative.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview pipeline for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 210: Total proposal Amount matches total Product value

Section titled “Check 210: Total proposal Amount matches total Product value”

Label: Example: Proposal and Product totals. Record Health Check Name: Example_Average_Deal_Vs_Largest. Result on Acme Corporation: Unable to Check. The proposal has no Opportunity Products to total.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check sums proposal Amounts and Product Total Prices across the Account. It passes when the totals match. Differences between individual proposals can cancel out; this is an Account-level reconciliation.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote' AND Amount != null
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no proposal-stage Opportunity with an Amount to compare.
Source QuerySELECT SUM(Amount) proposalAmount FROM Opportunity WHERE AccountId = {!record.Id} AND StageName = 'Proposal/Price Quote' AND Amount != null
Source Query FieldproposalAmount
How To Read Query ResultsOne row or aggregate
Comparison OperatorEqual to
Comparison QuerySELECT SUM(TotalPrice) productTotal FROM OpportunityLineItem WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.StageName = 'Proposal/Price Quote'
Comparison Query FieldproductTotal
If Query Finds No RecordsUnable to evaluate
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatCurrency
Failure SeverityWarning
Message When FailedProposal Amount does not match the Opportunity Product total for {!record.Name fallback="this Account"}.
Fix MessageFor {!record.Name fallback="this Account"}, review the proposal Opportunity and its Opportunity Products. Correct the Amount or Product quantities and prices only from approved commercial terms.
Message When Unable To Evaluate{!record.Name fallback="This Account"} has no Product total to compare with proposal Amount. Add Opportunity Products to test the comparison.
Action LabelReview proposal Products for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/related/Opportunities/view

Check 220: Sales and service share a Contact name

Section titled “Check 220: Sales and service share a Contact name”

Label: Example: Sales and service Contacts. Record Health Check Name: Example_Contact_Cities_Overlap_Parent. Result on Acme Corporation: Warning. No Contact on an open Case is also a Contact Role on an open Opportunity.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check compares Contact names on open Cases with names on open Opportunities. It passes when the lists overlap. Matching names do not prove Contact identity; use IDs when distinct people can share a name.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND ContactId != null
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no open Case with a named Contact, so sales-service overlap does not apply.
Source QuerySELECT Contact.Name FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND ContactId != null
Source Query FieldContact.Name
How To Read Query ResultsCompare as lists
Comparison OperatorLists overlap
Comparison QuerySELECT Contact.Name FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false AND ContactId != null
Comparison Query FieldContact.Name
If Query Finds No RecordsSkip
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatText
Failure SeverityWarning
Message When FailedNo customer Contact currently connects open service work and open sales work for {!record.Name fallback="this Account"}.
Fix MessageFor {!record.Name fallback="this Account"}, confirm whether sales and service should share a stakeholder. Adapt this example when teams intentionally work with different people.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview stakeholders for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/view

Check 230: Sales Contact names cover priority Case Contacts

Section titled “Check 230: Sales Contact names cover priority Case Contacts”

Label: Example: Priority Case Contact coverage. Record Health Check Name: Example_Parent_Covers_Contact_Cities. Result on Acme Corporation: Warning. The Contacts on High-priority Cases are not Contact Roles on open Opportunities.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check compares Contact names on open Opportunities with names on high-priority open Cases. It passes when the first list contains every name in the second. Shared names can represent different Contacts.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND Priority = 'High' AND ContactId != null
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no high-priority open Case with a Contact, so this handoff check does not apply.
Source QuerySELECT Contact.Name FROM OpportunityContactRole WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false AND ContactId != null
Source Query FieldContact.Name
How To Read Query ResultsCompare as lists
Comparison OperatorLists contain all
Comparison QuerySELECT Contact.Name FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND Priority = 'High' AND ContactId != null
Comparison Query FieldContact.Name
If Query Finds No RecordsSkip
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatText
Failure SeverityWarning
Message When FailedOne or more Contacts on high-priority open Cases for {!record.Name fallback="this Account"} are missing from its open-deal stakeholder map.
Fix MessageFor {!record.Name fallback="this Account"}, review whether sales should know priority service Contacts. Add legitimate roles or adapt the handoff rule.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview handoffs for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/view

Check 240: Open Opportunity names match those with Products

Section titled “Check 240: Open Opportunity names match those with Products”

Label: Example: Opportunity Product coverage. Record Health Check Name: Example_Contact_Cities_Exact_Parent. Result on Acme Corporation: Warning. Neither open Opportunity has Products, so the two name lists do not match.

FieldValue
Evaluation TypeCompare two queries
Check DescriptionThe Compare Two Queries check compares open Opportunity names with names represented by Products. It passes when the lists match exactly. Duplicate names can hide missing Product coverage; use IDs when names are not unique.
Applies ToWhen a count query matches
Applies When (Count Query)SELECT COUNT() FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Count Must BeGreater than
Count Value0
Message When Not Applicable{!record.Name fallback="This Account"} has no open Opportunities, so product coverage does not apply.
Source QuerySELECT Name FROM Opportunity WHERE AccountId = {!record.Id} AND IsClosed = false
Source Query FieldName
How To Read Query ResultsCompare as lists
Comparison OperatorLists match exactly
Comparison QuerySELECT Opportunity.Name FROM OpportunityLineItem WHERE Opportunity.AccountId = {!record.Id} AND Opportunity.IsClosed = false
Comparison Query FieldOpportunity.Name
If Query Finds No RecordsFail
If Field Value Is EmptyIgnore the record
Display: Found Text{!rhcResult.foundValue}
Display: Expected Text{!rhcResult.expectedValue}
Display: Value FormatText
Failure SeverityWarning
Message When FailedOne or more open Opportunities on {!record.Name fallback="this Account"} have no Opportunity Product.
Fix MessageFor {!record.Name fallback="this Account"}, confirm whether sales uses Opportunity Products. Add verified products and prices, or deactivate this example.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelReview products for {!record.Name fallback="Account"}
Action URL/lightning/r/Account/{!record.Id}/view

This Check runs AccountHasRecentActivityCheck, the Apex class that installs with the package. The class adds its own message, fix text, and Open account link on the card, which replace the Message When Failed, Fix Message, and action fields shown here; those fields remain the fallback. See Check that an Account has recent activity.

Check 250: Account activity meets the 60-day cadence

Section titled “Check 250: Account activity meets the 60-day cadence”

Label: Example: Verified engagement cadence. Record Health Check Name: Example_Guide_Recent_Activity. Result on Acme Corporation: Pass. Two Tasks were completed on Acme in the last 60 days, which meets the minimum of two.

FieldValue
Evaluation TypeVerify with Apex
Check DescriptionThe 2.0.10 Apex example declares typed parameters, counts completed Tasks and Events during the last 60 days, and returns typed evidence and safe display guidance. It passes when at least two completed activities are recorded.
Applies ToAll records
Apex ClassAccountHasRecentActivityCheck
Apex Parameters (JSON){"daysBack": 60, "minimumActivities": 2}
Display: Value FormatText
Failure SeverityWarning
Message When FailedFewer than two completed activities are recorded for {!record.Name fallback="this Account"} in the last 60 days.
Fix MessageFor {!record.Name fallback="this Account"}, review completed Tasks and Events. {!link label="Open this Account" href="/lightning/r/Account/{!record.Id}/view"} to record genuine completed activity, or change the example cadence to the approved standard.
Message When Unable To Evaluate{!rhcCheck.checkTitle fallback="This check"} could not run for {!record.Name fallback="this Account"}. Review the check setup and the running user's access, then try again.
Action LabelLog an activity for {!record.Name fallback="Account"}
Action URL/lightning/r/Task/new?defaultFieldValues=WhatId={!record.Id}

This installed Check uses /lightning/r/Task/new. Salesforce’s create pattern is /lightning/o/Task/new; when you copy this Check, use /lightning/o/Task/new?defaultFieldValues=WhatId={!record.Id} and test the link.

Test each Check with the Salesforce access of the people who will use it.

Result to proveHow to test it
PassUse an Account that meets the requirement and confirm the row shows Pass.
A failureChange one value so the requirement is not met. Confirm the label, message, fix message, and link.
SkippedFor a Check with Applies To set, use an Account outside its scope and confirm the not-applicable message.
Unable to CheckIn a sandbox, remove the test user’s access to one field the Check reads, run it, and restore the access afterward.
SharingKeep one related record hidden from the test user and confirm the result counts only records the user can see.

Before you copy a Check, answer the question for its order number.

OrderSetting or requirement to consider
10Which Type values describe your Account relationships? This example accepts any populated Type, including values added by your org.
20Is either Phone or Website sufficient? This example checks presence, so decide separately whether format or reachability validation is needed.
30Does centralized billing require the child address to match its parent? Define how to handle legitimate address differences; a missing parent skips.
40Is one simultaneous high-priority Case the approved capacity, and should exceeding it be Critical for every Account segment?
50Does the sales organization use Forecast Category Commit, and is one Commit deal per Account a useful requirement?
60Should an Account with no open Cases Pass or Skip, and is Contact Name mandatory for every Case type and channel?
70Is Case Description the approved place for customer impact, or does the org use another standard or custom Case field?
80Confirm that all open Opportunities are user-owned and that Owner Active is readable by intended users. Define the approved transfer process for inactive owners.
90Confirm the proposal Stage value, $25,000 floor, currency behavior, and whether blank Amount should be treated the same as an Amount below the floor.
100Is one Decision Maker anywhere in open pipeline enough, or must every qualifying Opportunity have one? Confirm the exact Contact Role value.
110Is either Email or Phone sufficient, and may the intended users read both fields for every Contact Role they can see?
120Confirm the exact Technical Buyer Contact Role value and which Opportunity Stages require it.
130Is 30 days long enough for meaningful Account-level Case volume, and should the comparison use all Cases or only selected Case types?
140Must every won Opportunity have Amount, and how should migrated or confidential historical deals be handled?
150Does Next Step contain the agreed customer action, or does the sales process store mutual actions elsewhere?
160Does the organization consistently maintain Primary Campaign Source before proposal Stage, including Opportunities created without a Campaign?
170Is 180 days the approved planning horizon for every sales motion, and should overdue Close Dates be reported separately from dates beyond the horizon?
180Must every open Opportunity have a Contact Role, or only Opportunities at selected Stages?
190Must every won Opportunity retain a primary Contact Role, including renewals, channel deals, and migrated history?
200Confirm the 90-day period, currency handling, which open Stages count as replacement pipeline, and whether Amount is the approved measure of replaced value.
210Is Opportunity Amount expected to equal Opportunity Product Total Price, or can services, taxes, adjustments, or manual pricing create approved differences?
220Which Account segments require one Contact to connect open sales and service work? If separate Contacts are normal, deactivate or narrow this Check.
230Must every priority service Contact appear on an open Opportunity, or is sales awareness recorded through Account Teams, notes, or another Salesforce relationship?
240Does the sales process require Opportunity Products on every open Opportunity or only after a selected Stage?
250Which Task and Event types count toward the cadence? The class counts closed Tasks and Events related to the Account, including future Events, but does not judge whether an activity was meaningful.

Also identify every Flow, Apex class, report, integration, or saved reference that uses an existing Check Qualified API Name before changing an API name.