> ## 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. # Finding Resolution Rate (90d), Monday.com > Finding Resolution Rate (90d) for Monday.com stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Project Management](/nerve-centre/connectors#connectors-by-type) ## At a glance > The percentage of Vortex IQ findings created in Monday.com in the last 90 days that have moved to a closed-set Status label. Below 50% the team is falling behind; above 75% the team is matching or beating intake. Marketing-led Monday teams typically run this card a touch lower than engineering-led Linear teams because Monday's status taxonomy is more permissive (more in-flight states, looser closure discipline). | | | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **The formula** | `resolved_in_window ÷ created_in_window`, where `resolved_in_window` counts items in the connected Findings board with `Status` in the closed set AND `updated_at` within the 90-day window (we use `updated_at` as a proxy for the close timestamp because Monday's GraphQL surface does not expose `closed_at` directly); `created_in_window` counts items with `created_at` within the same window. | | **API endpoints** | Monday GraphQL `items_page` queries with `created_at` and `updated_at` filters, paged via cursor. We bucket by `vortexiq_finding_id` to avoid double-counting if a finding was re-created. | | **Window** | Rolling 90 days, refreshed hourly. The headline number updates on every webhook for the live count; the rate calculation is hourly to smooth single-item volatility. | | **What "resolved" means** | `Status` ∈ closed set (default `Done`, `Cancelled`, `Won't Do`; tunable). Both *Done* and *Won't Do* are treated as resolutions because closing the loop is what the rate measures. | | **Closed-set configuration** | Editable in **Settings → Connectors → Monday → Status mapping**. Marketing teams sometimes add custom labels like *Approved*, *Live*, or *Shipped* to the closed set. | | **Workspace scope** | All `vortex_iq_outbound` Monday boards across all connected workspaces. | | **Time zone** | UTC for both `created_at` and `updated_at`. The 90-day window aligns to UTC. | | **Alert trigger** | `< 50%` raises a critical alert. | | **Sentiment thresholds** | Gauge: green ≥ 75%, amber 50-74%, red \< 50%. | | **Multi-workspace aggregation** | Yes, computed on summed numerator and denominator. Per-workspace stack panel available. | | **Roles** | owner, operations | ## Calculation Calculated automatically from your Monday.com data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A UK marketing-led DTC bedding brand on Shopify, 19-person team, Monday.com primary tool. Snapshot taken on 02 May 26 at 14:00 BST. | Last 90 days (02 Feb 26 - 02 May 26) | Count | | ---------------------------------------------------------------------------------- | ----- | | Findings created (Monday items with `vortexiq_finding_id`, `created_at` in window) | 72 | | Findings resolved (above set, AND Status in closed set, `updated_at` in window) | 47 | | Findings still open from window | 17 | | Findings re-created (counted once on first close in numerator) | 3 | ```text theme={null} Resolution rate = 47 ÷ 72 = 0.653 = 65.3%, displayed as 65% ``` **What the merchant should read into this:** 1. **65% sits in the amber band (50-74%).** Above the alarm threshold but below the green target. The team is closing more than it is opening, but the open queue shrinks slowly. 2. **Marketing-led Monday teams commonly run 60-70%.** This is platform-typical, not exceptional. Engineering-only teams using Linear typically run 75-85%; Monday's permissive status taxonomy and visual-numbness pattern explain most of the gap. 3. **Pair this card with [Avg Time-to-Fix](/nerve-centre/kpi-cards/monday/avg-time-to-fix).** A 65% rate with a 7-day mean time-to-fix is healthy. A 65% rate with a 25-day mean would mean the team is closing easy items and stalling on harder ones. 4. **Compare against [Findings Open](/nerve-centre/kpi-cards/monday/vortexiq-findings-open) trend.** If open count is rising for three weeks while resolution rate sits at 65%, the audit programme is producing more findings than the team can absorb, a calibration issue with the audit, not a team problem. 5. **The team should aim for 75% sustained.** The fastest way to lift a Monday rate is to tighten the closed-set configuration (adding *Approved* or *Live* if the team's convention treats those as final), and to pair this card with a weekly board-walk discipline. Both are no-cost moves. ## Sibling cards merchants should reference together | Card | Why pair it with Resolution Rate | What the combination tells you | | ------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | | [VortexIQ Findings Open](/nerve-centre/kpi-cards/monday/vortexiq-findings-open) | Resolution rate's denominator-half. | Falling rate + climbing open count = capacity bottleneck. | | [Abandoned Findings (>14d)](/nerve-centre/kpi-cards/monday/abandoned-findings) | Items that count in the denominator but never become numerators. | High abandoned + low rate = visual-numbness; the team thinks it is moving but is not. | | [Avg Time-to-Fix (days)](/nerve-centre/kpi-cards/monday/avg-time-to-fix) | Cycle time inside this rate. | High rate + low time-to-fix = excellent. High rate + high time-to-fix = closing eventually but slowly. | | [Tickets Resolved (7d)](/nerve-centre/kpi-cards/monday/tickets-resolved) | Short-window throughput of all items. | High overall throughput but low findings rate = audit work being deprioritised. | | [Sprint Velocity (avg)](/nerve-centre/kpi-cards/monday/sprint-velocity) | Capacity ceiling. | Flat rate with rising velocity = audit work not entering weekly batches. | | [Throughput Trend](/nerve-centre/kpi-cards/monday/throughput-trend) | The slope. | A rate dipping while throughput climbs = deliberate prioritisation away from audit work. | | [Sprint Progress](/nerve-centre/kpi-cards/monday/sprint-progress) | Whether items are getting committed to the current week. | Low sprint progress + low rate = items queued but never pulled in. | ## Reconciling against the vendor's own dashboard **Where to look in Monday.com's own UI:** > **[monday.com](https://monday.com)** then open **Dashboards** in your workspace. Add a **Numbers** widget showing item count filtered by `Status is Done OR Cancelled OR Won't Do` AND `Created at in last 90 days`, alongside a second Numbers widget showing total items created in the same window. The ratio is the resolution rate. Monday's Dashboards are the primary native rollup; the **Battery** widget displays a percent gauge that approximates this card directly when configured for the same filter. Monday does not have a single native "resolution rate" widget; the Battery widget filtered to your closed-set Status labels is the closest visual analogue. **Why our number may legitimately differ from a Monday Dashboard widget:** | Reason | Direction | Why | | ------------------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------- | | **Status label mapping** | Either | We use the configured closed-label set; a Dashboard widget filtered to a different set will diverge. | | **Window definition** | Either | Monday's Dashboard "Last 90 days" rolls daily at midnight in your account-profile timezone; our window rolls hourly in UTC. | | **Re-created findings** | Ours lower | Dashboard widgets count each closure event; we count once per finding-id. | | **Subitem handling** | Either | Configurable in the Dashboard widget; our default is parent-items only. | | **Cross-workspace aggregation** | Ours wider | Monday Dashboards are typically per-workspace; we sum across all connected workspaces. | **Cross-connector reconciliation. Monday resolution rate vs operations-health peers:** | Card | Expected relationship | What causes the divergence | | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`datadog.dd_health_score`](/nerve-centre/kpi-cards/datadog/operational-health-score) | Independent. Datadog is server-side production health; Monday rate is internal team operations. | A high Datadog Health Score with a low Monday rate means production is fine but the marketing team is falling behind on the work that prevents future regressions. The cause-and-effect lag is typically 4-8 weeks (longer than Linear because marketing audit findings tend to surface in organic traffic and conversion rate, which lag production metrics). | | [`newrelic.nr_apdex`](/nerve-centre/kpi-cards/newrelic/apdex-score) | Same shape. | Same lag. |
Documentation cross-reference (for agencies running multiple PM tools) The same metric exists with the same definition across other PM tools we connect to. * [`asana.asa_vortexiq_finding_resolution_rate`](/nerve-centre/kpi-cards/asana/finding-resolution-rate) * [`basecamp.bas_vortexiq_finding_resolution_rate`](/nerve-centre/kpi-cards/basecamp/finding-resolution-rate) * [`clickup.cli_vortexiq_finding_resolution_rate`](/nerve-centre/kpi-cards/clickup/finding-resolution-rate) * [`linear.lin_vortexiq_finding_resolution_rate`](/nerve-centre/kpi-cards/linear/finding-resolution-rate) * [`teamwork.tea_vortexiq_finding_resolution_rate`](/nerve-centre/kpi-cards/teamwork/finding-resolution-rate) * [`smartsheet_api.sma_vortexiq_finding_resolution_rate`](/nerve-centre/kpi-cards/smartsheet-api/finding-resolution-rate)
## Known limitations / merchant FAQs **My Monday Dashboard Battery widget shows 72% but you say 65%. Why?** Seven points of gap is normal. Most likely: closed-set differences (we use the configured set; your Battery may include or exclude *Approved*, *Live*, *On Hold*), or window-rolling timezone (UTC vs profile-timezone). Pin a per-workspace stack panel and the gap usually closes to 2-3 points. **Does *Won't Do* count as resolved?** Yes. The team chose to close the loop, that is the rate's purpose. If you want to track *Won't Do* and *Done* separately, that is on the backlog as a future "Won't Do Rate" card; for now they are both resolutions. **Our team uses a custom *Live* status. How does it interact with this card?** Depends on the closed-set mapping. If *Live* means "shipped and final" the team should map it as closed in **Settings → Connectors → Monday → Status mapping**. If *Live* means "live in market and being monitored" leave it as open. The card will count whichever way the team configures. **Our rate sits at 45%. Should I be concerned?** Yes. Below 50% is the alarm threshold for a reason: the open queue compounds week-over-week. Standard playbook: open this card, [Findings Open](/nerve-centre/kpi-cards/monday/vortexiq-findings-open), [Abandoned Findings](/nerve-centre/kpi-cards/monday/abandoned-findings), and [Tickets by Assignee](/nerve-centre/kpi-cards/monday/tickets-by-assignee). On a Monday team the most common cause is *In Review* sign-off backlog; check whether the marketing-director review meeting is happening on cadence. **We use multiple Monday workspaces. Which workspace's rate matters most?** The lowest. Open the per-workspace stack panel; on agencies running 5+ client workspaces the lowest-rate workspace is usually the leading indicator of a client-relationship issue. **Throughput dropped this week, rate is still high. What's happening?** "Team closed everything easy and left the hard stuff." Open [Avg Time-to-Fix](/nerve-centre/kpi-cards/monday/avg-time-to-fix). If mean cycle time climbed alongside the throughput drop, the team has finished quick-wins and is starting on heavier findings. Healthy phase, lasts 1-3 weeks. **Today's rate looks volatile. Why?** At low resolution volumes the rate is sensitive: 5 resolutions out of 8 is 62.5% and one extra close moves it to 75%. The 90-day window makes daily volatility small but visible. The 7-day moving rate is less noisy. **Multi-board reporting: how do I see resolution rate per board?** Each connected board gets its own per-board stack panel. If you want per-team rather than per-board breakdown within one workspace, the workaround is to use one board per team and tag each as a separate `vortex_iq_outbound` route in connector setup. **Is Monday.com the right tool for tracking this metric?** For marketing-led DTC teams that benefit from visual board+timeline+gantt views, yes. The cost is the visual-numbness pattern, the board makes accumulation feel benign, so this rate is the truth-teller. Asana with portfolios is closer for cross-functional ops; Linear is closer for engineering teams; Smartsheet is closer for spreadsheet-style PMOs; Teamwork is closer for time-tracking-driven agencies; ClickUp is closer for "everything-app" use cases; Basecamp is closer for small calm-process teams. Monday's strength here is the visual planning power; the metric this card adds is the discipline overlay that visual planning alone does not provide. **Resolution rate climbed but I don't think the team did anything different. What changed?** Three usual causes. (1) Audit programme produced fewer findings (denominator shrank). Check [Findings Open](/nerve-centre/kpi-cards/monday/vortexiq-findings-open) trend. (2) A bulk close (the team did a board cleanup). Check Monday's Activity log on the board. (3) A Status label was added to the closed set in connector configuration; items in that label now count as resolved overnight. Check **Settings → Connectors → Monday → Status mapping** for recent edits. *** ### Tracked live in Vortex IQ Nerve Centre *Finding Resolution Rate (90d)* is one of hundreds of KPI pulses Vortex IQ tracks across Monday.com and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.