---
title: "How do you prioritize HubSpot audit findings? · Jetstack AI"
description: "How to prioritize HubSpot audit findings by impact and effort, which findings come first regardless of score, and how to turn the list into a plan of work."
url: "https://jetstack.ai/answers/prioritize-hubspot-audit-findings/"
---

# How do you prioritize HubSpot audit findings?

Prioritize HubSpot audit findings by impact and effort: rate each finding for its effect on customers, revenue, compliance or reporting, then for the work to fix it. Do high-impact, low-effort fixes first, schedule high-impact, high-effort projects, and drop low-impact, high-effort items. Security, consent and email authentication come first whatever their score.

![](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

HubSpot’s own health views flag issues but don’t rank them across the portal.

| Native view           | What it flags                                                             | Ranking?                 |
| --------------------- | ------------------------------------------------------------------------- | ------------------------ |
| Workflows Health tab  | Workflows needing review; unused workflows                                | No                       |
| Data quality overview | Recommended actions on duplicates, formatting issues and unused workflows | Within data quality only |
| Email sending domains | Authentication status per domain                                          | No                       |
| Connected apps        | Apps needing attention                                                    | No                       |

Ranking findings against each other is left to you.

## How to prioritize HubSpot audit findings

1. **Pull out the non-negotiables.** Security and access problems, consent and subscription issues, unauthenticated sending domains. These go first.
2. **Rate impact from 1 to 5.** Does it affect customers, revenue, compliance or a report leadership uses?
3. **Rate effort from 1 to 5.** Hours, people involved, and risk of breaking something else.
4. **Sort into four groups:**

| Group           | Impact | Effort | Action               |
| --------------- | ------ | ------ | -------------------- |
| Quick wins      | High   | Low    | Do first             |
| Major projects  | High   | High   | Plan and schedule    |
| Fill-ins        | Low    | Low    | Do when there’s time |
| Thankless tasks | Low    | High   | Skip or defer        |

5. **Check dependencies.** Some fixes must come before others, such as cleaning a property before rebuilding the report that uses it.
6. **Agree the plan** with the business owner, and record what you’re leaving.
7. **Re-audit** after the first round to confirm the fixes worked.

For a portal with hundreds of workflow findings, see [where to start with broken workflows](https://jetstack.ai/answers/hubspot-audit-broken-workflows-where-to-start).

## Common mistakes

- Sorting by score instead of business impact.
- Treating every low score as a task.
- Starting a major project before the quick wins, so nothing visible improves for months.
- Ignoring dependencies, then rebuilding a report before fixing the data it uses.
- Not recording the findings you decided to leave, so they come back as new in the next audit.

Share the ranked list with everyone who’ll do the work before anyone starts.

## Where Jetstack AI fits

Every Jetstack AI [Portal Audit](https://jetstack.ai/audit) recommendation carries an impact and an effort rating from 1 to 5 and is placed in the same four groups, so the report starts with a ranked list. Turning a recommendation into a change is a separate step you decide. For major projects that mean building something new, such as a clean property set, a pipeline or replacement workflows, write the brief in [Projects](https://jetstack.ai/build), currently in limited release, or upload the agreed plan as a document. Jetty turns it into a plan you review and builds in dependency order, properties before the workflows that use them, with deployment approved separately; it builds new assets and doesn’t change ones built elsewhere. See the [impact and effort matrix](https://jetstack.ai/docs/audits/recommendations/impact-effort) and the [Projects quickstart](https://jetstack.ai/docs/projects/quickstart).

## Sources

- [Manage email authentication in HubSpot (HubSpot Knowledge Base)](https://knowledge.hubspot.com/marketing-email/manage-email-authentication-in-hubspot)
- [Monitor your workflow health (HubSpot Knowledge Base)](https://knowledge.hubspot.com/workflows/monitor-your-workflow-health)
- [Impact and effort matrix (Jetstack AI documentation)](https://jetstack.ai/docs/audits/recommendations/impact-effort)
- [Acting on recommendations (Jetstack AI documentation)](https://jetstack.ai/docs/audits/recommendations/acting)

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.

How do you prioritize HubSpot audit findings?

Prioritize HubSpot audit findings by impact and effort: rate each finding for its effect on customers, revenue, compliance or reporting, then for the work to fix it. Do high-impact, low-effort fixes first, schedule high-impact, high-effort projects, and drop low-impact, high-effort items. Security, consent and email authentication come first whatever their score.

Should we fix everything the audit found?

No. Some findings cost more to fix than they're worth. Write down the ones you decide to leave and why, so the next audit doesn't raise them again as new.

Who should set the priorities?

The auditor proposes them; the business owner decides. Impact depends on what the business cares about, which an audit can't fully know.
