A CRM is not installed and finished. It drifts. Fields get added for a campaign and never removed. Automations accumulate and begin to contradict each other. A manager asks for “just one more picklist value.” Two years in, nobody can explain why half the screens look the way they do, and the reports disagree with each other.

A quarterly review is the cheapest defence. It is not a project. It is a few hours, on the calendar, with a fixed agenda, that stops drift from compounding. Below is the agenda I would use, in the order that tends to surface the most value for the least effort.

Set the Ground Rules

Put the review in the calendar as a recurring event with two people: the administrator and a business owner, usually the head of sales operations or a sales manager. The business owner matters because many decisions, such as retiring a field, are business choices rather than technical ones.

Keep a running document where each review’s findings, decisions and owners are recorded. Without that, the next review repeats the last one.

1. Users and Licences

Start where the money is. Pull the list of active users and compare it with the current staff list and recent login activity. Look for departed people still active, users who have not signed in for a long period, and people on a higher-tier licence than their actual use justifies.

Also check admin and elevated permissions. The number of users who can change configuration or export all data should be small, known and deliberate. If you cannot name why each person has it, remove it and see who complains.

2. Fields, Objects and Layouts

Custom fields are cheap to create and expensive to keep, because every one adds clutter to a page someone has to read. Run a usage check: for each custom field, how many records have a value, and when was it last populated? Fields that are almost always blank, or have not been touched in a long time, are candidates for removal or archival.

Look for near-duplicates such as “Lead Source,” “Source” and “Origin,” and for picklists with values nobody uses. Before deleting anything, find where it is referenced: reports, workflows, integrations, validation rules. Many platforms can show field dependencies; check the current documentation for how.

3. Automations and Rules

Workflows, flows, validation rules and assignment rules accumulate in layers. List them with owner, purpose and last-modified date. Disable anything nobody can justify, and watch for a week before deleting.

The danger zone is overlap. Two rules updating the same field, or a workflow triggering another, can produce results that appear random. If a user reports “the system changed my data,” this is where to look first.

4. Integrations and Connected Apps

Confirm each integration still has an owner, a current purpose and a working connection. Look at error logs and failed sync counts, and check the authentication method is not tied to a person who has left. Remove abandoned trials and marketplace apps; each one has permissions you granted and probably forgot.

5. Data Quality

Spot-check the basics: duplicate rate on a key such as email, records with no owner, contacts with no account, deals with close dates in the past that are still open, and missing values in fields your reports depend on. You do not need a perfect score. You need to know whether the trend is improving or worsening.

6. Vendor Changes and Contract

Scan the vendor’s release notes and announcements for changes affecting you: deprecated features, new limits, altered pricing structures, retired API versions. Check the vendor’s current documentation rather than relying on memory. Note the contract renewal date and confirm that preparation tasks, such as seat counts, are on someone’s calendar well ahead.

The Review Agenda

Area	Key question	Output
Users	Who is active that should not be?	List to deactivate or downgrade
Licences	Are we on the right tier per user?	Seat and tier changes
Fields	Which are unused or duplicated?	Retire list with dependencies
Automations	Which are undocumented or overlapping?	Disable, merge or document
Integrations	Any failing, unowned or abandoned?	Fixes and removals
Data quality	Which indicators moved?	Cleanup tasks with owners
Vendor and contract	What changes affect us?	Actions and dates

A Hypothetical Example

At a first review, a small company’s administrator finds several users who left months earlier but remain active, a couple of dozen custom fields never filled in on any record created this year, and two workflows that both set the lead status on conversion with different values. The business owner approves retiring the unused fields in stages, hiding them from layouts first. The overlapping workflows are merged into one, and the departed users are deactivated.

Three months later the second review takes half the time, because the first pass removed the backlog and the log shows what was decided. That change in effort is the point: a regular review turns an overwhelming mess into routine maintenance.

Keep a Change Log and a Request Process

Much drift comes from ad-hoc requests granted on the spot. Give people a simple way to ask for changes, such as a form or shared board, and review requests in batches against a few questions: what problem does this solve, who owns it, will it affect reports, and does something existing already do this? Record what you approve. That log also helps when a new administrator inherits the system.

Frequently Asked Questions

How long should a quarterly review take? Plan a few hours for a modest system after the first pass. The first review is longer because it clears the backlog.

Who should attend? The administrator and a business owner as a minimum. Bring in IT or security for the integration and permission sections if they are separate teams.

Should we delete unused fields right away? Hide them first, wait a cycle, and delete once nothing breaks. Confirm dependencies and retention needs before permanent removal.

What if we have no dedicated administrator? Assign the role explicitly to someone, with protected time. An unowned system degrades faster than any other kind.

Is a quarterly cadence right for everyone? It suits most growing teams. A very small or very stable setup might review twice a year; a fast-changing one might want monthly checks of users and integrations.

Next Step

Book the first review for the next two weeks, invite a business owner, and start the findings log with the user list. That one section often pays for the whole exercise.