Skip to content

Monthly Litify Deep Dive

Cadence: Monthly, 4th week Duration: ~1 hour Trigger: "Run the Litify deep dive" Deploys changes: May propose Salesforce config changes (with approval)

Purpose

A thorough monthly review of the Salesforce/Litify environment: reports, packages, knowledge center, forms, and data quality. The weekly Wednesday check catches operational issues. This monthly dive catches structural debt.

Audit Steps

1. Report Inventory Refresh

  • Pull all Salesforce reports with sf CLI
  • Count: total reports, reports by folder, reports by owner
  • Last-run date for each report
  • Flag reports not run in 90+ days (candidates for archive)
  • Flag duplicate reports (same name or same query in different folders)
  • Compare to the April 4 baseline (310 stale reports triaged)

2. Package Deprecation Check

  • List all installed packages with versions
  • Check each against Litify's current supported packages
  • Flag packages marked for deprecation
  • Flag packages not used by any active configuration
  • Compare to the April 7 deprecation audit

3. Knowledge Center Content Update

  • Review the Litify Knowledge Center articles
  • Are they current with the firm's processes?
  • Do they reference the correct forms, fields, and workflows?
  • Any articles that need creation for new processes?

4. Form Parity Check

  • Compare current intake forms against the baseline
  • Verify all required fields are present
  • Check form routing rules (which form goes to which queue)
  • Verify web-to-lead integration is passing all fields correctly
  • Compare to the April 14 form parity trace

5. Data Quality Sweep

Deep scan for data issues: - Matters missing case type (affects reporting) - Contacts without email or phone (affects communication) - Duplicate contacts (potential merge candidates) - Intakes stuck in limbo (created but never converted or rejected) - Custom fields with null values that should be populated

6. Automation Health

  • Review all Salesforce flows, triggers, and process builders
  • Any that are erroring?
  • Any that are deprecated (process builders → flow migration)?
  • Check the RingSense merge trigger status

Expected Output

A categorized action list: - Fix now: broken automations, erroring flows, stale packages - Clean up: duplicate reports, unused packages, orphaned records - Improve: form updates, knowledge center articles, data quality fills