Home / Org Health Check / Sample report

Sample report. Brightwater Supply Co. is a fictional company, and all figures below are illustrative. This shows the format and depth of a real Cloud Zip Health Check.

// org health check report

Brightwater Supply Co. Org Health Check

Salesforce Enterprise Edition · Sales Cloud and Service Cloud · 85 licensed users

// 1. executive summary

The short version

Brightwater's org is fundamentally sound and supports the business well, but years of growth have left real risks. The biggest are too much admin-level access, heavy reliance on retired automation, and code that is harder to deploy safely than it should be.

None of these issues requires a rebuild. The roadmap below addresses the highest risks in the first two weeks, mostly with small changes.

64/ 100

Overall health score

3Critical

5High

4Medium

// 2. scorecard

Health by area

Each area is scored from 0 to 100. Below 60 needs attention soon; 75 and above is healthy.

Security & access

Too many users hold admin-level permissions; integration access is shared with a named user.

Automation

Heavy reliance on retired Workflow Rules and Process Builders, with overlapping automation on Account.

Apex & code quality

Coverage meets the minimum, but many tests don't verify behavior; some limit and deployment risks.

Data quality

Significant duplicate Accounts; duplicate rules exist but are inactive.

Configuration & tech debt

Many unused fields and dormant users add clutter and cost.

Performance & limits

Generally healthy; one overloaded page layout slows down the most-used screen.

// 3. findings

Detailed findings

Every finding explains what we found, why it matters to the business, and what we recommend. Effort is an estimate: small is under a day, medium is a few days, large is one to several weeks.

CriticalC1SecurityEffort: Small

14 users can modify all data

What we found: 14 users have the "Modify All Data" permission through their profiles. Only 3 of them are administrators.
Why it matters: Any of these users can edit or delete any record in the org, bypassing sharing rules. A single mistake, or a compromised login, could affect every record.
Recommendation: Remove the permission from non-admin profiles. Grant specific access through permission sets instead.

CriticalC2AutomationEffort: Large

23 Workflow Rules and 11 Process Builders still active

What we found: 34 retired automations are active across Account, Opportunity, Case and two custom objects.
Why it matters: Salesforce has retired these tools. They no longer receive fixes or support, and they make the order of automation harder to predict.
Recommendation: Migrate to Flow, consolidating to one record-triggered Flow per object where possible.

CriticalC3CodeEffort: Small

Hardcoded record IDs in 9 Apex classes

What we found: 9 classes reference specific record type and queue IDs directly in code.
Why it matters: IDs differ between sandboxes and production. This causes failures after sandbox refreshes and makes deployments risky.
Recommendation: Replace with lookups by developer name, or move the values to Custom Metadata.

HighH1SecurityEffort: Small

Integration uses a named employee's login

What we found: The marketing platform integration authenticates as a named administrator's account.
Why it matters: If that person leaves or changes their password, the integration breaks. Their account also has far more access than the integration needs.
Recommendation: Create a dedicated integration user with a minimal permission set and move the connection to it.

HighH2AutomationEffort: Medium

Overlapping automation on Account

What we found: Account has 4 Apex triggers, 2 Flows and 3 Process Builders that all run on update.
Why it matters: Automation can run in an unexpected order, causing inconsistent data. Debug logs show occasional CPU time limit errors during bulk updates.
Recommendation: Consolidate to a single trigger framework plus one record-triggered Flow, with clear ownership of each field.

HighH3CodeEffort: Medium

31% of test methods have no assertions

What we found: Overall test coverage is 81%, but 31% of test methods run code without checking the results.
Why it matters: Coverage looks healthy while bugs go undetected. Changes can break existing features without any test failing.
Recommendation: Add meaningful assertions, starting with the classes that change most often.

HighH4CodeEffort: Small

Database queries inside loops in 5 classes

What we found: 5 Apex classes run SOQL queries inside loops.
Why it matters: These work for single records but hit governor limits during data loads or bulk updates.
Recommendation: Refactor to query once outside the loop and use maps for lookups.

HighH5DataEffort: Medium

About 18% of Accounts are duplicates

What we found: Matching analysis found roughly 4,200 likely duplicates among 23,000 Accounts. Duplicate rules exist but are inactive.
Why it matters: Duplicates split activity history, inflate reports and confuse sales and service teams.
Recommendation: Activate duplicate rules to stop new duplicates, then merge existing ones in prioritized batches.

MediumM1ConfigurationEffort: Medium

212 custom fields unused for 12+ months

What we found: 212 of 640 custom fields have had no data entered in the past 12 months.
Why it matters: Unused fields clutter page layouts and reports, and slow down every future change.
Recommendation: Confirm with owners, hide from layouts, then archive and delete in stages.

MediumM2ConfigurationEffort: Small

19 active users haven't logged in for 90+ days

What we found: 19 active users have not logged in for over 90 days.
Why it matters: Each holds a paid license and remains a potential security exposure.
Recommendation: Review with managers, then deactivate or reassign the licenses.

MediumM3CodeEffort: Small

46 Apex classes on old API versions

What we found: 46 classes use API versions older than 50.0.
Why it matters: Older versions miss newer platform behavior and can behave differently from the rest of the org.
Recommendation: Update API versions in batches, running the full test suite after each batch.

MediumM4PerformanceEffort: Medium

Opportunity page layout has 140 fields

What we found: The main Opportunity layout shows 140 fields and 11 related lists.
Why it matters: It's the most-used screen in the org, and it's slow to load and hard to scan.
Recommendation: Redesign with Dynamic Forms and tabs, showing only the fields each role needs.

// 4. roadmap

Recommended roadmap

Findings grouped into phases: highest risk and lowest effort first.

Weeks 1 to 2

Phase 1: Reduce risk

C1 14 users can modify all data
C3 Hardcoded record IDs in 9 Apex classes
H1 Integration uses a named employee's login
H4 Database queries inside loops in 5 classes
M2 19 active users haven't logged in for 90+ days

Weeks 3 to 8

Phase 2: Stabilize automation

C2 23 Workflow Rules and 11 Process Builders still active
H2 Overlapping automation on Account
H3 31% of test methods have no assertions

Weeks 9 to 12

Phase 3: Clean up and improve

H5 About 18% of Accounts are duplicates
M1 212 custom fields unused for 12+ months
M3 46 Apex classes on old API versions
M4 Opportunity page layout has 140 fields

// 5. methodology

How we reviewed the org

The review was completed with read-only access. No changes were made to the org during the Health Check.

Metadata scan of objects, fields, layouts and configuration
Inventory of all automation: triggers, Flows, Workflow Rules and Process Builders
Apex review: test quality, governor limit patterns, hardcoded values, API versions
Profile, permission set and sharing analysis
Data profiling: duplicates, field usage and completeness
Login history, license usage and org limit review

Want this for your org?

Every Health Check is fixed price and read-only. Book a free call and we'll tell you what it would cover for your org.

Book a free consultation → About the Health Check