Skip to main content
Below we list the available export types. Some export types are configurable and can be configured in the TechWolf’s Console via the export builder or by your TechWolf representative. If no configuration options are specified, this export type is not configurable. When no configuration is specified by the user, the default settings are used.

​
Employee Info

Provides an overview of all Employees and their fields, including their current position, organisational unit, and data availability status.
The Employee info export provides an overview of all Employees and their fields.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Employee.There is a header row present with the following values, indicating the contents of every column (in order):Currently supported configurations are:
  • Mask external_id: mask the Employee’s external ID to protect privacy.
  • Include Custom Properties: the selected Custom properties will be added as a column to every row. If the Employee does not have this Custom Property, the field will be empty.
Entity Relationships:

​
Job Info

Provides an overview of all Jobs and their fields, including Job Family information, data availability status, and active status.
The Job info export provides an overview of all Jobs and their fields.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Job.There is a header row present with the following values, indicating the contents of every column (in order):Currently supported configurations are:
  • Include Custom Properties: the selected Custom properties will be added as a column to every row. If the Job does not have this Custom Property, the field will be empty.
Entity Relationships:

​
Course Info

Provides an overview of all available Courses, including their titles and source systems.
The Course info export provides an overview of all the available Courses.The CSV or XLSX contains one row for every Course.There is a header row present with the following values, indicating the contents of every column (in order):Currently supported configurations are:
  • include_course_description: when enabled, adds a course_description column to every row containing the description of the Course. Defaults to false.
Entity Relationships:

​
Vacancy Info

Provides an overview of all available Vacancies, including their job titles and optionally job descriptions.
The Vacancy info export provides an overview of all the available Vacancies.The CSV or XLSX contains one row for every Vacancy.There is a header row present with the following values, indicating the contents of every column (in order):Currently supported configurations are:
  • include_job_description: when enabled, adds a job_description column to every row containing the description of the Vacancy. Defaults to false.
Entity Relationships:

​
Course Skill Profiles (Course to Skill)

Maps the relationship between Courses and their associated Skills, showing which Skills are taught in each Course.
The Course Skill Profile export provides an overview of all the Skills of every Course.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Skill of every Course, with Courses without Skills not being represented.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Vacancy Skill Profiles (Vacancy to Skill)

Maps the relationship between Vacancies and their associated Skills, showing which Skills are inferred from each Vacancy’s job title and description.
The Vacancy Skill Profile export provides an overview of all the Skills of every Vacancy.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Skill of every Vacancy, with Vacancies without Skills not being represented.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Employee Skill Profiles (Employee to Skill)

Maps the relationship between Employees and their Skills, including validation states and sources of skill inference.
The Employee Skill Profile export provides an overview of all the Skills of every Employee.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - one or more rows for every Skill of every Employee (every Skill has one row for each of its sources if it has any, and one row otherwise), with Employees without Skills not being represented.The matrix has six columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Include rejected Skills.
Entity Relationships:

​
Job Skill Profiles (Job to Skill)

Maps the relationship between Jobs and their required Skills, including skill types, validation states, and proficiency levels.
The Job Skill Profile export provides an overview of all the Skills of every Job. Note that only the governed Skill Profiles are taken into account, not the suggested Skill Profiles.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - one or more rows for every Skill of every Job (every Skill has one row for each of its Skill types), with Job without Skills not being represented.The matrix has the following columns for every row (in order).
Entity Relationships:

​
Skill Info

Provides comprehensive information about all Skills, including descriptions and their location in the Taxonomy. Note: This export will be updated on November 1st. From then on, the columns marked as [deprecated*] will not be part of the export anymore. To still receive Taxonomy information, the Taxonomy Info export can be used.
The Skill info export provides an overview of all Skills and their description. For Skills that are part of the Taxonomy, the location in the Taxonomy is also provided.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill.The matrix has ten columns, containing the following fields for every row (in order):
Entity Relationships:

​
Taxonomy Info

Provides the full Taxonomy structure, listing every placement of Skills across domains, subdomains, and clusters.
The Taxonomy info export provides the full Taxonomy structure.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - one row for every Skill-Taxonomy assignment.The matrix has eleven columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set include_business_relevant: when set to true, the business_relevant column is included in the export. When set to false, the column is omitted.
Entity Relationships:

​
Task Info

Provides an overview of all Tasks, including their name, AI impact assessment, and position in the work taxonomy.
The Task info export provides an overview of all Tasks.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Task.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Employee to Task

Maps the relationship between Employees and their Tasks, including validation states.
The Employee to Task export provides an overview of all the Tasks of every Employee.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Task of every Employee, with Employees without Tasks not being represented.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Employee Task to Skill

Maps the relationship between Employee Tasks and their associated Skills, showing which Skills are linked to each Task for every Employee.
The Employee Task to Skill export provides an overview of the Skills linked to every Task of every Employee.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Skill of every Task of every Employee, with Employees or Tasks without linked Skills not being represented.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Job to Task

Maps the relationship between Jobs and their Tasks, including validation states.
The Job to Task export provides an overview of all the Tasks of every Job.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Task of every Job, with Jobs without Tasks not being represented.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Job Task to Skill

Maps the relationship between Job Tasks and their associated Skills, showing which Skills are linked to each Task for every Job.
The Job Task to Skill export provides an overview of the Skills linked to every Task of every Job.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Skill of every Task of every Job, with Jobs or Tasks without linked Skills not being represented.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Employee AI Goals

Provides an overview of AI Goals generated for every Employee, including all historical versions. One row per AI Goal version per Employee.
The Employee AI Goals export provides an overview of the AI development goals for every Employee, written to employee_ai_goals.csv.The CSV or XLSX represents a two-dimensional matrix, containing one row for every version of every Employee’s AI Goal. Each row is uniquely identified by the (employee_id, version) pair.There is a header row present with the following values, indicating the contents of every column (in order):This export type requires the Work Intelligence feature, and additionally requires AI Goals to be enabled on the tenant. If Work Intelligence is enabled but AI Goals is not, the export type is listed but generation will fail.Currently supported destinations are SFTP, Visier and Crunchr.
Entity Relationships:

​
Employee Skill Gap

Shows the match score between Employees and their assigned positions, helping identify Skill gaps.
The Employee Skill Gap export provides an overview of the match score between Employees and their assigned position.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Employee-Job match.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
Entity Relationships:

​
Employee Skill Gap Explained

Provides detailed analysis of Skill gaps between Employees and their positions, including adjacent Skills and alignment scores.
The Skill Gap Explained export provides a detailed information of the match score between Employees and their assigned positions, including adjacent Skills and how closely they align with the required Skills for their assigned position.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill for every Employee-Job match.The matrix has 6 columns (10 if matching with skill properties is enabled), containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
Entity Relationships:

​
Internal Mobility

Shows potential matches between Employees and Jobs within the organisation, with match scores.
The internal mobility export provides an overview of potential matches between Employees and Jobs within the organisation, with their match score. It contains both the best matching Employees for each Job and the best matching Jobs for each Employee. Only active Jobs and Employees are included in the export. When matching Employees for a Job, Employees that have this Job assigned are excluded from the results. When matching Jobs for an Employee, the Employee’s current Job is excluded from the results.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Employee-Job match.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
Entity Relationships:

​
Internal Mobility Explained

Provides detailed analysis of potential matches between Employees and Jobs, including Skill-level comparisons.
The internal mobility explained export provides an overview of potential matches between Employees and Jobs within the organisation, including adjacent Skills and how closely they align with the required Skills for the job. This export contains both the best matching Employees for each Job and the best matching Jobs for each Employee. Only active Jobs and Employees are included in the export. When matching Employees for a Job, Employees that have this Job assigned are excluded from the results. When matching Jobs for an Employee, the Employee’s current Job is excluded from the results.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill of every Employee-Job match.The matrix has 6 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
Entity Relationships:

​
Matching Employees for Job

Shows the best suited Employees for every Job within the organisation, with match scores.
The Matching Employees for Job export provides an overview of the best suited Employees for every Job within the organisation, with their match score. Only active Jobs and Employees are included in the export. The Employees that have the Job assigned are excluded from the results.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Employee-Job match.The matrix has 3 columns (4 if proficiency matching is enabled), containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Employees with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Employees are shown for each Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set include_overqualified: when set to true, includes matches where the Employee is overqualified for the Job. Overqualified matches are those where the Employee’s skill level significantly exceeds the requirements. Default is true. This filter will only work if proficiency matching is enabled on the tenant.
  • Set min_critical_skills_match_ratio: the minimum ratio of critical skills that must be matched. Only matches meeting or exceeding this ratio will be returned. When null, no critical skills ratio filtering is applied. Required range: 0 ≤ x ≤ 1. This filter will only work if criticality matching is enabled.
  • Set exclude_low_data_available_entities: when set to true, Employees with low data availability are excluded from the matching results.
  • Set mapping_filter: only keep rows where Employee and Job Custom Properties match the configured mapping.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Employees for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Employees for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all Employees for which the list Custom Property does not contain the Custom Property of the Job.
Entity Relationships:

​
Matching Employees for Job Explained

Provides detailed analysis of the best suited Employees for every Job within the organisation, including Skill-level comparisons.
The Matching Employees for Job Explained export provides an overview of the best suited Employees for every Job within the organisation, including adjacent Skills and how closely they align with the required Skills for the job. Only active Jobs and Employees are included in the export. The Employees that have the Job assigned are excluded from the results.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill of every Employee-Job match.The matrix has 6 columns (10 if matching with skill properties is enabled), containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Employees with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Employees are shown for each Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set include_overqualified: when set to true, includes matches where the Employee is overqualified for the Job. Overqualified matches are those where the Employee’s skill level significantly exceeds the requirements. Default is true. This filter will only work if proficiency matching is enabled on the tenant.
  • Set min_critical_skills_match_ratio: the minimum ratio of critical skills that must be matched. Only matches meeting or exceeding this ratio will be returned. When null, no critical skills ratio filtering is applied. Required range: 0 ≤ x ≤ 1. This filter will only work if criticality matching is enabled.
  • Set exclude_low_data_available_entities: when set to true, Employees with low data availability are excluded from the matching results.
  • Set mapping_filter: only keep rows where Employee and Job Custom Properties match the configured mapping.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Employees for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Employees for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all Employees for which the list Custom Property does not contain the Custom Property of the Job.
Entity Relationships:

​
Matching Jobs for Employee

Shows the best suited Jobs for every Employee within the organisation, with match scores.
The Matching Jobs for Employee export provides an overview of the best suited Jobs for every Employee within the organisation, with their match score. Only active Jobs and Employees are included in the export. The Employee’s current Job is excluded from the results.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Employee-Job match.The matrix has 3 columns (4 if proficiency matching is enabled), containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Jobs with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Jobs are shown for each Employee. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set include_overqualified: when set to true, includes matches where the Employee is overqualified for the Job. Overqualified matches are those where the Employee’s skill level significantly exceeds the requirements. Default is true. This filter will only work if proficiency matching is enabled on the tenant.
  • Set min_critical_skills_match_ratio: the minimum ratio of critical skills that must be matched. Only matches meeting or exceeding this ratio will be returned. When null, no critical skills ratio filtering is applied. Required range: 0 ≤ x ≤ 1. This filter will only work if criticality matching is enabled.
  • Set exclude_low_data_available_entities: when set to true, Jobs with low data availability are excluded from the matching results.
  • Set mapping_filter: only keep rows where Employee and Job Custom Properties match the configured mapping.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Jobs for which the Custom Property is not equal to the Custom Property of the Employee.
    • Custom Property is in filter: filter out all Jobs for which the list Custom Property does not contain the Custom Property of the Employee.
Entity Relationships:

​
Matching Jobs for Employees Explained

Provides detailed analysis of the best suited Jobs for every Employee within the organisation, including Skill-level comparisons.
The Matching Jobs for Employee Explained export provides an overview of the best suited Jobs for every Employee within the organisation, including adjacent Skills and how closely they align with the required Skills for the job. Only active Jobs and Employees are included in the export. The Employee’s current Job is excluded from the results.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill of every Employee-Job match.The matrix has 6 columns (10 if matching with skill properties is enabled), containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Jobs with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Jobs are shown for each Employee. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set include_overqualified: when set to true, includes matches where the Employee is overqualified for the Job. Overqualified matches are those where the Employee’s skill level significantly exceeds the requirements. Default is true. This filter will only work if proficiency matching is enabled on the tenant.
  • Set min_critical_skills_match_ratio: the minimum ratio of critical skills that must be matched. Only matches meeting or exceeding this ratio will be returned. When null, no critical skills ratio filtering is applied. Required range: 0 ≤ x ≤ 1. This filter will only work if criticality matching is enabled.
  • Set exclude_low_data_available_entities: when set to true, Jobs with low data availability are excluded from the matching results.
  • Set mapping_filter: only keep rows where Employee and Job Custom Properties match the configured mapping.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Jobs for which the Custom Property is not equal to the Custom Property of the Employee.
    • Custom Property is in filter: filter out all Jobs for which the list Custom Property does not contain the Custom Property of the Employee.
Entity Relationships:

​
Matching source Jobs for Jobs

Shows the most relevant Jobs from which potential candidates can be hired to fill a given Job’s Skill requirements, with match scores. This helps identify which existing Jobs within your organisation could serve as talent pools for filling open positions.
The Matching source Jobs for Jobs export provides an overview of the most relevant Jobs from which potential candidates can be hired to fill a given Job’s Skill requirements for every Job within the organisation, with their match score. Only active Jobs are considered as potential source Jobs. A given Job cannot be a source Job for itself.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every match between Job and source Job.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set the score_min_threshold: only include source Jobs with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching source Jobs are shown for each Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Jobs with low data availability are excluded from the matching results.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all source Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all source Jobs for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all source Jobs for which the list Custom Property does not contain the Custom Property of the Job.
Entity Relationships:

​
Matching source Jobs for Jobs explained

Provides detailed analysis of the most relevant Jobs from which potential candidates can be hired to fill a given Job’s Skill requirements, including Skill-level comparisons. This helps identify which existing Jobs within your organisation could serve as talent pools for filling open positions.
The Matching source Jobs for Jobs explained export provides detailed analysis of the most relevant Jobs from which potential candidates can be hired to fill a given Job’s Skill requirements, including adjacent Skills and how closely they align with the required Skills. Only active Jobs are considered as potential source Jobs. A given Job cannot be a source Job for itself.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every match between Job and source Job.The matrix has 6 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set the score_min_threshold: only include source Jobs with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching source Jobs are shown for each Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Jobs with low data availability are excluded from the matching results.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all source Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all source Jobs for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all source Jobs for which the list Custom Property does not contain the Custom Property of the Job.
Entity Relationships:

​
Matching target Jobs for Jobs

Shows the most relevant Jobs to which Employees in a Job can be moved based on Job Skill requirements for each Job of the organisation, with match scores. This helps identify potential career paths for Employees currently in specific Jobs.
The Matching target Jobs for Jobs export provides an overview of the most relevant Jobs to which Employees in a Job can be moved based on Job Skill requirements for each Job of the organisation, with their match score. Only active Jobs are considered as potential target Jobs. A given Job cannot be a target Job for itself.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every match between Job and target Job.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set the score_min_threshold: only include target Jobs with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching target Jobs are shown for each Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Jobs with low data availability are excluded from the matching results.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all target Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all target Jobs for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all target Jobs for which the list Custom Property does not contain the Custom Property of the Job.
Entity Relationships:

​
Matching target Jobs for Jobs explained

Provides detailed analysis of the most relevant Jobs to which Employees in a Job can be moved based on Job Skill requirements for each Job of the organisation, including Skill-level comparisons. This helps identify potential career paths for Employees currently in specific Jobs.
The Matching target Jobs for Jobs Explained export provides an overview of the most relevant Jobs to which Employees in a Job can be moved based on Job Skill requirements for each Job of the organisation, including adjacent Skills and how closely they align with the required Skills. Only active Jobs are considered as potential target Jobs. A given Job cannot be a target Job for itself.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every match between Job and target Job.The matrix has 6 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set the score_min_threshold: only include target Jobs with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching target Jobs are shown for each Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Jobs with low data availability are excluded from the matching results.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all target Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all target Jobs for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all target Jobs for which the list Custom Property does not contain the Custom Property of the Job.
Entity Relationships:

​
Matching Jobs by Tasks

Shows the most relevant Jobs to each Job based on the Tasks they share, with match scores. Unlike the Skill-based Job matching exports, this export compares Jobs on their Task profiles, making it useful for task-based role design and internal mobility.
The Matching Jobs by Tasks export provides the top task-based matching Jobs for every Job within the organisation, with their match score. The score is symmetric: a single score is returned per Job pair. Because the result limit is applied per source Job, both the (A, B) and (B, A) rows can appear if both Jobs rank each other within their limit. Only active Jobs are included in the results. A given Job cannot match itself.This export is part of TechWolf’s Work Intelligence offering and requires Work Intelligence to be enabled on the tenant.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every match between Job and matching Job.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set the max_matches_per_entity: limit how many matching Jobs are shown for each source Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all matching Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all matching Jobs for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all matching Jobs for which the list Custom Property does not contain the Custom Property of the Job.
These are the only filter types this export accepts. Matching is automatically restricted to active Jobs (the is_active filter is applied for you), so is_active is not a configurable filter here.
Entity Relationships:

​
Matching Jobs by Tasks explained

Provides a per-Task breakdown of the task-based Job-to-Job matches, showing for each Job pair which Tasks contributed to the match and which Tasks had no sufficiently similar counterpart. This helps explain why two Jobs are considered task-relevant to each other.
The Matching Jobs by Tasks explained export expands every Job pair from the Matching Jobs by Tasks export into one row per Task per direction. Because the match is symmetric, each pair is evaluated in both directions: source_to_target covers the Tasks on the source Job (job_id) matched against the target Job, and target_to_source covers the Tasks on the target Job (target_job_id) matched against the source Job. A Task is marked present when it has a sufficiently similar Task on the other side (its adjacent Task), or missing when it does not. Only active Jobs are included, and a given Job cannot match itself.This export is produced from the same matching call as the Matching Jobs by Tasks export (it uses response_format=explained), so both files describe the same Job pairs.This export is part of TechWolf’s Work Intelligence offering and requires Work Intelligence to be enabled on the tenant.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Task on either side of every Job pair.The matrix has 10 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Set the max_matches_per_entity: limit how many matching Jobs are shown for each source Job. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all matching Jobs for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all matching Jobs for which the Custom Property is not equal to the Custom Property of the Job.
    • Custom Property is in filter: filter out all matching Jobs for which the list Custom Property does not contain the Custom Property of the Job.
These are the only filter types this export accepts. Matching is automatically restricted to active Jobs (the is_active filter is applied for you), so is_active is not a configurable filter here.
Entity Relationships:

​
Matching Vacancies for Employee

Shows the best suited Vacancies for every Employee within the organisation, with match scores.
The Matching Vacancies for Employee export provides an overview of the best suited Vacancies for every Employee within the organisation, with their match score. Only active Vacancies and Employees are included in the export.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Employee-Vacancy match.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Vacancies with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Vacancies are shown for each Employee. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Vacancies with low data availability are excluded from the matching results.
  • Weights: configure weights to influence the matching score. Supported weights are skills_match, desired_functions, and geo_distance (with full_score_distance and zero_score_distance parameters).
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Vacancies for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Vacancies for which the Custom Property is not equal to the Custom Property of the Employee.
    • Custom Property is in filter: filter out all Vacancies for which the list Custom Property does not contain the Custom Property of the Employee.
Entity Relationships:

​
Matching Vacancies for Employee Explained

Provides detailed analysis of the best suited Vacancies for every Employee within the organisation, including Skill-level comparisons.
The Matching Vacancies for Employee Explained export provides an overview of the best suited Vacancies for every Employee within the organisation, including adjacent Skills and how closely they align with the required Skills for the Vacancy. Only active Vacancies and Employees are included in the export.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill of every Employee-Vacancy match.The matrix has 6 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Vacancies with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Vacancies are shown for each Employee. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Vacancies with low data availability are excluded from the matching results.
  • Weights: configure weights to influence the matching score. Supported weights are skills_match, desired_functions, and geo_distance (with full_score_distance and zero_score_distance parameters).
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Vacancies for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Vacancies for which the Custom Property is not equal to the Custom Property of the Employee.
    • Custom Property is in filter: filter out all Vacancies for which the list Custom Property does not contain the Custom Property of the Employee.
Entity Relationships:

​
Matching Employees for Vacancy

Shows the best suited Employees for every Vacancy within the organisation, with match scores.
The Matching Employees for Vacancy export provides an overview of the best suited Employees for every Vacancy within the organisation, with their match score. Only active Vacancies and Employees are included in the export.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Employee-Vacancy match.The matrix has 3 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Employees with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Employees are shown for each Vacancy. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Employees with low data availability are excluded from the matching results.
  • Weights: configure weights to influence the matching score. Supported weights are skills_match, desired_functions, and geo_distance (with full_score_distance and zero_score_distance parameters).
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Employees for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Employees for which the Custom Property is not equal to the Custom Property of the Vacancy.
    • Custom Property is in filter: filter out all Employees for which the list Custom Property does not contain the Custom Property of the Vacancy.
Entity Relationships:

​
Matching Employees for Vacancy Explained

Provides detailed analysis of the best suited Employees for every Vacancy within the organisation, including Skill-level comparisons.
The Matching Employees for Vacancy Explained export provides an overview of the best suited Employees for every Vacancy within the organisation, including adjacent Skills and how closely they align with the required Skills for the Vacancy. Only active Vacancies and Employees are included in the export.The CSV or XLSX represents a two-dimensional matrix, containing - besides the header row - a row for every Skill of every Employee-Vacancy match.The matrix has 6 columns, containing the following fields for every row (in order):Currently supported configurations are:
  • Mask employee_id: mask the Employee’s external ID to protect privacy.
  • Set the score_min_threshold: only include Employees with a match score above this threshold, higher values mean stricter matching. When not set, the default is used.
  • Set the max_matches_per_entity: limit how many matching Employees are shown for each Vacancy. Higher numbers give you more options but significantly increases data size. When not set, the default limit is used.
  • Set exclude_low_data_available_entities: when set to true, Employees with low data availability are excluded from the matching results.
  • Weights: configure weights to influence the matching score. Supported weights are skills_match, desired_functions, and geo_distance (with full_score_distance and zero_score_distance parameters).
  • Filters: add custom filters on Custom Properties to further refine the results. We currently support 3 types of filters:
    • Custom Property filter: filter out all Employees for which the given Custom Property does not match the condition defined by an operator and a value.
    • Custom Property equal filter: filter out all Employees for which the Custom Property is not equal to the Custom Property of the Vacancy.
    • Custom Property is in filter: filter out all Employees for which the list Custom Property does not contain the Custom Property of the Vacancy.
Entity Relationships:

​
Market Info

Shows the configuration of peer groups and their member companies.
The Market info export provides an overview of the different peer groups that are configured, and which companies are in each peer group. A peer group consists of a list of companies used to create external market Skill Profiles for Jobs.The CSV or XLSX represents a two-dimensional matrix, containing one row for every company of every peer group.There is a header row present with the following values, indicating the contents of every column (in order):
Entity Relationships:

​
Market Skill Profiles (Market to Skill)

Shows the Skills required by companies in different peer groups for each Job.
The Market Skill Profiles export provides an overview of all Skills required by the companies in the different peer groups, for every Job.The CSV or XLSX represents a two-dimensional matrix, containing one row for every market Skill of every Job-peer group combination, with Job-peer group combinations without market Skills not being represented.The matrix has four columns, containing the following fields for every row (in order)
Entity Relationships:

​
Market Comparison

Shows alignment scores between Jobs and their peer group market Skill Profiles, in both directions.
The Market Comparison export provides an overview of alignment scores between Jobs and their peer group market Skill Profiles, including both Job to market (how well the Job covers peer requirements) and market to Job (how well peers cover Job requirements) alignment scores.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Job-peer group combination.The matrix has four columns, containing the following fields for every row (in order):
Entity Relationships:

​
Market Comparison Explained

Provides detailed analysis of alignment between Jobs and peer group Skill Profiles, including Skill-level comparisons.
The Market Comparison Explained export provides detailed alignment analysis between Jobs and their peer group market Skill Profiles, including comprehensive breakdowns of how well Job Skill Profiles match peer requirements and vice versa, with detailed Skill-level comparisons and gap analysis.The CSV or XLSX represents a two-dimensional matrix, containing one row for every Skill of every Job-peer group combination.The matrix has eight columns, containing the following fields for every row (in order):
Entity Relationships: