Skip to main content

Report Metrics Reference

This page defines every report metric available in Kazinex Workflows, including what it counts, how it is calculated, and which filters apply.

Document metrics​

document_count​

What it measures: Total number of document records in the project register.

Filters: Status, discipline, document type, zone, date range (created date).

Grouping options: Status, Discipline, Document Type, Zone, Created Date (month/quarter).

Calculation: Count of distinct document_id values matching the filter criteria. Each document is counted once regardless of how many revisions it has.

Use case: "How many documents are in the register by discipline?"

document_by_status​

What it measures: Number of documents broken down by their current status.

Grouping: Always grouped by status. Can add a secondary grouping (e.g. by Discipline).

Status values counted: draft, pending_review, under_review, approved, approved_with_comments, rejected, issued_for_construction, superseded, archived, no_longer_in_use.

Calculation: For each document, the current status at report run time is used. Historical statuses are not shown — this is a point-in-time snapshot.

document_by_discipline​

What it measures: Number of documents broken down by discipline.

Grouping: Always grouped by Discipline metadata field value.

Calculation: Aggregates all documents matching the filter, grouped by the Discipline field's code/label.

Workflow metrics​

workflow_count​

What it measures: Number of workflow instances by status.

Filters: Template name, status, date range (created date), assignee.

Grouping options: Status, Template, Created Date.

Status values counted: draft, active, completed, cancelled, returned.

Calculation: Count of distinct workflow_instance_id values matching the filter criteria at report run time.

workflow_cycle_time​

What it measures: Average time (in calendar days) from workflow instance creation to completion.

Filters: Template name, date range (completion date).

Calculation:

  • For each completed workflow: completion_date - created_date in days
  • Average across all matching completed workflows
  • Cancelled and returned workflows are excluded from cycle time calculations

Use case: "Is our structural drawing review template taking longer than expected? Is it improving over time?"

Task & step metrics​

overdue_tasks​

What it measures: Count of workflow steps currently past their due date.

Filters: Template, assignee, step name, project.

Calculation: Count of active workflow steps where step_due_date < now() and the step status is still pending or in_progress.

Important note: This metric counts current overdue state. It does not count steps that were overdue but have since been completed. Use workflow_cycle_time to identify chronic lateness.

Transmittal metrics​

transmittal_count​

What it measures: Number of transmittals by status.

Filters: Status, recipient, date range (issued date), purpose.

Status values counted: draft, issued, partially_acknowledged, fully_acknowledged, archived.

Grouping options: Status, Purpose, Recipient, Issued Date.

User activity metric​

user_activity​

What it measures: Actions taken by each project member within the date range.

Filters: User, date range, action type.

Action types counted:

  • Document uploads
  • Workflow approvals
  • Correspondence sent
  • Transmittals issued
  • Step completions

Grouping: Always grouped by User. Can add secondary grouping by action type.

Privacy note: User activity data is visible to all members with view_reports permission, not just admins. See Reporting Governance if you need to restrict this.

Correspondence metrics​

correspondence_count​

What it measures: Number of correspondence items by status and type.

Filters: Type (NCR, RFI, TQ, SI), status, date range, sender, recipient.

Status values counted: draft, pending_approval, sent, responded, overdue, closed.

Grouping options: Type, Status, Sender, Recipient, Sent Date.

Date range behaviour​

All metrics with date range filters use the following defaults:

  • Default date range: Current project to date (project start → today)
  • Date field used: Depends on metric (creation date vs completion date vs status change date — see individual metric definitions above)
  • Timezone: Project timezone (set in General Settings)

What's next​