---
title: "Audit HubSpot quarterly or annually?"
description: "Whether to audit HubSpot quarterly or annually: which checks to run monthly or quarterly, when a full annual audit is enough, and what events need one now."
url: "https://jetstack.ai/answers/audit-hubspot-quarterly-or-annually/"
---

# Should you audit HubSpot quarterly or annually?

Audit HubSpot annually in full, and run lighter checks quarterly. The quarterly checks cover what changes fastest: new workflows, duplicates, unused properties, users and connected apps. Run a full audit sooner after a change of admin or agency, a migration or merger, a new hub, or a sudden reporting or email problem. Quarterly or annually matters less than comparing each result with the last.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

On this page

## What HubSpot supports natively

Several native views are built for frequent, light checks. Their retention windows set a minimum cadence if you want the evidence.

| Native check                           | Good cadence         | Why                                                           |
| -------------------------------------- | -------------------- | ------------------------------------------------------------- |
| Audit logs (Super Admins)              | Monthly              | The in-app views show the last 30 days                        |
| Workflows Health tab                   | Monthly or quarterly | Flags workflows needing review and those unused for 90 days   |
| Data quality tools                     | Monthly              | New duplicates and formatting issues arrive with every import |
| Connected apps: “Needs your attention” | Monthly              | Expired or disconnected apps break syncs quietly              |
| Workflow action logs                   | Before day 90        | Action log data is kept for 90 days                           |

## A quarterly and annual HubSpot audit plan

| Cadence                   | Scope                                                                                                      |
| ------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Monthly (30 minutes)      | Users and Super Admins, connected app alerts, new duplicates                                               |
| Quarterly (a few hours)   | New and changed workflows, unused properties, form and email authentication, dashboard use                 |
| Annually (full audit)     | Every hub in use, data model, lifecycle and lead status logic, reporting definitions, integrations, access |
| Event-driven (full audit) | New admin or agency, migration, merger, new hub, major reporting or email incident                         |

Use the same checklist each time, so you can compare. See [what an audit checklist should review](https://jetstack.ai/answers/hubspot-audit-checklist-what-to-review).

## Signs you need an audit now

- A new admin or agency is taking over. See [evaluating an inherited portal](https://jetstack.ai/answers/evaluate-inherited-hubspot-portal).
- Lifecycle stages or owners change and nobody knows why.
- Sales and marketing report different numbers for the same thing.
- You’re planning a migration or adding a hub.

## Common mistakes

- Running a big audit once and never comparing it with a second.
- Changing the checklist every time, so results can’t be compared.
- Waiting for the annual audit when a change of admin or a migration has already happened.
- Treating the light checks as optional. Most problems start small: one new workflow, one new integration, one import.

Record the date, the scope and the result of every check in one place, so the next person can see the trend.

## Where Jetstack AI fits

Jetstack AI’s [Portal Audit](https://jetstack.ai/audit) can be re-run on the same portal whenever you choose; each run recalculates the score from scratch, so you can compare quarters. Reusing one template keeps the scope the same between runs. See [how the portal score changes over time](https://jetstack.ai/docs/audits/scoring/portal-score).

## Sources

- [Monitor your workflow health (HubSpot Knowledge Base)](https://knowledge.hubspot.com/workflows/monitor-your-workflow-health)
- [View and export account activity history (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account/export-account-activity-history)
- [Portal score: score changes over time (Jetstack AI documentation)](https://jetstack.ai/docs/audits/scoring/portal-score)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

Portal audits

## See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

[Explore Portal Audit](https://jetstack.ai/audit)

On this page

Portal audits

## Related questions.

Should you audit HubSpot quarterly or annually?

Audit HubSpot annually in full, and run lighter checks quarterly. The quarterly checks cover what changes fastest: new workflows, duplicates, unused properties, users and connected apps. Run a full audit sooner after a change of admin or agency, a migration or merger, a new hub, or a sudden reporting or email problem. Quarterly or annually matters less than comparing each result with the last.

Which checks should run every month?

Super Admin and inactive users, apps that need attention in Connected Apps, and new duplicates. These change often and are cheap to check.

Do we need a full audit if nothing seems broken?

Once a year is still worth it. Problems such as unused properties, overlapping workflows and stale dashboards build up slowly and rarely announce themselves.
