> ## 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. # Basecamp on Vortex IQ > Monitor Basecamp performance signals, run automated checks, and prepare approved work through Vortex IQ. Monitor Basecamp performance signals, run automated checks, and prepare approved work through Vortex IQ. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=basecamp) performance signals automated checks automated fixes workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Find failures, leaks and risks before they cost sales. Monitor orders, fulfilment, delivery and settlement. Improve discovery, conversion, campaigns and repeat purchase. Keep tracking, access and change under governed control. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 24 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ---------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Avg Cycle Time (days)** | Alert band 3 / 7 | Mean days from to-do creation to completion. | | **Avg Lead Time (days)** | Merchant rule | Mean days from finding creation to to-do completion. | | **Avg Time-to-Fix (days)** | Merchant rule | Mean days from finding creation to to-do completion. | | **Backlog by Priority** | Merchant rule | Priority derived from VortexIQ name-prefix convention - Basecamp has no priority field. | | **Backlog by Status** | Watch only | Open vs done split - the only two states Basecamp's data model exposes. | | **Blocked Tickets** | Alert band 3 / 8 | To-dos tagged blocked by VortexIQ convention - the operational queue's stuck list. | | **Critical Findings Without a Basecamp To-do** | Merchant rule | Critical / high findings older than 7 days with no Basecamp to-do - coverage gap. The auto-dispatch missed these or the merchant disabled it. | | **Cycle Time by Priority** | Merchant rule | Cycle time bucketed by VortexIQ-tagged priority. | | **Finding Resolution Rate (90d)** | Alert band 75 / 50 | Share of findings ticked complete in 90 days. The most useful single number for a Basecamp owner - Basecamp surfaces no velocity or throughput nativel | | **In Progress** | Watch only | Basecamp has no native in-progress status; this maps to-dos VortexIQ tags as started via name-prefix convention. | | **Oldest Open (days)** | Alert band 30 / 90 | Age of the longest-open to-do - backlog-rot signal Basecamp does not surface natively. | | **Open Tickets** | Merchant rule | Total open to-dos across the default project - top-of-funnel backlog volume. A to-do counts as open until the checkbox is ticked. | | **Overloaded Assignees (>10 open)** | Alert band 0 / 1 | People with >10 open to-dos - capacity bottleneck candidates. | | **Throughput Trend** | Watch only | Completions per day over 30 days. | | **Tickets Resolved (7d)** | Merchant rule | To-dos ticked complete in the last 7 days vs the prior 7 - the closest thing Basecamp has to throughput. | | **Tickets by Assignee** | Merchant rule | Open to-dos per assignee - capacity distribution across the team. | | **Unassigned Tickets** | Alert band 5 / 20 | Open to-dos with no assignee - work nobody owns. | | **VortexIQ Findings In Progress** | Watch only | Description pending editorial review; the signal is live. | | **VortexIQ Findings Open** | Merchant rule | Open to-dos VortexIQ created from audit findings - the live backlog of things we surfaced. Basecamp surfaces no rollups, so this is the only place the | | **VortexIQ Findings Resolved** | Watch only | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | -------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Scope Added Mid-Sprint** | Merchant rule | To-dos added after the cadence started - scope creep on the active findings batch. | | **Sprint Progress** | Alert band 80 / 50 | Completed-ratio of the active findings cadence (Basecamp's completed\_ratio on the to-do list). Basecamp has no sprints; this models the cadence betwee | | **Sprint Velocity (avg)** | Merchant rule | To-dos completed per cadence, last 5 cadences. | | Signal | Alert behaviour | What it tracks | | ----------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Open to-dos in the Vortex IQ Findings list with no movement in 14+ days. On Basecamp this is the ONLY staleness signal - no priority field, no last-to | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time finding here goes stale from that moment, silently, until someone notices the numbers stopped updating. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PM-AUTH-001` **Severity** high · **Outcome** Grow revenue · **Fix status** Report only Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PM-RESOLUTION-001` **Severity** high · **Outcome** Protect revenue · **Fix status** Report only More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PM-ABANDONED-001` **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PM-CAPACITY-001` **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PM-BACKLOG-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PM-CYCLE-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **7 read** and **4 write** operations across buckettodocompletionjsons, buckettodolisttodojsons, bucketrecordingcommentjsons, buckettodos, buckettodolisttodocompletedjsons, buckettodosettodolistjsons on Basecamp. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=basecamp) #### Ready to build your first Basecamp workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | -------------------------------- | --------------- | ---------------- | | buckettodocompletionjsons | 0 | 2 | | buckettodolisttodojsons | 1 | 1 | | bucketrecordingcommentjsons | 0 | 1 | | buckettodos | 1 | 0 | | buckettodolisttodocompletedjsons | 1 | 0 | | buckettodosettodolistjsons | 1 | 0 | | myprofilejsons | 1 | 0 | | projectjsons | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.