Tickets we created from audit findings that haven’t been resolved yet.
At a glance
Live count of rows Vortex IQ created in your Smartsheet Findings sheet that aren’t marked closed yet. Smartsheet is the spreadsheet-power-user’s project tool, findings are rows in a dedicated sheet, with status as a Dropdown List column. PMO offices love this one because you can build resource-allocation Gantt views over the same data.
Calculation
Calculated automatically from your Smartsheet (API) 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 US wholesale-and-DTC home goods brand on BigCommerce. Their PMO runs everything in Smartsheet: marketing campaigns, supplier deliveries, vendor onboarding, audit-finding triage. Findings live in Vortex IQ Findings sheet with 41 rows. Snapshot taken on 18 Apr 26.>20). The dashboard banner reads “25 open findings in the PMO sheet, queue grew by 4 this week”.
The PMO benefit: the same 25 rows appear in the team’s Card view (grouped by Assigned To, used in the daily standup), in the Report rollup the PMO Director uses across multiple workstreams, and in the Gantt view that the resource-planning analyst uses to forecast capacity. Vortex IQ doesn’t write to those views, they’re all projections of the underlying findings sheet. So the count here, 25, drives every PMO conversation about findings without anyone needing to learn a new tool.
Why “Cancelled” rows don’t count: during connector setup the PMO admin mapped the Smartsheet Cancelled dropdown value into the closed set, signalling “we explicitly decided not to pursue this”. This is the recommended pattern. Note: cancelling is different from Won't Fix, the PMO admin uses Cancelled when the underlying audit finding turned out to be invalid (e.g. measuring a feature that’s been removed) and Won't Fix when the finding is valid but the team has prioritised against it.
Sibling cards merchants should reference together
Open Findings is the queue depth. Read it next to:Reconciling against the vendor’s own dashboard
Where to reproduce this in Smartsheet itself: The fastest method is a saved Filter on the Findings sheet:Open the Vortex IQ Findings sheet → Filter (top toolbar) → Create New Filter. Name it Open. Add condition:PMO admins typically save this filter and pin it as the default sheet view, so the team always sees only open findings on first open. For multi-sheet PMOs, the same number can be aggregated via a Smartsheet Report (cross-sheet rollup):Statusis not one ofDone, Won't Fix, Duplicate, Cancelled. Save and apply. The bottom-of-sheet row count is your open total.
Cross-connector reconciliation:
If this merchant also connected Asana, Jira, ClickUp, or another PM tool, the Findings counts there are not the same population. Vortex IQ writes to one mapped destination per workspace. If you switched destination from Smartsheet to Jira in the last 90 days, the Smartsheet sheet will show a frozen historical count and Jira will reflect ongoing inflow.
Known limitations / merchant FAQs
Why is my Open count rising? Three usual reasons, in order of likelihood: (1) inflow exceeds outflow, the team isn’t moving rows to closed statuses, check Resolution Rate; (2) someone added a custom dropdown value toStatus that isn’t mapped, e.g. “Pending Vendor”, and we count it as open by default, re-map; (3) the PMO created a new copy of the sheet for the next quarter and findings are now writing there but the connector still points at the old one.
Can the card aggregate across multiple Smartsheet sheets?
Not today. One mapped sheet per workspace. The PMO pattern of “one sheet per workstream” can produce 4-5 separate finding sheets, the recommended setup is to use a single master findings sheet with a Workstream column for filtering. Cross-sheet rollups via Smartsheet Reports work natively for the merchant’s PMO, but Vortex IQ’s KPI cards count from the mapped sheet only.
Our PMO uses Smartsheet’s “Sheet Summary” with calculated fields. Does Vortex IQ read those?
No, only column data on rows. Sheet Summary fields are out of scope. If you need a calculated metric on findings, expose it as a new column (e.g. Days Since Created) and Vortex IQ will read it.
My team uses Smartsheet’s hierarchical rows (parent-child). How are they counted?
Each row counts independently if it carries a Status value. A parent row marked Open with three child rows marked Done counts as 1 open + 3 closed (4 total). The connector treats hierarchy as visual organisation, not data semantics.
Why “20 open” as the alert threshold? Our PMO manages 100+ items routinely.
Default calibrated for small ecommerce teams. PMO-style merchants who run multi-workstream operations should raise it in Settings → Connectors → Smartsheet → Alerts → Open findings threshold. Rule of thumb: 2× weekly resolution rate.
Does the count include rows in deleted sheets?
No. Smartsheet keeps deleted sheets in a 30-day Recycle Bin; we exclude them immediately. If you accidentally deleted the Findings sheet and recreated it from a template, this card resets to 0 until findings start writing again.
Can I see which findings are open, not just the count?
Yes, click the card to drill into the row list. Or open the saved Open filter in Smartsheet directly (recommended for PMO triage workflows).
Smartsheet’s API has rate limits, does that affect this card?
The connector’s reconciliation respects Smartsheet’s 300 requests/minute per token limit. For sheets with thousands of rows, the reconciliation uses the cursor-paginated GET /sheets/{id} endpoint, which counts as 1 request per page (500 rows per page). Even a 5,000-row sheet refreshes in 10 requests, well within the limit.
Why is this a Key Metrics card?
Because it’s the single most-asked operational question for PMO-led merchants: “how many audit findings are sitting in our PMO sheet?”. One number, scannable in 1 second, gates everything else.