e-Recruiting : Requisition status
Dear experts ,
Please throw some light on the following thoughts :
I can see that if the object NB has status draft,released,on hold or closed, i can assign candidates to the Requisition.
Is this the standard system behaviour? or have i missed something here.
Can someone explain the need/provision to assign candidates to a requisition when it is in status Draft, On Hold or Closed?
Thanks in advance,
Roman Weise replied
I'll give you two answers please choose which you like.
The scientific process focused one
- it is necessary to assign applicants / candidates to requisition in status draft if you want to evaluate if a publication of the requisition is necessary or if you are confident to do the hiring based on your candidate pool only. In addition assignment must be able when you are redoing requisition and posting for better applicant address or changed requirements. This also requires status draft while the exisiting hiring process has to continue.
- it is necessary to add applicants to the requisition in status closed if you have already closed it as you thought you were finished but in the last moment the candidate does not show up. Espacially combined with mass hiring where a single requisition means many positions filled this can be a valid issue (often happens with apprentices). If you use the approval process it is often very handy to not set the status back to released as it would require new approval which makes no sense.
- adding candidates in status on hold is used to put spontaneous applicants to requisitions wich soon will be open (as far as the on hold is temporary) so you do not loose a suitable candidate int the depths of the candidate pool where it gets probably lost.
The unscientific but probably true one
- if you ever would have worked in hr you would have learned that no matter what is done for process design (which is often done by organization experts of hr the other hr guys do not like) recruiter will not give a s*** about the processes. They will do what they think it is right. Process designs do not care. But to be fair this is not only caused be the hr guys but by the field of work. You can define a process which requires 2 screenings and 4 tests for hiring and still the upper management shows up with a candidate and says "hire him!". So a real process flow control in a sense of the restriction of action posibilities will fail. So the reason for the status of requisition is not to say you can assign someone or not, it is more a guideline how far the process is and to filter them in the lists. You can assign a candidate whenever you want as not recruiter would accept a stronger restriction.
Best Regards and Happy E-Recruiting