Tool Guide · Org Assessment

WHAT A SALESFORCE ORG ASSESSMENT COVERS BEFORE CLEANUP OR HANDOFF.

An org assessment is the structured review that comes before decisions. Before cleanup, before a consultant engagement, before an admin handoff — you need a documented baseline of what the org contains and what risks exist. KeelCadence produces first-pass discovery workbooks for four of those areas.

Read-only diagnostics · Review-ready workbooks · No package install · No Connected App

01 — Why an Assessment First

DECISIONS WITHOUT A BASELINE ARE GUESSES.

The most common failure mode in Salesforce change work is not a technical mistake — it is a missing-context mistake. A cleanup project removes a field that was quietly being written to by an integration. A permission change removes access that a small team was relying on. An automation change triggers a conflict with a validation rule that nobody remembered existed.

A structured org assessment before the change work reduces those risks. It does not eliminate them — metadata review has inherent limits — but it changes the conversation from "we assumed it was unused" to "we reviewed the available signals and documented our rationale."

An assessment is not permission to proceed. It is the information you need to decide whether proceeding is the right move.

02 — When to Run It

RUN THE ASSESSMENT BEFORE THE WORK THAT DEPENDS ON IT.

An org assessment earns its value when it happens before a decision is locked in — not as a post-mortem after something breaks. These are the moments where a documented baseline changes the outcome.

When a baseline pays off

  • Before cleanup — so a field, automation, or permission is reviewed against multiple signals before anyone marks it as a removal candidate.
  • Before a migration or data import — so required fields, restricted picklists, and validation rules are mapped before records start failing on load.
  • Before automation changes — so you know which Flows, Apex, and validation rules fire on the objects you are about to touch.
  • Before inheriting an org — so a new admin or owner starts from a documented picture instead of reverse-engineering undocumented config.
  • Before a consultant engagement — so the discovery phase starts from structured evidence rather than billable hours spent rebuilding context.
  • Before AI-assisted change work — so the quality of the org going in is understood, since automated output is only as reliable as the org it reasons about.
03 — What to Review

WHAT A SALESFORCE ORG ASSESSMENT SHOULD REVIEW.

A thorough assessment is broader than any single workbook. Use this as a grouped checklist of review areas — work through the ones that match your scope, and document what you find in each before you change anything.

Data Model

  • Custom and standard fields, and their fill rates
  • Objects and their relationships
  • Record types and page layout assignments
  • Picklists and restricted picklist values

Access & Security

  • Profiles, permission sets, and permission set groups
  • Object permissions and field-level security (FLS)
  • Integration users and their effective access
  • External and community user access patterns

Automation

  • Active and inactive Flows, and process type
  • Apex classes, triggers, and test coverage signals
  • Validation rules and approval processes
  • Legacy workflow rules and process builder

Stale Metadata & Pre-Change Risk

  • Fields with no usage signal across layouts and reports
  • Unreferenced automations and deprecated record types
  • Required fields and validation rules that block imports
  • Automation that fires on save during bulk changes

KeelCadence workbooks surface read-only diagnostic signals for the field, permission, automation, and record-readiness areas above. Business-context, integration mapping, and governance decisions still require human review.

04 — What This Helps You Review

FOUR DIAGNOSTIC AREAS FOR A FIRST-PASS ORG ASSESSMENT.

What this helps you review

  • Field inventory and fill rates — which fields exist, which are populated, which are hidden but contain data
  • Permission and FLS structure — object access, field-level security exposure, and permission set sprawl
  • Automation inventory — Flows, Apex, validation rules, approval processes, and legacy automation
  • Selected-object record readiness — required fields, restricted picklists, and record type configuration
  • First-pass cleanup candidates with multi-signal context rather than single-signal guesses

Relevant Workbook

Field & Object Audit

The starting point for most org assessments — field inventory, fill rates, hidden populated fields, layout coverage, and FLS visibility across selected objects.

05 — The Other Tools

RUN MULTIPLE WORKBOOKS FOR A BROADER ASSESSMENT.

A field-level view gives you the data model picture. A permission review adds the access layer. An automation inventory adds the change-risk layer. An impact awareness check adds the object-readiness layer for imports and UAT. Each workbook is independent — run as many as your assessment scope requires.

Permission & FLS Audit

Object permissions, FLS exposure, and permission set sprawl.

Learn more →

Automation Inventory

Flows, Apex, validation rules, and approval processes.

Learn more →

Automation Impact Awareness

Required fields, restricted picklists, and record-readiness.

Learn more →
06 — Manual vs. Workbook

MANUAL ORG REVIEW VS. DIAGNOSTIC WORKBOOK REVIEW.

Both approaches end in human judgment. The difference is how long it takes to reach a documented baseline and how consistent that baseline is across objects and runs.

DimensionManual org reviewDiagnostic workbook review
Time to baselineHours to days of clicking through setup, screen by screenA read-only session produces a structured XLSX workbook
ConsistencyVaries by reviewer and how tired they are by object 40Same signals captured the same way across every object
CoverageEasy to miss hidden populated fields or inactive automationSurfaces fill rates, FLS, and inventory in one pass
OutputNotes and screenshots that go stale quicklyA shareable workbook you can sort, filter, and hand off
RepeatabilityRe-running means starting the clicking over againRe-run any time to compare against the prior baseline
What it cannot doBoth still require human judgment on business contextBoth stop at evidence — neither writes changes to Salesforce

A workbook does not replace the reviewer — it removes the manual collection step so the reviewer spends their time on judgment instead of data gathering.

07 — What This Does Not Include

WHAT A FIRST-PASS ASSESSMENT DOES NOT COVER.

Outside scope of first-pass diagnostics

  • Business-context review — whether existing configuration still matches current process needs
  • Integration and connected app dependency mapping
  • Data quality assessment — duplicate records, stale data, referential integrity
  • Compliance documentation and sign-off
  • Full runtime dependency analysis requiring code review or execution tracing
08 — Related Resources

RELATED GUIDES.

FAQ

FREQUENTLY ASKED QUESTIONS.

What is a Salesforce org assessment?
A Salesforce org assessment is a structured review of an org's configuration, data model, permissions, and automation — typically conducted before cleanup work, a consultant engagement, an admin handoff, or a significant change project. The goal is to establish a documented baseline of what exists before making decisions.
What should a Salesforce org assessment cover?
A first-pass org assessment should cover field inventory and usage, permission and FLS structure, automation inventory across Flows, Apex, and validation rules, and selected-object record readiness. Deeper assessments also cover technical debt, documentation gaps, integration dependencies, and governance history.
When should you run a Salesforce org assessment?
When inheriting an org with unclear ownership or missing documentation. Before a cleanup, migration, or automation change project. Before a consultant engagement — to give the consultant a structured starting point. Before an AI-assisted development project where org quality affects output quality. Essentially: any time you need to make confident decisions about a Salesforce org you do not fully understand.
Does KeelCadence produce a complete Salesforce org assessment?
KeelCadence produces diagnostic workbooks for four focused areas: fields and objects, permissions and FLS, automation inventory, and selected-object record readiness. These are first-pass discovery artifacts — structured starting points for the review, not a complete assessment of every org component. A full org assessment may also require manual review of integrations, governance, and business-context decisions that metadata alone cannot surface.
What is the difference between an org assessment and an org audit?
The terms are often used interchangeably. Broadly, an assessment tends to focus on scope and readiness — what does this org contain and is it ready for the next phase of work. An audit tends to focus on compliance and accuracy — does the current state match what is documented or expected. KeelCadence workbooks serve both purposes as first-pass discovery artifacts.
Do I need to install a Salesforce package for an org assessment with KeelCadence?
No. KeelCadence does not require a package install, Connected App, or persistent OAuth token. The diagnostic runs read-only for the session and does not export customer record data.
Start Your Assessment

GET A STRUCTURED ORG DIAGNOSTIC BEFORE PLANNING CHANGE WORK.

KeelCadence Field & Object Audit is the first diagnostic for most org assessments — field inventory, fill rates, cleanup candidates, and FLS visibility in a review-ready XLSX workbook.

Opens audit.keelcadence.com. Best run from desktop, since the diagnostic uses your active Salesforce browser session. On mobile, view the sample workbook or save this page for later.

Read-only · No package install · No Connected App setup · No Salesforce writes

KeelCadence uses session cookies and Google Analytics 4 for site usage insights. GA4 does not receive Salesforce credentials, Org IDs, Report IDs, or payment data. You can opt out for this browser.