Contingent Hiring - Exceptions to Standard Behavior

Important information regarding the behavior of specific features if used with contingent hiring.

Feature	Exception
Sourcing and posting	For contingent requisitions, sourcing is achieved exclusively through invitations sent to agents. There is no direct posting to career sections. This is because contingent hiring process relies on the association between a worker and an agent, and such association is requested at all time to correctly support contingent. To be able to invite an agent, the agent must be associated to an agency portal.
Matching candidates	Although matching candidates is allowed, matching a non-contingent candidate to a contingent requisition will generate a worker without an associated agent.  This situation, which is probably an exception, can be corrected by adding the agent once the candidate is matched. Matching a contingent worker to a non-contingent requisition is also allowed, but can generate surprises to those workers since they might start to receive direct correspondences if they have an email in their candidate file (for example, invitations to complete their file and overwrite values entered originally by the agent). This should be considered carefully to avoid generating surprises to candidates. This might also look as an attempt to bypass the agent if this was not discussed previously.
Number of positions	For a contingent requisition, the start date and end date are managed within the requisition. As such, all positions of a single requisition will always have the same rate boundaries and start and end dates. If different boundaries are needed, different requisitions must be created.
Resume parsing	Resume parsing can be used within the agency portal.  It can also be used by sending attachments through emails. However, if the agent sending the email is associated to a portal without a general profile flow, the system will not be able to parse the attachment. This is because all email based parsing is profile based and never for a specific job. This is why there is a standard message template that informs agents associated to a portal without a profile flow that if they ever send a resume to the [e-mail] address, the email parsing is not supported for them. If a profile flow is active, then all standard parsing responses might be triggered.  The message template is named Resume Parsing Service Unavailable to Agents. This message is triggered when the profile flow is not activated in the agency portal associated with the agent.
Offer module	The offer module can be used with contingent hiring, although conceptually, the interaction between the organization and the candidate is done by the agent, thus the offer module, meant to serve as a contractual agreement between the candidate and the organization, is not the natural path. While most standard fields and user-defined fields can be made available for contingent specific offers, the contingent-specific fields such as Start Date, End Date, Start Time, End Time and Staffing Agency Hourly Rate are not available in the offer module. This aligns to the original design of contingent and is the current expected behavior.
Agency with both Staffing and Contingent Staffing services	When both the Staffing and Contingent Staffing services are selected for a specific agency, the system will act as contingent or not based on the requisition where the candidate is submitted. But if the agents associated to such agencies are submitting new candidates as general profiles - through either a profile flow or resume parsing by email - then the system will consider those candidates as non-contingent candidates. It is recommended to have only job-specific application flows when agencies serving both contingent and non contingent are required. If an agent associated to a contingent only agency is submitting a candidate profile, then the ownership delay of the contingent definition will be applied.
Hiring contingent candidates	In order to hire a candidate on a contingent requisition, the candidate must be associated to an agent. All candidates submitted through the agency portal will get such association. However, candidates created manually, matched to a contingent requisition or imported might not have such agent association at first and it must be added before being able to hire the candidate on any contingent requisition.