Org Health Check: sample report
This is what you receive at the end of a Health Check. The company below is fictional, but the findings are typical of what we see in Salesforce orgs that have grown for several years.
What is an Org Health Check?
A fixed-scope, fixed-price review of your Salesforce org: automations, Apex and triggers, security and access, integrations and technical debt. You get a written report like this one and a walkthrough call, with no commitment beyond the report.
See the offer →Summary
Where the org stands
The org is secure and its integrations are reliable. The main risks are in legacy automation and trigger design, which slow down saves today and will cause errors as data volumes grow.
Findings
What we found, and what to do
Automations
ConsolidateFinding. 11 active Workflow Rules and 3 Process Builders on Opportunity and Case run alongside 6 record-triggered flows.
Why it matters. Workflow Rules and Process Builders are no longer supported by Salesforce, and mixing three automation tools makes the order of execution hard to predict.
Recommendation. Migrate the legacy rules to record-triggered flows: before-save flows for field updates, after-save flows for actions, with clear entry conditions and a defined order. Retire the old rules once tested.
Apex and triggers
RefactorFinding. Account has two triggers with logic written directly in the trigger body. One of them runs a SOQL query inside a loop. Org-wide test coverage is 78%, but several tests have no assertions.
Why it matters. Two triggers on the same object run in an unpredictable order. The query inside the loop will hit the “Too many SOQL queries: 101” limit during bulk loads or integrations. Tests without assertions pass without proving anything.
Recommendation. Move to one trigger per object that delegates to a handler class, query outside loops using collections, and add meaningful assertions to the existing tests.
Security and access
HealthyFinding. Access is managed through permission sets and a private sharing model for accounts. Two non-admin users have “Modify All Data”.
Why it matters. The model is sound. “Modify All Data” lets those two users change any record, bypassing sharing rules.
Recommendation. Remove “Modify All Data” from the two users and grant only the specific permissions they need.
Integrations
HealthyFinding. The ERP integration uses named credentials and logs every call. Errors are recorded, but nobody is alerted when a call fails.
Why it matters. Failures are only noticed when a user reports missing data, sometimes days later.
Recommendation. Add an alert when an integration call fails, sent to the admin team, with a daily summary of errors.
Technical debt
ModerateFinding. About 140 custom fields on Account have stayed empty for over a year. Several page layouts and reports are no longer used.
Why it matters. Unused fields and layouts clutter screens, slow down admin work and make every change riskier.
Recommendation. Confirm with each team which fields are still needed, archive the data if required, then remove the rest in stages.
Prioritized roadmap
Quick wins first, then the bigger fixes
Weeks 1–2 · Quick wins
Remove “Modify All Data” from the two users, move the query out of the loop, and add failure alerts on the ERP integration.
Weeks 3–6 · Core fixes
Refactor Account triggers into a handler pattern and migrate Workflow Rules and Process Builders to flows.
Weeks 7–10 · Cleanup
Strengthen test assertions and remove unused fields, layouts and reports in stages.
Want this picture for your own org?
A Health Check is fixed in scope and price, with a written report and a walkthrough call.
Sample for illustration only. Nordvale Distribution is fictional. Findings, priorities and timelines in a real Health Check depend on your org and are confirmed in the proposal.