Average Time To Fill metric for Recruiting Subject Areas - Target: 20C

Craig Stevens

Description

There is no way to accurately determine the time it takes to fill or complete the job requisition lifecycle.  Only metric available is Average Time since creation (which grows daily as the end date is current date)  At 20A - Recruiters were given the ability to put a job requisition into suspension.  This should stop any clock or bucket from accumulating days.  it does not.  There needs to be a normalized metric to determine the average time a job requisition spends in OPEN to when that opening is FILLED that does not account/add any time spent in SUSPENDED status.

Would be nice to have the following: Day's in Suspended Status

A formula could be written to start the clock with Date Job Req Opened minus Date Offer Accepted (now need to pull in two fields as this important date got split out); then take this result and minus Days in Suspended Status.  

Without the ability to account for # of days a Job Req spends in Suspended status, there is no accurate way to determine how long an opening is actually being worked on by Recruitment.

Use Case and Business Need

Without the ability to account for # of days a Job Req spends in Suspended status, there is no accurate way to determine how long an opening is actually being worked on by Recruitment - thus giving inaccurate metics.

More details

we are not able to provide the organization a realistic account of time to fill.

We can see dates in the UI - under the progression tab - but not able to report out on those.

New fields - such as Job Req Open Date and Date Moved to HR are not fully incorporated into the subject areas to allow for meaningful metrics.

Original Idea Number: dcb86e8fad

Mark Jayson Tamaray

We have the same requirement. Did Oracle already addressed this concern? Thanks

Ahmed Maher K.

Good idea.

LipLooi

We also have the same requirements not to count the days during the suspension. I saw the idea is marked as planned, is there any timeline for the update?

Craig Stevens

@LipLooi

@Mark Jayson Tamaray

I am not aware of any timeline on when this might be added to the system. I've received nothing from Oracle on the idea and was surprised to see that it was marked as Planned. We've had to develop a long formula to attempt to make this concept work in our pod.

Raghavendra Raghunath-Oracle

Hi @Craig Stevens

1. If a requisition has been in suspended state multiple time during its lifecycle until it reaches the filled state, you want to have the cumulative suspended duration? I think the answer is yes, but wanted to confirm
2. Do you plan to use this(requisition suspended duration) in conjunction with the candidate's application lifecycle also? i.e. to determine the time taken for an application to confirm till it reaches the HR phase? If yes, can you provide more details?

Raghu

Craig Stevens

@Raghavendra Raghunath-Oracle

in using the suspended state duration, we're attempting to capture all the time a req has spend in a state of suspended. So if the req was approved, formated and opened in a week - then put in a suspended state for 5 days, reopened and the suspended /open cycle done again. the opening would have been suspended for a total of 10 days.

Currently any of the Facts that are available in the subject areas do not account for this total suspended duration.

Our time to fill begins when recruiting has the opening for work so it begins at approval date. the time ends when the offer has been accepted. this date difference needs to account for any suspended time. we have openings with multiple spots to fill. if the first hire takes 7 days and the second takes 14 days - then the average time to fill would be 10.5 days. if the req was suspended to 5 days, then the days should be reduced by whatever the suspended time was.

Hope that quick explanation makes sense.

Craig

Raghavendra Raghunath-Oracle

Hi Craig,

yes, this is in-line with what we were planning to incorporate.

Thanks

Raghu

LipLooi

@Raghavendra Raghunath-Oracle

Hi Raghu,

The "Suspended Duration" field has been introduced in the recent R3 upgrade.

Nonetheless, we've observed that the field only reflects the last instance of suspended days. If there are multiple suspended states, the days are not compounded.

This doesn't appear to align with the proposed initial use case. Or is this still a work in progress?

Rgds,

LipLooi

Raghavendra Raghunath-Oracle

Hi LipLooi,

thank you for testing this and reaching out to me. I think you might be missing something here. I created a similar report where a specific requisition has gone through 'suspended' state twice with different intervals. Against the requisition, the cumulative suspended duration value is displayed(the viz on top). When i bring in the event details, the duration is split . Refer the attached screenshot. Can you please try something similar at your end?

Raghu

LipLooi

Hi Raghu,

Yes! This is helpful and explains. I figured out the filter I have for the workbook cause the other suspended day not showing. Thank you so much!!

Rgds,

LipLooi