Resource managers are responsible for reviewing incoming resource requests and deciding how (or if) they should be fulfilled.
Productive supports this process by:
Suggesting suitable people based on request criteria
Showing availability directly on the Resource Timeline
Enabling discussion in the request feed before resolving the request
π Note: Only users with the Resolve resource requests permission can approve or reject requests. Other actions, like viewing or commenting, depend on your individual permissions. See the full guide on resource request permissions here.
Accessing Resource Requests
Resource requests are available from the main navigation:
Resourcing > Resource Requests
This opens a dedicated resource requests screen
Resource Requests Screen
Default View
Pending requests: Shows all pending requests, grouped by project
Custom Views
Like other areas in Productive, you can customize this screen using:
Additional fields
Filters
Grouping
π Tip: Create a Closed requests view to quickly access your Resolved, Rejected, and Canceled requests. Custom views like these can be saved, reused, and marked private or public.
Reviewing a Request
Each row represents a single resource request.
Clicking a row opens the Resource Timeline with the request details shown in a read-only sidebar (on the right):
Request details: Company, Budget, Service, Requested date range, Requested allocation, and Maximum cost per hour
Requested person profile: Employee and custom field details, note
Booking dates: Originally match the request, but are adjustable here
Suggested people are filtered and sorted based on request parameters (on the left).
β
Finding People on the Resource Timeline
How Matching Works
People are filtered using an OR condition across selected fields. People are automatically sorted by best fit first. For each person, youβll see:
A fit indicator (for example, 4/4 = perfect match)
βA tooltip explaining missing parameters if the match is partial
β
Assigning Preview Bookings
In the timeline, youβll see a purple preview booking representing the request. Preview bookings:
Do not affect real capacity
Can be adjusted or removed freely
Help you compare multiple options and capacity
π Tip: Right-click the preview booking to quickly duplicate or split it. Splitting creates two bookings based on where you click, making it faster to test different allocation options.
β
Creating Assignments
When resolving a request, you can create one or multiple assignments (bookings) if needed:
Select one or more people (dropdown includes fit indicators)
βDefine period and allocation for each assignment
β
π All assignments appear as preview capacity (requested) until the request is resolved.
Resolving Actions
At the bottom of the request sidebar, resource managers can take action on the request.
Resolve
When you select Resolve:
The request status changes to Resolved
All preview assignments are converted into real bookings
π Important: Approved requests create bookings, but assigned users may not automatically be included in the budget.
Project managers and resource managers should make sure that all booked users are added to the relevant budget or deal. This ensures their time can be tracked against the correct services.
At the moment, Productive allows bookings to be created for users who arenβt explicitly included in the budget/deal, which can cause issues with time tracking.
You can add a user either directly from the booking (using the violet Add button) or via the sharing options on the budget or a deal.
Additional Actions for Pending Requests
For pending requests, open the three-dot menu in the upper right to access the options described below.
1) Edit: Available only when the person reviewing the request is also its creator. Opens the request input screen, where you can edit request details, copy the request, or cancel it.
π Resolved or rejected requests canβt be edited, and you canβt edit requests created by other users.
β
2) Reject: Rejects the request and allows you to add a reason.
π The requester will need to submit a new request if changes are required.
3) Delete: Permanently removes the request from the system.
π Resolved requests cannot be deleted.
Feed (Communication and History)
Each resource request includes a feed that keeps a record of:
Status changes
βComments and discussion (mentioning users will notify them automatically)
β





















