Overview

Tracks how the Resource Management module is being used and the outcomes it drives, organized across three tabs: Active Users, Engagement, and Programs & Projects Activity.

Metrics

Active Users tab

Active Users (Weekly)

Definition: Active Users (Weekly) measures the count of distinct users who performed at least one qualifying Resource Management (RM) action, tracked by week. A user is counted in a given week based on when the qualifying RM action occurred.

How it is calculated: Counts distinct user emails per week, grouped by event date.

Note:

• Drilldown available by User Type.
• Filtered by event date (event_ts).

Active Users (Monthly)

Definition: Active Users (Monthly) measures the count of distinct users who performed at least one qualifying Resource Management (RM) action, tracked by month. A user is counted in a given month based on when the qualifying RM action occurred.

How it is calculated: Counts distinct user emails per month, grouped by event date.

Note:

• Drilldown available by User Type.
• Filtered by event date (event_ts).

User Login Frequency

Definition: User Login Frequency measures how consistently each user engages with Resource Management, broken down by user and role tier (user type). Active Days counts the distinct calendar days on which a user performed at least one qualifying RM action, while Total Events counts every qualifying action recorded. Together they show both the breadth (how often a user returns) and the depth (how much they do) of usage.

How it is calculated: Active Days counts distinct calendar days per user per month. Total Events counts all qualifying actions per user per month. Both are grouped by user name and user type.

Note:

• Filtered by event date (event_ts).

Engagement tab

Demands Created

Definition: Demands Created measures the count of distinct staffing demands or resource requests created within a given time period.

How it is calculated: Counts distinct demand IDs.

Note:

• Filtered by demand creation date (demand_creation_ts).

Bookings Created

Definition: Bookings Created measures the count of distinct bookings made against staffing demands within a given time period.

How it is calculated: Counts distinct booking IDs.

Note:

• Filtered by booking creation date (created_at).

Demands Creation Trend

Definition: Demands Creation Trend tracks the count of distinct staffing demands or resource requests created, by month.

How it is calculated: Counts distinct demand IDs per calendar month, grouped by demand creation date.

Note:

• Filtered by demand creation date (demand_creation_ts).

Bookings Creation Trend

Definition: Bookings Creation Trend tracks the count of distinct bookings made against staffing demands, by month.

How it is calculated: Counts distinct booking IDs per calendar month, grouped by booking creation date.

Note:

• Filtered by booking creation date (created_at).

Monthly Trend of Employee Applications

Definition: Monthly Trend of Employee Applications measures how many times employees applied to a resourcing demand directly. Only applications with source type 'employee' are counted.

How it is calculated: Counts distinct application IDs where the application source type is 'employee', grouped by application date, monthly.

Note:

• Filtered by application date (application_ts).
• The period reflects when the application was submitted, not when the underlying demand was created.

Monthly Trend of Nominations

Definition: Monthly Trend of Nominations measures how many times a manager nominated one of their reports for a resourcing demand. Only applications with source type 'manager' are counted.

How it is calculated: Counts distinct application IDs where the application source type is 'manager', grouped by application date, monthly.

Note:

• Filtered by application date (application_ts).
• The period reflects when the nomination was submitted, not when the underlying demand was created.

Avg Match Quality

Definition: Avg Match Quality measures the average AI-generated match score among employees whose last recorded stage is 'Shortlisted' or 'Staffed', reflecting how well matched the candidates considered for staffing decisions are.

How it is calculated: Averages the match score (in stars) of employees whose last stage is Shortlisted or Staffed, rounded to two decimal places.

Note:

• Filtered by demand creation date (demand_creation_ts).

Outstanding Demands by Age

Definition: Outstanding Demands by Age measures the count of distinct demands currently in Draft or Open status, broken down by how long they have been outstanding and split by status. A demand's age bracket is the number of days between its creation date and the current date, grouped into 0–7d, 8–30d, 31–90d and 90d+. The breakdown helps identify requests that have been unresolved for extended periods.

How it is calculated: Counts distinct demand IDs in Draft or Open status, grouped by age bracket (0–7d, 8–30d, 31–90d, 90d+) and split by demand status. Age is calculated as days between creation date and today.

Note:

• Filtered by demand creation date (demand_creation_ts).

Bench Duration

Definition: Bench Duration measures the number of bench periods — the gaps between one approved booking ending and the employee's next approved booking starting. If an employee finishes an assignment with nothing else lined up, they are considered on the bench until their next booking begins. Each bench period is bucketed by how long the gap lasted: 2–7 days, 8–30 days, 31–90 days, or 90+ days, and each bar shows the number of bench periods in that range. Only approved bookings are used to calculate bench periods.

How it is calculated: Counts bench periods (gaps between consecutive approved bookings) per employee, grouped into duration buckets. Overlapping bookings are excluded.

Note:

• Filtered by the end date of the previous booking (prev_booking_end_date), so only bench periods that started in the selected time period are included.

Programs & Projects Activity tab

Programs Created

Definition: Programs Created measures the count of distinct programs that were created within a given time period.

How it is calculated: Counts distinct program IDs.

Note:

• Filtered by program creation date (org_unit_created_at).

Program Completion Rate

Definition: Program Completion Rate measures the percentage of programs that have reached full staffing, meaning every demand under the program has been staffed. Only programs with at least one demand are eligible; programs with zero demands are excluded from both the numerator and the denominator.

How it is calculated: Divides the count of programs where staffed demands equals total demands by the count of all programs with at least one demand, expressed as a percentage.

Note:

• Filtered by program creation date (org_unit_created_at).

Projects Created (RM)

Definition: Projects Created (RM) measures the count of distinct projects that were created within a given time period.

How it is calculated: Counts distinct project IDs.

Note:

• Filtered by project creation date (org_unit_created_at).

Program Creation Trend

Definition: Program Creation Trend tracks the count of distinct programs created, by month.

How it is calculated: Counts distinct program IDs per calendar month, grouped by program creation date.

Note:

• Filtered by program creation date (org_unit_created_at).

Project Creation Trend

Definition: Project Creation Trend tracks the count of distinct projects created, by month.

How it is calculated: Counts distinct project IDs per calendar month, grouped by project creation date.

Note:

• Filtered by project creation date (org_unit_created_at).

Active Programs By Booking Count

Definition: Active Programs By Booking Count shows each currently active program alongside the total number of bookings associated with it.

How it is calculated: For each active program, takes the total booking count, grouped by program name and program ID.

Note:

• Filtered by program creation date (org_unit_created_at), so the programs included are determined by when they were created.

Active Projects By Booking Count

Definition: Active Projects By Booking Count shows each currently active project alongside the total number of bookings associated with it.

How it is calculated: For each active project, takes the total booking count, grouped by project name and project ID.

Note:

• Filtered by project creation date (org_unit_created_at), so the projects included are determined by when they were created.

Program Duration Distribution

Definition: Program Duration Distribution measures how long each program is planned to run, calculated as the gap between its end date and start date, and groups programs into duration bands. Only programs with both a start date and an end date are included; a program missing either date has no duration and is excluded from every band.

How it is calculated: Counts distinct program IDs grouped by duration band (<1 year, 1–2 years, 2–3 years, 3–4 years, 4–5 years, >5 years). Duration is the number of days between start date and end date.

Note:

• Filtered by program creation date (org_unit_created_at).
• Programs missing a start or end date are excluded from all duration bands.

Project Duration Distribution

Definition: Project Duration Distribution measures how long each project is planned to run, calculated as the gap between its end date and start date, and groups projects into duration bands. Only projects with both a start date and an end date are included; a project missing either date has no duration and is excluded from every band.

How it is calculated: Counts distinct project IDs grouped by duration band (<1 year, 1–2 years, 2–3 years, 3–4 years, 4–5 years, >5 years). Duration is the number of days between start date and end date.

Note:

• Filtered by project creation date (org_unit_created_at).
• Projects missing a start or end date are excluded from all duration bands.