# CRM and pipeline audit checklist

> Work through it with a CRM export and a few hours. Each item says what to look for and what it tells you. Mark what you find, then use the last section to decide what to fix first.

Free to copy. From NeuroGTM, a fractional RevOps practice in Denver. Page: https://neurogtm.com/templates/crm-pipeline-audit-checklist

## Stages

- [ ] **Each stage has a written definition and an exit point.** If not, reps are guessing, and every report built on stages is a guess too.
- [ ] **Deals sit in each stage for a believable time.** Deals parked in one stage for far longer than the rest usually mean the stage is a holding pen.
- [ ] **Lost deals have a reason recorded.** Without it, you can't tell product problems from sales problems.

## Open deals

- [ ] **Deals with no activity in a long time.** List them. Most are dead and are inflating the pipeline.
- [ ] **Close dates that have moved more than once.** Each move is a signal the deal is weaker than its stage suggests.
- [ ] **Deals with no amount, no next step or no contact.** These can't be forecast.

## Records and fields

- [ ] **Fields that are never filled in.** Remove them, or fill them automatically from calls and email.
- [ ] **Fields filled with the default value.** Reps are clicking past them. Treat the data as missing.
- [ ] **Duplicate contacts and companies.** They split activity history and break reporting.
- [ ] **Contacts missing job title or company.** Routing and scoring can't work without them.

## How the team uses it

- [ ] **Ask reps where they keep notes.** If it's a notebook, an inbox or a spreadsheet, the CRM is missing the best information.
- [ ] **Ask when they update the CRM.** End of day, from memory, means the details are already fading.
- [ ] **Check what lives outside the CRM.** Side spreadsheets usually exist because a report someone needs isn't in the CRM.

## Connections

- [ ] **Call recorder connected to the CRM.** If not, the richest record of every deal never reaches it.
- [ ] **Email and calendar logging on.** Activity data depends on it.
- [ ] **Automations that fail without anyone noticing.** Check each one still runs, especially after fields or stages were renamed.

## Reporting

- [ ] **The reports leadership reads, and where each number comes from.**
- [ ] **Numbers that differ by source.** If the CRM, finance and the board deck disagree, settle the definition before fixing the data.

## What to fix first

1. Stage definitions, because every other number depends on them.
2. Dead deals, because they distort the forecast today.
3. Call and email capture, because it stops the problem growing.
4. Unused fields and duplicates, last, once the inflow is fixed.

Related: [How do you audit a sales pipeline you inherited?](/blog/audit-inherited-sales-pipeline) and [How do you fix CRM data quality with AI?](/blog/crm-data-quality-ai-agents)
