Employment process/Application notification, Prospective employee upper bound condition, Application steps confirmation, Application steps change request

This is a business process for job offers; from recruitment of part-timers and the employees through interviews upto informal job offers.

After informal decision, a prospective employee receives a formal job offer approved by in-house circular. (Not covered in this business process.)

Summary

 * 1) The deirector of demand section registers demands for part-timers and the employee expected to be hired.
 * 2) The person in charge of recruitment confirms demands.
 * 3) The person in charge registers the application steps, and confirms the director of demand section the application beginning.
 * 4) The person in charge accepts the applicant, and executes the interview.
 * 5) The person in charge registers the informally appointed worker.

(note)You repeat this process from the applicant's acceptance to the registration of the informally appointed worker of the interview until number of informally appointed workers becomes reachs the limit.

Participant

 * Demand section(any-section@company.com)
 * Director(any-section-leader@company.com)
 * Personnel(personnel@company.com)
 * Person in charge of recruitment(personnel-person@company.com)
 * Applicant(someone@general.com)

Process owner
Person in charge of personnel(personnel-person@company.com)

The person in charge of recruitment is often responsible for the process of the recruitment steps and the recruitment interview.

Advantage

 * The grasp of the application activity is easy.
 * It is easy to understand the present number of applications and the informally appointed worker because recruitment beginning is notified thoroughly.

Disadvantage

 * Delay of informal job worker decision
 * The person in charge can't start the task of the final decision until informal job workers reach the fixed number. Therefore, there is a possibility for delay of the procedure after job offers.
 * Unnecessary Change in application steps by an operation mistake
 * There is sometimes a change in the application steps of Suggestions for content of application steps and Change request of application steps after it enters application period. Therefore, there is a possibility of executing unnecessary Change in application steps when Change request of application steps is kept Necessity in Change request of application steps after it enters application period.

Feature

 * Confirmation of application steps
 * Depend on medium for applying (Web site and information magazine, etc), there are expenses.In that case, The demand section might bear the budget.
 * Therefore, it is necessary to sometimes confirm the content of the application steps including cost.

this is a business process in which cost-effectiveness ratio is good because of there is an Confirmation of application steps unlike Employment process/Application notification, Prospective employee upper bound condition.


 * Revision of application
 * The applications might don't apply for them, expections are disappointed. The person in charge increase of budget and other application steps and increases the application in this case. The application steps can be revision according to the number of applications.

Process diagram and process data
digraph developing_capability { compound=true; graph [size="10,8",rankdir=LR]; node [shape=box, style=rounded]; edge [color="#444444", labelfloat=true]; //label text float OFF(=true) subgraph clusterl{ labeljust=l; label="any-section-leader@company.com(Director of demand section)"; LX [label="", shape=circle, width="0.3"]; L1 [label="L1:Recruitment demand registration"]; L2 [label="L2:Application steps confirmation"]; L3 [label="L3:Interview result confirmation"]; LX -> L1 [weight=10]; L1 -> L2 -> L3 [style=invis]; } subgraph clusterp { labeljust=l; label="personnel-person@company.com(Person in charge of personnel)\n\n\n\n\n\n\n"; P1 [label="P1:Recruitment demand confirmation"]; P2 [label="P2:Recruitment application steps registration"]; P3 [label="P3:Interview result registration"]; PY [label="", shape=circle, width="0.3",style=bold]; P1 -> P2 [arrowtail=rcrowlvee]; P2 -> P3 [arrowtail=rcrowlvee, label="Approval"]; P3 -> PY [arrowtail=odiamond, label="Number of those who informal decision upper bound\nAchievement",minlen=2]; } subgraph clusters { labeljust=l; style=dotted; label="someone@general.com(Applicant)"; S1 [label="S1:Interview application \n (E-mail/Web form etc)",style="dotted,rounded"]; } LX -> P1 [style=invis,weight=20]; L1 -> P1 [weight=10,tailport=sw,headport=nw]; P1 -> L1 [arrowtail=odiamond, label="Requirement correction necessity",weight=10]; P2 -> L2 [arrowtail=odiamond, label="No input \n orRejection \n orChange request having"]; L2 -> P2 [tailport=sw,headport=nw]; S1 -> P3 [style=dotted]; P3 -> L3 [arrowtail=rcrowlvee, label="Number of those who informal decision upper bound\nUnderachievement"]; L3 -> P3 [arrowtail=rcrowlvee, headport=nw,tailport=sw]; L3 -> P2 [arrowtail=odiamond, label="Application steps\nChange request", tailport=w]; }


 * (note)The split achieve/underachive in P3:Intervew result registration depends on Number of demands and Number of informal decisions.


 * (note) The reason why P3-L3 of “Number of informally appointed workers” and “Informally appointed worker's information” is RW(Read and Write) is because this sample Process corresponds to the case in which the director changes number of recruitment.


 * (note) The attribution of Request of change of steps of adoption's applying is RW. This is because the manager is supposed to sets Request unnecessary of application method change in L2:Application steps confirmation.