Information processing method, program and information processing device

Abstract

To simply set up waiting recruitment.SOLUTION: An information processing method executes one or more processors included in an information processing device to execute: acquiring setting information related to regular recruitment from a first information processing device used by a business operator; generating waiting recruitment information for waiting recruitment for the regular recruitment information based on the setting information; and publishing the waiting recruitment information.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present disclosure relates to an information processing method, a program, and an information processing device. [Background technology]

[0002] BACKGROUND ART Conventionally, there have been systems that support recruitment, and for example, a job-seeking / recruitment matching method that allows smooth transmission and reception of information between job seekers and recruiters is known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-173293 Summary of the Invention [Problem to be solved by the invention]

[0004] For example, on a job information platform that provides temporary work, workers often work on a spot basis and can easily cancel, which can lead to vacancies. When a sudden vacancy occurs, businesses must set up new job information each time.

[0005] Therefore, one of the objectives of the present disclosure is to provide an information processing method, program, and information processing device that can easily generate job openings (also referred to as "standby job openings") in preparation for vacancies. [Means for solving the problem]

[0006] An information processing method according to one embodiment of the present disclosure includes an information processing device acquiring setting information related to regular job information from a first information processing device used by a business operator, generating waiting job information for waiting job offers for the regular job information based on the setting information, and publishing the waiting job information. [Effects of the Invention]

[0007] According to the disclosed technology, it is possible to easily set up waiting job offers. [Brief explanation of the drawings]

[0008] [Figure 1] 1A and 1B are diagrams illustrating exemplary configurations of an information processing system according to an embodiment. [Figure 2] FIG. 1 is a block diagram illustrating an example of an information processing apparatus according to an embodiment. [Figure 3] FIG. 2 is a block diagram illustrating an example of a server according to an embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of user information according to the embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of regular job information according to the embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of waiting job information according to the embodiment. [Figure 7] FIG. 10 is a diagram illustrating an example of work status information according to the embodiment. [Figure 8] FIG. 10 is a sequence diagram illustrating an example of a process related to a waiting job offer according to the embodiment. [Figure 9] 10 is a flowchart illustrating an example of a job information publishing process according to the embodiment. [Figure 10] 10 is a flowchart illustrating an example of a process related to cancellation according to the embodiment. [Figure 11] 10 is a flowchart illustrating an example of a process related to waiting according to the embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of a recruitment screen for a regular job offer according to the embodiment. [Figure 13] FIG. 2 is a diagram illustrating an example of waiting job information according to the embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a work notification according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that the same elements are denoted by the same reference numerals, and redundant description will be omitted.

[0010] [Embodiment] First, we will explain the "standby job" used in this embodiment. Standby job is different from general job and includes job formats called same-day standby or standby personnel (hereinafter collectively referred to as "standby job"). Standby job is a job that requires waiting at a specified location for a specified period of time, and is also a job that requires going to a workplace and working when a vacancy occurs. In this embodiment, when a business sets regular job information ("regular job information") on a platform that provides job information (also referred to as a "job information providing platform"), it generates standby job information ("standby job information") based on the regular job information. This eliminates the need for businesses to set standby job information separately from regular job information, allowing them to easily set standby job information.

[0011] Furthermore, on employment information platforms that offer temporary work, if a sudden vacancy occurs, businesses find it difficult to fill the vacancy even if they advertise at that time.

[0012] Therefore, in this embodiment, standby job information is generated automatically, or semi-automatically including final confirmation work, based on regular job information set by the business operator, making it easy to set up standby job information and making it possible to recruit standby job applicants in advance.As a result, when a regular job worker (also called a "regular worker") becomes vacant, the vacancy can be immediately filled with a standby job worker (also called a "standby worker").

[0013] Hereinafter, workers will be referred to as first users and businesses as second users, and when there is no distinction between the two, they may be referred to as "users." In addition, in this embodiment, a service (hereinafter also referred to as "job service") is provided that allows users to view and apply for job information provided on a job information providing platform. When there is no distinction between regular job offers and waiting job offers, they may be referred to as "job offers," and similarly, when there is no distinction between regular job offer information and waiting job offer information, they may be referred to as "job information."

[0014] <System configuration example> Fig. 1 is a diagram showing an example of each configuration of an information processing system 1 according to an embodiment. In the example shown in Fig. 1, information processing devices 10A, 10B, and 10C used by each user, an information processing device or server 20 that manages a job information providing platform, and a database 30 that manages, for example, user information, regular job information, waiting job information, and work status information of each worker are connected via a network N. Note that when any number of information processing devices 10A, 10B, and 10C are connected to the network N and are not individually distinguished, they are also referred to as information processing devices 10.

[0015] The information processing device 10 is, for example, a smartphone, a computer, or a tablet terminal. By installing an application (hereinafter also referred to as a "recruitment app") that executes the recruitment service disclosed in the embodiment, the information processing device 10 can provide the recruitment service to users. Furthermore, if the recruitment service is implemented on a web page, the information processing device 10 can also use the recruitment service using a web browser.

[0016] The information processing device 20 is, for example, a server, and may be composed of one or more devices. The information processing device 20 also manages a job information providing platform, provides job information, registers users, processes job viewing and applications, and generates waiting job information from regular job information. Hereinafter, the information processing device 20 is also referred to as the server 20.

[0017] The database 30 has a memory unit that stores or manages user information of each worker registered with the recruitment service, regular recruitment information of each business operator, waiting list recruitment information of specified businesses among the businesses, and work status information of each worker.

[0018] <Example of the configuration of the user device> 2 is a block diagram showing an example of an information processing device 10 according to an embodiment. The information processing device 10 includes one or more processing units (CPUs) 110, one or more network or other communication interfaces 120, a memory 130, a user interface 150, and one or more communication buses 170 for interconnecting these components.

[0019] The user interface 150 is, for example, a user interface including a display 151 and an input device (such as a keyboard and / or a mouse or any other pointing device) 152. The user interface 150 may also be a touch panel.

[0020] Memory 130 may be, for example, a high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory, or may be a non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory 130 may also be a non-transitory computer-readable recording medium.

[0021] Another example of memory 130 may be one or more storage devices installed remotely from CPU 110. In one embodiment, memory 130 stores the following programs, modules, and data structures related to the recruitment application, or a subset thereof.

[0022] Operating system 131, for example, handles various basic system services and includes procedures for performing tasks with the hardware.

[0023] The network communication module 132 is used, for example, to connect the information processing device 10 to other computers via one or more network communication interfaces 120 and one or more communication networks, such as the Internet, other wide area networks, local area networks, metropolitan area networks, etc.

[0024] The application data 133 includes data that is processed when a user uses a job recruitment service. For example, the application data 133 includes user information and information acquired from the server 20. Specifically, the application data 133 includes job recruitment information related to job recruitment.

[0025] The service processing module 134 executes each process in the job information providing platform provided by the server 20. For example, the service processing module 134 has an acquisition module 135, an output module 136, and a processing module 137, which will be described later. The service processing module 134 may change the processing content depending on whether the user who has logged in to the job information providing platform is a business operator or a worker. The service processing module 134 corresponds to the above-mentioned job application or web browser.

[0026] For example, information processing device 10A is a device used by a user (second user) on the business side, and information processing device 10B is a device used by a user (first user) on the worker side. In the following, the reference numeral A is attached to the reference numeral of information processing device 10A on the business side, and B is attached to the reference numeral of information processing device 10B on the worker side. In the following, an example in which processing is divided depending on the logged-in user for a job recruitment app will be described, but applications for business use and applications for workers may also be implemented separately. Note that information processing device 10C is also a device used by a user on the worker side, but as it is similar to information processing device 10B, description thereof will be omitted.

[0027] ≪Business side≫ First, each process in the information processing device 10A on the business side will be described. The acquisition module 135A acquires a user operation on a button (an example of a UI widget) in a display screen displayed on the display 151A. For example, the acquisition module 135A acquires, via the user interface 150A, a command corresponding to a click operation on a job recruitment setting button in a web page or application screen. The setting button is a button that the business uses to set recruitment conditions, etc. when recruiting.

[0028] The acquisition module 135A may also acquire a command corresponding to a click operation on a job posting setting button on a web page or an application screen via the user interface 150A. The job posting setting button is a button used when a business operator wants to set and publish job posting information.

[0029] The job information includes regular job information that is generally made available to users who have registered with the job service, and waiting job information that is made available when certain conditions are met. For example, waiting job information is made available when all the positions available for the regular job information have been filled.

[0030] The output module 136A outputs to the server 20 regular job information set by the user on the business side and a request for setting a regular job.

[0031] Processing module 137A performs processes such as setting the regular job information described above, and confirming and / or approving workers who have applied for the job information (also referred to as "applying workers"). For example, processing module 137A accepts operations by the business operator, and works in cooperation with server 20 to set individual condition information included in the regular job information, and confirm and / or approve the applying workers.

[0032] The display control module 138A controls the display of a screen of a job application or a web page. For example, the display control module 138A controls the display of a job setting screen, a confirmation screen for worker applicants, etc. on the display 151A.

[0033] <Worker side> Next, each process in the worker-side information processing device 10B will be described. The operating system 131B accesses the server 20 based on the worker's operation, and downloads and installs the recruitment application program. This makes the service processing module 134B executable.

[0034] Furthermore, service processing module 134B may be a recruitment app as described above, or may be a web browser. Service processing module 134B accesses a URL that provides a recruitment information providing platform, obtains screen information related to recruitment services from server 20 via the recruitment app, and transmits information to server 20.

[0035] The acquisition module 135B acquires user operations for each button on the display screen displayed on the display 151 B. For example, the acquisition module 135B acquires registration information set by the user operation of the worker on the user registration screen.

[0036] When the registration information of the new user is set based on the user operation, the output module 136B transmits the registration information and a new registration request to the server 20. The registration information includes, for example, the user's name, address, telephone number, etc. input by the worker. When the server 20 receives the new registration request, it performs registration processing of the new user based on the registration information.

[0037] Furthermore, when a worker performs an operation to view job information, the output module 136B outputs a view request to the server 20. Furthermore, when a worker performs an operation to apply for a job from the job information viewing screen, the output module 136B outputs an application request to the server 20.

[0038] The processing module 137B performs processing related to the recruitment service. For example, on the worker side, it has various functions such as a notification function for favorite recruitments and a message function for communicating with businesses.

[0039] Display control module 138B controls the display of the screen of the job application or web page. For example, display control module 138B controls the display of a user registration screen, a job information viewing screen, a job application screen, etc. on display 151B.

[0040] Note that one or more processing units (CPUs) 110 read and execute each module from memory 130 as necessary. For example, one or more processing units (CPUs) 110 may configure a communication unit by executing network communication module 132 stored in memory 130. Also, one or more processing units (CPUs) 110 may configure a service processing unit, an acquisition unit, an output unit, a processing unit, and a display control unit by respectively executing service processing module 134, acquisition module 135, output module 136, processing module 137, and display control module 138 stored in memory 130. Also, the processing of service processing module 134, acquisition module 135, output module 136, processing module 137, and display control module 138 may be executed by one or more processing units (CPUs) 110.

[0041] In other embodiments, service processing module 134, acquisition module 135, output module 136, processing module 137, and display control module 138 may be standalone applications stored in memory 130 of information processing device 10. Standalone applications include, but are not limited to, an acquisition application, an output application, a processing application, and a display control application. In yet other embodiments, service processing module 134, acquisition module 135, output module 136, processing module 137, and display control module 138 may be add-ons or plug-ins to another application.

[0042] Each of the above-identified elements may be stored in one or more of the aforementioned storage devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or reconfigured in various embodiments. In some embodiments, memory 130 may store a subset of the modules and data structures described above. Additionally, memory 130 may store additional modules and data structures not described above.

[0043] As described above, the business-side application and the worker-side application may be implemented as separate applications. In this case, the worker downloads and installs the worker's recruitment app program from a predetermined website or the like onto their own information processing device 10B, and the business downloads and installs the business-side recruitment app program from a predetermined website or the like onto their own information processing device 10A, thereby enabling each of them to use the recruitment app described above.

[0044] <Example of the configuration of the server-side device> 3 is a block diagram illustrating an example of a server 20 according to an embodiment. The server 20 includes one or more processing units (CPUs) 210, one or more network or other communication interfaces 220, memory 230, and one or more communication buses 270 for interconnecting these components.

[0045] The server 20 may optionally include a user interface 250, which may include a display device (not shown) and a keyboard and / or mouse (or some other input device, such as a pointing device, not shown).

[0046] Memory 230 may be, for example, a high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory, or may be a non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory 230 may also be a non-transitory computer-readable recording medium.

[0047] Additionally, another example of memory 230 may include one or more storage devices located remotely from CPU 210. In one embodiment, memory 230 stores the following programs, modules, and data structures, or a subset thereof:

[0048] Operating system 231 includes, for example, procedures for handling various basic system services and for performing tasks with the hardware.

[0049] The network communication module 232 is used, for example, to connect the server 20 to other computers via one or more network communication interfaces 220 and one or more communication networks, such as the Internet, other wide area networks, local area networks, metropolitan area networks, etc.

[0050] The user information 233 includes information about users who use the job information providing platform. For example, the user information 233 includes the user's name, address, phone number, group, etc., associated with each user ID. The group includes, for example, attributes used to group workers into predetermined categories. The user information 233 will be described later with reference to FIG. 4.

[0051] Regular job information 234 includes one or more pieces of regular job information registered in a job information providing platform or a job service. For example, regular job information 234 includes information such as a regular job ID, job offer date, working hours, business operator, work location, and hourly wage. Regular job information 234 will be described later with reference to FIG. 5.

[0052] The waiting job information 235 includes waiting job information generated based on the regular job information. For example, the waiting job information 235 includes a regular job ID, a waiting job ID, the number of waiting employees, a waiting location, a waiting time, a waiting hourly wage, public information, etc. The waiting job information 235 will be described later with reference to FIG. 6.

[0053] The work status information 236 includes a user ID, a job offer ID, a location, work dates, work hours, a salary, etc. The work status information 236 may also include an evaluation from the business operator. The work status information 236 will be described later with reference to FIG. 7. At least one of the user information 233, the regular job offer information 234, the waiting job offer information 235, and the work status information 236 may be stored in the database 30.

[0054] The service control module 237 manages processes related to recruitment and benefits in the recruitment information providing platform. For example, the service control module 237 includes an acquisition module 238, a creation module 239, a publication module 240, a payment module 241, and an output module 242 as processes related to recruitment.

[0055] When a business operator performs a setting operation related to the recruiting conditions for a regular job offer, the acquisition module 238 acquires each setting information of the regular job offer information along with a setting request for the regular job offer. For example, the acquisition module 238 acquires each setting information of the regular job offer information from a first information processing device (e.g., information processing device 10A) used by the business operator. The regular job offer information includes, for example, the date of recruitment, working hours, work location, hourly wage, etc.

[0056] The generation module 239 generates standby job information for a standby job for a regular job based on each setting information of the regular job information. For example, the generation module 239 generates, as standby job information, each setting information corresponding to attributes similar to the attributes of the regular job information based on each setting information of the regular job information. As a specific example, the generation module 239 sets the nearest station to the store where the regular job information is located as the standby location, or sets a predetermined time based on the work start time of the regular job information as the standby time of the standby job information. For example, the standby start time may be set to a time based on the work start time of the regular job information, taking into account the travel time to the work location.

[0057] The generation module 239 may generate waiting job information when instructed to generate waiting job vacancies by a business operator, or may generate waiting job information when a job placement agency sets the generation of waiting job vacancies as part of a campaign, etc. In addition, when waiting job information is generated at the instruction of a business operator, the system may collect a fee for generating waiting job vacancies from the business operator.

[0058] The publication module 240 publishes the waiting job information generated by the generation module 239. For example, the publication module 240 may publish the waiting job information to workers on a job service. Furthermore, the publication module 240 may determine whether to publish the waiting job information depending on the determination result of predetermined conditions related to the publication of the waiting job information, and publish the waiting job information to workers on the job service.

[0059] The above process makes it possible to easily set up waiting job offers. For example, when setting up regular job offers, businesses do not need to set up waiting job offers to match the required job offers. In addition, since the waiting job offers are based on the regular job offer information set by the business, appropriate waiting job offer information is generated.

[0060] Furthermore, as described above, the disclosure module 140 may disclose information about a waiting job when the disclosure conditions for the waiting job are met. For example, the disclosure module 240 determines whether the disclosure conditions are met when a predetermined event occurs, and discloses the waiting job information when the disclosure conditions are met. The disclosure conditions may be set using each piece of information included in the regular job information. As an example, the disclosure conditions may include gathering workers equal to the number of positions advertised in the regular job information.

[0061] By performing the above process, job information on waiting jobs can be published at the appropriate time, and job postings for waiting jobs can be made available. As a result, it is not necessary to publish all waiting jobs, and the processing load on the system can be reduced.

[0062] The disclosure conditions may also include at least one of the following: that the regular job information has been published and that a certain number of people have been recruited based on the number of positions advertised in the regular job information. For example, the regular job information may be made private when the publication period for the regular job information has ended or when matching with workers has been achieved for the number of positions advertised. In such cases, the disclosure module 240 may disclose the waiting job information. The disclosure module 240 may also disclose the waiting job information when matching is achieved for a certain number of people based on the number of positions advertised in the regular job information, for example, the number of positions advertised or a number obtained by adding or subtracting a certain number from the number of positions advertised.

[0063] The above process allows you to set multiple publishing conditions for waiting job openings, or to set one of multiple conditions, making it possible to flexibly publish waiting job openings.

[0064] The disclosure module 240 may also switch between public and private status for waiting job listings depending on the result of a determination of whether a disclosure condition is met, which is determined when a predetermined condition is met. For example, the disclosure module 240 may set a trigger for determining whether a disclosure condition is met as the predetermined condition. As a specific example, the disclosure module 240 may determine whether a disclosure condition is met when at least one of the predetermined conditions is met (when at least one event occurs), such as when a worker applies for or approves an application, or when a cancellation occurs during the period when a regular job listing or waiting job listing is published.

[0065] In this case, if the disclosure module 240 determines that the disclosure conditions for the regular job information or the waiting job information are met within the disclosure period of the regular job information or the waiting job information, the disclosure module 240 may make the publicly available regular job information private and make the waiting job information public. On the other hand, if the disclosure module 240 determines that the disclosure conditions for the waiting job information are not met within the disclosure period of the regular job information or the waiting job information due to cancellation by a regular worker, etc., the disclosure module 240 may make the private regular job information public and make the public waiting job information private.

[0066] The above process makes it possible to appropriately switch between publishing and non-publishing regular job information and waiting job information depending on the application status for regular job information, the number of workers matched with the number of positions available for regular job information, etc. Depending on the publication conditions, both regular job information and waiting job information may be published at the same time.

[0067] The generation module 239 may also set at least one of the number of waiting employees, waiting location, waiting time, and waiting salary corresponding to the number of employees to be recruited, work location, work start time, and salary included in each setting information of the regular job offer information. For example, the generation module 239 may set each setting information of the waiting job offer based on a determination method set in advance according to the attributes of each setting information (number of employees, location, etc.). Note that some of the information may be set by the business operator; for example, the waiting location may be set by the business operator.

[0068] As an example, the generation module 239 may set the number of waiting employees as an integer value of a predetermined percentage (e.g., 20%, 10%, etc.) of the number of employees, set the nearest station to the workplace or the workplace store, etc. as the waiting location, set a time based on the start time of work as the waiting time, and set an amount based on the salary of a regular job offer (the same amount or a different amount) as the waiting salary. The number of waiting employees may also be calculated, for example, from the work performance of past job offers (the average percentage of cancellations). The generation module 239 may also use machine learning to learn information about waiting job offers for past regular job offers as learning data, input the regular job offer information into a learning model, and output waiting job offer information.

[0069] The above process makes it possible to set appropriate setting values ​​for the corresponding attributes of the waiting job information according to the attributes of each setting information of the regular job information. Furthermore, once the regular job information is set, the generation module 239 can automatically set the waiting job information. Furthermore, the generation module 239 may also enable semi-automatic generation by allowing the business operator to confirm or, if necessary, modify the waiting job information after setting it.

[0070] The generation module 239 may also include setting the standby time to be from the work start time or the first hour before the work start time to the second hour after the work start time. For example, the generation module 239 may set the standby start time or standby end time depending on the work content (e.g., whether or not the work requires changing clothes, etc.). As a specific example, the generation module 239 may set the standby period to be from the work start time to one hour after the work start time. The second hour may also be set depending on the working hours of the regular job offer. For example, if the working hours are five hours, the second hour may be set to one hour, which is 20% of the working hours, and the size of the percentage may be changed depending on the length of the working hours.

[0071] The above processing makes it possible to set an appropriate waiting time for the salary-related waiting time of the waiting job information, and also makes it possible to set the waiting start time and waiting end time according to the work content.

[0072] The acquisition module 238 may also acquire certification information regarding at least one of the waiting location and the waiting time from the second information processing device used by the user who applied for the waiting job. The certification information may include, for example, image data indicating the waiting location and time information indicating the start time of the waiting. For example, if the waiting location is a station, the waiting worker may be asked to take an image of a signboard or the like containing the station name using the camera function of the second information processing device or the like and send the image data to the server 20. In this case, the image data may contain the image date and time as attribute information, and thus may serve as certification information indicating the waiting location and the start time of the waiting. The waiting worker may also be notified of the imaged object several hours before the waiting time. Note that location information obtained using a GPS (Global Positioning System) function installed in a smartphone or the like may be used as information indicating the waiting location. Similarly, certification information may be sent at the end time of the waiting. This makes it possible to verify whether the waiting actually took place both at the start and end of the waiting period.

[0073] In this case, the payment module 241 may execute a process of paying the standby pay to the standby worker depending on the verification result of the authentication information. For example, the payment module 241 may verify the authentication information, and if it is proven that the standby worker is at the standby location at the standby start time, the payment module 241 may pay the standby pay, and if it is not proven that the standby worker is at the standby location at the standby start time, the payment module 241 may not pay the standby pay and may further impose a penalty.

[0074] The payment module 241 implements at least one of the following methods for paying the salary: bank transfer in cash, transfer of electronic money to the user account, granting of points to the user account, etc. The payment method may be selected by the worker.

[0075] The above process makes it possible to pay wages to standby workers on the condition that they are waiting appropriately. It is also possible to prevent them from proving their waiting status based on information obtained in advance by notifying the standby worker of the image target just before they are about to wait.

[0076] The output module 242 may output information about how the waiting worker spends his or her waiting time to a second information processing device used by the waiting worker. For example, the output module 242 may output information about cafes or public facilities near the waiting location as information about how the waiting worker spends his or her waiting time, or may output part-time job information that can be handled by a smartphone or the like (e.g., questionnaire responses). An example of part-time job information includes part-time jobs based on annotations of learning data.

[0077] The above processing makes it possible to provide waiting workers with a system for spending their waiting time effectively, and to provide workers with a service that makes it easy for them to apply for waiting jobs.

[0078] Furthermore, the output module 242 may output a work notification to the second information processing device used by the user who applied for the waiting job offer, if a predetermined time has elapsed since the work start time included in the regular job offer information and the number of users equal to the number of recruited people has not started work. The predetermined time may be set by the job placement agency or the business operator.

[0079] For example, the service control module 237 manages the attendance of regular workers, and when it detects that the number of workers recruited through regular job information is not working, it identifies standby workers to make up the shortage in order of priority (e.g., in order of application). Regular worker attendance management can be performed using known technology, for example, by having the regular worker read a two-dimensional code at their workplace. The output module 242 may notify the standby workers identified by the service control module 237 that they have started work using a push notification or by automatically contacting them by phone.

[0080] The above process makes it possible to quickly notify standby workers of their availability when a regular worker becomes vacant, thereby reducing the burden on the business operator.

[0081] The output module 242 may also include outputting a work cancellation notice to a third information processing device used by a user who applied for the regular job information but has not yet started work, after a predetermined time has elapsed since the start time of work. For example, if a regular worker is late without permission and a specified time (e.g., 10 minutes) has passed since the start of work, the right to work will be transferred to a standby worker, and the regular worker will be notified that their work will be canceled.

[0082] This process makes it possible to automatically notify regular workers who have not started work within a certain amount of time from their start time of their shift that their work has been canceled, thereby preventing standby workers and regular workers from overlapping in their work schedules.

[0083] Furthermore, when regular workers equal to the number of positions advertised in the regular job information start working, the output module 242 may send a notice of the end of waiting to the second information processing device used by the waiting worker who applied for the waiting job. In this case, the payment module 241 may execute payment of wages for the time period including the time from the start of waiting to the notice of the end of waiting.

[0084] For example, the output module 242 may notify standby workers that their standby time has ended when it receives a notification that the number of regular workers equal to the number of recruited workers has started work through attendance management by the service control module 237. It is advisable to state in the standby job posting that the standby time may end before the end time of the standby time has elapsed.

[0085] In this case, the payment module 241 executes a process of paying the waiting worker a salary for the time period including at least the time from the waiting start time to the waiting end notice. The time period to be paid may be the waiting time posted in the waiting job offer, or may be the net waiting time actually spent waiting from the waiting start time to the waiting end notice.

[0086] By the above process, it is possible to notify waiting workers who no longer need to wait before the waiting end time that the waiting time has ended and release them from waiting, thereby creating a user-friendly system.

[0087] Furthermore, the generation module 239 may collectively generate waiting job information for multiple regular job offers if the work start times and work locations of the multiple regular job offers satisfy similar conditions. For example, if regular job offer A and regular job offer B have work start times within a predetermined time period and are located at the same nearest station to the work location, the generation module 239 may collectively set one waiting job offer information for regular job offer A and regular job offer B. In this case, the waiting job information may include, as work content, the possibility of working for either regular job offer A or regular job offer B. If the work start times of the multiple regular job offers are different, the generation module 239 may set the waiting start time based on the earliest work start time.

[0088] Furthermore, when a regular job offer is set by a business operator, the service control module 237 may allow the business operator to select between generating job waiting information or a cancellation waiting list. The cancellation waiting list is a service that allows registration of a cancellation waiting list when there are more applications than the number of positions available, in preparation for the possibility of cancellations during the recruitment period of the regular job offer. Note that the generation of job waiting information may be provided for a fee, while the registration of a cancellation waiting list may be provided free of charge.

[0089] Furthermore, in regard to matching between job offers and workers, if a cancellation occurs for a regular worker for a regular job offer while the waiting job information is being published, and there are waiting workers for the waiting job offer, the service control module 237 may advance the waiting workers to fill the vacant position and make them regular workers. Advancement is determined, for example, in the order of application.

[0090] In this case, if a cancellation occurs for a regular worker, and the vacancy can be filled by a standby worker, the disclosure module 240 continues to disclose the standby job information. On the other hand, if the vacancy cannot be filled by a standby worker, the disclosure module 240 may make the publicly disclosed standby job information private and resume disclosing the regular job information.

[0091] Each of the elements identified above may be stored in one or more of the storage devices described above. Each of the modules identified above corresponds to a set of instructions for performing a function described above. The modules or programs (i.e., sets of instructions) identified above need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or reconfigured in various embodiments. In some embodiments, memory 230 may store a subset of the modules and data structures identified above. Additionally, memory 230 may store additional modules and data structures not described above.

[0092] Note that one or more processing units (CPUs) 210 read and execute each module from memory 230 as necessary. For example, one or more processing units (CPUs) 210 may configure a communication unit by executing network communication module 232 stored in memory 230. Also, one or more processing units (CPUs) 210 may configure a service control unit, an acquisition unit, a generation unit, a publication unit, a payment unit, and an output unit by respectively executing service control module 237, acquisition module 238, generation module 239, publication module 240, payment module 241, and output module 242 stored in memory 230. Also, the processing of each of service control module 237, acquisition module 238, generation module 239, publication module 240, payment module 241, and output module 242 may be executed by one or more processing units (CPUs) 210.

[0093] Although Figure 3 shows "servers," Figure 3 is intended as an illustration of various features that may be present in a set of servers, rather than as a structural overview of the embodiments described herein. In practice, as will be recognized by those skilled in the art, items shown separately could be combined and certain items could be configured separately. For example, items shown separately in Figure 3 could be implemented on a single server, and a single item could be implemented by one or more servers.

[0094] The database 30 may have a configuration similar to that shown in Fig. 3. At least one of the user information 233, regular job information 234, waiting job information 235, and work status information 236 shown in Fig. 3 may be stored in the storage unit of the database 30.

[0095] <Example of data structure> FIG. 4 is a diagram showing an example of user information 233 according to an embodiment. The user information 233 manages information about each member user created by a user who uses the job recruitment service. The "user ID" includes user identification information (user ID: Identifier) ​​that allows the server 20 to uniquely identify the user. The user ID is associated with "user information."

[0096] "User information" includes personal information of the user (e.g., worker), such as "name," "address," and "telephone number." The user ID may also be associated with a "group" set by the business. The user ID may also be included as one piece of user information. The user information may also include an email address, password, etc.

[0097] FIG. 5 is a diagram showing an example of regular job information according to an embodiment. The "regular job ID" includes identification information for the regular job information. The regular job information includes information such as "job offer date," "working hours," "business operator," "work location," and "hourly wage" associated with the regular job ID. Note that while the "hourly wage" is used in the example shown in FIG. 5, "salary" calculated by multiplying the hourly wage by the working hours may also be used.

[0098] "Recruitment date" includes the date (or a specified period) when the business needs a worker. "Working hours" includes the start and end times of the worker's work on the recruitment date. "Business" includes the name of the business that has set up the recruitment information and is seeking employees. "Work location" includes at least one of the store name, location, place name, facility name, etc. where the worker will work. "Hourly wage" includes the hourly wage for the recruitment.

[0099] FIG. 6 is a diagram showing an example of waiting job information according to an embodiment. The "regular job ID" includes identification information of the regular job information that is the basis for generating the waiting job information. The "waiting job ID" includes identification information of the waiting job information. The waiting job information includes information such as "number of people waiting," "waiting location," "waiting time," "waiting hourly wage," and "disclosure conditions," associated with the regular job ID or the waiting job ID. Note that, although the "waiting hourly wage" is used in the example shown in FIG. 6, a "waiting salary" calculated by multiplying the waiting hourly wage by the waiting time may also be used.

[0100] The "number of waiting workers" includes the number of waiting workers. The number of waiting workers may be set to a default value or may be set according to the number of positions available for regular job offers. The "waiting location" includes the location where waiting workers wait. The waiting location may be set according to the work location of the regular job offer, or may be set by input by the business, etc. The "waiting time" includes the start time and end time of the waiting period for the waiting worker. The wait start time may be set according to the work start time of the regular job offer, for example, it may be set to the same time as the work start time. The wait end time may be set a predetermined time after the wait start time, for example, it may be set to one hour after the wait start time. The "standby hourly wage" includes the hourly wage of the waiting worker. For example, the "standby hourly wage" may be the same as the hourly wage of the regular job offer, or may be calculated by subtracting or adding an offset value to the hourly wage of the regular job offer. The "publication conditions" include the conditions for publicizing the waiting job information.

[0101] FIG. 7 is a diagram showing an example of work status information according to an embodiment. The "user ID" in the work status information includes user identification information. The work status information includes information such as "job offer ID," "location," "working date," "working hours," and "salary" associated with the user ID. In the example shown in FIG. 7, "salary" is used, but "hourly wage" may also be used.

[0102] "Job ID" includes identification information that identifies the matching regular job offer or standby job offer. "Location" includes the work location of the regular worker or the standby worker's standby location. "Work date" includes the day the worker worked. "Working hours" includes the working hours of the worker on the job offer date. "Hourly wage" includes the hourly wage for the job offer. In addition, work status information may include information about the "business operator" and evaluation information for the work.

[0103] <Operation description> Next, the operation of the information processing system 1 according to the embodiment will be described. Fig. 8 is a sequence diagram showing an example of processing related to a waiting job offer according to the embodiment. In the example shown in Fig. 8, the information processing device 10A is a device used by the business operator, the information processing device 10B is a device used by a regular worker, and the information processing device 10C is a device used by a waiting worker.

[0104] In step S102, the business operator's information processing device 10A transmits each setting information about the regular job information of regular job offer N to the server 20 in response to the business operator's operation on the job offer recruitment screen (e.g., FIG. 12). Each setting information about the regular job information includes working days, working hours, hourly wage, etc. (e.g., see FIG. 5).

[0105] In step S104, the acquisition module 238 of the server 20 acquires each setting information about the regular job information from the information processing device 10A, and the generation module 239 of the server 20 sets the regular job information based on each setting information.

[0106] In step S106, the generation module 239 of the server 20 generates waiting job information for a waiting job offer M for a regular job offer N based on each setting information of the regular job offer information to be set. As described above, the generation module 239 may set the waiting job information automatically or semi-automatically.

[0107] In step S108, the disclosure module 240 of the server 20 discloses the regular job information of the regular job offer N to workers who access the job service. At this time, if a disclosure time for the regular job information is set, the disclosure module 240 discloses the regular job information of the regular job offer N when the disclosure time arrives.

[0108] In step S110, when the information processing device 10B logs in and requests viewing of, for example, regular job offer N, the disclosure module 240 of the server 20 transmits regular job information for regular job offer N to the information processing device 10B.

[0109] In step S112, similarly to step S110, when the information processing device 10C logs in and requests to view, for example, regular job offer N, the disclosure module 240 of the server 20 transmits regular job information for regular job offer N to the information processing device 10C.

[0110] In step S114, when information processing device 10B accepts an application for regular job offer N in response to an operation by the worker, it requests server 20 to apply for regular job offer N.

[0111] In step S116, the service control module 237 of the server 20 matches the applied worker with the job information. For example, the server 20 notifies the business operator of the regular job offer N of the user information of the applied worker, and determines whether or not to hire the worker. The service control module 237 of the server 20 may automatically match the information of the applied worker with the job information. In this case, automatic matching may be performed if predetermined conditions, such as the age and desired working hours of the applied worker, are included in the age and working hours of the job information.

[0112] In step S118, the disclosure module 240 of the server 20 determines whether the disclosure conditions of the waiting job information are met. For example, the disclosure module 240 may determine the disclosure conditions of the waiting job information when an application for or cancellation of a regular job offer occurs. In the example shown in Figure 8, the disclosure module 240 determines that the disclosure conditions of the waiting job information are met.

[0113] In step S120, the disclosure module 240 of the server 20 discloses the waiting job information of the waiting job offer M corresponding to the regular job offer N. Note that the disclosure module 240 may keep the regular job information of the regular job offer N private according to the disclosure conditions.

[0114] In step S122, when the information processing device 10C logs in and requests viewing of, for example, waiting job offer M, the disclosure module 240 of the server 20 transmits waiting job offer information of waiting job offer M to the information processing device 10C.

[0115] In step S124, when the information processing device 10C accepts an application for the waiting job offer M in response to the operation of the worker, it requests the server 20 to apply for the waiting job offer M.

[0116] In step S126, the service control module 237 of the server 20 matches the applied worker with the job information. For example, the server 20 notifies the business operator of the waiting job M of the user information of the applied worker, and determines whether or not to have the applied worker wait. The service control module 237 of the server 20 may automatically match the information of the applied worker with the waiting job information. In this case, automatic matching may be performed if predetermined conditions, for example, the age, desired working hours, etc. of the applied worker are included in the age and working hours of the waiting job information.

[0117] The above process makes it possible to easily set up waiting job offers. For example, when setting up regular job offers, businesses do not need to set up waiting job offers to match the required job offers. In addition, since the waiting job offers are based on the regular job offer information set by the business, appropriate waiting job offer information is generated.

[0118] 9 is a flowchart showing an example of a job information publishing process according to the embodiment. The process shown in FIG. 9 corresponds to steps S108, S118, S120, etc. shown in FIG.

[0119] 9, the disclosure module 240 of the server 20 discloses regular job information when the time for disclosing the regular job information arrives. As a specific example, when a worker accesses a job listing or the like on the job service, the disclosure module 240 makes the regular job information available to the worker.

[0120] In step S204, the disclosure module 240 of the server 20 determines whether a predetermined condition that serves as a trigger for determining the disclosure conditions is met when an event occurs. For example, this predetermined condition includes the occurrence of an application or cancellation for a regular job offer. If the predetermined condition that serves as a trigger is met (step S204-YES), the process proceeds to step S206, and if this predetermined condition is not met (step S204-NO), the process proceeds to step S212.

[0121] In step S206, the disclosure module 240 of the server 20 determines whether the disclosure conditions for the waiting job information are met. The disclosure conditions include, for example, gathering regular workers equal to the number of positions recruited for the regular job offer, or keeping the regular job information private. If the disclosure conditions are met (step S206-YES), the process proceeds to step S208. If the disclosure conditions are not met (step S206-NO), the process proceeds to step S210.

[0122] In step S208, the disclosure module 240 of the server 20 makes the regular job information that is currently public private and makes the waiting job information public. Note that if the process of S208 is performed two or more times, the disclosure module 240 continues to make the regular job information private if it is private, makes it private if it is public, and continues to make the waiting job information public if it is public, and makes it public if it is private.

[0123] In step S210, the disclosure module 240 of the server 20 continues to disclose the regular job information that is currently disclosed, and continues to keep the undisclosed waiting job information private. Note that if the processing of S210 is performed two or more times, the disclosure module 240 discloses the regular job information if it is private, continues to disclose it if it is currently disclosed, and continues to keep the waiting job information private if it is private, and makes it private if it is currently disclosed.

[0124] In step S212, the disclosure module 240 of the server 20 determines whether the disclosure deadline for the regular or standby job information has arrived. If the disclosure deadline has arrived (step S212-YES), the process ends, and if the disclosure deadline has not arrived (step S212-NO), the process returns to step S204, and a condition determination is made when an event occurs.

[0125] Through the above processing, in this embodiment, waiting job information is made public at the appropriate time, and waiting job information can be recruited. As a result, it is not necessary to make all waiting job information public, which makes it possible to reduce the processing load on the system. Furthermore, in this embodiment, it is possible to appropriately switch between public and private status for regular job information and waiting job information depending on the application status for regular job information, the number of workers matched with the number of positions available for regular job information, etc.

[0126] (Cancellation processing) 10 is a flowchart showing an example of a process related to cancellation according to the embodiment. The process shown in Fig. 10 shows specific processes to be performed when canceling steps S204, S206, S208, S210, etc. shown in Fig. 9.

[0127] In step S302, the acquisition module 238 of the server 20 acquires an event indicating that a cancellation has occurred for the job information. For example, a cancellation occurs when a worker performs a cancellation operation for a job that they have applied for on a job service.

[0128] In step S304, the disclosure module 240 of the server 20 determines whether the cancellation is for a regular job offer or a waiting job offer. For example, a job offer ID is also notified when a cancellation event is notified, and the disclosure module 240 can determine whether the job offer is regular or waiting based on the job offer ID notified along with the cancellation event. Here, if the job offer to be canceled is a regular job offer, processing proceeds to step S306, and if the job offer to be canceled is a waiting job offer, processing proceeds to step S312.

[0129] In step S306, the disclosure module 240 of the server 20 determines whether the cancellation of a regular job offer allows the shortage of workers to be promoted from the waiting workers of the waiting job offer. For example, the disclosure module 240 determines that promotion is possible if there are waiting workers equal to the number of canceled regular workers, and determines that promotion is not possible if there are not. If promotion is possible (step S306-YES), the process proceeds to step S310, and if promotion is not possible (step S306-NO), the process proceeds to step S308.

[0130] In step S308, the disclosure module 240 of the server 20 discloses the regular job information and keeps the standby job information private. This is because a regular worker vacancy has occurred and there are no standby workers, so regular workers are being recruited.

[0131] In step S310, the service control module 237 of the server 20 moves the promoted standby worker to a regular job offer and changes the worker to a regular worker. For example, the service control module 237 notifies the promoted standby worker that he or she will become a regular worker, and changes the standby worker's attributes to those of a regular worker, thereby changing the worker to a regular worker. For example, the service control module 237 changes the job offer ID included in the work status information shown in FIG. 7 from the job offer ID of the standby job offer to the job offer ID of the regular job offer.

[0132] In step S312, the publishing module 240 of the server 20 publishes the waiting job information. If the waiting job information is currently published, it continues to be published.

[0133] With the above process, if a regular worker cancels, a standby worker can be promoted, and if a regular worker becomes vacant, regular job information can be made public again. As a result, it becomes possible to appropriately switch between regular job offers and standby job offers depending on the application status for regular job offers and the availability of regular workers.

[0134] (Waiting process) 11 is a flowchart illustrating an example of a process related to waiting according to the embodiment. The process illustrated in FIG. 11 shows a process for a waiting worker.

[0135] 11, the service control module 237 determines whether the standby start time has arrived. For example, if the standby start time for standby job offer X has arrived (step S402-YES), the service control module 237 proceeds to step S404, and if the standby start time for standby job offer X has not arrived (step S402-NO), the service control module 237 returns to step S402.

[0136] In step S404, the service control module 237 determines whether to acquire certification information indicating the waiting location and / or waiting time from the information processing device 10C used by each waiting worker. If the certification information is acquired (step S404-YES), the process proceeds to step S406. If the certification information is not acquired (step S404-NO), the process proceeds to step S408.

[0137] In step S406, the service control module 237 associates the certification information with the standby worker who transmitted it and stores it. For example, the service control module 237 may associate the certification information with the corresponding standby worker in the work status information shown in FIG. 7 and store it. At this point, the service control module 237 may use the certification information to verify that the standby worker was at the appropriate standby location at the standby start time. For example, if the service control module 237 uses both the standby location and the standby start time, if both are verified, the service control module 237 may certify that the standby worker is appropriately waiting. If appropriately authenticated, an authenticated flag may be assigned to the standby worker included in the work status information shown in FIG. 7.

[0138] In step S408, the service control module 237 determines whether a vacancy has occurred in the regular job offer corresponding to the standby job offer due to a sudden cancellation, absence without notice, lateness, etc. (examples of working conditions), and whether working conditions have arisen for the standby worker. If working conditions for the standby worker have arisen (step S408-YES), the process proceeds to step S410, and if working conditions for the standby worker have not arisen (step S408-NO), the process proceeds to step S412.

[0139] In step S410, the output module 242 outputs a work notice to standby workers in order of priority. For example, the output module 242 identifies a standby worker to whom a work notice is to be output in order of priority, such as the order of application, and outputs the work notice to the information processing device 10C used by the identified standby worker (see, for example, FIG. 14). Note that the output module 242 may not output a work notice to a standby worker whose standby status has not been verified by certification information, even if the standby worker is the highest priority worker. In other words, the output module 242 may output a work notice in order of priority among standby workers whose standby status has been verified by certification information.

[0140] In step S412, the service control module 237 determines whether a standby end condition is satisfied. The standby end condition includes at least one of, for example, the arrival of the standby end time, the start of work by all regular workers, etc. If the standby end condition is satisfied (step S412-YES), the process proceeds to step S414, and if the standby end condition is not satisfied (step S412-NO), the process returns to step S404.

[0141] In step S414, the service control module 237 uses the authentication information to verify that each waiting worker was at the appropriate waiting location at the waiting start time. For example, if the service control module 237 uses both the waiting location and the waiting start time, the service control module 237 may not process the waiting pay unless both are authenticated. The service control module 237 may also acquire authentication information including the waiting end time and the waiting location, and verify whether the waiting worker was waiting at the appropriate location at the end of the waiting period. Note that if the authentication information is verified when it is acquired and an authenticated flag is present, the service control module 237 may not verify the authentication information for waiting workers with the authenticated flag.

[0142] In step S416, the payment module 241 executes payment of standby pay to standby workers whose standby status is proven as a result of verifying the certification information. Note that the payment module 241 does not pay standby pay to standby workers whose standby status is not proven, and further, the service control module 237 may impose a penalty on such standby workers.

[0143] Through the above processing, this embodiment can verify whether a standby worker is waiting appropriately based on certification information indicating that they are waiting, or can pay wages to standby workers whose standby status has been certified, or can notify standby workers of their work hours in the event of a sudden vacancy.

[0144] <Screen example> Next, examples of each screen displayed on the user-side information processing device 10 will be described. FIG. 12 is a diagram showing an example of a recruitment screen for a regular job offer according to the embodiment. The screen shown in FIG. 12 is an example showing the content of a job offer made available to workers belonging to the "AAA Experience" group by the Shibuya store of the business "AAA." Note that the job offer can be similarly set to be open to the public instead of being open to the public.

[0145] In the example recruitment screen for regular job offers shown in Figure 12, for example, the business operator sets the recruitment date, working hours, deadline, hourly wage, whether or not they wish to create a waiting job offer, etc. (for example, step S102 in Figure 8). In the example recruitment screen shown in Figure 12, the business operator checks a checkbox G2 that asks whether or not they wish to create a waiting job offer. As a result, waiting job offer information is created based on the regular job offer information shown in Figure 12 (for example, see Figure 13).

[0146] 13 is a diagram showing an example of a job listing for a waiting job according to an embodiment. In the example shown in FIG. 13, the job listing for a waiting job includes a waiting time from a waiting start time to a waiting end time, a deadline setting, a waiting location, certification information, a waiting hourly wage, etc. For example, each piece of information in the job listing for a waiting job shown in FIG. 13 is generated in step S106 of FIG. 8.

[0147] The standby time shown in Fig. 13 is generated based on the work start time of the regular job information shown in Fig. 12. The generation module 239 sets the standby start time to, for example, 20:30, a predetermined time before the work start time of 21:00. The standby start time may also be set to be the same as the work start time. The standby end time is set to, for example, 21:30, a predetermined time after the work start time of 21:00.

[0148] The deadline for the standby job offer may be set to the same as the deadline for the regular job offer. The standby location may be set based on the work location of the regular job offer. For example, the generation module 239 may allow the user to select from options such as the work location (work location) of the regular job offer, the station closest to the work location of the regular job offer, or other options (such as entering an address or specifying a location on a map). In the example shown in FIG. 13, the nearest station (AA Station) close to the work location is selected. The proof information is information that proves that the standby worker is waiting at a specified location at a specified time, and may be an image containing the characters of the station name of the standby location. For example, since the standby location is AA Station, the generation module 239 may use an image containing the characters for AA Station as the proof information. The standby hourly wage may be the same as the hourly wage of the regular job offer, or may be an amount obtained by subtracting a specified amount from the hourly wage of the regular job offer.

[0149] Any of the information on the waiting time, deadline, waiting location, certification information, and waiting hourly wage may be changed by an operation of the business operator. Also, any of the information on the waiting time, deadline, waiting location, certification information, and waiting hourly wage may be set by a user input instead of being set by the generation module 239.

[0150] FIG. 14 is a diagram showing an example of a work notification according to the embodiment. In the example shown in FIG. 14, a pop-up is displayed to a standby worker notifying them of the start of work due to a vacancy (for example, step S410 in FIG. 11). The screen shown in FIG. 14 includes information such as the name of the store where the standby worker will be working, whether they are available to start work, and how many minutes after which they need to arrive at the store. If a standby worker who receives this work notification works at a AAA store within 10 minutes, the standby worker can become a regular worker.

[0151] The disclosed technology is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the spirit of the disclosed technology. Therefore, the above-described embodiment is merely an example in all respects and should not be interpreted as being limiting. For example, the order of the above-described processing steps can be arbitrarily changed or executed in parallel as long as no contradiction occurs in the processing content.

[0152] The program of the embodiment of the present disclosure may be provided in a state stored in a computer-readable storage medium. The storage medium can store the program in a "non-transitory tangible medium." The program includes, but is not limited to, a software program or a computer program. [Explanation of symbols]

[0153] 1. Information Processing Systems 10, 10A, 10B Information processing device 20 Information processing device (server) 110, 210 Processing Unit (CPU) 120, 220 network communication interface 130, 230 memory 131, 231 operating systems 132, 232 Network Communication Module 133 App Data 134 Service Processing Module 135 Acquisition Module 136 Output Module 137 Processing Module 138 Display Control Module 150 User Interface 170, 270 communication bus 233 User Information 234 Regular Job Information 235 Waiting Job Information 236 Work Status Information 237 Service Control Module 238 Acquisition Module 239 Generation Module 240 Public Modules 241 Payment Module 242 Output Module

Claims

1. The information processing device Acquiring setting information related to regular job information from a first information processing device used by the business; generating waiting job information for waiting job offers for the regular job offer information based on the respective setting information; To publish the information on job vacancies; An information processing method that performs the above.

2. The disclosure is The information processing method according to claim 1 , further comprising publishing the waiting job information when a publication condition for the waiting job is met.

3. The disclosure is The information processing method according to claim 2 , further comprising switching between public and private status of the waiting job information depending on a result of a determination as to whether the disclosure condition is met, the determination being made when a predetermined condition is met.

4. The information processing method according to claim 2 , wherein the disclosure conditions include at least one of the regular job information being made public and the number of people based on the number of positions advertised in the regular job information being gathered.

5. The generating step comprises: The information processing method according to claim 1, further comprising setting at least one of the number of people on standby, the standby location, the standby time, and the standby salary corresponding to the number of people to be recruited, the work location, the work start time, and the salary included in each of the setting information.

6. The setting The information processing method according to claim 5 , further comprising setting the standby time to be from the work start time or a first hour before the work start time to a second hour after the work start time.

7. The obtaining includes: acquiring, from a second information processing device used by a user who has applied for the job offer on standby, verification information relating to at least one of a waiting location and a waiting time; The information processing method according to claim 1 , wherein the information processing device further executes a process of paying standby pay to the user depending on a result of checking the certification information.

8. The information processing method according to claim 7 , further comprising outputting, to the second information processing device, information relating to how to spend the waiting time.

9. The information processing method described in claim 1, wherein the information processing device further outputs a work notification to a second information processing device used by a user who applied for the waiting job offer if a predetermined time has elapsed since the start time of work included in the regular job offer information and the number of users equal to the number of positions being recruited has not started work.

10. The outputting step includes:

10. The information processing method according to claim 9, further comprising outputting a cancellation notice to a third information processing device used by a user who applied for the regular job information but has not yet started working after the predetermined time has elapsed.

11. The information processing method described in claim 1, wherein the information processing device further executes the following: when users equal to the number of recruits specified in the regular job information start working, a notification of the end of waiting is sent to a second information processing device used by the user who applied for the waiting job, and payment of wages for the time including the time from the start of waiting to the notification of the end of waiting is made.

12. In the information processing device, Acquiring setting information related to regular job information from a first information processing device used by the business; generating waiting job information for waiting job offers for the regular job offer information based on the respective setting information; To publish the information on job vacancies; A program that executes the following.

13. An information processing device including one or more processors, the one or more processors: Acquiring setting information related to regular job information from a first information processing device used by the business; generating waiting job information for waiting job offers for the regular job offer information based on the respective setting information; To publish the information on job vacancies; An information processing device that executes the above.

Images