> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Monday.com audit profile, Vortex IQ

> What the Vortex IQ Monday.com health audit checks: Monday.com: Backlog, Capacity & Finding Lifecycle

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/monday) · [Audit Profile](/nerve-centre/kpi-cards/monday/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/monday/sentiment)**

Surfaces the daily ops questions a marketing-led merchant or agency lives with in Monday.com: is the token still good, is the Findings board drowning, are People overloaded, and (most importantly) are the findings we filed actually getting closed or quietly going stale behind Monday's visually-busy board? The visual-numbness pattern makes the abandoned-finding check the highest-value signal this audit produces.

## What this audit checks

### Authentication & access

* API token still valid (me query on POST /v2 returns account)
* Findings board exists, is active (not archived), and is writable
* Status column present on the Findings board with the configured closed-set labels
* vortexiq\_finding\_id text column exists for finding correlation
* Complexity-budget headroom > 30% (Monday throttles on complexity points)

### Backlog health

* Open item count vs 30-day baseline (sudden growth = drowning signal)
* Blocked/Stuck-label count + change WoW
* Oldest open item age (>90 days = backlog rot)
* Unassigned items > 5 (People column empty - work nobody owns)
* Backlog-by-priority skew (mostly Low = no one is grooming)

### VortexIQ findings lifecycle (the stickiness test)

* Abandoned findings - VortexIQ-created items, no updated\_at change >14d (the visual-numbness pattern)
* Finding resolution rate over rolling 90d (target >75%; Monday teams typically run 60-70%)
* Avg time-to-fix for resolved findings, by priority
* Items closed Won't Do without an update (silent dismissals)
* Regression rate - items reopened after reaching a closed-set label
* Custom Status labels not mapped to open/closed set (count drift risk)

### Team capacity

* People with >10 open items (overload signal; often the marketing-ops lead)
* People with zero closed items in 14d (parked work)
* Cycle time degradation > 25% week-over-week
* Mid-week scope added to the configured weekly-batch group (scope creep)

### Cross-connector signals

* Critical findings from sibling connectors (shopify/bigcommerce/adobe/ga4/google\_ads) older than 7 days with no Monday item - coverage gap
* Monday items referencing decommissioned/archived integrations - stale work
* Findings routed to Monday vs Jira split inconsistent with the connector routing config

## Severity thresholds

| Signal                             | Warn | Critical |
| ---------------------------------- | ---- | -------- |
| `vortexiq_findings_abandoned`      | 5    | 15       |
| `vortexiq_finding_resolution_rate` | 75   | 50       |
| `blocked_tickets`                  | 3    | 8        |
| `unassigned_tickets`               | 5    | 20       |
| `oldest_open_ticket_age_days`      | 60   | 90       |
| `cycle_time_change_pct`            | 25   | 50       |
| `complexity_budget_headroom_pct`   | 30   | 10       |

## Data sources

* `POST https://api.monday.com/v2` - Single GraphQL endpoint - me (token + account), boards (board state), items\_page (rule-based backlog reads: open count, blocked, abandoned, by-assignee), users (capacity).