odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/hr/recruitment/schedule_interviews.md

@@ -0,0 +1,319 @@
+---
+title: "Schedule interviews"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/recruitment/schedule_interviews.html"
+---
+
+===================
+# Schedule interviews
+
+Schedule in-person, virtual, and phone interviews with Odoo through the *Recruitment* app.
+
+An interview can be scheduled in one of two ways: either by the :ref:`recruitment team
+<recruitment/schedule_interviews/recruitment-scheduled>`, or by the :ref:`applicant
+<recruitment/schedule_interviews/applicant-scheduled>`.
+
+.. _recruitment/schedule_interviews/recruitment-scheduled:
+
+# Recruitment team scheduled interviews
+
+When an applicant reaches the interview stage, the recruitment team should schedule the interview,
+by first coordinating a suitable date and time with the applicant and interviewers.
+
+To schedule the interview, navigate to the applicant's card, by first going to the
+:menuselection:`Recruitment app`, and clicking the relevant job card. This opens the
+:guilabel:`Applications` page for that job position. Then, click the desired applicant's card to
+view their detailed applicant form.
+
+To schedule an phone, virtual, or in-person interview, click the :guilabel:`No Meeting` smart button
+at the top of the applicant's record.
+
+> **note**:
+>    The *Meetings* smart button displays :guilabel:`No Meeting` if no meetings are currently
+   scheduled. For applicants who are new to the :guilabel:`First Interview` stage, this is the
+   default.
+
+   If there is one meeting already scheduled, the smart button displays *1 Meeting*, with the date
+   of the upcoming meeting beneath it. If more than one meeting is scheduled, the button displays
+   *Next Meeting*, with the date of the first upcoming meeting beneath it.
+
+Clicking the *Meetings* smart button loads a calendar, showing the scheduled meetings and events
+for the currently signed-in user, as well as the employees who are listed under the
+:guilabel:`Attendees` section, located to the right of the calendar.
+
+To change the currently loaded meetings and events being displayed, uncheck an attendee whose
+calendar events are to be hidden. Only the checked attendees are visible on the calendar.
+
+.. image:: schedule_interviews/calendar.png
+   :align: center
+   :alt: The calendar view, highlighting how to change the displayed meetings.
+
+To add a meeting to the calendar when in the *Day* or *Week* view, click on the start time of the
+meeting and drag down to the end time. Doing so selects the date, time, and the length of the
+meeting.
+
+A meeting can also be added in this view by clicking on the desired day *and* time slot.
+
+Both methods cause a :ref:`New Event <recruitment/schedule_interviews/event-card>` pop-up window to
+appear.
+
+.. _recruitment/schedule_interviews/event-card:
+
+## New event pop-up window
+
+Clicking a grid, corresponding with the time and date, opens the :guilabel:`New Event` pop-up window
+to schedule a meeting.
+
+Enter the information on the form. The only required fields to enter are a title for the meeting,
+along with the :guilabel:`Start` (and end date/time) fields.
+
+Once the card details are entered, click :guilabel:`Save & Close` to save the changes and create the
+interview.
+
+After entering in a required name for the meeting, the fields available to modify on the
+:guilabel:`New Event` card are as follows:
+
+- :guilabel:`Meeting Title`: enter the subject for the meeting. This should clearly indicate the
+  purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the
+  applicant's card.
+- :guilabel:`Start`: start and end date and times for the meeting. Clicking either of these fields
+  opens a calendar pop-up window. Click :guilabel:`Apply` to close the window.
+- :guilabel:`All Day`: tick the box to schedule an all-day interview. If this box is ticked, the
+  :guilabel:`Start` field changes to :guilabel:`Start Date`.
+- :guilabel:`Attendees`: select the people who should attend the meeting. The default employee
+  listed is the person who created the meeting. Add as many other people as desired.
+- :guilabel:`Videocall URL`: if the meeting is virtual, or if there is a virtual option available,
+  click :icon:`fa-plus` :guilabel:`Odoo meeting`, and a URL is automatically created for the
+  meeting, which populates the field.
+- :guilabel:`Description`: enter a brief description in this field. There is an option to enter
+  formatted text, such as numbered lists, headings, tables, links, photos, and more. Use the
+  powerbox feature, by typing a `/` to reveal a list of options.
+
+  Scroll through the options and click on the desired item. The item appears in the field, and can
+  be modified. Each command presents a different pop-up window. Follow the instructions for each
+  command to complete the entry.
+
+### More options
+
+To add additional information to the meeting, click the :guilabel:`More Options` button in the
+lower-right corner of the :ref:`New Event <recruitment/schedule_interviews/event-card>` pop-up
+window. Enter any of the following additional fields:
+
+- :guilabel:`Duration`: this field auto populates based on the :guilabel:`Start` (and end) date and
+  time. If the meeting time is adjusted, this field automatically adjusts to the correct duration
+  length. The default length of a meeting is one hour.
+- :guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a
+  first interview), tick the checkbox next to :guilabel:`Recurrent`. Several additional fields
+  appear when this is enabled:
+
+  - :guilabel:`Timezone`: using the drop-down menu, select the :guilabel:`Timezone` for the
+    recurrent meetings.
+  - :guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`,
+    :guilabel:`Yearly`, or :guilabel:`Custom` recurring meetings. If :guilabel:`Custom` is selected,
+    a :guilabel:`Repeat Every` field appears beneath it, along with another time frequency parameter
+    (:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or :guilabel:`Years`). Enter a number
+    in the blank field, then select the time period using the drop-down menu.
+  - :guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is selected in the
+    :guilabel:`Repeat` field. Choose the day the weekly meeting falls on.
+  - :guilabel:`Day of Month`: configure the two drop-down menu options to select a specific day of
+    the month, irrespective of the date (e.g. the first Tuesday of every month). To set a specific
+    calendar date, choose :guilabel:`Date of Month` and enter the calendar date in the field (e.g.
+    `15` to set the meeting to occur on the fifteenth of every month).
+  - :guilabel:`Until`: using the drop-down menu, select when the meetings stop repeating. The
+    available options are :guilabel:`Number of repetitions`, :guilabel:`End date`, and
+    :guilabel:`Forever`. If :guilabel:`Number of repetitions` is selected, enter the number of
+    total meetings to occur in the blank field to the right. If :guilabel:`End date` is selected,
+    specify the date using the calendar pop-up window, or type in a date in a XX/XX/XXXX format.
+    :guilabel:`Forever` schedules meetings indefinitely.
+
+- :guilabel:`Location`: enter the location for the meeting.
+- :guilabel:`Tags`: select any tags for the meeting using the drop-down menu, or add a new tag by
+  typing in the tag and clicking :guilabel:`Create "tag"`. There is no limit to the number of tags
+  that can be used.
+- :guilabel:`Appointment`: if an appointment is associated with this meeting, select it from the
+  drop-down menu, or create a new appointment by typing in the appointment name, then clicking
+  :guilabel:`Create & Edit...` from the resulting drop-down men. A :guilabel:`Create Appointment`
+  form loads. Enter the information on the form, then click :guilabel:`Save & Close`.
+- :guilabel:`Privacy`: select if the organizer appears either :guilabel:`Available` or
+  :guilabel:`Busy` for the duration of the meeting. Next, select the visibility of this meeting,
+  using the drop-down menu to the right of the first selection. Options are :guilabel:`Public`,
+  :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone
+  to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the
+  meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see
+  the meeting.
+- :guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the
+  drop-down menu to change the selected employee.
+- :guilabel:`Reminders`: select a reminder from the drop-down menu. Default options include
+  :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a
+  specific time period before the event (hours, days, etc). The chosen reminder chosen alerts the
+  meeting participants of the meeting, via the selected option at the specified time. Multiple
+  reminders can be selected in this field.
+
+.. image:: schedule_interviews/new-event.png
+   :align: center
+   :alt: A new meeting card with all the details populated, and ready to save.
+
+## Send meeting to attendees
+
+Once changes have been entered on the :ref:`New Event <recruitment/schedule_interviews/event-card>`
+pop-up window, and the meeting details are correct, the meeting can be sent to the attendees, via
+email or text message, from the expanded event form (what is seen when the :guilabel:`More Options`
+button is clicked on in the :guilabel:`New Event` pop-up window).
+
+To send the meeting via email, click the :icon:`fa-envelope` :guilabel:`Email` button next to the
+:guilabel:`Attendees` field on the expanded meeting form.
+
+A :guilabel:`Contact Attendees` email configurator pop-up window appears. A pre-formatted email,
+using the default :guilabel:`Calendar: Event Update` email template, populates the email body field.
+
+The followers of the job application, as well as the user who created the meeting, are added as
+:guilabel:`Recipients` by default. If needed, add the applicant's email address to the list to send
+the email to the applicant, as well. Make any other desired changes to the email. If an attachment
+is needed, click the :guilabel:`Attachments` button, navigate to the file, then click
+:guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`.
+
+.. image:: schedule_interviews/email-event.png
+   :align: center
+   :alt: Enter the information to send the event via email.
+
+To send the meeting via text message, click the :icon:`fa-mobile` :guilabel:`SMS` button next to
+the :guilabel:`Attendees` field on the expanded meeting form. A :guilabel:`Send SMS Text Message`
+pop-up window appears.
+
+At the top, a blue banner appears if any attendees do not have valid mobile numbers, and lists how
+many records are invalid. If a contact does not have a valid mobile number listed, click
+:guilabel:`Close`, and edit the attendee's record, then redo these steps.
+
+When no warning message appears, type in the message to be sent to the attendees in the
+:guilabel:`Message` field. To add any emojis to the message, click the :icon:`oi-smile-add`
+:guilabel:`(smile add)` icon on the right-side of the pop-up window.
+
+The number of characters, and amount of text messages required to send the message (according to
+GSM7 criteria) appears beneath the :guilabel:`Message` field. Click :guilabel:`Put In Queue` to have
+the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send
+the message immediately.
+
+.. image:: schedule_interviews/send-sms.png
+   :align: center
+   :alt: Send a text message to the attendees of the meeting.
+
+> **note**:
+>    Sending text messages is **not** a default capability with Odoo. To send text messages, credits
+   are required, which need to be purchased. For more information on IAP credits and plans, refer to
+   the :doc:`../../essentials/in_app_purchase` documentation.
+
+.. _recruitment/schedule_interviews/applicant-scheduled:
+
+# Applicant scheduled interviews
+
+By default, the recruitment interview stages are **not** set up for applicants to schedule their own
+interviews.
+
+However, if the :guilabel:`First Interview` or :guilabel:`Second Interview` stages are modified to
+send the :guilabel:`Recruitment: Schedule Interview` email template when an applicant reaches that
+stage, the applicant receives a link to the recruitment team's calendar, and can schedule the
+interview on their own. The recruitment team's availability is reflected in the calendar.
+
+In order for applicants to be able to schedule their own interviews, a :ref:`stage must first be
+modified <recruitment/schedule_interviews/modify-stage>` in the *Recruitment* app.
+
+.. _recruitment/schedule_interviews/modify-stage:
+
+## Modify stage
+
+To modify either the :guilabel:`First Interview` or :guilabel:`Second Interview` stage, first
+navigate to the main :menuselection:`Recruitment` app dashboard. Next, click on the desired job card
+to navigate to the :guilabel:`Applications` page for that job position.
+
+Hover over the name of the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears in the
+upper-right hand side of the stage name. Click the :icon:`fa-cog` :guilabel:`(gear)` icon, and a
+drop-down menu appears. Then, click on the :guilabel:`Edit` option, and an :guilabel:`Edit: (Stage)`
+form appears.
+
+.. image:: schedule_interviews/edit-stage.png
+   :align: center
+   :alt: The drop-down that appears after clicking the cog.
+
+The :guilabel:`Email Template` field is blank, by default. Using the drop-down menu, select
+:guilabel:`Recruitment: Schedule interview` for the :guilabel:`Email Template` field, then click
+:guilabel:`Save & Close` when done.
+
+.. image:: schedule_interviews/interview-template.png
+   :align: center
+   :alt: The Recruitment: Schedule Interview email template populating the Email Template field.
+
+## Send email
+
+After either the :guilabel:`First Interview` or :guilabel:`Second Interview` stages are
+:ref:`modified to send the <recruitment/schedule_interviews/modify-stage>` :guilabel:`Recruitment:
+Schedule interview` email to the applicant upon moving their applicant card to one of those stages,
+the following email is received by the applicant:
+
+`Subject: Can we plan an interview together for your (Job Position) application?`
+
+`Congratulations!
+Your application is really interesting and we'd like to plan an interview with you.
+Can you please use the button below to schedule it with one of our recruiters?`
+
+`Plan my interview`
+
+## Schedule interview
+
+When the applicant received the email, they click the :guilabel:`Plan my interview` button at the
+bottom of the email. This navigates the applicant to a private online scheduling page, which is
+**only** accessible through the emailed link.
+
+This page displays the :guilabel:`MEETING DETAILS` on the right side of the screen. This includes
+the format and length of the meeting. In this example. the interview is virtual
+(:icon:`fa-video-camera` :guilabel:`Online`) and the duration is a half hour (:icon:`fa-clock-o`
+:guilabel:`30 minutes`).
+
+First, if there is an option of who to meet with, the user selects who they are scheduling their
+meeting with, by clicking on their icon and name. If only one person is available to interview the
+applicant, this step is not available. If the applicant does not wish to chose an interviewer, they
+can just click :guilabel:`See all availabilities` :icon:`fa-arrow-right`.
+
+.. image:: schedule_interviews/select-interviewer.png
+   :align: center
+   :alt: The first screen seen after clicking 'Plan my interview', where the applicant selects their
+         interviewer.
+
+> **note**:
+>    If the applicant selects an interviewer, the applicant is shown a :guilabel:`Select a date &
+   time` page, and **only** sees the dates and times that specific person is available. In addition,
+   that interviewer's information (name, email, and phone number) appears on the right-side of the
+   screen, under the heading :guilabel:`OPERATOR`, located beneath the :guilabel:`MEETING DETAILS`.
+
+   If the applicant clicks :guilabel:`See all availabilities` :icon:`fa-arrow-right` instead, or if
+   there are no interviewer options available, the user is navigated to the same :guilabel:`Select a
+   date & time` page, but there is no :guilabel:`OPERATOR` section visible.
+
+Then the applicant clicks on an available day on the calendar, signified by a square around the
+date. Once a day is selected, they click on one of the available times to select that date and time.
+
+.. image:: schedule_interviews/select-date-time.png
+   :align: center
+   :alt: The calendar screen with dates and times to schedule an interview.
+
+> **tip**:
+>    Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to ensure it is set to the
+   correct time zone. Changing the time zone may alter the available times presented.
+
+Once the date and time are selected, the applicant is navigated to an :guilabel:`Add more details
+about you` page. This page asks the applicant to enter their :guilabel:`Full name`,
+:guilabel:`Email`, and :guilabel:`Phone number`. The contact information entered on this form is how
+the applicant is contacted to remind them about the scheduled interview.
+
+When everything is entered on the :guilabel:`Add more details about you` page, the applicant clicks
+the :guilabel:`Confirm Appointment` button, and the interview is scheduled.
+
+.. image:: schedule_interviews/confirmation.png
+   :align: center
+   :alt: The confirmation page with all the details for the interview displayed.
+
+After confirming the interview, the applicant is taken to a confirmation page, where all the details
+of the interview are displayed. The option to add the meeting to the applicant's personal calendars
+is available, through the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda`
+buttons, beneath the interview details.
+
+The applicant is also able to cancel or reschedule the interview, if necessary, with the
+:guilabel:`Cancel/Reschedule` button.

package/payload/skills/odoo18-docs/references/docs/applications/hr/recruitment/source_analysis.md

@@ -0,0 +1,86 @@
+---
+title: "Source analysis reporting"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/recruitment/source_analysis.html"
+---
+
+=========================
+# Source analysis reporting
+
+Reporting is a critical tool used by recruiting departments to gain insights into the entire
+recruitment process.
+
+Determining where applicants come from can provide information about which sources have the best
+results. This information is determined by the *Source Analysis* report. With this data, recruitment
+teams can better pivot their recruiting strategies to gain better applicants, in both quantity and
+quality.
+
+# Open report
+
+To access the *Source Analysis* report, navigate to :menuselection:`Recruitment app --> Reporting
+--> Source Analysis`.
+
+This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days Applicant`, in a default
+:icon:`fa-area-chart` :guilabel:`(Graph)` view, showing the amount of applicants by
+:guilabel:`Source`, and further separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)
+
+Hover the cursor over any column to view the specific numbers fort that column.
+
+.. image:: source_analysis/source-analysis.png
+   :align: center
+   :alt: The default bar chart of the source analysis information.
+
+To view more details, view the :guilabel:`Source Analysis` report in a pivot table. To do so, click
+the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The data is presented in
+a pivot table, with rows populated by job positions, and columns populated stages.
+
+# Source effectiveness report
+
+To identify which sources (e.g., job boards, social media, employee referrals, company website)
+produce the most hires, the pivot table view of the :guilabel:`Source Analysis` report can be
+configured to display further details.
+
+To expand this chart to show what specific sources the applicants came from, click the
+:icon:`fa-plus-square` :guilabel:`Total` box above the columns, to reveal a drop-down menu, and
+click :guilabel:`Source`.
+
+Each column is then grouped by the source, such as: :guilabel:`Search engine`, :guilabel:`Facebook`,
+:guilabel:`Newsletter`, etc. Each source displays a separate count for :guilabel:`Applicant`,
+:guilabel:`Hired`, and :guilabel:`Refused`.
+
+This information, as presented, makes it difficult to view the specific numbers for each source.
+Click the :icon:`fa-exchange` :guilabel:`(Flip axis)` icon, to swap the information. After that, the
+rows represent the source, and the columns represent the job positions, further divided by stage.
+
+.. image:: source_analysis/source-pivot.png
+   :align: center
+   :alt: The axes flipped in the source analysis report, in pivot table view.
+
+In this view, the total number of applicants, hired employees, and refused applicants, are displayed
+for each source, as well as for each stage by job position.
+
+## Medium
+
+Viewing the medium for the applicants can be beneficial to see which specific medium is more
+successful.
+
+*Mediums* are the specific methods the applicant used to discover and then apply for job positions,
+such as organic search, paid search, social media ad, email, etc.
+
+To further group the results by medium, click into one of the :icon:`fa-plus-square`
+:guilabel:`[Source]` rows. Click :guilabel:`Medium` in the resulting drop-down menu. The row
+presents the specific mediums, relevant to that specific source.
+
+Once :guilabel:`Medium` is selected for one source, clicking into another row automatically reveals
+the specific metrics for the mediums for that source.
+
+.. image:: source_analysis/medium.png
+   :align: center
+   :alt: The sources rows, expanded to also show the medium for each source.
+
+> **note**:
+>    The only mediums that appear for a source, are mediums that have been set on an applicant's form.
+   If a medium has **not** been set for any applicants, the medium does not appear in the drop-down
+   rows beneath the source.
+
+   For example, if no applicants applied with the medium *Google Adwords*, that medium does **not**
+   appear beneath the *Search engine* source row.

package/payload/skills/odoo18-docs/references/docs/applications/hr/recruitment/team_performance.md

@@ -0,0 +1,96 @@
+---
+title: "Team performance reporting"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/recruitment/team_performance.html"
+---
+
+==========================
+# Team performance reporting
+
+The *Team Performance* report in the **Recruitment** app shows how many applicants each recruiter is
+managing.
+
+This information is determined by the individuals populating the :ref:`Recruiter
+<recruitment/applicant-details>` field on each applicant form.
+
+# Open report
+
+To access the *Team Performance* report, navigate to :menuselection:`Recruitment app --> Reporting
+--> Team Performance`.
+
+The number of :guilabel:`In Progress`, :guilabel:`Hired`, and :guilabel:`Refused` applicants for
+each recruiter is displayed in the :icon:`fa-area-chart` :guilabel:`(Graph)` view.
+
+The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days Applicant` default
+filter, as displayed in the search bar.
+
+Hover the cursor over any column to view a popover window, displaying the specific details for that
+column.
+
+.. image:: team_performance/team-performance.png
+   :align: center
+   :alt: The default bar chart of the team performance report.
+
+## Pivot table view
+
+For a more detailed view of the information in the :guilabel:`Team Performance` report, click the
+:icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. This displays all the
+information in a pivot table.
+
+In this view, the job positions are displayed in the rows, while the columns display the total
+number of applicants. The applicants are further organized by :guilabel:`# Applicant` (in process),
+:guilabel:`# Hired`, and :guilabel:`# Refused`.
+
+The displayed information can be modified, if desired.
+
+In this example, there are 19 total applicants. Out of those 19, eight have been hired, and three
+refused.
+
+From the data presented, the :guilabel:`Experienced Developer` job position is the most successful.
+This job position has the highest number of total applicants, as well as the most hires. In
+addition, the :guilabel:`Experienced Developer` has the least amount of refused applicants.
+
+This pivot table also shows that the :guilabel:`Chief Executive Officer` position is the hardest to
+fill, as it has the fewest total applicants.
+
+.. image:: team_performance/team-perf-pivot.png
+   :align: center
+   :alt: The detailed pivot table view.
+
+# Use case: recruiter performance over time
+
+One way to modify this report is to show how recruiters are performing over time. To show this
+information, begin with the :guilabel:`Team Performance` report in the :icon:`oi-view-pivot`
+:guilabel:`(Pivot)` view.
+
+Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing a
+drop-down menu. Click :guilabel:`Add Custom Group` :icon:`oi-caret-down` at the bottom of the
+:icon:`oi-group` :guilabel:`Group By` column, then click :guilabel:`Recruiter`. Click away from the
+drop-down menu to close it. Now, each row on the table represents a recruiter.
+
+.. image:: team_performance/by-recruiter.png
+   :align: center
+   :alt: The pivot table now displaying the recruiters in the rows.
+
+To compare the team's performance over different time periods, click the :icon:`fa-caret-down`
+:guilabel:`(down arrow)` in the search bar. Click :guilabel:`Start Date` :icon:`fa-caret-down` in
+the :icon:`fa-filter` :guilabel:`Filters` column, revealing various time periods to select.
+
+In this example, the desired data is the comparison between the team's performance in the third
+quarter (June - August) and the second quarter (April - July). To do so, click :guilabel:`Q3`. Once
+clicked, the current year is also ticked. In this example, it is :guilabel:`2024`.
+
+After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` column appears. Click
+:guilabel:`Start Date: Previous Period` to compare the third quarter with the second quarter, for
+the various recruiters.
+
+.. image:: team_performance/compare.png
+   :align: center
+   :alt: A comparison table of recruiter totals of Q2 and Q3.
+
+From this report, several things can be extrapolated: the total number of applicants increased, the
+number of hired applicants remained the same, while the number of refused applicants decreased.
+
+Additionally, :guilabel:`Jane Jobs` had the highest increase in number of applicants during the
+third quarter, but her number of hired applicants went down :guilabel:`67%`. The recruiter with the
+best overall numbers was :guilabel:`Rose Recruiter`, who had both their active applicants and hired
+applicants, increase in the third quarter, while their refused applicants went down.

package/payload/skills/odoo18-docs/references/docs/applications/hr/recruitment/time_in_stage.md

@@ -0,0 +1,81 @@
+---
+title: "Time in stage analysis"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/recruitment/time_in_stage.html"
+---
+
+======================
+# Time in stage analysis
+
+The *Time In Stage Analysis* report provides information on how long applicants stay in each stage
+of the recruitment process. This is important, as every job position has specific :ref:`process
+details <recruitment/new_job_position/edit>` that state the length of time applicants should expect
+to wait between specific stages.
+
+Knowing how long applicants remain in each stage can help highlight possible bottlenecks. Analyzing
+this data allows the recruitment team to assess each stage, identify any issues, and pivot their
+strategies to move applicants through each stage, within the expected time interval.
+
+# Time in stage analysis report
+
+To access the report, navigate to :menuselection:`Recruitment app --> Reporting --> Time in Stage
+Analysis`. By default, the report displays data from all job positions, with the stages populating
+the x-axis, and the number of days populating the y-axis, in a :icon:`fa-line-chart`
+:guilabel:`(Line Chart)`.
+
+The default filter is :guilabel:`Last 365 Days Applicant`, showing information for the last 365
+days.
+
+Hover over a stage in the line chart to reveal a popover window listing all the job positions within
+it, and the average number of days each job position sits in each stage.
+
+For a more visually digestible view of the information in the :guilabel:`Time In Stage Analysis`
+report, click the :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` icon in the upper-left corner. This
+displays all the information in a bar chart.
+
+In this view, it is easier to visualize the differences between the job positions, regarding how
+long applicants stay in each stage. From this view, recruiters can more easily determine which job
+positions have delays or bottlenecks at certain stages.
+
+.. image:: time_in_stage/bar-chart.png
+   :align: center
+   :alt: The bar chart view of the Time In Stage Analysis report.
+
+## Use case: comparing times by month
+
+With the :guilabel:`Time In Stage Analysis` report, it is possible to see if there are certain
+months where applicants take longer to be moved through the pipeline. To view this data, switch to
+the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view in the upper-right corner.
+
+This presents the data in a detailed pivot table, with the rows representing the different job
+positions, and the columns representing the stages. The average :guilabel:`Days in Stage` populates
+the various boxes.
+
+> **note**:
+>    If a field is empty, it indicates no applicant has been in that stage. Instead, all applicants
+   moved from a previous stage without being placed in the stage with an empty field.
+
+.. image:: time_in_stage/time-pivot.png
+   :align: center
+   :alt: The pivot table view of the Time In Stage Analysis report.
+
+Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position rows to collapse the
+information. Next, click :icon:`fa-plus-square` :guilabel:`Total` again, revealing a drop-down menu.
+Click :guilabel:`Add Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing
+further grouping options. Click :guilabel:`Start Date` from the expanded list.
+
+After doing so, the data presented is grouped with the various months from the previous 365 days for
+the rows, leaving the :guilabel:`Days In Stage` as the columns.
+
+.. image:: time_in_stage/time-dates.png
+   :align: center
+   :alt: The pivot table showing the months averages for times in stage.
+
+In this example, :guilabel:`July 2024` had the longest time that applicants spent in each stage, on
+average. In addition, the :guilabel:`Contract Proposal` stage had the longest wait time in July,
+with an average of :guilabel:`31.62` days in that stage.
+
+While this report does not display the reasons applicants stayed in the various stages for these
+lengths of time, it can be helpful to know when delays occur.
+
+.. seealso::
+   :doc:`Essentials reporting documentation <../../essentials/reporting>`