Data quality
2 findings · ~10h if fixed separately
Sample audit report
B
86/100
Read the full verdict
This wholly synthetic HubSpot fixture found deterministic access, CRM-model, data-quality, pipeline, automation, marketing and CMS configuration issues across all eight scored categories. The published overall result is grade B (86/100). The report contains no real customer records, traffic, backlink, revenue or conversion claims.
This week
Fixes you can land this week
High-leverage changes you can start without a project plan. Effort figures are indicative.
High~1h
Domains without SSL enabled
1 domain(s) reported SSL as disabled. Domain names are deliberately not retained in the report.
Web/CMS · Specialist
Medium~1h
Invalid or ambiguous pipeline stage order
deals pipeline "Synthetic deal pipeline" has missing or duplicated displayOrder values among active stages.
RevOps · Specialist
Also in: Pipelines and process (4 findings)
Medium~2h
High super admin count
7 of 12 users are marked as super admins (mid-size portal threshold 5).
IT/Security · Specialist
Medium~2h
Campaign configuration ownership is incomplete
2 of 6 campaigns had no observed owner. Campaign metrics remain associative and are not causal ROI proof.
Marketing Ops · Specialist
Low~1h
Many users have no primary team
4 of 12 users do not have a primary team.
CRM Admin · Specialist
Low~2h
High share of landing pages stuck in draft
2 of 5 sampled landing pages are in DRAFT state.
Marketing Ops · Specialist
90 days
Next 90 days
Prioritised by severity, impact, effort, confidence and simple dependency order. Owner suggestions are heuristic; adjust to your team. Effort figures are indicative.
Next 30 days
6Critical and high-impact items first
Mostly RevOps work
30% of contacts (15,000 of 50,000 records) have no owner — mid-size portal threshold 25%.
Why now: medium severity with roughly 4h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "contacts ownership gaps", protecting an impact score of 8/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
20 of 40 sampled contacts had no primary company association. Any-company and primary-company evidence are reported separately.
Why now: medium severity with roughly 4h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "Contacts lack a primary company association in the sample", protecting an impact score of 7/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
1 domain(s) reported SSL as disabled. Domain names are deliberately not retained in the report.
Why now: high severity with roughly 1h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the high risk described by "Domains without SSL enabled", protecting an impact score of 9/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
deals pipeline "Synthetic deal pipeline" has missing or duplicated displayOrder values among active stages.
Why now: medium severity with roughly 1h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "Invalid or ambiguous pipeline stage order", protecting an impact score of 5/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
7 of 12 users are marked as super admins (mid-size portal threshold 5).
Why now: medium severity with roughly 2h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "High super admin count", protecting an impact score of 7/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
2 of 6 campaigns had no observed owner. Campaign metrics remain associative and are not causal ROI proof.
Why now: medium severity with roughly 2h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "Campaign configuration ownership is incomplete", protecting an impact score of 6/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
~14h indicative in this horizon
Days 31–60
3Medium-impact follow-ups
Mostly RevOps work
30% of sampled deals with an explicit open/closed state have not changed in over 180 days. This is operating/stage-health evidence from the bounded deal sample, not a pipeline configuration defect.
Why now: medium severity with roughly 4h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "Open deals stuck for over 180 days", protecting an impact score of 8/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
40% of contacts (20,000 of 50,000 records) have not been modified in over 3 years — mid-size portal threshold 30%.
Why now: medium severity with roughly 6h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "contacts are largely stale", protecting an impact score of 8/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
12 of 40 sampled contacts records had no companies association (30%). Source object, target object, numerator and denominator are explicit; relationship correctness is not inferred from presence alone.
Why now: medium severity with roughly 6h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the medium risk described by "Contacts records have missing companies associations", protecting an impact score of 7/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
~16h indicative in this horizon
Days 61–90
5Cleanup and longer-running work
Mostly RevOps work
4 of 12 users do not have a primary team.
Why now: low severity with roughly 1h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the low risk described by "Many users have no primary team", protecting an impact score of 4/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
2 of 5 sampled landing pages are in DRAFT state.
Why now: low severity with roughly 2h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the low risk described by "High share of landing pages stuck in draft", protecting an impact score of 3/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
deals pipeline "Synthetic deal pipeline" has 16 stages, above SpotDev's guidance threshold of 15.
Why now: low severity with roughly 3h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the low risk described by "Long pipeline stage set", protecting an impact score of 4/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
6 enabled workflows have not been edited in over 12 months ("Synthetic workflow 1" (synthetic-workflow-1), "Synthetic workflow 2" (synthetic-workflow-2), "Synthetic workflow 3" (synthetic-workflow-3), "Synthetic workflow 4" (synthetic-workflow-4), and 2 more). Last-edit age is only a review proxy because HubSpot's API does not expose workflow execution or enrolment history.
Why now: low severity with roughly 6h indicative effort; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the low risk described by "Active but stale workflows", protecting an impact score of 6/10.
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
HubSpot's public pipeline read contract does not expose conditional required-stage property enforcement. SpotCheck cannot automatically confirm which properties are required in which stages.
Why now: info severity; prioritised before lower-confidence or lower-impact work.
Outcome: Reduce or remove the info risk described by "Conditional required-stage properties need manual verification".
Verify: Re-run SpotCheck and confirm this finding is resolved or materially reduced.
Dependencies:
~12h indicative in this horizon
Licence
Are you using the HubSpot you pay for?
STANDARD
Reported tier: STANDARD. Tier fit could not be concluded because HubSpot did not report a recognised subscription tier. 2 relevant inventories were unavailable, so absence was not interpreted as feature underuse.
Platform limits and headroom
- Custom properties42% used
- Custom objectsNot availableThis limit could not be read for this portal.
- Association labelsNot availableThis limit could not be read for this portal.
See hub-by-hub tiers
Your HubSpot subscriptions
Add the tier you hold for each Hub and this report will show your licence at a glance. We only ever show what you confirm, never a guess.
Root causes
Where issues concentrate
These areas account for many of the high-impact findings.
CRM data model
2 findings · ~10h if fixed separately
Pipelines and process
4 findings · ~8h if fixed separately
Explore
View as
Showing all findings across every owner. Pick a tab above to retell the same audit through one role's lens.
Findings
14 of 14 findings shown
Search, filter, sort and expand findings. Results update without leaving this report.
14 findings shown after filtering and sorting.
Severity
Category
Owner
Fix type
Security and access
- Medium Specialist
- Low Specialist
CRM data model
- Medium Specialist
- Medium Specialist
Data quality
- Medium Specialist
- Medium Specialist
Pipelines and process
- Medium Specialist
- Medium DIY
- Low Specialist
- Info Specialist
Automation
- Low Specialist
Marketing setup
- Medium Specialist
CMS and assets
- High Specialist
- Low Specialist
Category breakdown
How the grade is made up
Each category is scored out of 100 and contributes to the overall grade by its weight. The rationale explains what moved each score.
| Category | Grade | Score | Weight | Confidence | Why |
|---|---|---|---|---|---|
| Security and access | B | 86 | 20% | High | High super admin count. Many users have no primary team. |
| CRM data model | B | 80 | 15% | High | Contacts records have missing companies associations. Contacts lack a primary company association in the sample. |
| Data quality | B | 84 | 15% | High | contacts are largely stale. contacts ownership gaps. |
| Pipelines and process | B | 82 | 12% | High | Pipeline rule set hubspot-pipeline-rules-v1 (configuration and stage-health layers assessed separately). Long pipeline stage set. Invalid or ambiguous pipeline stage order. Open deals stuck for over 180 days. Conditional required-stage properties need manual verification. |
| Automation | A | 94 | 12% | High | Workflow rule set hubspot-workflow-rules-v1; configuration assessed, execution history not. Active but stale workflows. |
| Marketing setup | B | 88 | 10% | High | Campaign configuration ownership is incomplete. |
| CMS and assets | B | 82 | 8% | High | Domains without SSL enabled. High share of landing pages stuck in draft. |
| Governance | A | 100 | 8% | High | No major deterministic issues detected. |
Severity heatmap
Where issues cluster
Categories down, severities across. Cell intensity scales with finding count.
| Critical | High | Medium | Low | Info | Total | |
|---|---|---|---|---|---|---|
| Security and access | 0 | 0 | 1 | 1 | 0 | 2 |
| CRM data model | 0 | 0 | 2 | 0 | 0 | 2 |
| Data quality | 0 | 0 | 2 | 0 | 0 | 2 |
| Pipelines and process | 0 | 0 | 2 | 1 | 1 | 4 |
| Automation | 0 | 0 | 0 | 1 | 0 | 1 |
| Marketing setup | 0 | 0 | 1 | 0 | 0 | 1 |
| CMS and assets | 0 | 1 | 0 | 1 | 0 | 2 |
| Governance | 0 | 0 | 0 | 0 | 0 | 0 |
Shape versus peers
Category radar
Where this portal stands
Higher is better. The shaded shape is this portal; the dashed line is the portfolio median for similarly-tiered HubSpot portals SpotCheck has audited.
Strongest category: Governance at 100/100. Lowest category: CRM data model at 80/100. A reliable compatible benchmark is not available for this chart.
This portal
View category radar data
| Category | This portal |
|---|---|
| Security and access | 86/100 |
| CRM data model | 80/100 |
| Data quality | 84/100 |
| Pipelines and process | 82/100 |
| Automation | 94/100 |
| Marketing setup | 88/100 |
| CMS and assets | 82/100 |
| Governance | 100/100 |
Benchmark values appear only for compatible cohorts with enough retained audits to be reliable.
Impact × Effort
Where to focus
Each dot is a finding. Top-left means quick wins and top-right means strategic projects. Use the chart or the finding controls below to jump to a finding.
10 plotted findings look like quick wins. Highest plotted impact: Domains without SSL enabled, 9/10 impact and about 1 hours. 1 finding lacked impact or effort estimates and are listed in the findings table instead.
View impact and effort chart
Findings in the chart
- 7/10 impact, about 2 hours, IT/Security
- 4/10 impact, about 1 hours, CRM Admin
- 7/10 impact, about 6 hours, RevOps
- 7/10 impact, about 4 hours, CRM Admin
- 8/10 impact, about 6 hours, RevOps
- 8/10 impact, about 4 hours, RevOps
- 4/10 impact, about 3 hours, RevOps
- 5/10 impact, about 1 hours, RevOps
- 8/10 impact, about 4 hours, Sales Manager
- 6/10 impact, about 6 hours, RevOps
- 6/10 impact, about 2 hours, Marketing Ops
- 9/10 impact, about 1 hours, Web/CMS
- 3/10 impact, about 2 hours, Marketing Ops
View impact and effort data
| Finding | Severity | Impact | Effort | Owner |
|---|---|---|---|---|
| High super admin count | medium | 7/10 | 2 hours | IT/Security |
| Many users have no primary team | low | 4/10 | 1 hours | CRM Admin |
| Contacts records have missing companies associations | medium | 7/10 | 6 hours | RevOps |
| Contacts lack a primary company association in the sample | medium | 7/10 | 4 hours | CRM Admin |
| contacts are largely stale | medium | 8/10 | 6 hours | RevOps |
| contacts ownership gaps | medium | 8/10 | 4 hours | RevOps |
| Long pipeline stage set | low | 4/10 | 3 hours | RevOps |
| Invalid or ambiguous pipeline stage order | medium | 5/10 | 1 hours | RevOps |
| Open deals stuck for over 180 days | medium | 8/10 | 4 hours | Sales Manager |
| Active but stale workflows | low | 6/10 | 6 hours | RevOps |
| Campaign configuration ownership is incomplete | medium | 6/10 | 2 hours | Marketing Ops |
| Domains without SSL enabled | high | 9/10 | 1 hours | Web/CMS |
| High share of landing pages stuck in draft | low | 3/10 | 2 hours | Marketing Ops |
Critical High Medium Low Info
1 finding has no effort/impact estimate and is not plotted here. See the findings table for the full list.
Assessment boundaries
What this report measures
Wholly synthetic golden fixture. Wholly synthetic fixture. No customer or anonymised production data is used.
- Configuration and implementation health
- 86/100, grade B, across 8 categories.
- Observed business performance
- Not measured. This report makes no revenue, conversion, traffic or commercial-performance judgement from configuration evidence.
- Evidence coverage
- 33 of 117 sources succeeded; 8 of 8 categories were assessed.
Method and source proof
How this assessment was produced
Each deterministic rule records its outcome and the evidence it used. Checks that could not run are omitted here rather than shown as errors; they never count as a pass and never lower the score. The coverage summary above accounts for those gaps.
Digest facts and recorded outcomes
- Audit type
- HubSpot portal
- Scored at
- 22 Jun 2026, 09:14 UTC
- Methodology
spotcheck-methodology-v2- Rule registry
deterministic-rule-registry-v2- Scorer
hubspot-scorer-v8-independent-evidence-groups- Assessment basis
hubspot-score-evidence-v1- Headline result
- 86/100, grade B
- Evidence ledger
deterministic-evidence-ledger-v2- Ledger digest
ece92e73e7855ea88549d10953a2c9487b68b92b26b4e02a4e1155fda8727abb
Recorded rule outcomes
- 23Passes
- 13Fails
- 22Unavailable
- 0Not applicable
- 0Errors
Category scoring basis
- automation12% weight94/100, grade A
- cms assets8% weight82/100, grade B
- crm model15% weight80/100, grade B
- data quality15% weight84/100, grade B
- governance8% weight100/100, grade A
- marketing10% weight88/100, grade B
- pipelines process12% weight82/100, grade B
- security access20% weight86/100, grade B
Deterministic rule proof
FailSuper administrator count6 point deduction
Compare the observed aggregate Super Admin count with the portal-size band maximum.
- Rule ID
hubspot.check.security.super-admin-count.v1- Observed result
- 7 of 12 observed active users were Super Admins; the mid-size portal maximum was 5. 1 matching deterministic finding was recorded with 6 total points before category clamping.
- Decision boundary
- Deduct only when the aggregate Super Admin count exceeds the registered portal-size band maximum.
- Structured proof
- 2 of 2 sources available; 1 finding, 6 point impact
Evidence references
Related findings
FailPrimary team coverage8 point deduction
Measure the aggregate share of active users without a primary team.
- Rule ID
hubspot.check.security.primary-team-coverage.v1- Observed result
- 4 of 12 observed active users lacked a primary team (33%). 1 matching deterministic finding was recorded with 8 total points before category clamping.
- Decision boundary
- Deduct when more than 25% of observed active users have no primary team.
- Structured proof
- 1 of 1 sources available; 1 finding, 8 point impact
Evidence references
Related findings
PassArchived-owner sample
Compare hashed archived-owner references with the bounded CRM record sample.
- Rule ID
hubspot.check.security.archived-owner-sample.v1- Observed result
- 0 archived owners and 10 bounded CRM sample records were available for hashed-reference comparison. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- This check is non-scored; sampled assignments to archived owners are reported for manual review.
- Structured proof
- 1 of 5 sources available; 0 findings, 0 point impact
Evidence references
FailStale-record share10 point deduction
Compare complete object counts with records not modified for three years.
- Rule ID
hubspot.check.data-quality.stale-share.v1- Observed result
- 4 core-object populations were evaluated; the highest observed aggregate share was 40% (20000 of 50000). 1 matching deterministic finding was recorded with 10 total points before category clamping.
- Decision boundary
- Deduct only when the object population exceeds 100 and its stale share meets the registered portal-size band threshold.
- Structured proof
- 9 of 9 sources available; 1 finding, 10 point impact
Evidence references
Related findings
PassRecent-activity share
Compare complete object counts with records modified in the previous twelve months.
- Rule ID
hubspot.check.data-quality.recent-activity-share.v1- Observed result
- 4 core-object populations were evaluated; the highest observed aggregate share was 100% (1000 of 1000). The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when an object has more than 5,000 records and fewer than 10% were modified in the previous twelve months.
- Structured proof
- 8 of 8 sources available; 0 findings, 0 point impact
FailRecord owner coverage6 point deduction
Compare complete object counts with complete unowned-record counts.
- Rule ID
hubspot.check.data-quality.owner-coverage.v1- Observed result
- 4 core-object populations were evaluated; the highest observed aggregate share was 30% (15000 of 50000). 1 matching deterministic finding was recorded with 6 total points before category clamping.
- Decision boundary
- Deduct when the unowned-record share meets the registered portal-size band threshold.
- Structured proof
- 9 of 9 sources available; 1 finding, 6 point impact
Evidence references
Related findings
PassPipeline inventory size
Count validated deal and ticket pipeline definitions by object and name the observed pipelines.
- Rule ID
hubspot.check.pipelines.inventory-size.v1- Observed result
- The larger observed object inventory contained 1 pipelines; the mid-size portal maximum was 10. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when one object exceeds the registered portal-size band pipeline maximum.
- Structured proof
- 4 of 4 sources available; 0 findings, 0 point impact
FailPipeline stage count5 point deduction
Count stages in every validated deal and ticket pipeline and name the pipeline that exceeds SpotDev guidance.
- Rule ID
hubspot.check.pipelines.stage-count.v1- Observed result
- 1 pipelines were evaluated; the highest observed stage count was 16 against SpotDev's guidance threshold of 15. 1 matching deterministic finding was recorded with 5 total points before category clamping.
- Decision boundary
- Deduct once for each observed pipeline with more than 15 stages.
- Structured proof
- 2 of 2 sources available; 1 finding, 5 point impact
Evidence references
Related findings
PassTerminal stage probability
Validate closed-won probability 1 and closed-lost probability 0 on deal pipelines, and CLOSED ticketState where present.
- Rule ID
hubspot.check.pipelines.terminal-probability.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when terminal stage semantics are missing or non-terminal on closed stages.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
PassOpen-stage probability monotonicity
Check that open deal-stage probabilities do not decrease with display order when probability metadata is present.
- Rule ID
hubspot.check.pipelines.probability-monotonicity.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a later open stage has a lower probability than an earlier open stage.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassDuplicate stage labels
Detect duplicate active stage labels within a named pipeline.
- Rule ID
hubspot.check.pipelines.duplicate-stage-label.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when two or more active stages share the same label.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
PassEmpty stage labels
Detect active stages whose label is empty.
- Rule ID
hubspot.check.pipelines.empty-stage-label.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct once for each empty active stage label.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
FailInvalid stage order4 point deduction
Detect missing or duplicated displayOrder values among active stages.
- Rule ID
hubspot.check.pipelines.invalid-stage-order.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. 1 matching deterministic finding was recorded with 4 total points before category clamping.
- Decision boundary
- Deduct when active stage order is missing or ambiguous.
- Structured proof
- 2 of 2 sources available; 1 finding, 4 point impact
Evidence references
Related findings
PassArchived stage clutter
Count archived stages retained beside active stages in a named pipeline.
- Rule ID
hubspot.check.pipelines.archived-stage-clutter.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a pipeline retains three or more archived stages.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
FailStuck-deal sample9 point deduction
Measure unchanged open deals in the bounded, validated deal sample at the immutable audit timestamp as operating evidence.
- Rule ID
hubspot.check.pipelines.stuck-deal-sample.v1- Observed result
- 3 of 10 assessable sampled deals were open and unchanged for more than 180 days (30%). 1 matching deterministic finding was recorded with 9 total points before category clamping.
- Decision boundary
- Deduct when at least 20% of sampled deals with an explicit state are open and unchanged for more than 180 days.
- Structured proof
- 1 of 1 sources available; 1 finding, 9 point impact
Evidence references
Related findings
PassEmpty stage sample
Join the bounded deal sample to named pipeline stages and report stages unused in-sample as stage-health evidence.
- Rule ID
hubspot.check.pipelines.empty-stage-sample.v1- Observed result
- 10 sampled deals were joined to 1 deal pipelines for in-sample stage-health evidence. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when at least 25% of a sampled pipeline's active stages have no in-sample deals.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
PassRequired-stage enforcement review
Emit a non-scored manual verification card because the public pipeline read contract does not expose conditional required-stage properties.
- Rule ID
hubspot.check.pipelines.required-stage-enforcement.v1- Observed result
- 1 deal and 0 ticket pipelines were evaluated under pipeline rule set hubspot-pipeline-rules-v1. 1 non-scored review signal was recorded with 0 score impact.
- Decision boundary
- This check is non-scored and never claims automated verification of required-stage enforcement.
- Structured proof
- 1 of 1 sources available; 1 finding, 0 point impact
Evidence references
Related findings
PassEnabled workflow count
Count enabled workflows observed in the bounded workflow sample and cite named workflows.
- Rule ID
hubspot.check.automation.enabled-workflow-count.v2- Observed result
- 6 enabled workflows were observed in the collected sample of 6; the mid-size portal maximum was 200. Truncation can only understate the enabled count. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when enabled workflows observed in the collected sample exceed the registered portal-size band maximum. Truncation can only understate the count.
- Structured proof
- 3 of 3 sources available; 0 findings, 0 point impact
Evidence references
FailStale enabled workflows6 point deduction
Count enabled workflows in the bounded sample whose last-edit timestamp is more than twelve months before the audit timestamp.
- Rule ID
hubspot.check.automation.stale-enabled-workflows.v2- Observed result
- 6 of 6 enabled workflows in the collected sample had not been edited for more than twelve months. 1 matching deterministic finding was recorded with 6 total points before category clamping.
- Decision boundary
- Deduct when at least five enabled workflows in the collected sample have not been edited for more than twelve months; this is not execution-history evidence.
- Structured proof
- 1 of 1 sources available; 1 finding, 6 point impact
Evidence references
Related findings
FailCMS transport security15 point deduction
Count connected domains whose validated configuration reports HTTPS disabled.
- Rule ID
hubspot.check.cms.transport-security.v1- Observed result
- 1 of 1 observed connected domains reported HTTPS disabled. 1 matching deterministic finding was recorded with 15 total points before category clamping.
- Decision boundary
- Deduct when one or more observed connected domains report HTTPS disabled.
- Structured proof
- 1 of 1 sources available; 1 finding, 15 point impact
Evidence references
Related findings
PassPattern redirect share
Measure the share of pattern redirects in the bounded redirect sample.
- Rule ID
hubspot.check.cms.pattern-redirect-share.v2- Observed result
- 0 of 0 sampled redirects were pattern redirects (0%); the decision boundary is at least 35% in a sample of 20 or more. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a sample of at least 20 redirects contains 35% or more pattern redirects. Findings never claim a complete redirect inventory.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassPublic file share
Measure the share of files marked public or searchable in the bounded file sample.
- Rule ID
hubspot.check.cms.public-file-share.v2- Observed result
- 0 of 0 sampled files were public or searchable (0%); the decision boundary is at least 50% in a sample of 50 or more. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a sample of at least 50 files contains 50% or more public or searchable files. Findings never claim a complete file inventory.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassSite-page metadata coverage
Measure the share of sampled site pages without a meta description.
- Rule ID
hubspot.check.cms.site-page-metadata.v1- Observed result
- 0 of 5 sampled site pages lacked a meta description (0%). The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when at least 30% of a non-empty site-page sample has no meta description.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
FailLanding-page draft share3 point deduction
Measure the share of sampled landing pages in the draft state.
- Rule ID
hubspot.check.cms.landing-page-draft-share.v1- Observed result
- 2 of 5 observed landing pages were drafts (40%). 1 matching deterministic finding was recorded with 3 total points before category clamping.
- Decision boundary
- Deduct when at least 40% of a non-empty landing-page sample is in the draft state.
- Structured proof
- 1 of 1 sources available; 1 finding, 3 point impact
Evidence references
Related findings
PassMarketing forms coverage
Record validated marketing form capability coverage without inferring campaign performance.
- Rule ID
hubspot.check.marketing.forms-coverage.v1- Observed result
- 6 validated marketing form definitions were observed; the check is coverage-only and makes no campaign-performance inference. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- This check is non-scored and is unavailable when the product or approved grant does not expose the source.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassMarketing form field hygiene
Measure the share of sampled marketing forms with no configured fields.
- Rule ID
hubspot.check.marketing.forms-field-hygiene.v1- Observed result
- 1 of 6 sampled marketing forms had no field groups (17%). The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a sample of at least five forms has 40% or more forms with no field groups.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassAccount governance evidence
Record privacy-safe account and audit-context evidence separately from scored configuration findings.
- Rule ID
hubspot.check.governance.account-evidence.v1- Observed result
- The validated account-evidence source was available; this coverage-only check retains no account identifier or customer value. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- This check is non-scored and reports only the availability of the registered governance evidence.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassCustom role coverage
Count validated custom roles beside the portal user inventory.
- Rule ID
hubspot.check.governance.custom-roles.v1- Observed result
- 4 custom roles were observed beside 12 users; the decision boundary is two or fewer roles when the portal has at least ten users. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a portal with at least ten users has two or fewer custom roles.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
PassTeam configuration
Count validated teams beside the portal user inventory.
- Rule ID
hubspot.check.governance.teams-configured.v1- Observed result
- 2 teams were observed beside 12 users; the decision boundary is zero teams when the portal has at least ten users. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when a portal with at least ten users has no teams configured.
- Structured proof
- 2 of 2 sources available; 0 findings, 0 point impact
Evidence references
FailAssociation relationship completeness10 point deduction
Measure bounded source-object samples for missing target-object associations.
- Rule ID
hubspot.check.associations.relationship-completeness.v1- Observed result
- 1 bounded association batch-read pair produced aggregate relationship evidence with no associated record values retained. 1 matching deterministic finding was recorded with 10 total points before category clamping.
- Decision boundary
- Deduct when a sampled association direction of at least 30 records has 20% or more missing target associations. Presence alone is not treated as relationship correctness.
- Structured proof
- 1 of 9 sources available; 1 finding, 10 point impact
Evidence references
Related findings
FailPrimary company association coverage10 point deduction
Separate any-company contact association evidence from primary-company association evidence.
- Rule ID
hubspot.check.associations.primary-company-coverage.v1- Observed result
- 1 bounded association batch-read pair produced aggregate relationship evidence with no associated record values retained. 1 matching deterministic finding was recorded with 10 total points before category clamping.
- Decision boundary
- Deduct when a contact-to-company sample of at least 30 records has 20% or more contacts without a primary company association.
- Structured proof
- 1 of 1 sources available; 1 finding, 10 point impact
Evidence references
Related findings
PassCustom property limit pressure
Read the portal-wide custom-property usage percentage from the validated limits inventory.
- Rule ID
hubspot.check.crm-model.custom-property-limit-pressure.v1- Observed result
- Custom property usage was 42% of the HubSpot limit against a decision boundary of 80%. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- Deduct when overall custom-property usage reaches 80% or more of the HubSpot limit.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
PassAssociation label adoption
Compare configured association-label schema evidence with bounded association usage evidence.
- Rule ID
hubspot.check.associations.label-adoption.v1- Observed result
- 1 bounded association batch-read pair produced aggregate relationship evidence with no associated record values retained. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- This check is non-scored; unused-label review signals require both schema and usage evidence.
- Structured proof
- 1 of 10 sources available; 0 findings, 0 point impact
Evidence references
PassDeal amount currency basis
Inspect the bounded deal sample for amount completeness and mixed-currency risk.
- Rule ID
hubspot.check.sales-performance.currency-basis.v1- Observed result
- 0 deals were in the 365-day created cohort and 0 open deals were directly counted as stale for more than 180 days; observed performance is non-scored. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- This check is non-scored and never sums mixed currencies without an explicit common-currency basis.
- Structured proof
- 1 of 1 sources available; 0 findings, 0 point impact
Evidence references
FailCampaign configuration ownership12 point deduction
Measure campaign configuration ownership in the validated campaign inventory; attribution counters remain non-scored associative evidence.
- Rule ID
hubspot.check.marketing.campaign-performance.v1- Observed result
- 2 of 6 observed campaigns had no owner (33%). 1 matching deterministic finding was recorded with 12 total points before category clamping.
- Decision boundary
- Deduct when at least five campaigns are observed and 30% or more have no owner. Campaign metrics remain associative and are not causal ROI proof.
- Structured proof
- 1 of 3 sources available; 1 finding, 12 point impact
Evidence references
Related findings
PassCMS governance and redirects
Separate published/draft/scheduled/archived content, aggregate CMS change history by pseudonymous actor and analyse redirect chains and loops.
- Rule ID
hubspot.check.cms.governance-redirects.v1- Observed result
- 10 CMS content records, 0 pseudonymous content-audit events and 0 redirects were evaluated without page bodies or author identities. The registered deduction condition was not met, so the check produced 0 findings and 0 score impact.
- Decision boundary
- This check is non-scored; body content and author identity are not retained.
- Structured proof
- 3 of 5 sources available; 0 findings, 0 point impact
Evidence references
Source proof
These records identify the bounded source used by each completed check. They contain labels and non-identifying page roles, not raw customer payloads. Sources that could not be collected are omitted.
- Account governance detailsAvailable
- Associations batch contacts companiesAvailable
- Workflow automationAvailable
- CMS configurationAvailable
- CMS configurationAvailable
- CMS configurationAvailable
- CMS configurationAvailable
- CRM recent-activity share (Companies)Available
- CRM recent-activity share (Contacts)Available
- CRM recent-activity share (Deals)Available
- CRM recent-activity share (Tickets)Available
- CRM record sample (Deals)Available
- CRM record counts (Companies)Available
- CRM record counts (Contacts)Available
- CRM record counts (Deals)Available
- CRM record counts (Tickets)Available
- CRM stale-record share (Companies)Available
- CRM stale-record share (Contacts)Available
- CRM stale-record share (Deals)Available
- CRM stale-record share (Tickets)Available
- CRM record ownership (Companies)Available
- CRM record ownership (Contacts)Available
- CRM record ownership (Deals)Available
- CRM record ownership (Tickets)Available
- File manager configurationAvailable
- Custom property limit usageAvailable
- Marketing campaignsAvailable
- Marketing formsAvailable
- Sales/service pipeline configurationAvailable
- Sales/service pipeline configurationAvailable
- Custom user rolesAvailable
- Team structureAvailable
- User and team settingsAvailable
Coverage
What was checked, what wasn't
An honest read on how complete this run was. Only categories with applicable, validated evidence are assessed. An optional capability without a confirmed grant is excluded, not treated as a pass or a customer defect. Independent checks inside a category still score when their own evidence is valid.
8 of 8 produced a result 0 could not be run 0 errored
Automation1/1 checked (1 checked)
Cms assets1/1 checked (1 checked)
Crm model1/1 checked (1 checked)
Data quality1/1 checked (1 checked)
Governance1/1 checked (1 checked)
Marketing1/1 checked (1 checked)
Pipelines process1/1 checked (1 checked)
Security access1/1 checked (1 checked)
Governance evidence
Security, ownership and property controls
These are observed, non-scored review facts. Security events are not proof of compromise, and a missing property validation is not a defect until its business requirement is known.
Security activity
Property governance
Validation rules, sensitivity classifications and unique-value settings are separate facts. Uniqueness does not prove access control, encryption or protection.
HubSpot performance evidence
Campaigns, analytics, events, commerce and CMS governance
These are observed, non-scored facts. Attribution is associative, behavioural evidence is aggregate only, and inactive commerce or CMS features are treated as not applicable.
Campaigns6 inventoried; 0 sampled for metrics; owner gaps 33%; insufficient evidence sessions and insufficient evidence influenced contacts; revenue scope not approved or unavailable
Behavioural events0 allowlisted occurrences across 0 event types; 0 common path hypotheses. Raw contact IDs, unsafe URLs and individual sequences are not persisted.
HubSpot analyticsunavailable; 90-day visits insufficient evidence; contacts insufficient evidence; legacy Analytics v2 disclosed
Marketing events0 events; 0 registrations; 0 attended; no-show rate insufficient evidence. Participant identities are not retained.
Commercenot applicable; 0 activated object families (none); currency basis unknown; no accounting advice.
CMS governance3 published and 2 draft assets; 0 pseudonymous audit events; 0 redirect chains and 0 loops; page bodies are not collected.
Free website audit
Now audit your website
SpotCheck® also runs a free website audit covering public performance evidence, SEO, accessibility and conversion readiness.
Audit a website