Automation Sprawl Audit (QA)

Automation Sprawl Audit (QA)

1. 01

   Pull a complete inventory of live workflows from every platform the client pays for

   Export the active automation list from each connected tool, including the ones the client's marketing team bought on a card without telling anyone. Overlapping touchpoints and conflicting messages usually surface in this first pass.

2. 02

   Tag each workflow with an owner, a business process, and a last-edited date

   Anything without a named owner goes on the orphan list. Workflows untouched for 180 days are candidates for retirement, not maintenance.

3. 03

   Trace every workflow that writes to the client CRM and flag duplicate write paths

   Two automations updating the same contact field is the most common source of bad inputs propagating at scale. Confirm which one wins before the next send.

4. 04

   Test each workflow against a malformed input record

   Push a record with a missing email, a null phone, and a stale pipeline stage through the path. Record where it fails silently versus where it errors loudly.

5. 05

   Score each workflow on volume, error cost, and exception coverage

   A 40-run-per-day workflow that touches invoices outranks a 4,000-run workflow that only tags leads. Rank by cost of a wrong output, not by run count.

6. 06

   Confirm monitoring exists for every workflow above the error-cost threshold

   If nobody gets an alert when a run fails, the workflow is unmonitored regardless of what the platform dashboard shows. Name the person who receives the alert.

7. 07

   Deliver a retire, repair, or retain verdict per workflow with a remediation window

   Group the findings into three buckets and attach a date to each repair. Present the orphan list to the client as a decision they own, not a cleanup you absorbed.