Skip to main content

Exporting requisitions and recruitment metrics

How to export requisition data, recruitment metrics, and single requisition PDFs

Written by Austin Brummer

Exporting requisition lists

Users with permission can export requisition lists. A requisition export can include:

Hirers and agencies can optionally select regions and sectors in the export dialog to restrict the export to matching projects. These filters apply together with the other export selections and your existing access. Changing the selected company or companies clears the region and sector selections.

Hirers and agencies can export all requisitions within their access without choosing dates, or select both dates to narrow the export. The requisition list also offers Export filtered results, which applies its current table filters and search to the full matching result set, not only the visible page. After manually changing a table filter, this becomes the primary button. Preset filters do not trigger this switch; clearing manual filters restores the usual action.

For hirer users subject to Specific timesheet approvers, list exports, single requisition PDFs, and recruitment metrics include only accessible requisitions. Selected timesheet approvers, requisition approvers, and hiring managers can see matching requisitions within their project access. Agency access remains subject to its existing scope.

  • Core requisition data

  • Related agency response and candidate information

  • Recruitment stage history for hiring-side users

  • Activity history for each requisition

  • A submission answers sheet containing worker and whole-submission answers configured to display on requisitions, with submission and latest-edit details


​

What you see in the export

For hirers and agencies, the requisition sheet includes Sector and Region columns beside the project details. These show the names linked to the requisition's project and are blank when no value is available.

For hirers and agencies, exported start and end dates match the inclusive dates shown on the requisition. A one-day requisition has the same start and end date in the spreadsheet.

Exported data always respects the running user's access rules:

  • Company, project, supplier, and MSP scope from the user's role

  • Rate visibility — sensitive rates are hidden for users without rate access

  • Agency admin and agency user exports do not include the stage history sheet

  • Hirers can export answers from agencies within their requisition access. Agency exports include only answers belonging to the selected agency, even if another agency submitted the same worker

  • Status and date-type filters chosen in the export dialog


​

Filtering by company, status, and date type

Before exporting, choose the filters that should apply:

Hirers and agencies can select Cancelled Date in requisition list filters, exports, and custom reports. This uses the requisition’s latest recorded cancellation date. Requisitions without a recorded cancellation are excluded when a cancellation date range is applied. Reinstated requisitions can match their previous cancellation date; select the Cancelled status as well to include only currently cancelled requisitions. In list filters, Start / End Date keeps the existing requisition start and end date filtering.

  • Date range — optional for requisition exports; select both dates or leave both empty

  • Date filter type — Created Date, Approved Date, Start Date, or Cancelled Date

  • Requisition status — optional; the All option is filtered out before sending

  • Company — desk users with multiple connected companies can narrow the export to one or more connected companies


​

Exporting recruitment metrics

Recruitment metrics exports show recruitment progress across requisitions and submitted workers. Stage date columns use company-configured names and order, including custom stages. Custom stages also show days from their configured base stage, defaulting to Submitted. Default stages except Submitted also show elapsed days when the hirer explicitly selects a base in stage configuration. Changing a base recalculates elapsed days from existing history without changing standard timing metrics. Columns use the base stage’s configured name. Elapsed days are blank if the base or target date is missing, or the base occurs later. Existing recorded dates remain available for excluded stages in the configured order, even when only later submissions have recorded dates. Excluded stages without recorded dates are omitted. Current stage uses the configured name. Timing metrics keep their standard definitions. Metrics can include:

The export includes the original requisition created date and the latest reopened date. Time to fill uses the reopened date for offers or accepted responses recorded on or after that reopening; earlier fills retain the original creation-date baseline. Each later reopening replaces the latest reopened date, while reopening events remain in the activity log. Hirers can export these metrics; agencies can review the reopened date on requisitions they can access.

  • Supplier and worker details

  • Current recruitment stage and stage dates

  • Review and assignment timing, interview request-to-booking time, booking-to-interview time, and time to withdrawal

  • A Withdrawal summary sheet with worker submission counts, recorded withdrawal counts, and withdrawal percentage. A submission is counted once if it has a dated withdrawal stage, even if it later moves to another stage

  • Rejection information


​

Recruitment metrics filters and limits

Recruitment metrics exports require dates and limit the selected range to 12 months. The scope is taken from:

  • The current project context when run from a project

  • The current company context when run from a company view

  • The company id passed into the export dialog for desk users


​

Exporting a single requisition PDF

The requisition detail page currently has no PDF export action. Use the requisition list export for an export available in the UI. A separate PDF API endpoint exists and can include:

  • High-level requisition information and status

  • Project, site, requestor, and cost code

  • Supplier responses and candidate information

  • Comments and activity

  • Assignment details


​

Daily quota for bot users

Company bot users are subject to a daily export quota:

  • When the quota is exceeded, the export endpoints return an empty payload with a daily-quota message

  • The quota does not apply to standard interactive users

  • Worth knowing about when integrations call the export endpoints on a schedule

Did this answer your question?