22Offer job positions
33===================
44
5- Once an applicant has successfully passed the various interview stages, the recruitment team is
6- ready to send an offer for employment. The next step is to send the applicant a contract.
5+ After an applicant has successfully passed the various interview stages, the recruitment team is
6+ ready to send an offer for employment. The first step when offering a job position is to send the
7+ applicant a contract.
78
89.. seealso ::
910 Refer to the :doc: `recruitment <../recruitment >` documentation for details on the various stages
@@ -23,89 +24,97 @@ the top-right of the applicant's form.
2324The next step is to send an offer to the applicant. Start by selecting the desired applicant's card
2425to open their applicant form.
2526
26- On the applicant's form, click the :guilabel: `Generate Offer ` button. A :guilabel: `Generate a
27- Simulation Link ` pop-up window appears.
27+ On the applicant's form, click the :guilabel: `Generate Offer ` button to load the :guilabel: `Offer
28+ for (applicant's email) ` page.
29+
30+ .. important ::
31+ If the applicant does not have an email address listed on their applicant card, an
32+ :guilabel: `Invalid Operation ` pop-up window warning appears, stating: :guilabel: `Offer link can
33+ not be send. The applicant needs to have a name and email. `
34+
35+ Click :guilabel: `Close `, then enter an email on the applicant's card. Once an email is entered,
36+ click the :guilabel: `Generate Offer ` button, and the :guilabel: `Offer for (applicant's email) `
37+ page loads.
2838
2939Most fields are pre-populated with information from the job position. If any necessary fields are
3040blank, or if any information needs to be updated, enter, or update, the relevant information in the
3141corresponding fields.
3242
3343.. note ::
3444 Depending on the localization setting for the company, and which applications are installed, some
35- fields may not appear in the :guilabel: `Generate a Simulation Link ` pop-up window .
45+ fields may not appear on the :guilabel: `Offer for (applicant's email) ` page .
3646
37- For example, if the *Fleet * application is **not ** installed, any fields related to vehicles do
47+ For example, if the ** Fleet * * application is **not ** installed, any fields related to vehicles do
3848 **not ** appear.
3949
4050Universal fields
4151----------------
4252
43- The following fields appear in the :guilabel: `Generate a Simulation Link ` pop-up window , regardless
44- of the localization.
53+ The following fields appear in the :guilabel: `Offer for (applicant's email) ` page , regardless of the
54+ localization.
4555
46- - :guilabel: `Contract Template `: the template currently being used to populate the
47- :guilabel: `Generate a Simulation Link ` pop-up window. Use the drop-down menu to select a different
48- :guilabel: `Contract Template `, if desired.
56+ - :guilabel: `Title `: The name for the contract appears in a default `Offer for (applicant's email) `
57+ format.
58+ - :guilabel: `Contract Template `: The template currently being used to populate the :guilabel: `Offer
59+ for (applicant's email) ` page. Use the drop-down menu to select a different :guilabel: `Contract
60+ Template `, if desired.
4961
5062 .. note ::
51- To modify the template, hover over the current template name, and click the :icon: ` oi-launch `
52- :guilabel: `Internal link ` icon that appears to the right of the field. Make any desired
53- changes, then click :guilabel: `Save & Close `.
63+ To modify the template, hover over the current template name, and click the
64+ :icon: ` fa-arrow-right ` : guilabel: `( Internal link) ` icon that appears to the right of the field.
65+ Make any desired changes, then click :guilabel: `Save & Close `.
5466
55- - :guilabel: `Job Position `: the name of the :guilabel: `Job Position ` being offered to the applicant.
56- The selections available in the drop-down menu correspond to the job position configured on the
57- main *Recruitment * dashboard.
58- - :guilabel: `Job Title `: the selected :guilabel: `Job Position ` populates this field, by default.
59- The title can be modified to suit the specific applicant's position and provide more details.
67+ - :guilabel: `Employer Budget `: The salary being offered to the applicant.
68+ - :guilabel: `Job Title `: The selected :guilabel: `Employee Job ` populates this field, by default. The
69+ title can be modified to suit the specific applicant's position and provide more details.
6070
6171 .. example ::
6272 An applicant is offered a marketing manager job at a shoe company, specifically for the
6373 children's line.
6474
65- The :guilabel: `Job Position ` selected from the drop-down menu is `Marketing Manager `, and the
75+ The :guilabel: `Employee Job ` selected from the drop-down menu is `Marketing Manager `, and the
6676 :guilabel: `Job Title ` is modified for their specific responsibilities, `Marketing Manager:
6777 Children's Shoes `.
6878
69- - :guilabel: `Department `: the department the job position falls under.
70- - :guilabel: `Contract Start Date `: the date the contract takes effect. The default date is the
71- current date. To modify the date, click on the displayed date to reveal a calendar popover window.
72- Navigate to the desired month, then click the day to select the date.
73- - :guilabel: `Yearly Cost `: the annual salary being offered.
74- - :guilabel: `Link Expiration Date `: the number of days the job offer is valid. The default
75- expiration date is `30 ` days. Modify the expiration date, if desired.
79+ - :guilabel: `Employee Job `: The name of the :guilabel: `Job Title ` being offered to the applicant.
80+ The selections available in the drop-down menu correspond to the job position configured on the
81+ main **Recruitment ** app dashboard.
82+
83+ - :guilabel: `Department `: The department the job position falls under.
84+ - :guilabel: `Contract Start Date `: The date the proposed contract takes effect. The default date is
85+ the current date. To modify the date, click on the displayed date to reveal a calendar popover
86+ window. Navigate to the desired month, then click the day to select the date.
87+ - :guilabel: `Offer Create Date `: The day the offer is created, By default, the current date
88+ populates this field and *cannot * be modified.
89+ - :guilabel: `Offer Validity Date `: The last day the offer is valid. After this date the contract
90+ cannot be signed.
91+ - :guilabel: `Link `: The link to the contract being sent to the candidate.
92+ - :guilabel: `Validity Days Count `: The number of days the contract is valid. The default expiration
93+ date is `30 ` days. Modify the expiration date, if desired.
94+ - :guilabel: `Applicant `: The name of the applicant appears in this field, and cannot be modified.
7695
7796Send offer
7897----------
7998
80- Once the :guilabel: `Generate a Simulation Link ` pop-up window is complete, click :guilabel: `Send By
81- Email ` to reveal an email pop-up window.
82-
83- .. important ::
84- If the applicant does not have an email address listed on their applicant card, a warning appears
85- in a red box at the bottom of the :guilabel: `Generate a Simulation Link ` pop-up window, stating:
86- :guilabel: `The applicant does not have a valid email set. The Offer Link won't be able to be
87- completed. ` Click :guilabel: `Discard `, then enter an email on the applicant's card. Once an email
88- is entered, click the :guilabel: `Generate Offer ` button, and the email pop-up window loads again.
99+ Once all desired modifications have been made to the :guilabel: `Offer for (applicant's email) ` page,
100+ click the :guilabel: `Send By Email ` button to reveal an email pop-up window.
89101
90- The default :guilabel: `Recruitment: Your Salary Package ` email template is used (set in the
91- :guilabel: `Load template ` field), and the :guilabel: `Recipients `, :guilabel: `Subject `, and email
92- body are pre-populated based on the email template.
102+ The default `Recruitment: Your Salary Package ` email template is used, and the :guilabel: `To `,
103+ :guilabel: `Subject `, and email body are pre-populated based on the email template.
93104
94- If any attachments need to be added, click the :icon: `fa-paperclip ` :guilabel: `Attachments ` button,
105+ If any attachments need to be added, click the :icon: `fa-paperclip ` :guilabel: `(paperclip) ` button,
95106and a file explorer window appears. Navigate to the desired file, then click :guilabel: `Open ` to
96- attach it to the email. The attachment loads, and is listed above the :icon: `fa-paperclip `
97- :guilabel: `Attachments ` button.
107+ attach it to the email. The attachment loads, and is listed at the bottom of the email body.
98108
99109Once the email is ready to send, click :guilabel: `Send `. The email pop-up window closes, and an
100- :guilabel: `Offers ` smart button appears at the top of the applicant's card.
110+ :icon: ` fa-handshake-o ` : guilabel: `Offers ` smart button appears at the top of the applicant's card.
101111
102112.. note ::
103- To send an offer, ensure the *Sign * application is installed. This is necessary, so the offer can
104- be sent to the applicant by the recruiter, and they can actually sign the offer. The applicant
105- does **not ** need any software installed to sign the offer.
113+ To send an offer, ensure the ** Sign ** application is installed. This is necessary, so the offer
114+ can be sent to the applicant by the recruiter, and they can actually sign the offer. The
115+ applicant does **not ** need any software installed to sign the offer.
106116
107117.. image :: offer_job_positions/send-offer.png
108- :align: center
109118 :alt: Send an email to the applicant with a link to the offered salary.
110119
111120Configure your package
@@ -122,29 +131,29 @@ Once the applicant is hired, the personal information entered on the webpage is
122131employee record, when created.
123132
124133Once all the information is completed, the applicant can then accept the offer by clicking the
125- :guilabel: `Review Contract & Sign ` button to accept the contract, and sign it using the *Sign *
134+ :guilabel: `Review Contract & Sign ` button to accept the contract, and sign it using the ** Sign * *
126135application.
127136
137+ Management signatures
138+ ---------------------
139+
140+ Once the applicant has signed the contract, the next step is for the person responsible within the
141+ company (the :guilabel: `HR Responsible `) must then sign the contract.
142+
143+ The person responsible for signing the contract receives an activity alert that their signature is
144+ requested of them in the **Sign ** app.
145+
128146.. _recruitment/offer_job_positions/contract-signed :
129147
130148Contract signed
131149===============
132150
133- Once the applicant has accepted the offer and signed the contract, the next step is to move the
134- applicant to the :guilabel: `Contract Signed ` stage. This stage is folded in the Kanban view, by
135- default.
136-
137- To move the applicant to that stage, drag-and-drop the applicant's card to the :guilabel: `Contract
138- Signed ` stage. If the stage is not visible, click the :icon: `fa-ellipsis-h ` :guilabel: `(ellipsis) `
139- button to the right of :guilabel: `Contract Proposal ` on the applicant's form, and click
140- :guilabel: `Contract Signed ` from the resulting drop-down menu.
141-
142- Once the applicant is moved to the :guilabel: `Contract Signed ` stage, a green :guilabel: `HIRED `
143- banner appears in the top-right of the applicant's card and form.
151+ Once all parties have fully signed the contract, the applicant is automatically moved to the
152+ :guilabel: `Contract Signed ` stage, and a green :guilabel: `HIRED ` banner appears in the top-right of
153+ both the applicant's card and form.
144154
145155.. image :: offer_job_positions/hired.png
146- :align: center
147- :alt: Hired banner in the top right corner of applicant card.
156+ :alt: Hired banner in the top-right corner of applicant card.
148157
149158.. _recruitment/new-employee :
150159
@@ -159,4 +168,4 @@ An employee form appears, with information from the applicant's card, and the em
159168Fill out the rest of the employee form. For detailed information on the fields, refer to the
160169:doc: `../employees/new_employee ` documentation.
161170
162- Once completed, the employee record is saved in the *Employees * app.
171+ Once completed, the employee record is saved in the ** Employees * * app.
0 commit comments