Audit the CRM Views Your Team Actually Uses

The screen people work from becomes the process

Ask an advisor to show you the pipeline and you may get four different answers. The owner opens a forecast dashboard. An account manager uses a saved list called "My clients." Operations keeps a spreadsheet of renewals. Somebody else filters opportunities by close date and assumes that is the current priority list.

All of those screens may pull from the same CRM. They can still tell different stories.

This is not a dashboard-design problem. It is an operating problem. The view a person opens each morning decides what gets noticed, what gets ignored, and which records receive action. If that view no longer matches the firm's stages, ownership rules, service model, or current decisions, clean underlying data will not save the workflow.

Do not start by building another dashboard. First audit the views your team already trusts.

Inventory the real work surfaces

Do not limit the inventory to official CRM dashboards. Include every recurring screen or file people use to choose work:

• Saved pipeline filters and board views
• Personal client and prospect lists
• Renewal reports and contract exports
• Task queues and overdue activity lists
• Commission and revenue reports
• Supplier or partner trackers
• Spreadsheets rebuilt from CRM exports
• Bookmarks to filtered pages

Ask each person what they open before a pipeline review, client call, renewal meeting, commission check, or supplier conversation. Watch what they use. The official answer and the real answer are often different.

For every view, capture its name, purpose, owner, users, source records, filters, visible fields, sort order, review rhythm, and the decision it is supposed to support. Add the last time somebody confirmed that it still works.

Start with the decision, not the columns

A useful view helps a named person make a repeatable decision. "All opportunities" is a collection. "Deals requiring a client decision this week" is a work queue.

Write one sentence for each view:

This view helps [role] decide [action] during [operating rhythm].

For example, a weekly pipeline view might help the firm owner decide which deals stay active, move stage, return to discovery, enter nurture, or close. A renewal view might help an account owner decide which client conversations must begin before a notice window controls the options. A commission exception view might help operations decide which payment questions need evidence or supplier escalation.

If you cannot finish the sentence, the view probably exists because somebody once wanted a report. That is not enough reason to keep it in the operating system.

Separate personal views from shared operating views

Personal views are useful. An advisor may want a list of today's calls, a region, a supplier specialty, or accounts requiring travel. That does not mean the whole firm should adopt the same screen.

A shared operating view deserves a higher standard because other people will make decisions from it. It should have a defined audience, purpose, owner, required fields, common filter logic, and review schedule. The team should know what inclusion means and what absence means.

HubSpot's current saved-view documentation illustrates the distinction at the product level: a view can remain private or be shared with a team, selected users, or everyone in the account. The button is easy. Deciding which work should become shared is the harder part.

Make a view shared when the firm needs a common queue or common interpretation. Keep it personal when it only changes how one person organizes already assigned work. Do not publish every useful personal filter. A shared library full of near-duplicates recreates the same confusion with more tabs.

Test whether the filter logic matches the operating rule

Read every filter in plain language. Then compare it with the firm's current rule.

A view called "Renewals due" may filter on contract end date while ignoring the notice deadline that controls the actual decision window. "Stalled deals" may use days since record update even though an advisor added an internal note yesterday and the client has been silent for six weeks. "At-risk clients" may rely on a red status selected months ago without showing the evidence or next review date.

Run five records through the view:

1. One record that clearly belongs
2. One that clearly does not
3. One with missing data
4. One with conflicting fields
5. One recent exception your team handled outside the CRM

If the results surprise the people who use the queue, find out why. The filter may be wrong. The underlying records may be incomplete. The process may have changed without anyone updating either one.

Do not quietly adjust the filter until the list looks right. Decide whether the operating rule or the data needs to change, document that decision, and then update the view.

Show fields that support action

A giant table is usually a sign that the decision is unclear. A useful operating view should show enough context to act without becoming a second client record.

Most work queues need some version of the account, current state, accountable owner, next action, due date, last confirmed external event, decision date, and exception flag. A pipeline view may also need stage, expected value, and buyer evidence. A renewal view may need provider, service, end date, notice deadline, strategy, and client meeting date.

Remove fields that people never use during the decision. Add any field they repeatedly leave the view to find. If the answer lives only in an inbox or private note, the problem is bigger than column order.

This is where your ownership model matters. A single account owner cannot answer every question about an opportunity, client commitment, supplier escalation, and next action. Show the owner relevant to the work the view is asking someone to do.

Find the side spreadsheet without attacking it

A side spreadsheet is evidence. It may show that the CRM lacks a needed field, the official report is too slow, permissions block the user, the current view is noisy, or the process itself has no agreed rule.

Ask what the spreadsheet makes easier. Which columns get added after export? Which records get deleted? What color or comment changes the priority? Who receives the file? What happens after the meeting?

Then decide whether to move the logic into a shared CRM view, improve the underlying record, keep the spreadsheet as a temporary analysis tool, or retire it. Do not ban the workaround while leaving the reason for it untouched. People will build another one, and this time they may not tell you.

Give every shared view an owner and a retirement rule

The owner is responsible for the view's operating meaning, not just its technical setup. That person confirms the filters, required data, sharing scope, and fit with the meeting or workflow that uses it.

Review shared views when a pipeline stage changes, a service model changes, ownership rules move, a new product category is added, or a recurring meeting changes purpose. Also set a simple scheduled review. Quarterly may be enough for stable views. High-stakes renewal or revenue queues may deserve a monthly check.

Retire a view when nobody uses it, the decision moved to another queue, the source fields are no longer maintained, or a better shared view absorbed its purpose. Rename or archive it clearly before deletion if people may still have bookmarks or links.

Do not measure success by the number of dashboards created. Measure whether the team can open the same view, understand why each record appears, and leave the review with decisions and owners.

Run the audit in one operating meeting

Bring the views people actually use. For each one, answer six questions:

1. Which decision does this support?
2. Who uses it and who owns it?
3. What puts a record into the view?
4. Which fields are required to act?
5. What workaround exists outside the view?
6. Should it remain personal, become shared, be corrected, combine with another view, or retire?

Start with the views tied closest to revenue and client trust. Pipeline, renewals, open commitments, active projects, and commission exceptions usually deserve attention before a prettier executive dashboard.

Connect the cleaned views to an existing operating rhythm. Use the pipeline queue during your weekly pipeline cleanup. Use account evidence during the client business review. Use a firm-level exception list during the weekly operating review. A view without a decision meeting or work habit will become stale again.

Make the CRM earn its place in the business

Your CRM does not become useful because every field is filled in. It becomes useful when the right person can see the right records, understand why they are there, and make the next decision without rebuilding the business in a spreadsheet.

Advisor OS CRM connects pipeline, clients, contacts, suppliers, commissions, activity, and ownership in one operating record. Use that record to build fewer views with clearer jobs.

Use the free Advisor OS agency scorecard if your team still depends on disconnected work queues, private trackers, and memory.