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

# Progress Tracking

> See who's enrolled, in progress, and certified - reported in your CRM, next to pipeline.

> Progress Tracking turns training into a leading indicator - readiness you can see per partner and report on in the CRM, alongside the pipeline it drives.

## What it does

Progress Tracking gives you a live view of every course's enrollments, grouped by status - enrolled, not started, in progress, and completed - with completion metrics over any date range. Drill into a single learner to see exactly where they are. And because Introw is CRM-native, every enrollment is written back to HubSpot or Salesforce as a Course Enrollment record, with progress, dates, and module counts - so partner readiness lives next to deals, not in a side dashboard.

## The problem it solves

Training only counts if you can see it. When progress is trapped in a separate LMS, the questions that matter go unanswered:

* **Are our partners actually ready to sell?** → Live readiness per partner by status, not an anecdote.
* **Training is trapped in a separate LMS** → Every enrollment syncs to the CRM, so readiness sits right next to pipeline.
* **Enablement can't be tied to revenue** → Completion and certification report as leading indicators of partner-attached pipeline.
* **RevOps won't trust a second system** → Training data lands on standard CRM objects, with no duplicate system or manual reconciliation.

## From problem to solution

Readiness becomes measurable and reportable. Enablement watches completion roll in by status; leadership reports certification and completion as leading indicators of partner-attached pipeline; and RevOps gets the data on standard CRM objects, so partner training shows up in the same dashboards as everything else. No duplicate system, no manual reconciliation.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  complete["Partner completes"] --> status["Status tracked"]
  status --> sync["Synced to CRM"]
  sync --> report["Reported next to pipeline"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Readiness at a glance" icon="circle-check">
    See how many partners have completed the sales course versus how many are stalled.
  </Card>

  <Card title="Board-ready reporting" icon="circle-check">
    Report certification and completion as leading indicators of partner-attached revenue.
  </Card>

  <Card title="Training in the CRM" icon="circle-check">
    Show a partner's course progress on their company record, next to their deals.
  </Card>

  <Card title="Find the stalled cohort" icon="circle-check">
    Filter to in-progress and not-started learners to target follow-up.
  </Card>
</CardGroup>

## Impact

* **CRM-native** - Every enrollment and its progress sync to the CRM automatically, with no middleware.
* **Trust & accuracy** - Readiness reporting is grounded in the same source of truth as pipeline.

## Who it's for

<CardGroup cols={2}>
  <Card title="VP Partnerships / CPO" icon="user">
    Reports readiness as a leading indicator of partner-attached ARR.
  </Card>

  <Card title="Partner Marketing & Enablement" icon="user">
    Tracks completion and targets follow-up to drive it up.
  </Card>

  <Card title="Revenue Operations" icon="user">
    Gets training data on standard CRM objects for unified reporting.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Certificates" icon="graduation-cap" href="/features/courses/certificates">
    Completion triggers a certificate.
  </Card>

  <Card title="Enrollments" icon="graduation-cap" href="/features/courses/enrollments">
    Tracks the partners you enrolled.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>