Resource requests
A resource request is a unit of demand against a project. It captures "this project needs N consultants in role X with skill Y, for these dates." Requests are how sales hands off to staffing, and how staffing finds the right people.
Where resource requests fit
Resource requests sit between Projects and Candidate search:
- A project may have multiple resource requests: different roles, different time windows, sometimes split across teams.
- A resource request describes the demand; staffing fills it by attaching candidates.
- Once a candidate is confirmed on a request, it becomes a booking that shows up in the Resource Plan.
Working with resource requests
- Connecting Resource Requests to Projects: link sales demand to the delivery side.
- Candidate search: find the consultants who can fill the request, by skill, role, and availability.
- Generating CVs for Resource Requests: batch CV generation tailored to the request.
- Comments: discuss a request with collaborators directly inside the request.
- Grouping the request list: group the requests by project, status or another column.
Sizing a request: candidates or person days
A request states how much work it needs in one of two ways. Which one applies is a company-wide setting, so every request in your tenant is sized the same way.
By default a request is sized in Requested candidates: it asks for a number of people. decídalo sets the request to Done as soon as that many candidates hold a confirmed booking on it.
If your company sizes work in effort rather than head count, an administrator can switch on Fulfil resource requests by person days in Administration > System settings > Feature settings. The request is then sized in Person days, and decídalo sets it to Done once the person days of its confirmed bookings reach the requested person days. One consultant confirmed for 100 person days closes a 100 person-day request; five consultants confirmed for 20 person days each close it just as well.
While the setting is on:
| What changes | Effect |
|---|---|
| Requested candidates | Hidden everywhere: the request grid, the create dialog, the request overview, the request drawer and the project's Resource requests tab. |
| Person days | Becomes a required field when you create or edit a request. |
| Done | Reached by confirmed person days instead of by confirmed head count. |
| Soft booked / Reserved / Confirmed candidates | Still shown. Only the requested head count disappears. |
Note: A request whose Person days are empty or zero is never set to Done automatically. Fill in the person days so the request can close.
Switching the setting on or off applies to new fulfilment checks only. Requests that are already Done keep their status, and open requests are not re-evaluated until their next booking changes.
Note: The setting takes effect for a user the next time they sign in.
Following progress on a project
A project's Resource requests tab lists the requests raised for that project. Alongside the dates it shows how much of each request is already covered:
| Column | Description |
|---|---|
| Person days | The effort the request asks for. Editable directly in the grid. |
| Soft booked candidates, Soft booked person days | Covered by soft bookings. |
| Reserved candidates, Reserved person days | Covered by reservations. |
| Confirmed candidates, Confirmed person days | Covered by confirmed bookings. |
Note: Confirmed person days counts every confirmed booking, including bookings of users who have since been deactivated. The automatic Done check leaves those out, so a request can show its full person days in this column and still stay open.
Select a candidate count to open the candidates behind it, the same way the main resource request grid does. You can filter and sort on all of these columns.
Related scenarios
- Respond to an RfP or fill a resource request: the end-to-end flow from request to staffed proposal.
- Plan resources across a team: the broader staffing view that resource-request fulfillment feeds into.
See also
- Glossary: Resource Request, Booking, Soft Booking, Confirmed Booking.