Skip to main content

Reporting on Resource Requests

Track how resource requests are created, resolved, and distributed across your team using the Resource Requests report.

Updated this week

The Resource Requests report gives you a dedicated view into how requests flow through your team: how many are opened, how quickly they're resolved, and who's handling them.

To create one, go to Reports, open the + Report dropdown, and select Resource Requests as the data source.

Available Fields

The following fields are available in the Resource Requests report:

  • Title — the name of the request

  • Status — current state of the request (e.g. open, resolved)

  • Creator — who submitted the request

  • Closed by — who resolved the request

  • Date created — when the request was submitted

  • Date closed — when the request was closed or canceled

  • ID — resource request ID

  • Time to close — calculated time between creation and resolution

  • Start date / End date — the requested booking period

  • Time — requested hours

  • Service — the service the request is for

  • Service section — the section that service belongs to

  • Client — the client associated with the request

  • Project — the project the request is linked to

  • Budget / Deal — the budget or deal the request is tied to

  • Note — any notes added to the request

  • {employee_field_name} — any employee fields assigned to the person being requested (system fields like Workplace, or custom fields like Skill or Seniority)

📌 Most fields are available as both display fields and filters. Note can be added as a field but cannot be used as a filter.

What You Can Track

Request volume and resolution

Use Status and Date created to see how many requests were opened in a given period and how each resource manager is handling them.

Add Time to close to measure how quickly requests are being resolved.

📌 Example: Group by Closed by and add Time to close to compare resolution speed across resource managers.

Skills in demand

This is one of the most useful things you can do with this report. By filtering or grouping on employee fields like Skill, Seniority, or Workplace you can see which profiles are being requested most often.

📌 Example: Filter by Skill = "UI/UX Design" to see how often that profile was requested over the last quarter. If demand is consistently high, you may need to plan ahead for capacity gaps.

This works with any employee field, whether it's a built-in system field like Workplace or a custom field your organization has set up.

👉 For more on employee fields, see Employee Fields.

Did this answer your question?