Early access opens soon — special launch offer.
Back to blog

How often should you clean your CRM? The 4-pass calendar

A vendor-neutral CRM maintenance calendar for 1 to 50 teams: weekly 10-minute pass, monthly 30, quarterly 90, annual half-day audit. By stopwatch.

Guillermo Jara

Guillermo Jara · Co-founder

/ 9 min read / Art. #06

CRM data hygiene is the recurring set of small passes a team makes over its client and deal records to keep them current, accurate, and trustworthy. For a 1 to 50 person team, the working cadence is four passes by stopwatch: a weekly 10-minute pass, a monthly 30-minute pass, a quarterly 90-minute pass, and an annual half-day audit. Anything more is theatre. Anything less is the quarterly project that turns into a five-day cleanup.

This piece is the reference. Pass by pass, with the stopwatch, the checklist, and the moment each one prevents. Vendor-neutral: the same four passes work whether your records live in Google Sheets, Pipedrive, HubSpot, Notion, Airtable, or Syncek. The CRM is where the cadence runs. The cadence itself is yours.

Most teams clean the CRM once a quarter. By the time they sit down to do it, the data has rotted enough that the cleanup takes a week. Ten minutes every Friday beats one painful afternoon every March.

What is CRM data hygiene?

CRM data hygiene is the practice of keeping client and deal records correct enough for the team to trust the system on a Tuesday morning. The CRM is the source of truth for who is a client, what is in motion with them, and who on the team owns the next action. When the data goes stale, the team starts working around the CRM in Slack DMs, in their inbox, in a personal spreadsheet, and the source of truth quietly dies.

Hygiene is a different problem from deduplication, enrichment, or auditing. Deduplication is a step inside the monthly pass. An enrichment campaign is a feature of the quarterly pass. A full audit is the annual one. Hygiene is the rhythm that holds them together.

The 14 fields a record should carry, covered in the field-design cornerstone, describe who the client is. The five stages of a pipeline, covered in the pipeline-anatomy cornerstone, describe where the deal is. Hygiene is what keeps both of those layers true over time.

The four-pass maintenance calendar

Here is the working set. One pass per row. The stopwatch is the budget you put on the calendar; the checklist is what the pass touches; the prevented moment is the thing the pass keeps from happening.

# Pass Stopwatch What it touches The moment it prevents
1 Weekly 10-minute pass 10 min Records you touched this week. Missing phone numbers, wrong stage, unassigned owner, deals nobody updated. A Tuesday meeting opens with "wait, who owns this account?"
2 Monthly 30-minute pass 30 min Drift from the last 30 days. Duplicates, stale follow-ups past their window, abandoned drafts, missing lost-reasons. A duplicate account gets two parallel proposals from two teammates.
3 Quarterly 90-minute pass 90 min Structural rot. Fields nobody fills, stages that never disqualify, dormant deals older than the quarter. The quarterly forecast pulls in 30 deals from last year that should have been closed-lost in February.
4 Annual half-day audit ~4 hours The certify-clean checkpoint. Schema review, archive vs delete decisions, owner rebalance, fiscal-year tie-out. A new hire spends week one inheriting an account list with three former owners and no recent activity.

Four passes by stopwatch. If a pass runs over its budget, the checklist is too long, not the cadence. Trim the checklist, keep the stopwatch.

The weekly 10-minute pass

The weekly pass is the cheapest insurance the CRM has. Block ten minutes at the same time every week, a Friday afternoon works for most teams, and walk through the records you touched in the last seven days.

The checklist is small on purpose:

  • Every new lead has a phone number or another reachable contact.
  • Every deal that moved has its stage updated and an owner.
  • Every account you created has a segment and a value.
  • No deal sits in "next steps" with a blank next action.
  • Any record flagged "follow up by Friday" actually got followed up.

Ten minutes is enough because the surface is small. You are only touching this week's records. Older drift waits for the monthly pass. Older rot waits for the quarter.

The prevented moment is the one that costs the team trust faster than any other. A Tuesday meeting opens with the operations lead asking "who is owning this?", and the table goes quiet. Three weeks of those and the team stops treating the CRM as the answer.

The monthly 30-minute pass

The monthly pass picks up the drift the weekly pass cannot see. Thirty minutes, last Friday of the month, the same calendar block as the weekly pass extended once a month.

The checklist covers the things that need a full month to surface:

  • Duplicate accounts and duplicate contacts. Run the duplicate finder if your tool ships one; sort by company name and skim if it does not.
  • Follow-ups past their agreed window. A "follow up in 14 days" set on day one is overdue by day fifteen.
  • Drafts and abandoned records: half-typed accounts, half-imported lists, contacts with only a first name.
  • Owner balance across active deals. If one person on the team has twice the load of the others, that is a load-balancing question, not a hygiene one, but it shows up here first.
  • The lost-reason field on closed-lost deals. The single highest-leverage column in the entire system. A blank lost-reason is a closed-lost deal that will never teach anyone anything.

Thirty minutes is the floor for finding duplicates without rushing. At 200 accounts, thirty minutes is plenty. At 2,000 accounts, the duplicate sweep is its own subroutine and you may want to split it across two monthly passes for the first quarter, then settle into the steady cadence.

The prevented moment: two teammates open parallel proposals against the same account, find out at the eleventh hour, and one of them has to walk back a price. That conversation costs more than 90 minutes of hygiene a month, every time.

The quarterly 90-minute pass

Ninety minutes, once a quarter, on a calendar block you set six months in advance. The quarterly pass is where you stop maintaining the data and start asking whether the structure is still right.

The checklist is structural:

  • Fields nobody fills. If a field is blank on 70% of records, it is noise. Drop it or rename it. Anchored to the field-design floor in the 14-field cornerstone.
  • Pipeline stages that never disqualify. If a stage has not closed-lost a single deal in a quarter, the disqualification rule on that stage is wrong or absent. Anchored to the pipeline-anatomy floor in the five-stages cornerstone.
  • Dormant deals. Anything in "open" that has not moved for 90 days gets a hard call: closed-lost with a reason, or re-qualified with a real next step. There is no third option.
  • Saved views the team actually uses. A view nobody opens is a config screen pretending to be a workflow. Archive it.
  • The list of fields, stages, and views you wish you had. Write it down here. Do not act on it until the next quarter's review.

The prevented moment: the quarterly forecast meeting where someone reads out 30 deals from last year that should have been closed-lost in February, and the team realises the forecast is fiction.

The annual half-day audit

Once a year, half a day. Same operator, same desk, no meetings on the calendar. The annual audit is the only pass with permission to change the schema, redraw the pipeline, or rebalance ownership across the team.

What it covers:

  • Schema review. Run the 14-field floor against the current record layout. Remove fields that did not earn their square inch this year; add fields the team reached for twice.
  • Archive versus delete. Closed-lost deals older than two years move to the archive. Personal data with no business reason to stay gets deleted (and the deletion is logged, per the data-ownership principle).
  • Owner rebalance. If three people on a five-person team carry 80% of active accounts, the year-end audit is where the swap happens, not the Monday morning meeting.
  • Fiscal-year tie-out. Closed-won revenue matches the books. Closed-lost reasons aggregate into the quarterly themes for the next planning cycle.
  • The single-page maintenance calendar for next year. The annual audit ends with the calendar for the following twelve months printed and stuck on the wall.

The prevented moment: a new hire arrives in January and inherits an account list with three former owners listed, deals from two years ago marked "open," and no recent activity on half of them. Their first impression of the CRM decides whether they trust it for the next twelve months.

Why a calendar block beats a quarterly project

Most teams treat hygiene as a project they will get to once they have time. A project is something that lives outside the calendar. A calendar block is something the team has already paid for. The two have very different decay profiles.

A quarterly project takes a week because the operator has to learn the current state of the data before they can clean it. Three months of drift takes three days to map. Once the CRM cleanup is done, the data starts drifting again the next morning, and the next quarterly project is already 90 days away.

A weekly 10-minute pass does not need a learning phase. The operator already knows what changed because they changed it. Ten minutes catches the mistake the same week it was made. The monthly pass picks up what the weekly one missed. The quarterly pass picks up what the monthly one missed. The annual one closes out the year.

Your time is expensive. That is one of the four operating principles we run Syncek by, and the calendar-block model is the version of hygiene that respects it. A pass that runs by stopwatch has a known cost. A project that runs until done has an open one, and the open cost is what makes operators postpone the project until the next quarter.

Fields tell you who. Stages tell you where. Cadence tells you when.

A common confusion among operators who have already worked through the field-design pass and the pipeline pass: the CRM still feels messy a month later, and they suspect the design choices were wrong.

The design choices are usually fine. The missing piece is the calendar. A 14-field record schema starts decaying the day after you ship it. A five-stage pipeline starts collecting parking-lot deals the day after you draw it. Without a cadence on top, both layers rot back into the state they were in before the redesign.

The three layers stack:

  • A record has fields. Fields say who the client is.
  • A deal has stages. Stages say where the deal is.
  • Both have a calendar. The calendar says when you keep them honest.

If you have fixed your fields and your stages, and the CRM still feels messy in a month, the problem is the calendar. The four-pass model is the calendar.

How to start the calendar by next Friday

Whatever tool you use today, you can put the four passes on the team calendar before the end of this week. The work is small.

  1. Open your calendar. Set a recurring 10-minute block every Friday at 4:00 pm. Title it "CRM 10-minute pass." Not "review," not "tidy," not "cleanup." The literal name of the pass.
  2. On the last Friday of the month, extend the block to 30 minutes. The monthly pass replaces that week's weekly pass. It does not add to it.
  3. On the last Friday of every quarter, block 90 minutes. The quarterly pass replaces that week's monthly pass.
  4. Pick a half-day in the second week of January (or whenever your fiscal year resets). Block it. That is the annual audit.
  5. Print the four checklists on a single page. Tape it next to the monitor. The lead magnet on this post is exactly that page, EN and ES, ready to print.

The first month of running the passes will feel slow. The weekly pass uncovers backlog the monthly pass would normally catch. The monthly pass uncovers backlog the quarterly pass would normally catch. By week six the cadence has caught up with itself, and each pass runs inside its stopwatch.

A note on the tool

The four passes are the model. They work in whatever CRM you use today. Syncek ships saved views and duplicate merging that compress each pass into the stopwatch budget, but the model belongs to your team, not to the tool. Your CRM spreadsheet, supercharged.

If you want the printable version that fits on a single page, one row per pass, with the stopwatch and the checklist next to each other, the lead magnet on this post is exactly that. Save it for your next maintenance pass.

Get the printable version

We've prepared a printable reference card to keep on hand while you build or audit your CRM. One page, ready to print.

Download the 4-pass maintenance calendar (8-page PDF)

Don't pay for a CRM your team never opens.

We're in closed beta. Public launch is coming soon — be the first to know.