Analytics & Dashboard
Dashboards with metrics on task progress, contributor activity, and quality.
The dashboard is accessible from the Dashboard link in the sidebar. What you see depends on your role and whether a project is selected. Click on any metric card to open a detail view with the underlying data.
Admin dashboard
Without a project selected, the dashboard shows aggregate metrics across your organization. With a project selected, metrics are scoped to that project and include timeframe and pipeline filters.
Metrics
| Metric | Definition |
|---|---|
| Total submissions | Number of subtask and review submissions across all pipelines. |
| Completed tasks | Number of tasks that have reached Finished status. |
| Tasks created | Number of tasks seeded in the selected period. |
| Daily active contributors | Distinct contributors who submitted work today. |
| Active contributors | Distinct contributors who submitted work in the selected period. |
| Pipeline completion | For each pipeline, the percentage of tasks that have reached the End node out of total tasks created. |
| Avg submissions per contributor | Total submissions divided by the number of active contributors. |
| First review pass rate | Percentage of submissions that passed on the first review attempt without rework. |
| Avg reviews per review node | Average number of review rounds a task goes through before passing. |
Contributor dashboard
Contributors see personal metrics:
| Metric | Definition |
|---|---|
| Claimable tasks | Number of tasks currently available for the contributor to claim based on their role and pipeline assignments. |
| Submissions awaiting review | Count of the contributor's submitted work that is pending a reviewer's decision. |
| Your submissions | The contributor's submission count for today and all-time. |
| Tasks requiring action | Tasks that need the contributor's attention, including claimed tasks and tasks returned for rework. |
Activity history export
Export a detailed log of all pipeline activity to CSV. Available to project admins and above from the Export menu in the Data Explorer.
The export captures every submission, review, and routing decision across your pipelines. You can filter by date range and action type.
Action types
| Action type | What it captures |
|---|---|
| submit | A contributor submitted a subtask form. |
| review_pass | A reviewer approved a submission. |
| review_fail | A reviewer rejected a submission. |
| logic_then | A logic gate evaluated to the "then" (true) path. |
| logic_else | A logic gate evaluated to the "else" (false) path. |
Export columns
| Column | Description |
|---|---|
| Event ID | Unique identifier for the activity event. |
| Timestamp | When the event occurred (ISO format). |
| Action Type | The type of action (see table above). |
| Project Name / ID | The project the event belongs to. |
| Pipeline Name / ID | The pipeline the event belongs to. |
| Node ID / Name / Type | The specific node where the action occurred (subtask, review, or logic). |
| User Email / Name | The contributor or reviewer who performed the action. |
| Task ID | The task associated with the event. |
| Group Name | The task group name (if task groups are enabled). |
| Attempt Number | Which attempt this submission represents (1 = first attempt, 2+ = rework). |
| Is Rework | Whether this submission was a rework after a review rejection. |
| Response Data | The full form field values submitted, as JSON. |
| Upstream Edits | Any edits made to upstream fields during this submission, as JSON. |
What you can learn from the export
- Contributor productivity — who submitted what, when, and how often.
- Review patterns — which reviewers pass or fail submissions, and how consistently.
- Rework frequency — which tasks required multiple attempts and why (via rejection reasons in response data).
- Pipeline bottlenecks — where tasks spend the most time by comparing timestamps across nodes.
- Routing decisions — which logic gate paths are taken and how often.