Skip to main content

​
What Track Data is for

Individual instance pages answer: “Where is this person?” Track Data answers: “How is this workflow performing overall?” Use it when you manage pipelines, oversee multiple overseers, or report upward on throughput, bottlenecks, and completion rates — without opening every instance one by one.
Screenshot placeholder Track Data landing page: list of tracks with stat cards or summary metrics, search bar, and navigation to a specific track’s data view.

​
Open Track Data

Navigate to Track Data from your workspace (exact sidebar placement may vary by workspace configuration). You see tracks with high-level metrics — active instance counts, completion rates, and related summaries. Select a track to drill into detailed reporting for that workflow alone.

​
Track-level dashboard

The per-track view typically includes:

​
Summary metrics

Stat cards at the top — common examples:
  • Active instances — how many journeys are in progress.
  • Completed — how many finished successfully.
  • Completion rate — percentage over a time window.
  • Average time — how long instances take end to end (when available).
Screenshot placeholder Track-specific data page header with three or four stat cards (icons + numbers).

​
Checkpoint and milestone distribution

Charts showing where instances cluster — how many people sit at each checkpoint, or how many have achieved each milestone. Bottlenecks light up when one stage hoards volume.
Screenshot placeholder Milestone or checkpoint distribution chart (bar or donut). Label axes with user-facing checkpoint names.
Video placeholder (Screen Studio) Short clip: hover chart segments to see counts; click through to participant list filtered to that checkpoint.

​
Participants table

A searchable table of everyone on the track:
  • Name or entity label
  • Status (Active, Completed, etc.)
  • Current checkpoint or progress indicator
  • Dates (started, last activity)
Click a row to jump to the instance detail page for operational follow-up.
Screenshot placeholder Participants table with sortable columns and at least five rows of sample data.

​
Track Data vs. Tracks Manage tab

Both show who is on a track. Use the right surface for the job: Track Data is the manager’s lens; instance detail is the operator’s lens.

​
Reading bottlenecks

When a checkpoint bar towers over others, ask:
  • Is that stage genuinely slow (interviews, legal review)?
  • Are overseers not moving people forward?
  • Is a requirement gate blocking progress?
  • Do you need more instance-level overseers at that stage?
Pair chart insight with spot-checking instances in that checkpoint — data points you to cases; instance pages explain why.
Screenshot placeholder Same chart with one checkpoint bar notably higher — annotate in capture or caption “example bottleneck at Interview stage.”

​
Entity types in reporting

Track Data respects the entity type of each track. A File track’s participant table lists documents; a Contact track lists people. Metrics work the same — only labels change.
Planning new pipelines to measure?The Use Case Brainstorm agent in Evolve can help you define which checkpoints become KPI stages before you build the track.
If you would like something unique to your business or have a unique issue, use XSpada Evolve or ask a XSpada rep.