When to Perform a Health Check
- When the system has been in use for a year or more and the original implementation is not well-organized.
- Before a significant change — a new phase, integration, or expansion of use.
- When user adoption is low and teams are 'bypassing' the system.
- Before changing integrators or introducing a new partner.
- When it's unclear who owns specific areas of the system.
What is Checked in Practice
- Data model and quality of central records.
- Permissions model and information sharing.
- Automations, Flow, validation rules, and Apex.
- Active integrations, errors, and logs.
- Usage of Storage, API, and other quotas.
- Adoption metrics, login logs, and unused reports.
- Documentation debt — what is and isn't documented.
Expected Output
A useful Health Check report includes:
- Summary of findings classified by severity.
- Quick Wins that can be implemented in the short term.
- Architectural gaps requiring deeper planning.
- Recommendations for the roadmap for the coming quarters.
What to Do After the Check
The check alone does not improve a system. Its value comes from an action plan — Quick Wins first, followed by focused projects to reduce technical debt and improve adoption.
Frequently Asked Questions
A standard check for a medium-sized organization lasts between two weeks and a month, depending on system complexity and stakeholder availability.