Meridian - Canceling Hiring Activity


Introduction

Sometimes a candidate hiring activity needs to be stopped, either because the candidate has declined the offer, U-M has decided against the candidate, or for other reasons. In these cases, using Meridian's Cancel Candidate or Cancel Hiring features will end the current workflow.

Instructions

Cancel Candidate (Dept Only)

The "Cancel Candidate" button is available to department users, and allows them to stop the workflow of a candidate and immediately 'reset' the hiring activity for the next candidate. This occurs on the same position (PID) and so is used for when Candidate A needs to be stopped and Candidate B is now being considered for hire. Example:



  • Candidate A (CID 101) declines at some point during the hiring process for PID 999
  • The department has Candidate B in mind for the same position, and wants to instead pursue hiring Candidate B
  • The department user clicks "Cancel Candidate" on Candidate A (CID 101 / PID 999)
  • Candidate A's workflow is "cancelled" (but all data is preserved) and a new workflow is immediately started, still for PID 999, allowing the department user to enter Candidate B's (CID 102) information
    • During the reset, information specific to the position (Position Approval) is copied over, while data specific to the candidate (Offer Prep, Offer Response, Candidate Prep) is not copied

Note: The position is now in a 'Cancelled' state. The data about the hiring activity for that position is still preserved but it is now only findable through a filter ("Include Cancelled") on the Hiring List page. Cancelled candidates appear as gray cards on the List page, below their active (blue) candidate for the same PID.

Cancelled State

 

Cancel Hiring (Office of Faculty Affairs (OFA) Only)

An alternative to the above is Cancel Hiring, which is when a department wants/needs to stop a hiring workflow and NOT continue hiring for that position (such as if the department lost funding for a new position). Due to the gravity of this decision, only OFA can perform this function, so the department user needs to simply contact the Office of Faculty Affairs (OFA) and request that they "cancel hiring" for a given position ID (PID). Example:

  • The department users contacts OFA and requests that hiring be canceled for PID 456
  • OFA goes to the Hiring record for PID 456 and clicks "Cancel Hiring"
  • Any and all candidate workflows on PID 456 are cancelled and the position itself is now in a "cancelled" state

Note: A cancelled position's data is still preserved in Meridian but it is now only findable through a filter ("Include Cancelled") on the Hiring List page. Cancelled candidates appear as gray cards on the List page (all cards will be gray for a given PID).


Cancelled Candidates

 

A clarification on CID, PID, and PCN:

  • CID (Candidate ID) is associated with the candidate in a Hiring workflow (changes when you 'Cancel Candidate'), like it was in prior Meridian versions.
  • PID ([Hiring] Position ID) is associated with the position in a Hiring workflow (remains intact/unchanged when you 'Cancel Candidate'), like it was in prior versions
  • PCN (Position Control Number) is the seat ID, and is now also attached to the Hiring workflow. It is related to the Hiring workflow (similar to PID, so remains intact/unchanged when you 'Cancel Candidate') but also will continue to be active as you hire additional, future faculty into that same seat

Hiring example:

  • PID 1 anticipates that Bob (CID 1) will accept; Bob rejects the offer and is replaced with Cindy, who gets CID 2 (PID is still 1)
    • PCN is 12345, for originally Bob and now Cindy
  • Cindy then joins as a faculty member for 5 years, and then leaves U-M
  • Cindy's seat (now vacant) is still PCN of 12345
  • A new Hiring workflow to replace Cindy is created, with a new PID and CID, though choosing Cindy's vacant seat of 12345 will attach that PCN to this new workflow 

'Cancel Hiring' is different, wherein it cancels both the CID and PID associated with the workflow (in fact the workflow effectively disappears / is archived), like it was in prior Meridian versions. Regarding PCN functionality, in this case the seat (PCN) will also be reset, meaning a selected vacant seat will resume being vacant, a selected New Hire plan will resume being an unused plan, etc.