Matching system, recruiter device, computing device, and method

Abstract

To urge a user appropriate to a business item to apply for the business item in the case of matching the business item among a plurality of users.SOLUTION: A matching system 1 includes a user device 500 operated by a user, and a computing device 100 configured to access a database 120 registering the business item so as to transmit business information related to the business item to the user terminal 500. The computing device 100 selects a target candidate to whom the business information is notified from among a plurality of users on the basis of a selection reference, transmits the business information to a user device 500 operated by the selected candidate or a user device 500 operation by some of selected candidates, and the selection reference includes an inclusion reference for including a user as a notification object of the business information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a matching system, a recruiter device, a computing device, and a method for matching business cases. [Background technology]

[0002] Crowdsourcing has been used by companies for a long time. In general, crowdsourcing refers to the process of obtaining needed services, ideas, or content by collecting contributions from an unspecified number of people. Crowdsourcing requires finding people with the best skills to perform the required tasks.

[0003] Patent document 1 describes a method for comparing information about the human resources required by a development project with information about the company's members to see if they match, and extracting members who match the required human resources from within the company's entire organization as search results. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-44642 A Summary of the Invention [Problem to be solved by the invention]

[0005] The crowdsourcing described in Patent Document 1 is carried out within a single group, namely, a company. However, in order to find more suitable personnel, it is desirable to further expand the scope of crowdsourcing and build a matching system capable of matching business cases among a large number of people. In this case, the recruiter who proposes a business case hopes that someone familiar with the content of the business case will apply for the business case. However, for example, if a large number of recruiters register a large number of business cases in the system, it becomes difficult for the applicant to check all the business cases. For this reason, the recruiter may not be able to hire a person suitable for the business case as a contractor simply by waiting for applications from the applicants. This possibility increases as the number of users participating in the system increases.

[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to encourage, when matching business cases among multiple users, appropriate users corresponding to the business case to apply for the business case. [Means for solving the problem]

[0007] A matching system according to a first aspect of the present disclosure is a matching system for matching business cases, comprising a user device operated by a user and a computing device configured to access a database in which business cases are registered and transmit business information related to the business cases to the user device, wherein the computing device selects candidates to be notified of the business information from among a plurality of users based on selection criteria, and transmits the business information to a user device operated by the selected candidate or to a user device operated by some of the selected candidates, wherein the selection criteria include inclusion criteria for including users as targets for notifying of the business information.

[0008] A recruiter device according to a second aspect of the present disclosure is a recruiter device that communicates with a computing device that matches business cases and is operated by a recruiter, wherein the computing device is configured to access a database in which business cases are registered, select candidates from a plurality of applicants to whom business information related to the business cases will be notified based on selection criteria, and transmit the business information to an applicant device operated by the selected candidate or to an applicant device operated by some of the selected candidates, wherein the recruiter device has a reception unit that accepts operations by the recruiter to set the business information and the selection criteria, and a transmission unit that transmits the selection criteria accepted by the reception unit to the computing device, and the selection criteria include inclusion criteria for including applicants as targets for notifying of business information.

[0009] A computing device according to a third aspect of the present disclosure is a computing device that communicates with a user device and matches business cases, and includes a transmitting unit that accesses a database in which business cases are registered and transmits business information related to the business cases to the user device, and a selecting unit that selects candidates to be notified of the business information from among a plurality of users based on selection criteria, wherein the transmitting unit transmits the business information to a user device operated by the candidate selected by the selection unit, or to a user device of a user operated by some of the candidates selected by the selection unit, and the selection criteria include inclusion criteria for including users as targets for notifying the business information.

[0010] A method according to a fourth aspect of the present disclosure is a method for matching business cases, comprising the steps of accessing a database in which business cases are registered, selecting candidates from a plurality of users to be notified of business information related to the business cases based on selection criteria, and transmitting the business information to a user device operated by the candidate selected in the selection step, or to a user device operated by some of the selected candidates, wherein the selection criteria include inclusion criteria for including users as targets for notifying the business information. Effect of the Invention

[0011] According to the present disclosure, when matching business cases among a plurality of users, it is possible to encourage users appropriate for the business case to apply for the business case. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an overview of a matching system. [Diagram 2] 2 is a block diagram showing the configurations of a sharing server, a recruiter device, and an applicant device. FIG. [Diagram 3] FIG. 2 is a diagram illustrating an example of a company database. [Figure 4] FIG. 4 is a diagram illustrating an example of a member database. [Diagram 5] FIG. 4 is a diagram illustrating an example of a community database. [Figure 6] FIG. 2 is a diagram illustrating an example of a recruitment request database. [Figure 7] FIG. 13 is a diagram showing an example of a side job database. [Figure 8] FIG. 4 is a diagram illustrating an example of an evaluation input database. [Figure 9] FIG. 13 is a diagram illustrating an example of an evaluation summary database. [Figure 10] 2 is a diagram for explaining functions of a sharing server, a recruiter device, and an applicant device. FIG. [Figure 11] 2 is a diagram for explaining functions of a sharing server, a recruiter device, and an applicant device. FIG. [Figure 12] 2 is a diagram for explaining functions of a sharing server, a recruiter device, and an applicant device. FIG. [Figure 13] FIG. 2 is a diagram for further explaining the function of the applicant device. [Figure 14] FIG. 13 is a diagram for explaining a procedure for registering a recruitment request in a recruitment request database. [Figure 15] FIG. 13 is a diagram for explaining a procedure for searching for recruitment requests from a database. [Figure 16]13 is a diagram for explaining the procedure for registering side job plans and results in a database. FIG. [Figure 17] FIG. 13 is a diagram for explaining the procedure for registering an evaluation of an applicant in a database. [Figure 18] FIG. 13 is a diagram for explaining the procedure for registering an evaluation of a recruiter in a database. [Figure 19] 13 is a diagram for explaining a procedure for displaying evaluations of applicants and search results of members on a display. FIG. [Figure 20] A diagram for explaining the procedure for displaying evaluations of recruiters and search results of members on a display. [Figure 21] FIG. 13 is a diagram for explaining the viewable range of the evaluation summary database. [Figure 22] FIG. 13 is a diagram showing an example in which a disclosure range is set according to a disclosure level. [Diagram 23] FIG. 13 is a diagram showing a screen displayed on the applicant's device of a manager (applicant's boss) when the manager checks the side job status of his / her subordinates. [Figure 24] FIG. 2 is a diagram showing details of job content contained in a recruitment job database. [Diagram 25] FIG. 1 is a diagram for explaining positive matching and negative matching. [Figure 26] FIG. 13 is a screen diagram showing an example of a candidate list for a job offer. [Figure 27] 13 is a flowchart showing a processing procedure executed by a sharing server regarding an offer of an item. [Figure 28] 11 is a flowchart showing a processing procedure executed by a user device operated by a recruiter with respect to an offer of a project. [Figure 29] FIG. 4 is a diagram illustrating an example of a profile database. [Diagram 30] FIG. 10 is a diagram illustrating an example of an in-house terminology database. [Diagram 31] 13 is a flowchart showing a processing procedure relating to an index function of the matching system. [Diagram 32]13 is a flowchart showing a processing procedure of an in-house terminology registration unit. [Diagram 33] 13 is a flowchart showing a processing procedure of a case registration unit. [Diagram 34] 13 is a flowchart showing a processing procedure for displaying the meaning of in-house terms on a screen in response to an operation by an applicant. [Diagram 35] FIG. 13 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device according to the first modified example. [Diagram 36] FIG. 13 is a diagram showing an example of a member database according to the first modified example. [Figure 37] 13 is a flowchart showing the processing steps of a counter offer member search process according to the first modification. [Figure 38] FIG. 11 is a block diagram showing the configurations of a sharing server, a recruiter device, and an applicant device according to the second modified example. [Figure 39] FIG. 13 is a diagram showing an example of a member group database according to the second modified example. [Diagram 40] FIG. 11 is a diagram showing an example of a recruitment request database according to the second modified example. [Diagram 41] FIG. 13 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device according to the second modified example. [Diagram 42] FIG. 13 is a diagram for explaining the procedure for registering a solicitation request related to the modified example 2 in the solicitation request database. [Diagram 43] FIG. 13 is a diagram showing the configuration of a matching system according to Modification 3. [Diagram 44] FIG. 13 is a diagram showing an example (variation 4) in which Kerberos authentication is applied to a matching system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference characters and their description will not be repeated.

[0014] [Background of proposing Matching System 1] 1 is a block diagram showing an overview of a matching system 1 according to this embodiment. First, the background behind the proposal of the matching system 1 in this embodiment will be described.

[0015] The matching system 1 is used, for example, in crowdsourcing between businesses. Crowdsourcing is generally a process of soliciting contributions from an unspecified number of people to obtain needed services, ideas, or content.

[0016] Many companies are encouraging side jobs to make effective use of their human resources. Crowdsourcing between companies allows them to utilize the capabilities of their employees.

[0017] However, if typical crowdsourcing methods are applied directly between companies, the following problems may arise:

[0018] [Possibility of confidential information being leaked] In general crowdsourcing methods, the relationship between the client company and the recipient company is not taken into consideration, so adopting crowdsourcing entails corporate and personal risks. For example, there is a risk that confidential information may be leaked to rival companies through an employee's side job. With conventional crowdsourcing methods, managers cannot confirm that employees are not accepting projects from competitors as side jobs.

[0019] [Possibility of overwork] If a company allows its employees to have a side job, there is a risk that the employees' working hours will become excessively long. To eliminate the risk of overwork, the company may set an upper limit on the number of overtime hours, including the main job and the side job. However, as long as employees are free to take on side jobs, it is difficult for companies to control the amount of time that employees spend on side jobs. As a result, there is a risk that employees will end up overworked.

[0020] [The results of your side job may not be properly evaluated] Conventionally, there are crowdsourcing systems that request clients to evaluate contractors. When appropriate evaluations made by clients are shared on the crowdsourcing system, those who are looking for contractors for the work can refer to the evaluations and select highly capable individuals from among the many people who wish to receive the work.

[0021] However, a purchaser of a certain company may be so concerned about the contractors of other companies that they input a higher evaluation into the system than the actual evaluation. Also, a purchaser of a certain company may avoid giving a low evaluation to contractors of other companies, considering the possibility that the relationship between the companies may deteriorate. Furthermore, purchasers may not see any benefit in making an evaluation and may input an evaluation into the system that is far from the actual evaluation. Considering these possibilities, there is a risk that the reliability of the evaluation provided by the system will decrease. In this case, even if evaluations of contractors are shared, purchasers of work will not be able to use the evaluations as reference data when selecting contractors.

[0022] [Possibility of not getting accurate information about recruiters] In the above-mentioned crowdsourcing system, applicants who wish to apply for jobs will select jobs that satisfy them while taking into consideration the content of the jobs and the remuneration. However, among recruiters, there may be those who frequently make additional requests outside the scope of the contracted work or instruct changes to the content of the work. Applicants will want to avoid such recruiters when applying for the jobs. Conversely, there are also recruiters who do not cause any problems until the work is completed. Applicants will want to apply for jobs recruited by such recruiters, if possible. Therefore, it is desirable to widely share evaluations of not only applicants (contractors) but also recruiters (clients) in the crowdsourcing system.

[0023] If appropriate evaluations of job seekers are shared on a crowdsourcing system, people looking to apply for work can use the evaluations as a reference and select a job that satisfies them from among the many available jobs, taking into account the job seeker's past transaction history, etc.

[0024] However, when constructing an evaluation system that allows evaluation of recruiters, the same problems as those when constructing an evaluation system that allows evaluation of contractors may occur. That is, a contractor (applicant) of a certain company may input a higher evaluation into the system than the actual evaluation, thinking too much of the client (recruiter) of the other company being evaluated. Also, a contractor (applicant) of a certain company may avoid rating the client (recruiter) of the other company low, considering the possibility that the relationship between the companies may deteriorate. Furthermore, a contractor (applicant) may not see any benefit in making an evaluation and may input an evaluation into the system that is far from the actual evaluation. Considering these possibilities, there is a risk that the reliability of the evaluation provided by the system will decrease. In this case, even if the evaluation of the recruiter is shared, the applicant cannot use the evaluation as reference data when selecting a recruiter.

[0025] [The unique feature of having companies act as the matching body] Generally, in order to match talent and jobs across companies, a close relationship such as trust between the companies matching talent and jobs is required. Therefore, for example, it is very difficult to match talent and jobs across companies that do not have capital ties. In addition, large companies such as listed companies are prone to compete with other companies from the perspective of diversification, etc., and cannibalization occurs between other companies, so there are special circumstances in which it is not possible to match talent and jobs between many companies.

[0026] [In-house jargon can impede communication] In some companies, there are in-house terms specific to that company. In-house terms are understood by people in the company where they are used, but there is a risk that they may not be understood by people who do not belong to the company where they are used. Alternatively, in-house terms are understood as terms with a specific meaning among people in the company where they are used, but there is a risk that they may be understood as terms with a different meaning from that specific meaning by people who do not belong to the company where they are used.

[0027] There is a possibility that in-house terminology may be used in the job description. If the employer belongs to a different company than the applicant, the applicant may not be able to correctly understand the meaning of the in-house terminology used by the employer in the job description. The applicant may apply for the job without correctly understanding the meaning of the in-house terminology used by the employer in the job description. This may result in work-related problems.

[0028] In-house terms may be used during meetings between recruiters and applicants. If the recruiter belongs to a different company than the applicant, the applicant may not be able to correctly understand the meaning of the in-house terms used by the recruiter. Similarly, the recruiter may not be able to correctly understand the meaning of the in-house terms used by the applicant.

[0029] If the company term used by either the recruiter or the applicant is unfamiliar, the other person will be able to understand the meaning of the term by asking the speaker about its meaning. However, if the understanding of the meaning of a certain company term differs between the recruiter and the applicant, the meeting will proceed without correcting the difference in understanding between the two parties. As a result, there is a risk of business trouble occurring.

[0030] In-house terms are not limited to companies, but can also be used in non-profit organizations. Whether for profit or non-profit, an organization may be divided into multiple units such as departments and sections, and each unit may have its own terms. Such terms may also be prevalent in communities formed by multiple organizations such as companies. Therefore, when recruiters and applicants belong to different organizations, units, and communities, differences in understanding of terms may cause business troubles such as those mentioned above.

[0031] In this embodiment, the term "in-house terminology" refers not only to "internal terminology" used in profit-making organizations such as companies and units therein, but also to "terms similar to internal terminology" used in non-profit organizations, communities, and units therein. In the following, this embodiment will be described using "internal terminology" for a company as an example of "in-house terminology."

[0032] In this embodiment, a matching system 1, which will be described in detail below, is proposed for the purpose of solving at least one of the above-mentioned various problems that conventional crowdsourcing has.

[0033] [Overall configuration] The general configuration of the matching system 1 will be described with reference to Fig. 1. The matching system 1 includes a sharing server 100, recruiter devices 200A, 200B, 200C..., and applicant devices 300A, 300B, 300C....

[0034] The sharing server 100 provides a matching service to many companies that matches business orders and receipts between companies. FIG. 1 shows company A, company B, company C, etc. as examples of companies that use the matching service. Company A, company B, company C, etc. are registered as corporate members of the matching system 1. Employees of company A, company B, company C, etc. who use the matching system 1 are also individually registered as members of the matching system 1.

[0035] The work arranged by the matching system 1 is, for example, temporary work that is expected to be completed in a predetermined period of time. Therefore, a person who accepts a work arranged by the matching system 1 will work in a specific department to which he or she belongs within the company as a main job, and will be engaged in each of the jobs arranged by the matching system 1 as a side job. Note that in the matching system 1, for example, an applicant from company A can also accept a work from company A. Therefore, in the matching system 1, an applicant who belongs to a different department Y of company A is also allowed to accept a work from department X of company A.

[0036] Hereinafter, a job for which contractors are being recruited in the matching system 1 may be referred to as a "recruited job," "recruited case," or "business case," a person providing a recruited case may be referred to as a "recruiter," and a person applying to receive a recruited case may be referred to as an "applicant." Applying for a recruited job may be referred to as an "application for the recruited job" or an "application for the recruited case (business case)."

[0037] An applicant who accepts a recruitment project is referred to as the "contract recipient," and a recruiter who places an order for the project with the contractor is referred to as the "orderer." In what follows, however, the term "applicant" may include the "contract recipient," and the term "recruiter" may include the "orderer."

[0038] A database 120 necessary for the matching service is constructed in the sharing server 100. The database 120 includes various databases in which information necessary for providing the matching service is registered. For example, information on members and recruitment operations is registered in the database 120. The sharing server 100 is managed and operated by a company other than the companies that use the matching service. The sharing server 100 may be managed and operated by any of the companies that use the matching service.

[0039] The recruiter device 200A is operated by an administrator of company A. The recruiter device 200B is operated by an administrator of company B. The recruiter device 200C is operated by an administrator of company C. Hereinafter, the recruiter devices 200A, 200B, 200C... may be collectively referred to as "recruiter devices 200."

[0040] Applicant device 300A is operated by an applicant from company A. Applicant device 300B is operated by an applicant from company B. Applicant device 300C is operated by an applicant from company C. Hereinafter, applicant devices 300A, 300B, 300C... may be collectively referred to as "applicant devices 300." In FIG. 1, two applicants are depicted for each company, but the number of applicants is not limited to this. There may be more applicants for each company, or a company may have only one applicant. Sharing server 100 may also accept applicants who do not belong to a company, such as freelancers.

[0041] In this embodiment, the managers of companies A, B, C, etc. will assume the role of recruiters. Therefore, hereinafter, the managers of each company may be referred to as "recruiters." Recruiters can also act as applicants for jobs that other recruiters are recruiting for. In that case, the recruiter device 200 functions as the applicant device 300. In this embodiment, when a company manager acts as a recruiter, the device that the manager uses to use the matching service will be referred to as the recruiter device 200.

[0042] Company A may have one or more managers. When company A has managers, each manager may be given a recruiter device 200, or one recruiter device 200 may be shared by multiple managers. The same applies to companies B, C, etc.

[0043] The sharing server 100 and the recruiter device 200 are configured to be able to communicate with each other via the Internet 50, which is an example of a communication network. The sharing server 100 and the applicant device 300 are configured to be able to communicate with each other via the Internet 50.

[0044] The sharing server 100 requires sign-in with input of a member ID and password when accepting access to the recruiter device 200. Similarly, the sharing server 100 requires sign-in with input of a member ID and password when accepting access to the applicant device 300. The sharing server 100 identifies each of the recruiters and applicants by the member ID notified at the time of sign-in.

[0045] The recruiter device 200 accepts various operations by the recruiter. For example, the recruiter device 200 accepts an operation to input a recruitment case (requested work), an operation to input an evaluation of a contractor who has completed the work, and an operation to search for members of the matching service.

[0046] The recruiter device 200 communicates with the sharing server 100 in response to each operation on the recruiter device 200. The sharing server 100 registers a recruitment request in the database 120 in response to an operation of inputting a recruitment request (requested work), registers an evaluation of the target applicant (contractor) in the database 120 in response to an operation of inputting an evaluation, and provides member information to the recruiter device 200 in response to an operation of searching for members.

[0047] The applicant device 300 accepts various operations by the applicant. For example, the applicant device 300 accepts an operation to search for a job posting, an operation to apply for a job posting, an operation to input work results, and the like.

[0048] The applicant device 300 communicates with the sharing server 100 in response to each operation on the applicant device 300. The sharing server 100 provides the applicant device 300 with appropriate recruitment requests in response to an operation to search for recruitment requests, issues a notice of acceptance or rejection to the applicant device 300 in response to an operation to apply for the recruitment request, and registers the work performance in the database 120 in response to an operation to input the work performance.

[0049] As described above, the matching system 1 includes an evaluation system that evaluates applicants (contractors) for work, and a recruitment system that recruits contractors for work.

[0050] A recruiter belonging to a certain department of company A can employ an applicant belonging to another department of company A as a contractor for a recruitment project by using the matching system 1. A recruiter belonging to company A can employ an applicant belonging to company B as a contractor for a recruitment project by using the matching system 1.

[0051] In the following, members of the matching system 1 may be referred to as "users." In addition, in the following, the recruiter device 200 and the applicant device 300 operated by the members may be collectively referred to as "user device 500." A user who uses the matching system 1 accesses the sharing server 100 as a recruiter or an applicant by using the "user device 500."

[0052] Various information is displayed on the user device 500. When the user is accessing the sharing server 100 in the role of a recruiter, the user can also display the profile of the applicant on the user device 500. The user uses the user device 500 to check the job history of the applicant. Alternatively, the user device 500 displays the job requirements for the job. The user (applicant) looks at the screen 552 of the user device 500 to check the details of the job. The user (recruiter) looks at the screen 552 to check the job history of the applicant. Alternatively, the screen 552 displays a report on the job in progress, an instruction to change part of the request content, an instruction to add to the request content, and the like. The user checks the content displayed on the screen 552 and uses the user device 500 to perform necessary processing, such as replying to the other party with the necessary information.

[0053] There is a possibility that in-house terminology is included in information such as the recruitment requirements, work history, work reports, and instructions displayed on screen 552. If the company to which the user viewing screen 552 belongs is different from the company to which the user providing that information belongs, the user viewing screen 552 may not be able to correctly understand the in-house terminology.

[0054] Therefore, the matching system 1 registers the in-house terms of each company and their meanings in the database 21. The matching system 1 generates an index of in-house terms from documents such as job descriptions used by users, and links them to the in-house terms registered in the database 21. In this way, the matching system 1 has an indexing function.

[0055] When an in-house term is included in a sentence displayed on screen 552, user device 500 displays the in-house term in a different display mode from other terms. This allows the user to understand that it is an in-house term. Furthermore, user device 500 displays the intended meaning of the in-house term on screen 552 in response to a user operation (for example, a click operation on the in-house term portion).

[0056] For example, on the screen 552 shown in FIG. 1, "DX" is displayed as an example of an in-house term. "DX" is underlined to indicate that it is an in-house term. The user clicks on "DX". Then, a window that explains the meaning of the term "DX" is displayed on the screen 552. DX is an abbreviation of Digital Transformation, and generally means a transformation using digital technology. However, some companies may use "DX" as an in-house term meaning the creation of some new value, regardless of whether digital technology is used. In such a case, the meaning corresponding to the in-house term is explained in the window on the screen 552. This allows the user to correctly understand the meaning of "DX" that the other party intends.

[0057] [Positive and negative matching] When a user accesses the sharing server 100 as an applicant, a list of business cases to which the user can apply is displayed on the user device 500. The user can select a case to which he or she wishes to apply from the list of business cases.

[0058] Meanwhile, recruiters who propose business cases hope that people familiar with the contents of the business cases will be interested in their business cases and apply for them. However, for example, if many recruiters have many business cases registered in the matching system 1, it becomes difficult for applicants to check all the business cases. For this reason, recruiters may not be able to hire people who are suitable for the business cases as recipients of the business cases simply by waiting for applications from applicants. In this case, it is desirable to notify the offer of the business case to people who are considered suitable to accept the business case.

[0059] On the other hand, it is preferable that the scope of disclosure of highly confidential cases, such as cases related to new businesses, is limited depending on the contents of the cases. Therefore, the recruiter needs to decide who to offer the business case to, taking into consideration the competitive relationship between the recruiter and the offeree. For example, it would be convenient for the recruiter to notify the offer of the business case only to those who are familiar with the business related to the business case and do not compete with the recruiter's business, while keeping the business case confidential in principle. However, the work of checking the information of each user registered in the matching system 1 and considering who to offer to is complicated. However, making an offer of a business case to an unspecified number of users without checking the user information at all is the same as making a general public call for proposals.

[0060] In this embodiment, therefore, in order to extract appropriate users as recipients of job offers, a function for matching business cases with users from two aspects is introduced. One aspect is "positive matching" and the other aspect is "negative matching."

[0061] Here, positive matching and negative matching will be described with reference to Fig. 25. Fig. 25 is a diagram for explaining positive matching and negative matching.

[0062] "Positive matching" matches business cases with users based on "inclusion criteria." "Inclusion criteria" are criteria for including users as targets for offers. Inclusion criteria include, for example, a user's work history, qualifications, and skills. FIG. 25 shows an example of an inclusion criterion that "work history includes experience in the human resources department." Positive matching extracts a "positive group" from a large number of users (members). FIG. 25 shows an example in which users A to D have been extracted as the positive group.

[0063] "Negative matching" matches business cases with users based on "exclusion criteria." "Exclusion criteria" are criteria for excluding users as targets for offers. Exclusion criteria are, for example, the company to which the user belongs and companies included in the user's work history. FIG. 25 shows an example of an exclusion criterion, "including companies X and Y in the work history." Positive matching extracts a "negative group" from a large number of users (members). FIG. 25 shows an example in which users D to F are extracted as the negative group.

[0064] The matching system 1 automatically selects candidates to whom a job offer is to be made by excluding users included in the negative group from the positive group. For example, in the example shown in Fig. 25, offer candidates A to C are selected by excluding user D included in the negative group from users A to D included in the positive group.

[0065] In this way, the matching system 1 automatically selects candidates to whom a job offer will be made based on "selection criteria" that include inclusion criteria and exclusion criteria.

[0066] 1, a screen 553 for registering a business case in the matching system 1 is displayed on the user device 500. When a user who initiates a business case registers business information related to the business case in the matching system 1, the user can set inclusion criteria and exclusion criteria corresponding to the business information. The user may set the inclusion criteria and the exclusion criteria, or may set one of the inclusion criteria and the exclusion criteria. For example, when an inclusion criteria is set for business information and an exclusion criteria is not set, the matching system 1 selects a user who is matched by positive matching as a candidate.

[0067] 1, a screen 554 is displayed on the user device 500 of a user selected as a recipient of a business offer, which displays the contents of the business offer and encourages the user to apply for the business offer. The user who receives the offer applies for the business offer after considering the contents of the business offer.

[0068] According to this embodiment, a user who has proposed a business case as a recruiter can, in principle, keep the business case private and notify the offer of the business case only to those who are familiar with the business related to the business case and do not compete with the business of the recruiter. Of course, by setting the inclusion criteria and exclusion criteria as appropriate, the user can also make the business case public to everyone while notifying the offer of the business case to those who are familiar with the business related to the business case.

[0069] Alternatively, the user can set the inclusion criteria and exclusion criteria as appropriate to set the disclosure range of the business case, and notify the offer of the business case to users who are familiar with the business related to the business case among those included in the disclosure range. Note that the matching system 1 may accept a user operation to change the inclusion criteria and exclusion criteria after the business case is registered.

[0070] Here, work history is given as an example of the inclusion criteria and exclusion criteria. However, the inclusion criteria and exclusion criteria are not limited to work history. For example, the industry and size of the company to which the user belongs may be adopted as the inclusion criteria and exclusion criteria. In addition, skills, qualifications, etc. may be adopted as the inclusion criteria.

[0071] FIG. 2 is a block diagram showing the configurations of the sharing server 100, the recruiter device 200, and the applicant device 300. As shown in FIG.

[0072] [Configuration of Sharing Server 100] The sharing server 100 includes a processor 101 , a memory 102 , a storage 103 , and a communication interface 104 .

[0073] The memory 102 may include a random access memory (RAM), a read only memory (ROM), a flash memory, or any other suitable memory system. The memory 102 stores programs necessary for the arithmetic processing of the processor 101, temporary data calculated in the arithmetic processing, and the like.

[0074] The storage 103 is composed of a hard disk drive, a solid state drive, etc. A database 120 is stored in the storage 103. The database 120 includes a plurality of types of databases. The plurality of types of databases includes a company database (company DB) 121, a member database (member DB) 122, a community database (community DB) 123, a job posting database (job posting DB) 124, a side job database (side job DB) 125, an evaluation input database (evaluation input) 126, and an evaluation summary database (evaluation summary DB) 127.

[0075] Some of these multiple types of databases may be stored in a storage provided separately from the sharing server 100. For example, the sharing server 100 may be connected to a cloud service separate from the sharing server 100, and some of the multiple types of databases shown in Fig. 2 may be stored on that cloud. In this case, the sharing server 100 can access the necessary databases by communicating with that cloud via the Internet 50.

[0076] The processor 101 connects to the Internet 50 via the communication interface 104 in accordance with the program stored in the memory 102. The processor 101 connects to the Internet 50 and communicates with the recruiter device 200 and the applicant device 300. The processor 101 accesses the database 120 and executes processes such as a process of extracting necessary data, a process of registering new data in the database 120, and a process of updating data registered in the database 120.

[0077] [Configuration of recruiter device 200] The recruiter device 200 includes a processor 201, a memory 202, a communication interface 203, an input / output interface 204, a display 205, and an operation unit 206. The operation unit 206 is composed of a mouse, a keyboard, and the like. The processor 201 is an example of a control unit. The display 205 is an example of a display unit.

[0078] The memory 202 includes a random access memory (RAM), a read only memory (ROM), a flash memory, or any other suitable memory system. The memory 202 stores programs necessary for the arithmetic processing of the processor 201, temporary data calculated in the arithmetic processing, and the like.

[0079] The processor 201 connects to the Internet 50 via the communication interface 203 in accordance with a program stored in the memory 202. The processor 201 connects to the Internet 50 and communicates with the sharing server 100. The processor 201 communicates with the sharing server 100 and executes processes such as sending a recruitment request, displaying information on applicant members on the display 205, ordering work from a contractor selected from the applicants, and sending the contents of the evaluation of the contractor entered by the recruiter to the sharing server 100.

[0080] Information input by operating the operation unit 206 is notified to the processor 201 via the input / output interface 204 .

[0081] [Configuration of applicant device 300] Applicant device 300 comprises a processor 301, memory 302, a communication interface 303, an input / output interface 304, a display 305, and an operation unit 306. The operation unit 306 is composed of a mouse, a keyboard, etc. Processor 201 is an example of a control unit. Display 205 is an example of a display unit.

[0082] The memory 302 includes a random access memory (RAM), a read only memory (ROM), a flash memory, or any other suitable memory system. The memory 302 stores programs necessary for the arithmetic processing of the processor 301, temporary data calculated in the arithmetic processing, and the like.

[0083] The processor 301 connects to the Internet 50 via the communication interface 303 in accordance with a program stored in the memory 302. The processor 301 connects to the Internet 50 and communicates with the sharing server 100. The processor 301 communicates with the sharing server 100 and executes processes such as applying for a job, displaying a notice of acceptance or rejection of the job on the display 305, and transmitting the results of the received work to the sharing server 100.

[0084] Information input by operating the operation unit 306 is notified to the processor 301 via the input / output interface 304 .

[0085] [Database 120 Summary] An overview of the database 120 will be described below. In the company database 121, information on companies affiliated with the matching system 1 is registered. In the member database 122, information on members who use the matching system 1 is registered. Many of the members are employees of companies affiliated with the matching system 1.

[0086] Members registered in the member database 122 can act as recruiters (orderers) or applicants (recipients) by using the matching system 1. Members may include employees of companies registered in the company database 121 as well as individuals (freelancers) not belonging to a company.

[0087] The community database 123 stores information for identifying companies belonging to a community. A community is formed by agreement between companies. Therefore, multiple communities can be formed depending on how the agreement is reached between the companies. The number of companies belonging to one community can also be set in various ways. A relationship of trust is formed between companies having a community relationship to the extent determined by the manner of agreement when forming the community. The community database 123 registers information for identifying companies belonging to the community for each community.

[0088] Jobs (jobs) for which contractors are being recruited are registered in the job database 124. Employees of each company can work in their own department as a main business at the company, and, as members of the matching system 1, can accept jobs from other departments of their own company or jobs from other companies that are registered in the job database 124. In this case, the members accept jobs from other departments of their own company or jobs from other companies as a side job.

[0089] Data showing the status of a side job is registered for each member in the side job database 125. The data showing the status of a side job includes information such as side job results and side job plans.

[0090] Evaluation information on job applicants (contractors) is registered in the evaluation input database 126. A job recruiter (client) can use the matching system 1 to evaluate the work performance of an applicant (contractor) who has completed a job as an evaluator. Evaluations made by each evaluator are registered in the evaluation input database 126.

[0091] The evaluation summaries are registered in the evaluation summary database 127. The evaluation summaries are registered for each member in the evaluation summary database 127. The recruiter can view the evaluation summaries. The recruiter can view the evaluation summaries of the members who have applied for the recruitment item and select a member who is deemed appropriate as a contractor.

[0092] [Company Database 121] FIG. 3 is a diagram showing an example of the company database 121. In the company database 121, a company ID for identifying the company, a company name, a company address, and a side job upper limit time are registered for each company. The side job upper limit time is the upper limit time that an employee is permitted to work as a side job in addition to his / her main job. The side job upper limit time is set for each company. For example, the side job upper limit time can be calculated by "prescribed overtime hours - overtime hours of the main job other than the side job". The "prescribed overtime hours" differ depending on the company. Note that while FIG. 3 shows the side job upper limit time in months, it may also be set in weeks. The unit of the side job upper limit time may also be set for each company.

[0093] In this embodiment, members are permitted to apply for and accept work from various companies and departments, as long as it does not exceed the side job time limit set by the company to which the member belongs.

[0094] [Member Database 122] 4 is a diagram showing an example of member database 122. Various information about members is registered in member database 122. The various information about members includes a member ID for identifying the member, the ID of the company to which the member belongs, the member's name, the member's authority, the department to which the member belongs, and the amount of time allowed for side work.

[0095] The types of authority of members include administrator and applicant. A member with administrator authority is given the authority to use the matching system 1 as a recruiter and an applicant. A member with applicant authority is given the authority to use the matching system 1 as an applicant, but is not given the authority to use the matching system 1 as a recruiter. A department head within a company is given administrator authority to manage the side jobs of his or her subordinates within the department. A manager with administrator authority is given the authority to approve applications from applicants who are his or her subordinates. Thus, a manager functions as an approver.

[0096] The available side job time is the remaining time available for engaging in a side job. The available side job time is calculated by "maximum side job time - total side job time." If the subject is engaged in multiple side jobs, the total side job time includes the time already spent on those multiple side jobs. The total side job time includes the time already spent on the side job as well as the expected time for the side job. The expected side job time is calculated based on the expected man-hours registered in the job posting database 124. Figure 4 shows the available side job time on a monthly basis. For applicants who use the matching system 1 to search for available jobs, only jobs that can be completed with man-hours within the available side job time are provided as jobs available for application.

[0097] [Community Database 123] FIG. 5 is a diagram showing an example of the community database 123. Information on communities formed between companies is registered in the community database 123. The community information includes a community ID for identifying the community, a community name, and a list of IDs of companies belonging to the community. Each company can form various communities by reaching an agreement with other companies. A company belonging to a community can change the companies that belong to the community by reaching an agreement with the other companies.

[0098] [Recruitment Database 124] 6 is a diagram showing an example of the recruitment request database 124. Information on recruitment requests is registered in the recruitment request database 124. The information on the recruitment request includes a request ID for identifying the recruitment request, the ID of the company to which the recruiter who registered the recruitment request belongs, a non-disclosure company ID list, the recruiter's member ID, the disclosure level, the request title, the inclusion criteria, the exclusion criteria, the expected man-hours, the expected period, and the request details.

[0099] For example, the non-disclosure company ID list registers the IDs of companies that are prohibited from disclosing recruitment information. The disclosure level can be set to one of three levels: "Company", "Within the community", or "All". If the disclosure level is set to "All", applicants outside the community will also be disclosed.

[0100] The IDs of companies that can view the recruitment requests are shown on the right side of the recruitment request database 124 in Fig. 6. For example, the disclosure level is set to "our company" for the recruitment request corresponding to request ID=001. In this case, only members belonging to the company (company ID=00A) that registered the recruitment request can view the recruitment request corresponding to request ID=001.

[0101] Hereinafter, the recruitment cases corresponding to each case ID may be referred to as case 001, case 002, case 003, etc., using the case ID. Similarly, the communities corresponding to each community ID may be referred to as community 01, community 02, community 03, etc., using the community ID, and the members corresponding to each member ID may be referred to as member P1, member P2, member P3, etc., using the member ID. Also, hereinafter, the companies corresponding to each company ID may be referred to as company A, company B, company C, etc., using parts of the company ID.

[0102] The disclosure level for case 002 is set to "within the community." According to community database 123 shown in Fig. 5, companies that have a community relationship with company A, which registered case 002, are company B and company C. Therefore, as shown in Fig. 6, only members belonging to company A, company B, or company C can view case 002.

[0103] Case 003 has the same registered companies and disclosure level as case 002. However, case 003 has "00B" registered in the non-disclosure company ID list. Therefore, as shown in Figure 6, only members belonging to either company A or company C can view case 003, and members belonging to company B are not authorized to view case 003.

[0104] For recruitment proposals with the disclosure level set to "all," all members can view the target recruitment proposal. This is the case for proposal 005 shown in Figure 6. If one or more company IDs are registered in the non-disclosure company ID list for proposal 005, the members belonging to the companies with those company IDs will not be given the permission to view proposal 005.

[0105] The inclusion criteria column and the exclusion criteria column are registered with the inclusion criteria and exclusion criteria set by the user as a recruiter to select recipients of offers for business cases. A recruiter who has multiple business cases can set the inclusion criteria and exclusion criteria for each case. A recruiter who has multiple business cases can select one or more of the multiple business cases and set the inclusion criteria and exclusion criteria for the selected case. A recruiter may set only one of the inclusion criteria and exclusion criteria for a business case.

[0106] 6 shows an example in which inclusion criteria C1 and exclusion criteria C2 are set for case 005. Inclusion criteria C1 may be, for example, "having experience in the human resources department in one's work history," and inclusion criteria C2 may be, for example, "having experience in companies X and Y in one's work history." In this case, the matching system 1 selects, from among all users, those who have experience in the human resources department and have not worked for either company X or company Y as offer candidates for the case.

[0107] The estimated man-hours and estimated period are used by applicants and the matching system 1 to estimate the time it will take to process a recruitment request.

[0108] It is possible to adopt various modified examples regarding the setting of the disclosure level. For example, the user may be able to control the destination of the disclosure of business information by selecting a specific item. More specifically, a check box for selecting a company to which the business information is to be disclosed may be provided on a screen for registering a recruitment request. Also, the user may be able to control related information and functions by selecting one of predefined options. For example, a list may be displayed on a screen for registering a recruitment request, from which the user can select the disclosure scope of the business information from among "within the company," "within the community," and "all users."

[0109] The user device 500 may provide the user with a setting screen for setting various disclosure levels. For example, the setting screen may display check boxes for the user to select the targets for which the user will disclose cases by industry, such as "pharmaceuticals," "chemicals," "electrical equipment," "railroads and buses," and "food." Furthermore, the names of companies corresponding to each industry may be displayed on the setting screen, allowing the user to select the targets for which the user will disclose cases by "industry" and by "company."

[0110] For example, suppose that the companies corresponding to "pharmaceuticals" are Company A, Company B, Company C, and Company D, the companies corresponding to "chemicals" are Company E, Company F, Company G, and Company H, and the companies corresponding to "electrical equipment" are Company I, Company J, Company K, and Company L.

[0111] In this case, the setting screen indicates that the industry of "pharmaceuticals" includes "Company A" through "Company D," and displays check boxes corresponding to "pharmaceuticals," "Company A," "Company B," "Company C," and "Company D." Furthermore, the setting screen indicates that the industry of "chemicals" includes "Company E" through "Company H," and displays check boxes corresponding to "chemicals," "Company E," "Company F," "Company G," and "Company H." Furthermore, the setting screen indicates that the industry of "electrical equipment" includes "Company I" through "Company L," and displays check boxes corresponding to "electrical equipment," "Company I," "Company J," "Company K," and "Company L."

[0112] For example, suppose a user checks the check boxes corresponding to "Pharmaceuticals" and "Chemicals" but does not check the check box corresponding to "Electrical Equipment." In this case, the "Electrical Equipment" industry is excluded from the targets for which projects will be disclosed. Furthermore, suppose that the check boxes corresponding to Companies A through C belonging to "Pharmaceuticals" and Companies E through H belonging to "Chemicals" are checked, but the check box corresponding to Company D belonging to "Pharmaceuticals" is not checked. In this case, Companies A through C belonging to "Pharmaceuticals" and Companies E through H belonging to "Chemicals" are treated as targets for which projects will be disclosed, but Company D belonging to "Pharmaceuticals" is excluded from the targets for which projects will be disclosed.

[0113] In this way, a user who has proposed a business case as a recruiter can set various contents of the disclosure information. In addition to the operation of setting the disclosure information, the user can set selection criteria (inclusion criteria and exclusion criteria) for selecting a recipient of the case. The sharing server 100 determines a recipient of the case based on the selection criteria set separately from the disclosure information. However, the sharing server 100 may also adopt the disclosure information as part of the selection criteria to determine a recipient of the case.

[0114] For example, if inclusion criteria are set but exclusion criteria are not set, the sharing server 100 may limit the range of offer candidates based on the disclosed information.

[0115] [Side Job Database 125] 7 is a diagram showing an example of side job database 125. Information showing the side job status of members is registered for each side job case in side job database 125. The information showing the side job status includes the ID of the member engaged in the side job, the case ID, the month (period of engagement in the side job), planned side job hours, actual side job hours, expected side job hours, and progress rate.

[0116] The planned side job time is the time that a member is expected to need to process an order for which the member has already received the order. Members who have received orders for side jobs input their planned side job time each month from their own applicant device 300. The input planned side job time is reflected in the side job database 125. For example, the expected man-hours for case 001 are set to 5 hours / person / month in the recruited case database 124. This means that the amount of work is 5 hours per person per month. Usually, members input the planned side job time using the expected man-hours for the recruited case as a guide.

[0117] The side job actual time is the time that the member has actually worked on the case that has been received. In other words, the side job actual time is the time that the member has already worked as actual work. Each time the member works on the case that has been received, until the work is completed, the member inputs the time that the member worked on the work on the case at any timing on the applicant device 300. The cumulative value of the time inputted on the applicant device 300 is registered in the side job database 125 as the side job actual time for each month.

[0118] The expected side job time is the time expected to be required for the work of the target case. In other words, the expected side job time is the time expected as the member's future working hours. The sharing server 100 automatically sets the expected side job time in consideration of the planned side job time and the actual side job time. The member may be allowed to input the expected side job time on his / her own applicant device 300 at any time until the work of the target case is completed. In addition, the member may be allowed to correct the expected side job time that has been automatically set. It is desirable that the expected side job time is equal to or less than the planned side job time. However, depending on the situation of the case, the expected side job time may be longer than the planned side job time. The member engaged in the case may be allowed to update the expected side job time at any time until the work of the case is completed.

[0119] The progress rate indicates the degree of progress of the side job. The progress rate is input at the discretion of the person engaged in the side job. The progress rate is input, for example, between 0(%) and 100(%).

[0120] For example, when a member first accepts an order for a certain project, the progress rate is 0%, the actual side job time is 0 hours, and the planned side job time and expected side job time match. As the member progresses with the work on the project, the expected side job time changes in conjunction with the input of the actual side job time and progress rate.

[0121] The side job database 125 shown in FIG. 7 shows side job data for member P2 from October 2021 to December 2021. Referring to the side job database 125 shown in FIG. 7, it can be seen that member P2 was engaged in case 001 and case 002 between October 2021 and December 2021.

[0122] As data for case 001 in October, side job database 125 registers planned side job hours = 5, actual side job hours = 10, and expected side job hours = 10. From this, it can be seen that member P2 worked on case 001 in October beyond the planned side job hours.

[0123] As data for case 002 for November, side job database 125 registers planned side job hours = 10, actual side job hours = 4, and expected side job hours = 8. From this, it can be seen that member P2 worked on case 002 in November without exceeding the set expected side job hours. As the progress rate is 50, it can be seen that member P2 completed half of the total work for case 002 in November.

[0124] In the side job database 125, the December data for case 001 is registered as planned side job hours = 5 and expected side job hours = 5, but no actual side job hours are registered. Similarly, the December data for case 002 is registered as no actual side job hours. This means that the system is waiting for member P2 to input actual side job hours.

[0125] The sharing server 100 calculates the member's capacity to take on additional side jobs using the side job expected time and side job actual time in the side job database 125. If the member is engaged in multiple side jobs, the sharing server 100 calculates the "total expected side job time" which is the sum of the side job expected time corresponding to those multiple side jobs, and the "total actual side job time" which is the sum of the actual side job time corresponding to those multiple side jobs. The sharing server 100 calculates the capacity for side jobs by calculating "upper limit of side job time - (total expected side job time + total actual side job time)". Here, if "total expected side job time + total actual side job time" is defined as "total side job time", the capacity for side jobs, that is, "available side job time" is calculated by "upper limit of side job time - total side job time". For example, in the side job database 125 shown in FIG. 7, the total expected side job time, which is the sum of the expected side job time of member P2 in December, is 15 hours (5 hours + 10 hours). Additionally, the total side job hours of member P2 in December was zero. If the "side job limit" set by the company to which member P2 belongs is 30 hours, member P2's spare capacity for a side job (available side job hours) is calculated as 15 hours (30 hours - 15 hours).

[0126] Here, an example of a more specific calculation procedure for the expected side job time will be described. For example, the "expected side job time" may be calculated based on the calculation formula "(man-hour progress rate / progress rate) x planned side job time - actual side job time." Here, the "man-hour progress rate" is calculated by "actual side job time / planned side job time." As already explained, the "progress rate" is a rate entered into the side job database 125 at the discretion of the person engaged in the side job.

[0127] For example, if the planned side job time = 10 hours and the actual side job time = 2 hours, the man-hour progress rate is calculated to be 20%. Now, let's say the progress rate is 40%. In this case, the expected side job time is calculated as "(20% / 40%) x 10 hours - 2 hours" = 3 hours. In other words, according to this calculation result, the expected side job time for the target side job is 3 hours.

[0128] [Evaluation Input Database 126] 8 is a diagram showing an example of the evaluation input database 126. Information on evaluations of evaluatees is registered in the evaluation input database 126. The evaluation information includes the evaluation target, the member ID of the evaluatee, the member ID of the evaluator, and the evaluation result.

[0129] The evaluation input database 126 includes a recruiter evaluation section 126A and an applicant evaluation section 126B. The recruiter evaluation section 126A registers evaluation information for the recruiter (orderer). The applicant evaluation section 126B registers evaluation information for the applicant (recipient).

[0130] In the recruiter evaluation unit 126A, the evaluation target (evaluated person) corresponds to the recruiter (client), and the evaluator corresponds to an applicant who applied for the evaluation target's recruitment work and received an order for the work. The recruiter evaluation unit 126A registers evaluations of the evaluated person for each evaluator. FIG. 8 shows an example in which members P1 and P2, who correspond to the evaluated person, are evaluated by evaluator members. In particular, FIG. 8 shows an example in which member P1 is evaluated by each of evaluator members P5, P7, P11, and P12. The evaluation result (evaluation value) is expressed as a numerical value with 10 as the maximum value and 0 as the minimum value.

[0131] In the applicant evaluation unit 126B, the evaluation target (evaluated person) corresponds to the applicant (contract recipient) for the solicited item, and the evaluator corresponds to the recruiter (orderer) of the item. The applicant evaluation unit 126B registers evaluations of the evaluated person for each evaluator. FIG. 8 shows an example in which member P7, who corresponds to the evaluated person, is evaluated by each of members P1, P2, and P3, who correspond to the evaluators. Note that in FIG. 8, examples of evaluation results in the applicant evaluation unit 126B are omitted, but various evaluation results are registered there, as in the recruiter evaluation unit 126A.

[0132] When an applicant (recipient) completes an order received from a recruiter (orderer), he / she uses the applicant device 300 to evaluate the recruiter (evaluator), who is also the assessee. The evaluation result of the evaluator is registered in the evaluation input database 126. When an applicant receives an order for another job from a recruiter who has previously received an order for another job, the applicant evaluates the recruiter again. In this case, the average value of the previous evaluation result and the subsequent evaluation result is registered in the evaluation input database 126.

[0133] When an applicant (contractor) completes a task that the applicant (contractor) has requested, the recruiter (orderer) uses the recruiter device 200 to evaluate the applicant (contractor) as an evaluator. The evaluator's evaluation results are registered in the evaluation input database 126. When a recruiter orders another task from an applicant who has previously requested a task, the recruiter evaluates the applicant again. In this case, the average value of the previous evaluation result and the subsequent evaluation result is registered in the evaluation input database 126.

[0134] Therefore, the evaluation results registered in the evaluation input database 126 reflect the average value of the evaluations of each evaluator for the person being evaluated. Note that instead of the average value, a weighted average value calculated according to the number of evaluations, a standard deviation value, or the like may be used. Evaluation results by case ID may also be registered in the evaluation input database 126.

[0135] [Evaluation Summary Database 127] 9 is a diagram showing an example of the evaluation summary database 127. Information on the evaluation of the appraisee by department is registered in the evaluation summary database 127. The information on the evaluation by organization includes the evaluation target, the member ID of the appraisee, the ID of the company to which the appraisee belongs, the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, and the evaluation summary.

[0136] The evaluation summary database 127 includes a recruiter evaluation summary section 127A and an applicant evaluation summary section 127B. In the recruiter evaluation summary section 127A, the evaluation target (evaluated person) corresponds to the recruiter (orderer). In the applicant evaluation summary section 127B, the evaluation target (evaluated person) corresponds to the applicant (receiver). In the evaluation summary database 127, evaluation summaries for the evaluation targets are registered by department.

[0137] The evaluation summary is calculated based on the tabulation results of the evaluation input database 126. The department category includes each department such as the "System Department" and the "Planning Department" belonging to the company, and "whole" meaning the entire company. The evaluation summary is calculated for each such "department".

[0138] 9 shows an example in which member P1 corresponds to the person being evaluated as the recruiter evaluation summary section 127A. The company ID of the person being evaluated is "00A." Therefore, member P1 belongs to company A. In FIG. 9, data group 1271 represents company B's evaluation of member P1 acting as a recruiter, and data group 1272 represents company C's evaluation of member P1 acting as a recruiter.

[0139] With reference to data group 1271, it can be seen that the evaluation of company B is classified into an evaluation of the entire company, an evaluation of the system department within company B, and an evaluation of the planning department within company B. In the evaluation summary, the average value of the evaluation corresponding to each classified category is registered.

[0140] For example, the evaluation summary corresponding to company B as a whole is registered with the average of the evaluation results of the members of company B who evaluated member P1 acting as a recruiter. In FIG. 9, this value is "4.75." The evaluation summary corresponding to the system department is registered with the average of the evaluation results of the members of company B who are members of the system department and who evaluated member P1 acting as a recruiter. In FIG. 9, this value is "4.0." The evaluation summary corresponding to the planning department is registered with the average of the evaluation results of the members of company B who are members of the planning department and who evaluated member P1 acting as a recruiter. In FIG. 9, this value is "5.0."

[0141] As with data group 1271, the evaluation of company C in data group 1272 is classified into evaluation of the entire company and evaluation of each department in company C. Data groups 1271 and 1272 are data that evaluate recruiters. Therefore, the evaluation summaries registered in data groups 1271 and 1272 are recruiter evaluation summaries.

[0142] The recruiter evaluation summary section 127A has been described in detail above. Next, the applicant evaluation summary section 127B will be described. FIG. 9 shows an example of the applicant evaluation summary section 127B in which member P7 is the person being evaluated. The company ID of the person being evaluated is "00C." Therefore, member P7 belongs to company C. In the applicant evaluation summary section 127B, evaluations of member P7, who acts as an applicant, are registered by department.

[0143] The applicant evaluation summary section 127B has a similar structure to the recruiter evaluation summary section 127A, except that the evaluation target is the "applicant" instead of the "recruiter." Therefore, the explanation of the applicant evaluation summary section 127B will be replaced with the explanation of the recruiter evaluation summary section 127A already given.

[0144] The sharing server 100 identifies the evaluation results of each member using the evaluation input database 126, and identifies the affiliation of each member using the member database 122. The sharing server 100 updates the data in the evaluation summary database 127 based on these identification results.

[0145] 9 shows only members P1 and P7 as assessees, other members P2 to P6, member P8, member P9, etc. are also registered as assessees in the evaluation summary database 127. The evaluation summary database 127 may include data in which the same member is the subject of evaluation as both a recruiter and an applicant. For example, in addition to a recruiter evaluation summary for member P1, an applicant evaluation summary for member P1 may be registered in the evaluation summary database 127 shown in FIG.

[0146] [Functions of the sharing server, recruiter device, and applicant device] 10 to 12 are diagrams for explaining the functions of the sharing server, the recruiter device, and the applicant device.

[0147] 10, the sharing server 100 functionally includes a community registration unit 140, a company registration unit 141, a member registration unit 142, a member search unit 143, and a case registration unit 144. These various functions are realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 provided in the sharing server 100.

[0148] The community registration unit 140 has a function of registering a community in the community database 123. A system administrator who manages the matching system 1 inputs information about the community to the sharing server 100 using an operation unit such as a keyboard (not shown).

[0149] The information about the community includes the community name and information about the companies that belong to the community. The community registration unit 140 registers the community in the community database 123 according to the input by the system administrator (step S1). The community registration unit 140 further includes a function for updating the information about the community registered in the community database 123.

[0150] The company registration unit 141 has a function of registering a new company that will join the matching system 1. A system administrator inputs information about the company to the sharing server 100 using an operation unit such as a keyboard.

[0151] The information about the company includes information such as the company name, address, side job upper limit time, etc. The company registration unit 141 registers the company in the company database 121 according to the input by the system administrator (step S2). The company registration unit 141 further includes a function of updating the information about a company that has already been registered.

[0152] The member registration unit 142 has a function of registering (signing up) a new member who will join the matching system 1. The member registration unit 142 issues a member ID and a password in response to a request from an individual belonging to a company that is affiliated with the matching system 1. An individual who wishes to become a member executes a sign-up process using a personal computer or the like (step S3).

[0153] Specifically, a person who wishes to become a member inputs information such as his / her name, company, and department into a personal computer or the like, and transmits the input information to the sharing server 100. The member registration unit 142 registers the input information in the member database 122. New members can sign in to the sharing server 100 using the personal computer used for member registration. In this case, the personal computer functions as the recruiter device 200 or the applicant device 300.

[0154] FIG. 10 shows two applicant devices 300. One is a device that is assumed to be operated by a manager of the applying company. The other is a device that is assumed to be operated by someone in the applying company other than the manager. The manager of the applying company is a managerial employee such as a department head, and corresponds to the superior of the subordinate applicants. In this embodiment, the manager of the applying company plays the role of an approver who approves applications for recruitment jobs made by subordinates.

[0155] The member search unit 143 has a function of searching for members of the matching system 1. In response to requests from the recruiter device 200 and the applicant device 300, the member search unit 143 provides information on members registered in the member database 122 to the recruiter device 200 and the applicant device 300.

[0156] The recruiter's device 200 executes a member search process when it receives a search operation from the recruiter (step S4A). This allows the recruiter to view, for example, applicant information. The recruiter can select an applicant to accept an order from among multiple applicants, taking into consideration the applicant information. Similarly, the applicant's device 300 executes a member search process when it receives a search operation for a manager who is the superior of an applicant (step S4A).

[0157] Furthermore, when the applicant device 300 receives an applicant search operation, it executes a member search process (step S4B). This allows the applicant to view, for example, the information of the recruiter. The applicant can select the job to be accepted from among multiple recruited jobs, taking into consideration the information of the recruiter.

[0158] The member search process (step S4A) executed by the recruiter device 200 and the process of the member search unit 143 will be described in detail later with reference to Fig. 19. The member search process (step S4B) executed by the applicant device 300 and the process of the member search unit 143 will be described in detail later with reference to Fig. 20.

[0159] The matter registration unit 144 has a function of registering a recruitment matter in the recruitment matter database 124. When the recruiter device 200 receives an operation to input a recruitment matter, it executes a process of registering the recruitment matter (step S5). In the process of registering the recruitment matter, the recruiter device 200 transmits information on the recruitment matter to the sharing server 100. The matter registration unit 144 registers the received information on the recruitment matter in the recruitment matter database 124.

[0160] The recruitment request registration process (step S5) executed by the recruiter device 200 and the process of the request registration unit 144 will be described in detail later with reference to FIG.

[0161] 11, the sharing server 100 functionally includes a case extraction unit 145, an application unit 146, an approval unit 147, and a notification unit 148. These various functions are realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 provided in the sharing server 100.

[0162] The job extraction unit 145 has a function of extracting job postings that can be viewed by applicants. The application unit 146 has a function of submitting an application by an applicant to a manager (the applicant's superior). The approval unit 147 has a function of sending the contents of the application for the job posting to the recruiter on the condition that approval of the application has been received from the manager (approver). The notification unit 148 has a function of receiving the result of whether or not to employ the applicant from the recruiter, and notifying the applicant and the manager of the result.

[0163] An application unit 146, an approval unit 147, and a notification unit 148 realize, by using a workflow system, notifications to the administrator requesting approval, notifications of applicants to the recruiter, and notifications of application results to applicants.

[0164] When the applicant device 300 receives an operation from the applicant requesting a search for a recruitment request, the applicant device 300 executes a search process for the recruitment request (step S6). In the search process for the recruitment request, the applicant device 300 transmits a search request to the request extraction unit 145 of the sharing server 100.

[0165] When the case extraction unit 145 receives a search request, it extracts cases that the applicant is permitted to view from among the recruitment cases registered in the recruitment case database 124, and transmits the extracted cases to the applicant device 300. The case extraction unit 145 determines whether the applicant is permitted to view the case based on a first criterion and a second criterion. The first criterion is the disclosure range set for the recruitment case. The second criterion is the applicant's spare capacity for a side job. The disclosure range is determined by the disclosure information shown in FIG. 14. The spare capacity for a side job is calculated as the available time for a side job shown in FIG. 15.

[0166] The case extraction unit 145 determines cases that satisfy both the first criterion and the second criterion as cases that the applicant is permitted to view. Therefore, the case extraction unit 145 extracts cases that are permitted to be disclosed to the applicant who received the search request from among the recruitment cases registered in the recruitment case database 124. Furthermore, the case extraction unit 145 extracts cases that can be handled within the side job available time of the applicant who received the search request from among the recruitment cases registered in the recruitment case database 124. The case extraction unit 145 transmits the cases that the applicant is permitted to view to the applicant device 300.

[0167] The case extraction unit 145 may receive an operation for setting criteria for extracting cases. For example, a function may be added to the sharing server 100 that allows a system administrator to select from a first setting that enables only the first criterion, a second setting that enables only the second criterion, and a third setting that enables both the first and second criteria.

[0168] The applicant device 300 receives the recruitment request from the request extraction unit 145. The applicant device 300 displays the received recruitment request on the display 305 (step S7).

[0169] The job search process (step S6), the job display process (step S7), and the process of the job extractor 145 will be described in detail later with reference to FIG.

[0170] The applicant operates the applicant device 300 to select an application target from among the recruitment cases displayed on the display 305. The applicant device 300 executes application processing in response to the applicant's operation (step S8). In the application processing, the applicant device 300 transmits application information indicating the case to be applied for to the application unit 146 of the sharing server 100. As a result, a request to receive an order for the work is transmitted from the applicant device 300 to the application unit 146.

[0171] The application unit 146 transmits the application information received from the applicant device 30 to the applicant device 300 of the manager (the applicant's superior). The application unit 146 identifies the member ID of the superior who is the manager of the applicant, for example, based on the relationship between the applicant's member ID and the superior's member ID registered in the member database 122. The application unit 146 transmits the subordinate's application information to the applicant device 300 corresponding to the identified superior's member ID. The manager checks the job for which the subordinate has applied on his / her own applicant device 300. The manager performs an operation to approve the application on the applicant device 300. The applicant device 300 accepts the approval operation and executes application approval processing (step S9). In the application approval processing, the applicant device 300 transmits the approval information to the approval unit 147 of the sharing server 100. As a result, the approval information, which is an example of an approval notice, is transmitted from the applicant device 300 of the manager (approver) to the approval unit 147.

[0172] The approval unit 147 accepts the applicant's application on the condition that approval information has been received from the applicant device 300. Thus, in this embodiment, the applicant's application is accepted on the condition that approval is given by the manager to whom the applicant belongs. Therefore, the manager can check in advance the content of the job for which the subordinate is applying. As a result, it is possible to prevent confidential information from leaking outside the company through the side job of an employee.

[0173] 11 shows the flow when the manager approves an application. If an operation to reject the application is accepted in step S9, rejection information is transmitted from the applicant device 300 of the manager to the approval unit 147. When the rejection information is received, the approval unit 147 may notify the applicant device 300 of the applicant that the application has been rejected.

[0174] The approval unit 147, which has accepted the applicant's application, transmits application information to the recruiter device 200. The application information includes information about the applicant and the details of the job for which the applicant is being applied. The recruiter device 200 displays the details of the application on the display 205 (step S10). The recruiter checks the applicant and the job for which the applicant is being applied based on the display 205, and determines whether or not to hire the applicant.

[0175] The recruiter inputs the result of the hiring or non-hiring decision to the recruiter device 200. The recruiter device 200 accepts the input result (step S11). The recruiter device 200 transmits the accepted result of hiring or non-hiring to the notification unit 148 of the sharing server 100.

[0176] When the notification unit 148 receives a result of employment or rejection from the recruiter device 200, it transmits the application result (result of employment or rejection) to the applicant device 300 of the applicant and the applicant device 300 of the administrator.

[0177] The applicant's device 300 and the administrator's device 300 display the application results on the display 305 (steps S12 and S13). The applicant and the administrator check the application results by looking at the display 305.

[0178] 12, the sharing server 100 functionally includes a result receiving unit 149, a result output unit 150, a review receiving unit 151, and a review output unit 152. These various functions are realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 provided in the sharing server 100.

[0179] The performance receiving unit 149 has a function of receiving the planned side job hours and actual side job hours entered by the applicant on the applicant device 300. The performance output unit 150 has a function of outputting information including the applicant's planned side job hours and actual side job hours to the recruiter device 200 or the administrator's applicant device 300.

[0180] The evaluation receiving unit 151 has a function of receiving an evaluation of an applicant (recipient) input by a recruiter on the recruiter device 200. The evaluation output unit 152 has a function of outputting information indicating an evaluation of an applicant to the recruiter device 200.

[0181] When an applicant engages in a side job, he / she inputs the planned side job hours and the actual side job hours into the applicant device 300. An applicant normally inputs the planned side job hours into the applicant device 300 when he / she receives an order for a new side job, and inputs the actual side job hours into the applicant device 300 at any timing while he / she is engaged in the side job. For example, when an applicant receives an order for a side job that is expected to span multiple months, the applicant inputs the actual side job hours into the applicant device 300 for each month.

[0182] The applicant device 300 receives the input of the side job planned time and the side job actual time (step S14). The applicant device 300 transmits the received side job planned time and side job actual time to the actual time receiving unit 149 of the sharing server 100.

[0183] The result receiving section 149 registers the received side job planned time and side job actual time in the side job database 125. The process of step S14 executed by the applicant device 300 and the process of the result receiving section 149 will be described in detail later with reference to FIG.

[0184] The result output unit 150 transmits the side job planned time and side job actual time registered in the side job database 125 to the recruiter device 200 and the manager's applicant device 300. The recruiter device 200 displays the received information including the side job planned time and side job actual time on the display 205, and the manager's applicant device 300 displays the received information including the side job planned time and side job actual time on the display 305 (step S15). However, when comparing the information transmitted to the recruiter device 200 and the information transmitted to the manager's applicant device 300, the cases to be transmitted are different.

[0185] Data corresponding to cases that the subordinate is in charge of, among the many cases registered in the side job database 125, is transmitted from the achievement receiving unit 149 to the manager's applicant device 300. The manager can check the side job status of the subordinate by looking at the display 305. The screen displayed on the manager's applicant device 300 when the manager checks the side job status of the subordinate will be explained later using FIG. 23.

[0186] Data corresponding to the cases recruited by the recruiters among the many cases registered in the side job database 125 is transmitted from the achievement receiving unit 149 to the recruiter device 200. For example, in the side job database 125 shown in Fig. 7, consider a case in which, among multiple recruiters, a first recruiter is recruiting for case 001 and a second recruiter is recruiting for case 002.

[0187] In this case, various data corresponding to case 001 in the side job database 125 is transmitted from the achievement receiving unit 149 to the recruiter device 200 operated by the first recruiter. Various data corresponding to case 002 in the side job database 125 is transmitted from the achievement receiving unit 149 to the recruiter device 200 operated by the second recruiter.

[0188] The first and second recruiters can check the progress of their own cases by viewing the planned side job hours and actual side job hours, etc., displayed on the display 305 of the recruiter device 200.

[0189] When the side job is completed, the recruiter inputs the evaluation of the applicant to the recruiter device 200. The recruiter device 200 accepts the input of the evaluation of the applicant (step S16A). Therefore, when accepting the input evaluation, the recruiter device 200 functions as an evaluator device operated by the evaluator (recruiter).

[0190] The recruiter device 200 transmits the received evaluation to the evaluation receiving unit 151 of the sharing server 100. The evaluation receiving unit 151 updates the evaluation input database 126 and the evaluation summary database 127 based on the received evaluation. As a result, in the evaluation input database 126, the information in the applicant evaluation unit 126B is updated, and in the evaluation summary database 127, the information in the applicant evaluation summary unit 127B is updated.

[0191] The process of step S16A executed by the recruiter device 200 and the process of the evaluation receiving unit 151 will be described in detail later with reference to FIG.

[0192] When the recruiter accepts an operation to view the evaluation of the applicant, the recruiter device 200 executes a viewing request process (step S17A). In the viewing request process, the recruiter device 200 transmits a viewing request to the evaluation output unit 152 of the sharing server 100. In response to the viewing request, the evaluation output unit 152 transmits the evaluation of the applicant (applicant evaluation summary) registered in the evaluation summary database 127 to the recruiter device 200. The recruiter device 200 displays the received evaluation of the applicant on the display 205 (step S18A).

[0193] The processes of steps S17A and S18A executed by the recruiter device 200 and the process of the evaluation output unit 152 will be described in detail later with reference to FIG.

[0194] Fig. 13 is a diagram for further explaining the functions of the applicant device 300. Here, the input and output of evaluations of the recruiter will be explained using Fig. 13. The evaluation receiving unit 151 further has a function of receiving an evaluation of the recruiter input by the applicant on the applicant device 300. The evaluation output unit 152 further has a function of outputting information indicating an evaluation of the recruiter to the applicant device 300. When the applicant completes the ordered work, he or she inputs an evaluation of the recruiter to the applicant device 300. There are various points on which an applicant evaluates the recruiter.

[0195] For example, if the applicant can communicate smoothly with the recruiter and complete the work within the appropriate time, the applicant will give the recruiter a high evaluation. Conversely, if there are many requests for additions, changes, and modifications to the work content, too much time is spent outside the scope of the work, instructions are communicated too late, and instructions are given unilaterally without prior consultation regarding modifications to the work content, the applicant will give the recruiter a low evaluation.

[0196] The applicant device 300 receives the input of the evaluation for the recruiter (step S16B). Therefore, when receiving the input evaluation, the applicant device 300 functions as an evaluator device operated by an evaluator (applicant).

[0197] The applicant device 300 transmits the received evaluation to the evaluation receiving unit 151 of the sharing server 100. The evaluation receiving unit 151 updates the evaluation input database 126 and the evaluation summary database 127 based on the received evaluation. As a result, in the evaluation input database 126, the information in the recruiter evaluation unit 126A is updated, and in the evaluation summary database 127, the information in the recruiter evaluation summary unit 127A is updated.

[0198] The process of step S16B executed by applicant device 300 and the process of evaluation receiving section 151 will be described in detail later with reference to FIG.

[0199] When the applicant device 300 receives an operation for the applicant to view the evaluation of the recruiter, it executes a viewing request process (step S17B). In the viewing request process, the recruiter device 200 transmits a viewing request to the evaluation output unit 152 of the sharing server 100. In response to the viewing request, the evaluation output unit 152 transmits the evaluation of the recruiter (recruiter evaluation summary) registered in the evaluation summary database 127 to the applicant device 300. The applicant device 300 displays the received evaluation of the recruiter on the display 305 (step S18B).

[0200] The processes of steps S17B and S18B executed by applicant device 300 and the processes of evaluation output section 152 will be described in detail later with reference to FIG.

[0201] [Details of the processing by the case registration unit 144 and the recruiter device 200] Fig. 14 is a diagram for explaining the procedure for registering a recruitment request in the recruitment request database 124. Step S5 in Fig. 10 and the function of the request registration unit 144 will be described in more detail with reference to Fig. 14.

[0202] A recruiter who registers a recruitment case first signs in to the sharing server 100 using the recruiter device 200. This establishes a logical communication path identified by the recruiter's member ID between the recruiter device 200 and the sharing server 100. Next, the recruiter inputs the business information and disclosure information of the recruitment case into the recruiter device 200 using the operation unit 206 such as a mouse and keyboard.

[0203] The information inputted by the operation unit 206 is notified to the processor 201 via the input / output interface 204 of the recruiter device 200. The operation unit 206 and the input / output interface 204 constitute an interface that accepts an operation to input the contents of the business and an operation to input the disclosure information that specifies the target to which the business is to be disclosed.

[0204] The business information of the job posting includes the job title, job content, estimated man-months, and estimated period. The disclosure information includes the disclosure level. The disclosure information may include the IDs of companies that are not to be disclosed, depending on the selection of the job posting holder.

[0205] The recruiter device 200 receives input of the business information and disclosure information of the recruitment request, and executes a process of registering the recruitment request (step S5). In the process of registering the recruitment request, the recruiter device 200 transmits the business information and disclosure information of the recruitment request to the sharing server 100.

[0206] The request registration unit 144 of the sharing server 100 acquires information about the recruiter (step S1441). Specifically, the request registration unit 144 identifies the company to which the recruiter belongs.

[0207] The sharing server 100 stores the member ID used when a member signs in to the sharing server 100 using the recruiter device 200 or the applicant device 300. When the sharing server 100 receives any information from the recruiter device 200 or the applicant device 300 in communication established by this member ID, it identifies the member who sent the information by the member ID used to sign in.

[0208] Therefore, when business information and disclosure information of a recruitment business are received from the recruiter device 200, the case registration unit 144 uses the member ID used to sign in to identify the recruiter operating the recruiter device 200. The case registration unit 144 uses the identified member ID, the member database 122, and the company database 121 to identify the member who is the recruiter and the company to which the recruiter belongs.

[0209] Next, the case registration unit 144 executes a process of registering the solicited case in the solicited case database 124 (step S1442). Specifically, after generating a case ID, the case registration unit 144 registers the company information (company ID), the ID of the company to be withheld, the disclosure level, the case title, the estimated man-hours, the estimated period, the case content, and the like in the solicited case database 124 in association with the generated case ID.

[0210] According to this embodiment, the recruiter can freely control the disclosure scope of the recruitment request at the level of "within the company," "within the community," or "without restriction." As a result, the recruiter can prevent the recruitment request from being disclosed to a specific company without the recruiter's intention.

[0211] When registering a recruitment case, the recruiter can set selection criteria (inclusion criteria and exclusion criteria) for selecting offerees for the case, in addition to the disclosure information. Setting of selection criteria will be described later with reference to Figures 27 and 28.

[0212] According to this embodiment, the companies to be excluded from disclosure can be set separately from the disclosure level. Therefore, the recruiter can set the disclosure range by excluding some of the companies that have a community relationship with the recruiter's company. As a result, it is possible to prevent the business related to a specific company in the community from being disclosed to that specific company.

[0213] Instead of or in addition to the non-disclosure company ID list, a non-disclosure member ID list for registering member IDs for which disclosure of recruitment requests is prohibited may be provided in the recruitment request database 124. The recruiter device 200 may accept an operation to designate a member for whom disclosure of recruitment requests is prohibited, and transmit the member ID to the sharing server 100. The sharing server 100 may not provide the recruitment requests corresponding to the member IDs listed in the non-disclosure member ID list to the members corresponding to the member IDs listed in the list. In this way, the recruiter device 200 may accept either companies or members as persons for whom disclosure of business is prohibited.

[0214] Fig. 15 is a diagram for explaining the procedure for searching for recruitment requests from the database 120. The processes in steps S6 and S7 in Fig. 11 and the function of the request extraction unit 145 will be explained in more detail with reference to Fig. 15.

[0215] When the applicant device 300 receives an operation from the applicant requesting a search for a recruitment request, the applicant device 300 executes a search process for the recruitment request (step S6). In the search process for the recruitment request, the applicant device 300 transmits a search request to the request extraction unit 145 of the sharing server 100.

[0216] When the request extraction unit 145 receives the search request, it extracts requests that the applicant is permitted to view, from among the requests registered in the request database 124. To this end, the request extraction unit 145 executes the processes of steps S1451 to S1454.

[0217] Steps S1451 and S1452 are processes for extracting cases that the applicant is permitted to view based on the disclosure scope set for the recruitment case. In step S1451, the applicant's company and the company's community are determined. In step S1452, cases that can be disclosed are extracted.

[0218] Step S1453 is a process for extracting jobs that the applicant is permitted to view based on the applicant's spare capacity for a side job. Step S1454 is a process for finally extracting jobs that match the applicant.

[0219] [Process to extract cases based on disclosure scope] Step S1451 includes step S1451A and step S1451B.

[0220] In step S1451A, the applicant's company is identified based on the member ID, company database 121, and member database 122 used at the time of signing in.

[0221] In step S1451B, the community of the company to which the applicant belongs is identified based on the ID of the company to which the applicant belongs and community database 123.

[0222] Step S1452 includes step S1452A and step S1452B. In step S1452A, discloseable recruitment requests are extracted from recruitment request database 124 based on the community to which the applicant's company belongs and the disclosure level.

[0223] In step S1452B, among the recruitment jobs extracted in step S1452A, those in which the applicant's affiliated company is included in the non-disclosure company list are excluded. Here, the job extracted by the process of step S1452B is referred to as job X.

[0224] [Process to extract cases based on spare capacity for side jobs] Step S1453 includes step S1453A, step S1453B, and step S1453C.

[0225] In step S1453A, the applicant's permitted side job time T1 is calculated. The permitted side job time is derived by calculating "side job maximum time - side job total time". The side job maximum time is a time set by the company to which the applicant belongs, and is registered in the company database 121. The calculated permitted side job time is registered in the member database 122. The case extraction unit 145 may calculate the permitted side job time of all members at regular intervals, and register the calculated permitted side job time in the member database 122.

[0226] The total side job time is calculated by the formula "total expected side job time + total actual side job time" based on the expected side job time and actual side job time registered in the side job database 125. In other words, the total side job time includes the time already spent on the side job as well as the expected time not yet spent on the side job.

[0227] In step S1453B, time T2 required to complete the work is calculated for each job. Time T2 is calculated based on the estimated man-hours (man-months) and estimated period registered in job database 124. For example, the estimated man-hours (months) may be used as time T2. For example, 5 hours per month may be set as time T2 for the job corresponding to job ID 001.

[0228] In step S1453C, jobs that satisfy the condition "time T2≦available side job time T1" are extracted from the job database 124. Here, the job extracted by the process of step S1453C is referred to as job Y.

[0229] [Process to extract cases based on disclosure scope and side job capacity] The case extraction unit 145 extracts case X based on the disclosure scope, extracts case Y based on the side job capacity, and then extracts cases that overlap between case X and case Y as matching cases for the applicant (step S1454).

[0230] [Process to provide extracted cases] Next, the case extraction unit 145 transmits information about the matching cases to the applicant device 300 (step S1455). The applicant device 300 receives the matching cases. The applicant device 300 displays a list of the received matching cases as recruiting cases on the display 305 (step S7).

[0231] This provides applicants with job postings that are appropriate from two perspectives. First, applicants are provided with job postings that they can handle without exceeding the maximum number of hours they can work on a side job. This prevents applicants from becoming overworked. Second, a recruiter's job postings are provided only to applicants who fall within the scope of disclosure intended by the recruiter. This prevents confidential information about the recruiter's company from being leaked to competitors.

[0232] [Process to register planned and actual side job hours] Fig. 16 is a diagram for explaining the procedure for registering plans and results of a side job in database 120. Step S14 in Fig. 12 and the function of result receiving unit 149 will be described in more detail with reference to Fig. 16.

[0233] For example, when an applicant receives an order for a new side job, the applicant inputs the planned side job time into the applicant device 300, and inputs the actual side job time into the applicant device 300 at any timing while the applicant is engaged in the side job. The applicant device 300 accepts the input of the planned side job time (step S14). The applicant device 300 transmits the accepted planned side job time and actual side job time to the performance acceptance unit 149 of the sharing server 100.

[0234] The result receiving unit 149 receives the applicant's planned side job hours and actual side job hours, and registers the accepted applicant's planned side job hours and actual side job hours in the side job database 125 (step S1511). As a result, the applicant's planned side job hours and actual side job hours for each month are registered in the side job database 125 by case ID.

[0235] Typically, after an applicant inputs the planned side job hours, the applicant also inputs the actual side job hours at the end of the month. For this reason, side job database 125 may contain cases in which the planned side job hours are registered but the actual side job hours are not registered. For example, when an applicant who has received an order for a side job inputs the planned side job hours, the planned side job hours are registered as data corresponding to that side job, but the actual side job hours are not registered.

[0236] Next, the result receiving unit 149 automatically calculates the side job expected time for the current month (step S1512). The result receiving unit 149 calculates the side job expected time based on the planned side job time and the actual side job time. Specifically, as already explained, the "side job expected time" is calculated based on the calculation formula "(manpower progress rate / progress rate) x planned side job time - actual side job time". Note that the result receiving unit 149 may calculate the "side job expected time" using the calculation formula "planned side job time - actual side job time". The result receiving unit 149 registers the calculated side job expected time in the side job database 125. As shown in the side job database 125 in FIG. 7, the side job expected time is registered for each case ID.

[0237] [Process to register evaluation results (evaluation of applicants)] Fig. 17 is a diagram for explaining the procedure for registering an evaluation of an applicant in database 120. Step S16A in Fig. 12 and the function of evaluation receiving unit 151 will be described in more detail with reference to Fig. 17.

[0238] When the applicant completes the side job, he / she reports the delivery and completion to the recruiter and has the recruiter inspect the job. The recruiter then operates the recruiter device 200 to input an evaluation of the applicant to the recruiter device 200. The recruiter device 200 accepts the input evaluation (step S16A). The recruiter device 200 transmits the accepted evaluation to the evaluation receiving unit 151 of the sharing server 100. The information transmitted from the recruiter device 200 to the sharing server 100 includes the member ID of the applicant who is to be evaluated and the evaluation value (0 to 10).

[0239] When the evaluation receiving unit 151 receives information on the evaluation of the evaluatee (applicant) from the recruiter device 200, it reflects the evaluation of the evaluatee in the evaluation input database 126 (step S1513A).

[0240] If evaluation results for the assessee (applicant) have already been registered in the evaluation input database 126, the evaluation receiving unit 151 calculates the average value of the evaluation results for the assessee, including the currently received evaluation value. The evaluation receiving unit 151 updates the evaluation results registered in the evaluation input database 126 with the calculated average value. As a result, the average values ​​of the evaluations (evaluation results) for the assessee (applicant) are registered for each evaluator (recruiter) in the evaluation input database 126. This updates the information in the applicant evaluation unit 126B in the evaluation input database 126.

[0241] Next, the evaluation receiving unit 151 executes evaluation summary processing (step S1514A). In the evaluation summary processing, the evaluation receiving unit 151 calculates the average value of the evaluation results for the evaluatees (applicants) by company and department, and registers the calculation results in the evaluation summary database 127. As a result, the information in the applicant evaluation summary section 127B in the evaluation summary database 127 is updated.

[0242] For example, the evaluation receiving unit 151 identifies the evaluator (recruiter) by using the member ID used by the recruiter device 200 to sign in to execute step S16A. The evaluation receiving unit 151 identifies the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, the member ID of the person being evaluated, and the ID of the company to which the person being evaluated belongs, based on the evaluation information received in step S1513A, the company database 121, and the member database 122. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) of a person who has accessed the sharing server 100."

[0243] The evaluation receiving unit 151 accesses the evaluation summary database 127 and detects a data row in which the specified IDs (the member ID of the person being evaluated, the ID of the company to which the person being evaluated belongs, and the ID of the company to which the evaluator belongs) are lined up. The evaluation receiving unit 151 updates the value of the applicant evaluation summary corresponding to the detected data row.

[0244] [Process to register evaluation results (evaluation of recruiters)] Fig. 18 is a diagram for explaining the procedure for registering an evaluation of a recruiter in a database. Step S16B in Fig. 13 and the function of the evaluation receiving unit 151 will be described in more detail with reference to Fig. 18.

[0245] As described above, when an applicant completes a side job, he / she reports delivery and completion to the recruiter and has the recruiter inspect the job. The applicant then operates the applicant device 300 to input an evaluation of the recruiter to the applicant device 300. The applicant device 300 accepts the input evaluation (step S16B). The applicant device 300 transmits the accepted evaluation to the evaluation receiving unit 151 of the sharing server 100. The information transmitted from the applicant device 300 to the sharing server 100 includes the member ID of the recruiter who is being evaluated and the evaluation value (0 to 10).

[0246] When the evaluation receiving unit 151 receives information on the evaluation of the evaluatee (recruiter) from the applicant device 300, it reflects the evaluation of the evaluatee in the evaluation input database 126 (step S1513B).

[0247] If evaluation results for the assessee (recruiter) have already been registered in the evaluation input database 126, the evaluation receiving unit 151 calculates the average value of the evaluation results for the assessee, including the currently received evaluation value. The evaluation receiving unit 151 updates the evaluation results registered in the evaluation input database 126 with the calculated average value. As a result, the average values ​​of the evaluations (evaluation results) for the assessee (recruiter) are registered for each evaluator (applicant) in the evaluation input database 126. This updates the information in the recruiter evaluation unit 126A in the evaluation input database 126.

[0248] Next, the evaluation receiving unit 151 executes the evaluation summary process (step S1514B). In the evaluation summary process, the evaluation receiving unit 151 calculates the average value of the evaluation results for the evaluatees (recruiters) by company and department, and registers the calculation results in the evaluation summary database 127. As a result, the information of the recruiter evaluation summary unit 127A is updated in the evaluation summary database 127.

[0249] For example, the evaluation receiving unit 151 identifies the evaluator (applicant) by using the member ID used by the applicant device 300 to sign in to execute step S16B. The evaluation receiving unit 151 identifies the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, the member ID of the person being evaluated, and the ID of the company to which the person being evaluated belongs, based on the evaluation information received in step S1513B, the company database 121, and the member database 122. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) of a person who has accessed the sharing server 100."

[0250] The evaluation receiving unit 151 accesses the evaluation summary database 127 and detects a data row in which the specified IDs (the member ID of the person being evaluated, the ID of the company to which the person being evaluated belongs, and the ID of the company to which the evaluator belongs) are lined up. The evaluation receiving unit 151 updates the value of the recruiter evaluation summary corresponding to the detected data row.

[0251] For example, the data group 1271 in Fig. 9 includes the member ID P1 of the person being evaluated, the ID 00A of the company to which the person being evaluated belongs, and the ID 00B of the company to which the evaluator belongs. When a member belonging to the system department of company B evaluates member P1, the evaluation is accepted in step S1513B.

[0252] In this case, in step S1514B, the evaluation received in step S1513B is reflected in the recruiter evaluation summary corresponding to the “whole” of data group 1271 and the recruiter evaluation summary corresponding to the “system section”.

[0253] More specifically, the evaluation receiving unit 151 sets the average value of the evaluations of the entire company B, including the evaluations received in step S1513B, as the recruiter evaluation summary corresponding to the “overall” of the data group 1271. Similarly, the evaluation receiving unit 151 sets the average value of the evaluations of the system part, including the evaluations received in step S1513B, as the recruiter evaluation summary corresponding to the “system part” of the data group 1271.

[0254] Fig. 19 is a diagram for explaining the procedure for displaying the evaluation of an applicant and the search results of members on the display 205. Using Fig. 19, step S4A (processing of the recruiter device 200) and the function of the member search unit 143 in Fig. 10, as well as step S17A, step S18A and the function of the evaluation output unit 152 in Fig. 12 will be explained in more detail.

[0255] [Process to output the applicant's evaluation summary] First, the processes in steps S17A, S18A, S1521A, and S1522A shown in FIG. 19 will be described.

[0256] When the recruiter's device 200 receives an operation to view the evaluations of the applicant from the recruiter, the recruiter's device 200 executes a view request process (step S17A). In the view request process, the recruiter's device 200 transmits a view request to the evaluation output unit 152 of the sharing server 100. In response to the view request, the evaluation output unit 152 selects from the evaluation summary database 127 an applicant evaluation summary that the recruiter (view requester) is authorized to view (step S1521A).

[0257] The recruiter who made the viewing request is authorized to view the applicant evaluation summary that is for the entire company to which the recruiter belongs and the applicant evaluation summary that is for the department to which the recruiter belongs. The recruiter who made the viewing request is not authorized to view evaluation summaries other than these. The evaluation output unit 152 determines the viewing authority based on the member ID of the recruiter who sent the viewing request, the company database 121, and the member database 122. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) and viewing authority of a person who has accessed the sharing server 100."

[0258] The evaluation output unit 152 selects an applicant evaluation summary corresponding to the viewing authority from the evaluation summary database 127. The evaluation output unit 152 transmits data including the selected applicant evaluation summary to the recruiter device 200 (step S1522A). In addition to the applicant evaluation summary, the transmitted data includes the applicant's (evaluated) member ID, information about the company to which the applicant belongs, information about the department to which the applicant belongs, and the like. The transmitted data may include applicant evaluation summaries corresponding to each of multiple applicants (evaluated) in response to the viewing request.

[0259] Receiving the applicant evaluation summary, the recruiter device 200 displays the applicant evaluation summary together with information about the company to which the applicant belongs and information about the department to which the applicant belongs on the display 205 (step S18A). When applicant evaluation summaries corresponding to each of multiple applicants (evaluated persons) are received, the recruiter device 200 displays the applicant evaluation summaries in a list of multiple applicants (evaluated persons).

[0260] In this way, when the sharing server 100 receives a viewing request in communication established by a member ID that can identify the company and department to which the recruiter belongs, it transmits an applicant evaluation summary, which is an example of evaluation information, to the recruiter device 200 of the recruiter that sent the viewing request.

[0261] [Process to search for members (applicants)] Next, with reference to FIG. 19, the processes in steps S4A, S19A, and S1431A to S1433A will be described.

[0262] When the recruiter device 200 receives a search operation from the recruiter, it executes a member search process to search for information on the applicant (step S4A). In the member search process, the recruiter device 200 transmits a search request to the member search unit 143 of the sharing server 100. The search request includes a reference value for excluding members with low applicant evaluations. This reference value is determined, for example, based on the value of the applicant evaluation summary.

[0263] The member search unit 143 that has received the search request identifies the company to which the recruiter who sent the search request belongs (step S1431A). Here, the company identified in step S1431A is referred to as "company Xa."

[0264] The member search unit 143 identifies the recruiter operating the recruiter device 200 by using the member ID used when the recruiter device 200 signed in to the sharing server 100. The member search unit 143 identifies the company Xa to which the recruiter belongs by using the company database 121 and the member database 122.

[0265] Next, the member search unit 143 extracts members whose applicant evaluation summary values ​​for the identified company Xa as a whole exceed a reference value from the evaluation summary database 127 (step S1432A). In other words, the member search unit 143 extracts search results, excluding members whose evaluations of the company Xa as a whole are low.

[0266] It should be noted here that the member search unit 143 determines whether the evaluation is low or not based on the applicant evaluation summary. That is, member α, who has the authority of both an applicant and a recruiter, may behave as an applicant or as a recruiter. Therefore, as evaluation summaries for such member α, an applicant evaluation summary and a recruiter evaluation summary are registered in the evaluation summary database 127. Member α may have a high evaluation as a recruiter, but a low evaluation as an applicant. In this case, member α may be excluded from the extraction targets in step S1432A.

[0267] The sharing server 100 may be provided with a function for receiving setting information of the reference value from the recruiter device 200 of each company. This allows each company to exclude members with low evaluations based on its own reference value from the search results.

[0268] Next, the member search unit 143 outputs the extracted member information as a search result to the recruiter device 200 that made the search request (step S1433A). The recruiter device 200 displays the received search results in a list on the display 205 (step S19A).

[0269] As a result, the recruiter can view the search results excluding members whose companies have low overall ratings on the display 205. Therefore, when selecting contractors from among applicants, the recruiter can save the trouble of visually excluding members whose companies have low overall ratings.

[0270] In this embodiment, even if a member has a low evaluation of a department of the company to which the recruiter belongs, the member will not be excluded from the search results if the evaluation of the company as a whole is not low. However, the member search unit 143 may further exclude such a member from the search results.

[0271] Fig. 20 is a diagram for explaining the procedure for displaying the evaluation of the recruiter and the search results of the members on the display 305. Using Fig. 20, step S4B (processing of the applicant device 300) and the function of the member search unit 143 in Fig. 10, as well as step S17B, step S18B and the function of the evaluation output unit 152 in Fig. 13 will be explained in more detail.

[0272] [Process to output the recruiter's evaluation summary] First, the processes in steps S17B, S18B, S1521B, and S1522B shown in FIG. 20 will be described.

[0273] When the applicant device 300 receives an operation for the applicant to view the evaluation of the recruiter, the applicant device 300 executes a view request process (step S17B). In the view request process, the applicant device 300 transmits a view request to the evaluation output unit 152 of the sharing server 100. In response to the view request, the evaluation output unit 152 selects from the evaluation summary database 127 a recruiter evaluation summary for which the applicant (view requester) has been granted viewing authority (step S1521B).

[0274] The applicant who made the viewing request is authorized to view the recruiter evaluation summary that is for the entire company to which the applicant belongs and the recruiter evaluation summary that is for the department to which the applicant belongs. The applicant who made the viewing request is not authorized to view evaluation summaries other than these. The evaluation output unit 152 determines the viewing authority based on the member ID of the applicant who sends the viewing request, the company database 121, and the member database 122. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) and viewing authority of a person who has accessed the sharing server 100."

[0275] The evaluation output unit 152 selects a recruiter evaluation summary corresponding to the viewing authority from the evaluation summary database 127. The evaluation output unit 152 transmits data including the selected recruiter evaluation summary to the applicant device 300 (step S1522B). The transmitted data includes the recruiter evaluation summary as well as the member ID of the recruiter (evaluated person), information on the company to which the recruiter belongs, information on the department to which the recruiter belongs, etc. The transmitted data may include a recruiter evaluation summary corresponding to each of multiple recruiters (evaluated people) in response to the viewing request.

[0276] The applicant device 300 that has received the recruiter evaluation summary displays the recruiter evaluation summary together with information about the company to which the recruiter belongs and information about the department to which the recruiter belongs on the display 305 (step S18B). When receiving recruiter evaluation summaries corresponding to each of multiple recruiters (evaluated persons), the applicant device 300 displays the recruiter evaluation summary in a list of multiple recruiters (evaluated persons).

[0277] In this way, when the sharing server 100 receives a viewing request in communication established by a member ID that can identify the company and department to which the applicant belongs, it transmits an applicant evaluation summary, which is an example of evaluation information, to the applicant device 300 of the applicant who sent the viewing request.

[0278] [Process to search for members (recruiters)] Next, with reference to FIG. 20, the processes in steps S4B, S19B, and S1431B to S1433B will be described.

[0279] When the applicant device 300 receives a search operation from the applicant, it executes a member search process to search for information about the recruiter (step S4B). In the member search process, the applicant device 300 transmits a search request to the member search unit 143 of the sharing server 100. The search request includes a reference value for excluding members with low evaluations as recruiters. This reference value is determined, for example, based on the value of the recruiter evaluation summary.

[0280] Upon receiving the search request, member search unit 143 identifies the company to which the applicant who sent the search request belongs (step S1431B). Here, the company identified in step S1431B is referred to as "company Xb."

[0281] The member search unit 143 identifies the applicant who is operating the applicant device 300, using the member ID used when the applicant device 300 signed in to the sharing server 100. The member search unit 143 uses the company database 121 and the member database 122 to identify the company Xb to which the applicant belongs.

[0282] Next, the member search unit 143 extracts members whose recruiter evaluation summary values ​​for the entire identified company Xb exceed a reference value from the evaluation summary database 127 (step S1432B). In other words, the member search unit 143 extracts search results by excluding members whose evaluations of the entire company Xb are low.

[0283] The sharing server 100 may be provided with a function for receiving setting information of the reference value from the recruiter device 200 of each company. This allows each company to exclude members with low evaluations based on its own reference value from the search results.

[0284] Next, the member search unit 143 outputs the extracted member information as a search result to the applicant device 300 that issued the search request (step S1433B). The applicant device 300 displays the received search results in a list on the display 305 (step S19B).

[0285] As a result, the applicant can view the search results excluding members whose companies have low overall ratings on the display 305. Therefore, when selecting contractors from among the recruiters, the applicant can save the trouble of visually excluding members whose companies have low overall ratings.

[0286] In this embodiment, even if a member has a low evaluation for a certain department of the company to which the applicant belongs, the member is not excluded from the search results if the evaluation for the entire company is not low. However, the member search unit 143 may further exclude such a member from the search results.

[0287] [Availability of evaluation summary database 127] Fig. 21 is a diagram for explaining the viewable range of the evaluation summary database 127. Here, the viewable range will be explained by taking as an example the recruiter evaluation summary section 127A, which is also shown in Fig. 9, of the evaluation summary database 127.

[0288] The recruiter evaluation summary section 127A shown in FIG. 21 includes evaluation summaries from companies B and C for member P1, who acts as a "recruiter." Member P1 belongs to company A. The evaluation summary for company B is classified into "overall," "system department," and "planning department." The evaluation summary for company C is classified into "overall," "planning department," etc. Members belonging to companies B and C view the evaluation summaries for member P1 as "applicants."

[0289] The viewing authority for the evaluation summary calculated from the overall evaluation of company B is granted to all members belonging to company B, as shown in the "Viewable range" column in FIG.

[0290] Viewing rights for the evaluation summary calculated from the evaluation of the System Department of Company B are granted to members of the System Department of Company B, but are not granted to members other than the System Department of Company B. Viewing rights for the evaluation summary calculated from the evaluation of the Planning Department of Company B are granted to members of the Planning Department of Company B, but are not granted to members other than the Planning Department of Company B.

[0291] The right to view the evaluation summary calculated from the overall evaluation of Company C is granted to all members belonging to Company C. The right to view the evaluation summary calculated from the evaluation of the Planning Department of Company C is granted to members of the Planning Department of Company C, but not to members other than the Planning Department of Company C.

[0292] The above describes the viewable range using the recruiter evaluation summary section 127A as an example. In the matching system 1, the viewable range of the applicant evaluation summary section 127B (see FIG. 9) is also determined based on the same design concept as the recruiter evaluation summary section 127A.

[0293] If the viewers are members of Company X's first division and Company X's second division, the viewers' authority to the evaluation summary of Company X as a whole, the evaluation summary of Company X's first division, and the evaluation summary of Company X's second division will be as shown in Table 401 in Figure 21. Here, when the applicant corresponds to a "viewer," the evaluation summary to be viewed is the evaluation summary of the "recruiter." Conversely, when the recruiter corresponds to a "viewer," the evaluation summary to be viewed is the evaluation summary of the "applicant."

[0294] Members belonging to the first division of company X can view the evaluation summary of company X as a whole and the evaluation summary of company X's first division, but cannot view the evaluation summary of company X's second division. Members belonging to the second division of company X can view the evaluation summary of company X as a whole and the evaluation summary of company X's second division, but cannot view the evaluation summary of company X's second division. Members belonging to company Y other than company X cannot view the evaluation summary of company X as a whole, the evaluation summary of company X's first division, and the evaluation summary of company X's second division.

[0295] The evaluation summary of company X as a whole, the evaluation summary of company X's first division, and the evaluation summary of company X's second division will not be disclosed to members of companies other than company X. Therefore, when evaluating a recruiter belonging to company X, a member belonging to company Y acting as an applicant can objectively evaluate the recruiter belonging to company X without considering the relationship between the companies, etc. Similarly, when evaluating an applicant belonging to company X, a member belonging to company Y acting as a recruiter can objectively evaluate the applicant belonging to company X without considering the relationship between the companies, etc.

[0296] Additionally, the evaluations made by members of Company X (evaluations of recruiters and applicants) are shared within Company X as a recruiter evaluation summary and an applicant evaluation summary. This allows evaluators to be aware that the accumulation of each evaluation produces useful information. This motivates evaluators to make accurate evaluations.

[0297] As a result, the accuracy of the recruiter evaluation summary and the applicant evaluation summary is improved. This allows the recruiter evaluation summary to be usefully used as reference data when selecting a job to be recruited for. Similarly, the applicant evaluation summary can be usefully used as reference data when selecting a contractor.

[0298] Furthermore, according to this embodiment, when the recruiter device 200 executes the member search process (step S4A), the search results excluding low-rated members are provided to the recruiter (step S1432A). Similarly, when the applicant device 300 executes the member search process (step S4B), the search results excluding low-rated members are provided to the recruiter (step S1432B). In other words, the matching system 1 has a filtering function that provides search results excluding low-rated members.

[0299] Therefore, when deciding on a contractor for a job, the recruiter can prevent, on a company-by-company basis, the mistake of hiring a member with a low evaluation. Similarly, when deciding on a job to apply for from among a large number of jobs, the applicant can prevent, on a company-by-company basis, the mistake of selecting a job that is being recruited by a member with a low evaluation. The sharing server 100 may perform filtering using the evaluation summary on a department-by-department basis.

[0300] A command signal instructing which of filtering using the evaluation summary of the entire company or filtering using the evaluation summary of each department should be used may be transmitted from the recruiter device 200 to the sharing server 100. In this case, the sharing server 100 is provided with a function for changing the evaluation summary used for filtering in response to the command signal.

[0301] [Example of how the scope of disclosure is set according to the disclosure level] Fig. 22 is a diagram showing an example in which the disclosure range is set according to the disclosure level. Here, as shown in Fig. 22, consider a case in which companies A to E form a community relationship, and company F does not have a community relationship with any company. In this case, the disclosure range of the recruitment item will be as shown in Table 402, depending on the company to which the recruiter belongs and the disclosure level set by the recruiter.

[0302] The disclosure levels of "Level 1" to "Level 3" shown in FIG. 22 correspond to the three levels of "my company", "within the community", and "all" already described. Therefore, at level 1, the recruitment job of the recruiter is disclosed only to applicants who belong to the same company as the recruiter's company. At level 2, in addition to the scope of level 1, the recruitment job of the recruiter is disclosed to applicants who belong to companies that have a community relationship with the company to which the recruiter belongs. At level 3, the recruitment job of the recruiter is disclosed to applicants who belong to all companies including the company to which the recruiter belongs. However, if the recruiter specifies a company ID that is not to be disclosed, the company corresponding to that company ID is excluded from the companies to be disclosed regardless of the disclosure level set. Among the disclosure levels in this embodiment, "Level 1" is a level corresponding to "permitting disclosure of business information to the first applicant and prohibiting disclosure of business information to applicants who do not belong to the first group". "Level 2" corresponds to "allowing the disclosure of work information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and prohibiting the disclosure of work information to applicants who do not belong to either the first group or a community group." "Level 3" corresponds to "allowing the disclosure of work information to applicants regardless of the group to which they belong."

[0303] Here, the above-mentioned levels 1 to 3 have been described as an example of multiple types of disclosure levels. However, the multiple types of disclosure levels are not limited to these. For example, a certain community may be divided into multiple small communities, and whether or not to disclose recruiting operations may be set for each small community. More specifically, community 02 shown in FIG. 5 is divided into a first small community and a second small community. Company C belongs to the first small community, and companies D and E belong to the second small community. In this case, a recruiter of company D may be able to select whether the disclosure scope of his / her recruiting operations is the scope of the first small community or the scope of the second small community.

[0304] The sharing server 100 may accept an operation to set the disclosure range differently for each solicited case. For example, among many solicited cases, case 001 to case 003 are taken as examples to explain a specific example of setting the disclosure range differently for each solicited case.

[0305] For example, the disclosure range of job 001 may be limited to only companies A and C that belong to the community identified by community ID=03. Or the disclosure range of job 002 may be limited to only companies C, D, and E that belong to the community identified by community ID=02. Or the disclosure range of job 003 may be limited to companies C, D, and E that belong to the community identified by community ID=02, and companies A and C that belong to the community identified by community ID=03.

[0306] Company A may form a community separate from the community identified by community ID=01 or 02. For example, as shown by the dashed line in FIG. 22, company A may form a community identified by community ID=Z with company Z. For example, if a recruiter belongs to company A, the recruiter's recruitment opportunities may be disclosed to applicants belonging to company A and applicants belonging to company Z. This level of disclosure may be adopted as a modified example of "Level 3" as shown in FIG. 22.

[0307] In this case, "Level 3" corresponds to "permitting disclosure of business information to applicants who belong to a specific community group (a community identified by community ID=Z) other than the first group (Company A) and the second-level community groups (Companies A to C) that have formed a community relationship with the first group, and prohibiting disclosure of business information to applicants who do not belong to either the first group or the specific community group."

[0308] Here, levels 1 to 3 have been described as an example of a plurality of levels, but a greater number of levels may be set as a plurality of types of disclosure levels. As an example of an interface for the recruiter to set the disclosure range, a screen displaying check boxes for setting a desired level from a plurality of types of levels may be displayed on the user device 500.

[0309] [Example of the screen displayed when checking side job status] Fig. 23 is a diagram showing a screen displayed on the applicant device 300 of a manager (applicant's boss) when the manager checks the side job status of his / her subordinates. Fig. 23 shows an example in which the side job status of the manager's subordinates is displayed on the applicant device 300 (user device 500). The applicant device 300 is provided with a keyboard 306A and a mouse 306B as operation units.

[0310] Here, the manager is, for example, the head of the sales department of company C. Display 305 shows the side job status of employees in the sales department. The manager can check the side job status of employees in the sales department by selecting tab 307A, tab 307B, tab 307C, ... with keyboard 306A or mouse 306B. Therefore, the manager can manage the working hours of subordinates so that they do not fall into a state of overwork. The progress rate may also be displayed on the screen.

[0311] [Details of the project] Fig. 24 is a diagram showing details of job content included in the recruitment job database 124. The job content includes recruitment requirements. As shown in Fig. 24, the job content is registered in the recruitment job database 124 by job ID.

[0312] The job content includes the items of job name, job details, job registrant, and job registering company. The job name describes the title of the job. The job details include a sentence explaining the contents of the job. This sentence may include the skills, experience, and qualifications required of the applicant. The job registrant refers to the person who registered the job, i.e., the recruiter. The job registering company refers to the company to which the job registrant belongs.

[0313] The job content is made public to users (applicants) who are permitted to view the job. The sentences included in the job details may contain in-house terms. The in-house terms in such sentences are registered in the job database 124 as "index information" so that they can be linked to in-house terms in the in-house terminology database 136 described below.

[0314] As already explained with reference to FIG. 1, the user device 500 displays the in-house term in a different display mode from other terms. This allows the user to understand that it is an in-house term. Furthermore, the user device 500 displays the intended meaning of the in-house term in response to a user operation (for example, a click operation on the in-house term portion).

[0315] Applicants review the content of the projects and decide which one they would like to apply for from among the many available. Applicants may interview the project recruiter as necessary before finally applying for the project. In addition, after selecting a specific person from the applicants as a provisional contractor, the recruiter may interview the provisional contractor before entering into a business contract. After entering into a business contract with the applicant, the recruiter may interview the applicant (contractor) regarding the content of the work depending on the progress of the work.

[0316] The user device 500 may provide the recruiter and the applicant with a Web conference environment for conducting these interviews. When a sentence including an in-house term is displayed on the display during the Web conference, the user device 500 may display the in-house term in the manner shown in FIG.

[0317] [Candidate list] Fig. 26 is a screen diagram showing an example of a candidate list for offering a job. When a user as a recruiter sets selection criteria (inclusion criteria, exclusion criteria) for selecting offerees for a business job, the sharing server 100 selects candidates to whom the job will be offered based on the selection criteria. After selecting the candidates, the sharing server 100 transmits the candidate list to the user device 500 of the recruiter. As a result, a candidate list screen 555 shown in Fig. 26 is displayed on the user device 500.

[0318] 26 shows an example in which candidates A to C are displayed on a screen 555 together with summary information of their profiles. The screen 555 includes a detailed information button 5551, a check box 5552, and an offer button 5553. The detailed information button 5551 and the check box 5552 are provided for each candidate.

[0319] The user can click on each of the detailed information button 5551 and the offer button 5553 by operating a mouse or the like. The user can check the check box 5552 by operating a mouse or the like.

[0320] When the detailed information button 5551 is clicked, detailed profile information of the candidate corresponding to the clicked detailed information button 5551 is displayed on the screen 555. This allows the user to check the detailed profile information of the candidates in which he or she is interested and decide whether to send a job offer to all candidates or to some of the candidates.

[0321] Note that user device 500 may not display summary information of the profile on screen 555. In this case, user device 500 may arrange a profile button on screen 555 for each candidate, and when detecting a click operation of a profile button, display on screen 555 profile information (simple information or detailed information) of the candidate corresponding to the detected profile button.

[0322] After determining the target person to whom the job offer is to be sent, the user checks the check box 5552 corresponding to the target person. The user then clicks the offer button 5553. As a result, information indicating the offer target is sent to the sharing server 100. The sharing server 100 sends job offer information to the offer target. As a result, as shown in FIG. 1, a screen 554 is displayed on the user device 500 of the target person, encouraging the target person to apply for the business job.

[0323] In this example, an example has been described in which a job offer is sent to a target person selected by a user from among the candidates listed in the candidate list. However, the sharing server 100 may send a job offer to all candidates without presenting the candidate list to the user. In this case, the candidate corresponds to the target person.

[0324] [Processing procedure of sharing server 100] FIG. 27 is a flowchart showing the procedure of a process executed by the sharing server 100 regarding an item offer.

[0325] First, the sharing server 100 registers a business request in the solicited request database 124 in accordance with a user's instruction (step S131). At this time, the sharing server 100 also registers inclusion criteria and exclusion criteria related to the request offer in the solicited request database 124 in accordance with the user's instruction.

[0326] Next, the sharing server 100 reads the inclusion criteria and exclusion criteria for the job offer from the recruiting job database 124 (step S132). Next, the sharing server 100 searches for users who match the inclusion criteria (step S133). Here, step S133 corresponds to positive matching.

[0327] Next, the sharing server 100 searches for users who meet the exclusion criteria (step S134). Here, step S134 corresponds to negative matching. Steps S133 to S135 constitute a selection section.

[0328] Next, the sharing server 100 excludes users who meet the exclusion criteria from among the users who meet the inclusion criteria (step S135). Next, the sharing server 100 transmits a list of all candidates to the user device 500 of the recruiter (step S136). As a result, a candidate list screen 555 (see FIG. 26) is displayed on the user device 500.

[0329] Next, the sharing server 100 determines whether or not there has been an instruction to display detailed information on the candidate's profile (step S137). The instruction to display detailed information on the candidate is transmitted to the sharing server 100 from the user device 500 of the recruiter viewing the candidate list screen 555. More specifically, when a click operation on the detailed information button 5551 is detected on the user device 500, an instruction to display detailed information on the candidate is transmitted from the user device 500 to the sharing server 100.

[0330] If there is no instruction to display the detailed information of the candidate, the sharing server 100 returns the process to step S137. If there is an instruction to display the detailed information of the candidate, the sharing server 100 transmits the detailed information of the candidate to the user device 500 of the recruiter (step S138).

[0331] Next, the sharing server 100 judges whether or not an offer instruction has been given (step S139). The offer instruction is transmitted from the user device 500 of the recruiter viewing the candidate list screen 555 to the sharing server 100. More specifically, when a click operation on the offer button 5553 is detected in the user device 500, the offer instruction is transmitted from the user device 500 to the sharing server 100.

[0332] If there is no instruction to make an offer, the sharing server 100 returns the process to step S137. If there is an instruction to make an offer, the sharing server 100 transmits job offer information to the user device 500 of the candidate (target person) selected by the recruiter (step S140), and ends the process based on this flowchart. As a result, the job offer information is displayed on the screen 554 of the user device 500 of the candidate, as shown in Fig. 1. Step S140 constitutes a transmission unit.

[0333] [Processing Procedure of User Device 500] 28 is a flowchart showing a processing procedure executed by the user device 500 operated by the recruiter with respect to an offer of a job. First, the user device 500 accepts input operations of business information, inclusion criteria, and exclusion criteria (step S151). Step S151 constitutes a receiving unit.

[0334] Next, the user device 500 transmits the job request (including the job information, the inclusion criteria, and the exclusion criteria) to the sharing server 100 (step S152). The sharing server 100 registers the job request in the recruitment request database 124, performs positive matching and negative matching, and then transmits a list of all candidates to the user device 500 (steps S131 to S136 in FIG. 27).

[0335] Next, the user device 500 receives the list of all candidates (step S153). Next, the user device 500 displays the candidate list together with the summary information (step S154). As a result, the user device 500 displays a screen 555 as shown in FIG. 26.

[0336] Next, the user device 500 accepts an operation of selecting an offer target from among the candidates (step S155). More specifically, the user device 500 accepts an operation of the user checking a check box 5552 corresponding to the offer target.

[0337] Next, user device 500 determines whether or not an operation of detailed information button 5551 on screen 555 has been detected (step S156). If an operation of detailed information button 5551 has not been detected, user device 500 returns the process to step S154.

[0338] When an operation of the detailed information button 5551 is detected, the user device 500 requests detailed information about the profile of the candidate corresponding to the detailed information button 5551 whose operation was detected, from the sharing server 100 (step S157). The sharing server 100 returns the corresponding detailed information to the user device 500.

[0339] Next, the user device 500 receives the detailed information of the candidate corresponding to the detailed information button 5551 whose operation was detected from the sharing server 100 (step S158). Next, the user device 500 displays the detailed information of the candidate corresponding to the detailed information button 5551 whose operation was detected on the screen 555 (step S159).

[0340] Next, the user device 500 determines whether or not operation of the offer button 5553 has been detected (step S160). If operation of the offer button 5553 has not been detected, the user device 500 returns the process to step S154. If operation of the offer button 5553 has been detected, the user device 500 transmits an offer instruction including information (user information) of the selected candidate to the sharing server 100 (step S161), and terminates the process based on this flowchart. The sharing server 100 transmits job offer information to the user device 500 of the candidate (target person) selected by the recruiter. Note that step S161 constitutes a transmission unit.

[0341] According to this embodiment, the recruiter can effectively make job offers to people who belong to groups different from the group the person belongs to. Also, the recruiter can restrict job offers to groups competing with the group the person belongs to.

[0342] Depending on the selection conditions set, the recruiter can make a project offer to all users belonging to a group to which the recruiter wishes to make a project offer. Therefore, the recruiter does not need to set up project offers for each and every user. As a result, the recruiter can reduce the effort and time required to set up project offers. According to this embodiment, the recruiter can actively select recipients of the offer, thereby quickly gathering the desired members and having those members start work on the project.

[0343] According to this embodiment, the recruiter can narrow down the candidates to whom the offer is made from the candidate list. This allows the recruiter to make offer with higher accuracy. According to this embodiment, in addition to positive matching, negative matching is used to automatically select candidates for offer of a project. This prevents human error from accidentally making an offer to a user who should not be the target of the offer.

[0344] The sharing server 100 may accept a request from a company acting as an applicant to restrict some of its employees from being selected as candidates. For example, if a highly confidential team X exists within a company X, the manager of the company X uses the user device 500 to transmit restriction information regarding the job offer to the sharing server 100. The restriction information may include, for example, the member IDs of employees belonging to the team X.

[0345] The sharing server 100 handles the restriction information as one of the "exclusion criteria" in "negative matching." As a result, it is possible to prevent employees belonging to team X in company X from being selected by the sharing server 100 as candidates for a job offer. The sharing server 100 receives, from the applicant device (user device 500), restriction information that restricts the applicant from being selected as a candidate. Furthermore, the exclusion criteria include the restriction information.

[0346] The restriction information may include information about a recruiter who avoids presenting candidates for a job offer. For example, when company Y is included as information about the recruiter, the sharing server 100 restricts employees belonging to team X from being presented to company Y as candidates for a job offer when company Y is the recruiter. In this case, the sharing server 100 does not restrict employees belonging to team X from being presented to company Z as candidates for a job offer.

[0347] [Other databases] In the following, in addition to the various databases 121 to 127 shown in FIG. 2, other databases employed in this embodiment will be described.

[0348] FIG. 29 is a diagram showing an example of profile database 129. As shown in FIG. 29, in profile database 129, profile information of members (users) is registered by member ID. A part of the profile information may overlap with information registered in member database 122. The profile information includes the member's name, age, and gender. Furthermore, the profile information includes affiliation information that can identify the member's affiliation (company and department). The affiliation information is an example of group information for identifying either the company or a department within the company.

[0349] Furthermore, the profile information includes the member's possessed ability information. The member's possessed ability information is classified by skill, experience, and qualification. The sharing server 100 uses the information registered in the profile database 129 to display the profile summary information and detailed information on the screen 555 (see FIG. 26).

[0350] Fig. 30 is a diagram showing an example of the in-house terminology database 137. As shown in Fig. 30, in-house terminology information is registered by company ID in the in-house terminology database 137. The sharing server 100 refers to the in-house terminology database 137 to identify in-house terms by company.

[0351] The internal terminology information includes affiliation information that can identify the member's affiliation (company and department). The affiliation information is an example of group information for identifying either the company or a department within the company. The affiliation information can also be said to be information that indicates the company and department in which the internal term to be registered is prevalent.

[0352] The in-house term information further includes the "name," "reading," and "meaning" of the term to be registered. For example, in the case of the in-house term "DX," "DX" is registered as the "name," "reading" is registered as "D-X," and "meaning" is registered as "creating some kind of new value, regardless of whether digital technology is used or not."

[0353] Another example of an in-house term is "application development." "Application development" is generally understood to mean developing applications to be used on electronic devices such as smartphones. However, in a certain department of a company that handles electronic components, "application development" may mean "developing new uses for components." In such a case, the term "application development" and its meaning (developing new uses for components) are registered in the in-house term database 137.

[0354] [Explanation of the processing steps related to the index function] Next, various processing procedures related to the index function will be described with reference to Fig. 31 to Fig. 34. Fig. 31 is a flowchart showing the processing procedures related to the index function of the matching system 1.

[0355] In the flowchart shown in FIG. 31, first, the sharing server 100 registers in-house terms in the in-house terminology database 137 (step Sw1). In step Sw1, the sharing server 100 functions as an in-house terminology registration unit. Next, the sharing server 100 registers a recruitment request in the recruitment request database 124 (step Sw2). In step Sw2, the sharing server 100 functions as a request registration unit. When registering a recruitment request in the recruitment request database 124, the request registration unit indexes in-house terms included in the recruitment request information.

[0356] Next, the sharing server 100 displays the indexed case information on the user device 500 (step Sw3). For example, if an in-house term is used in a sentence explaining the details of the case, the sentence with the in-house term underlined is displayed on the user device 500. Instead of or in addition to underlining the in-house term, the in-house term may be displayed on the screen 552 of the user device 500 in a color different from other words. In step Sw3, the sharing server 100 functions as a display unit.

[0357] FIG. 32 is a flowchart showing the processing steps of the in-house terminology registration unit (Sw1). First, a company staff member compiles in-house terminology by using the company's own system or the like (step Sw11). In other words, the staff member creates something like an in-house glossary. Next, the staff member downloads a registration template from the sharing server 100 (step Sw12). Next, the staff member enters the necessary information into the template (step Sw13). The necessary information includes the in-house terminology, the meaning of the in-house term, and the meaning of the in-house term.

[0358] Next, the company's person in charge accesses the sharing server 100 and obtains the person's own profile information from the profile database 129 (step Sw14). The profile information includes the company ID of the company to which the person in charge belongs. The person in charge uploads a template along with the profile information to the matching system 1 (step Sw15). The sharing server 100 obtains the profile information and the template. The sharing server 100 generates in-house terminology information based on the obtained profile information and template, and registers the generated in-house terminology information in the in-house terminology database 137 (step Sw16). As a result, in-house terms and their meanings are registered in the in-house terminology database 137. In-house terms and their meanings are also registered by company in the in-house terminology database 137.

[0359] The processing of steps Sw11 to Sw16 is executed for each company. As a result, in-house terminology information is registered for each company in the in-house terminology database 137. Note that the sharing server 100 may register in-house terms collectively in the in-house terminology database 137 from an external file such as a CSV (Comma Separated Value) file.

[0360] 33 is a flowchart showing the processing procedure of the case registration unit (Sw2). First, a recruiter who wishes to register a recruitment case in the system accesses the profile database 129 to obtain the recruiter's company information (step Sw21). Next, the recruiter inputs the case information into the user device 500 (step Sw22). The case information includes various information such as the case contents registered in the recruitment case database 124. The recruiter may input the details of the case contents using in-house jargon commonly used in the company to which the recruiter belongs.

[0361] Next, the sharing server 100 automatically searches for in-house terms included in the input case information (step Sw23). At this time, the sharing server 100 indexes the in-house terms found by the search and links them to in-house terminology information registered in the in-house terminology database 137. Next, the sharing server 100 registers the case information input by the recruiter in the recruiting case database 124 (step Sw24). As a result, the case information is registered in the recruiting case database 124 with the in-house terminology and its meaning associated with each other.

[0362] Fig. 34 is a flowchart showing the processing procedure for displaying the meaning of in-house terminology on the screen in response to an applicant's operation. Here, the process for providing a job matching the applicant with consideration given to the disclosure range for the job and the applicant's side job capacity, and for informing the applicant of the meaning of in-house terminology as necessary, will be described.

[0363] First, the sharing server 100 receives a search request for a recruitment item from an applicant (step Sw101). Next, the sharing server 100 determines the affiliation of the applicant (step Sw102). The details of this process have already been described as step S1451.

[0364] Next, the sharing server 100 extracts cases that can be disclosed (step Sw103). Details of this process have been explained as step S1452. Next, the sharing server 100 extracts cases that can be handled with side job capacity (step Sw104). Details of this process have been explained as step S1453. Note that the process of step Sw104 may be deleted from this flowchart. In other words, the sharing server 100 may extract cases that match the applicant without taking side job capacity into consideration.

[0365] Next, the sharing server 100 extracts a matching case (step Sw105). Details of this process have been described as step S1454. Next, the sharing server 100 transmits the matching case (step Sw106). Details of this process have been described as step S1455. In this manner, the sharing server 100 transmits the matching case to the applicant device 300, thereby displaying the matching case on the applicant device 300.

[0366] Next, the sharing server 100 detects a click operation on the in-house term corresponding to the registered index (step Sw107). Next, the sharing server 100 refers to the in-house term database 137 and transmits the meaning of the in-house term to the applicant device 300 (step Sw108). Next, the applicant device 300 displays the meaning of the in-house term on the display 305 (step Sw109). As a result, for example, the screen 552 shown in FIG. 1 is displayed on the display 305. In this way, the sharing server 100 transmits the meaning of the in-house term to the applicant device 300, thereby displaying the meaning of the in-house term on the applicant device 300.

[0367] As described above, according to this embodiment, it is possible to provide a matching system 1 that functions as a crowdsourcing platform. In order to use crowdsourcing to find more suitable personnel, it is desirable to broaden the scope of crowdsourcing beyond a specific company or a small number of companies. In this case, it becomes necessary to consider the interests of the recruiter who is recruiting contractors for the work and the applicant who applies for the recruitment. In this embodiment, the sharing server 100 communicates with the applicant device 300 operated by the applicant via the communication interface 104. The sharing server 100 registers in the database the business information for which contractors are being recruited and disclosure information indicating the disclosure range of the business information (step S1442). The sharing server 100 determines, based on the disclosure information, the business information that is permitted to be disclosed to the applicant among the business information registered in the database 120 (step S1452). The business information includes detailed information on the content of the work (item content (recruitment outline)). The sharing server 100 displays on the applicant device 300 the business information that is permitted to be disclosed to the applicant and the meanings of terms (in-house terms including company terms) included in the detailed information (steps Sw3, Sw106, Sw109).

[0368] Therefore, according to this embodiment, it is possible to select an appropriate applicant taking into consideration the interests of the recruiter and the applicant. Furthermore, according to this embodiment, it is possible to prevent the applicant from misunderstanding the content of the business information due to terms that are unfamiliar to the ear or that are used in a different way from usual.

[0369] Also, according to this embodiment, the user can reduce the effort of providing supplementary explanations of in-house terms when exchanging information about a case with an external user. Furthermore, the sharing server 100 can automatically index in-house terms contained in the case information. Therefore, the user does not need to manually index the in-house terms. Furthermore, the sharing server 100 has a function for registering in-house terms in the in-house terminology database 137. Therefore, the user does not need to manually register the in-house terms in the in-house terminology database 137. Furthermore, the user can recognize that the in-house terms are not understood by other companies, and can therefore grasp cultural differences with other companies.

[0370] In this embodiment, "company terms" for companies are given as an example of "in-house terms" that are widespread in the group to which the user belongs. However, instead of or in addition to "company terms," ​​the embodiments described above may be applied to terms similar to company terms used in non-profit organizations, communities, and units (departments, sections, etc.) within them.

[0371] In the present embodiment, the "group by company" and the "group by department within the same company" are examples of a "group." Applicants who do not belong to a company, such as freelancers, may form one "group." A "company group" may be formed by multiple companies.

[0372] In this embodiment, a "company that forms a community relationship" is an example of a "community group."

[0373] In the present embodiment, the information on "non-disclosure targets" included in the disclosure information is an example of "information capable of identifying targets to whom disclosure of business information is prohibited."

[0374] The communication (S9 in FIG. 11) for transmitting approval information from the applicant device 300 of the manager functioning as an approver to the approval unit 147 is performed on a logical communication path identified by the member ID of the approver. "The approval unit 147 receiving the approval information on such a communication path" is an example of "receiving an approval notification in a communication involving the identification information of the approver of the first applicant."

[0375] In this embodiment, the "evaluation summary" registered in the evaluation summary database 127 is an example of "evaluation information based on evaluations received from the recruiter device 200 functioning as the evaluator device."

[0376] In this embodiment, the "recruiter device 200A" operated by a recruiter belonging to company A functions as an evaluator device and is an example of a "first evaluator device operated by one or more evaluators belonging to a first group."

[0377] In this embodiment, the "recruiter device 200B" operated by a recruiter belonging to company B functions as an evaluator device and is an example of a "second evaluator device operated by one or more evaluators belonging to a second group different from the first group."

[0378] 21 illustrates a system department and a planning department as examples of departments of company A. In this embodiment, "one of the system department and the planning department" is an example of a "first divided group" included in the first group, and the other is an example of a "second divided group" included in the first group.

[0379] The sharing server 100 extracts from the list of the recruitment job database 124 task information in which the applicant's working hours do not exceed the upper limit hours based on the expected man-hours registered in the recruitment job database 124, the side job upper limit hours registered in the company database 121, the side job actual hours registered in the side job database 125, and the side job expected hours registered in the side job database 125. Specifically, for example, if the applicant is engaged in multiple side jobs, the sharing server 100 calculates the total side job actual hours corresponding to each side job, calculates the total side job actual hours, calculates the total expected side job hours corresponding to each side job, and calculates the total expected side job hours. The sharing server 100 adds the calculated total side job actual hours and total expected side job hours to calculate the total side job hours. The sharing server 100 calculates the applicant's available side job hours by subtracting the total side job hours from the applicant's upper limit side job hours. The sharing server 100 searches the list of the recruitment job database 124 for jobs that can be handled with the calculated available side job hours. At this time, the sharing server 100 calculates the time required to respond to each recruitment request based on the estimated man-hours in the recruitment request database 124, and searches for recruitment requests within the range of side job available time. Here, the "side job upper limit time" is an example of "upper limit time that is the upper limit of the applicant's working hours", the "side job actual time" is an example of "actual time that is the time the applicant has already worked as actual", and the "side job expected time" is an example of "expected time expected as the applicant's working hours". The upper limit time may be not only the side job, but also the time that sets an upper limit on the total time of the main job time and the side job time. The first upper limit time may not be the side job upper limit time, but may be the upper limit time for all work including the main job and the side job. The first actual time and the first expected time may be not only the side job time, but also the total time of all work including the side job and the main job.

[0380] The recruiter device 200 and the applicant device 300 may not only be equipped with all of the processor, memory, communication interface, and input / output interface shown in FIG. 2, but may also be a thin client system using a VDI (Virtual Desktop Infrastructure). A thin client system using a VDI is a system in which a desktop environment on a server is transferred to a terminal in a remote location for use. The recruiter device 200, the applicant device 300, and the sharing server 100 do not necessarily need to be independent devices. When using a thin client system such as the above, the functions of the recruiter device 200, the applicant device 300, and the sharing server 100 can be provided on the same aggregation server.

[0381] The database 120 is not limited to a relational database, and an object-type or NoSQL-type database may be used.

[0382] The sharing server 100 is an example of a computing device. A computing device may be configured by a server (on-premise server, cloud server, etc.) or a serverless system. Here, an on-premise server is a server installed and managed in a facility managed within a company. A cloud server is a server (rented server) provided by another business operator via a network. A serverless system is a system in which computing and memory functions can be used only when necessary without being aware of the existence of a server. Computing devices include servers and serverless systems. Servers include on-premise servers and cloud servers.

[0383] <Variation 1> Next, a first modification will be described with reference to Fig. 35 to Fig. 37. In the first modification, a counter offer function will be described that allows a recruiter to encourage a person selected from a large number of members to recruit for a recruiting service.

[0384] [Background to proposing the counter offer feature] In crowdsourcing, recruiters generally disclose information about the job they are looking for and wait for applications from those who are interested in the job. However, with this method of recruitment, it may take a long time for applicants to respond. Also, it is unclear whether applications will come from people with the skills the recruiter expects.

[0385] Therefore, it is conceivable that the recruiter would search for members and nominate a suitable member (counter offer). However, if the recruiter is only informed of the member ID and the member's name, it is difficult for the recruiter to nominate the applicant he or she truly desires. Furthermore, to prevent confidential information from being leaked to rival companies, etc., the member information of rival companies, etc. must be excluded from the search results.

[0386] In consideration of this background, in Variation 1, search results including detailed member profile information are provided to recruiters who perform member searches. Furthermore, in Variation 1, member information of companies etc. that are in a rival relationship with the recruiter's company etc. is excluded from the search results. Variation 1 will be described in detail below with reference to the drawings.

[0387] FIG. 35 is a diagram for explaining the functions of the sharing server 100, the recruiter device 200, and the applicant device 300 according to the first modification.

[0388] 35, the sharing server 100 functionally includes, in addition to the member search unit 143, a counter offer request unit 161, a counter offer approval request unit 162, and a counter offer request acceptance notifying unit 163. These various functions are realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 that the sharing server 100 has.

[0389] As already explained, the member search unit 143 has a function of searching for members of the matching system 1. In particular, in the first variant, the member search unit 143 has a function of providing detailed profile information of members to a searcher. When the recruiter's search operation is accepted, the recruiter's device 200 executes a member search process (step S21). In particular, in step S21, the recruiter's device 200 accepts a search operation for the recruiter to make a counter offer. The member search unit 143 provides the recruiter's device 200 with information on members registered in the member database 122. The provided member information includes detailed profile information of the members. However, the member search unit 143 excludes member information of companies, etc. that are in a rival relationship with the recruiter's affiliated company, etc., from the search results.

[0390] The recruiter device 200 receives the member information (search result) from the member search unit 143, and displays the member information as the search result on the display 205 (step S22). Thereafter, the recruiter device 200 accepts an operation by the recruiter to select an applicant from the search result. That is, the recruiter selects a member to which to make a counter offer based on the search result, and makes a counter offer by operating the recruiter device 200 (step S23). The recruiter device 200 transmits the member ID of the member to whom the counter offer is to be made to the sharing server 100.

[0391] The counter offer request unit 161 receives the member ID of the member who is the target of the counter offer from the recruiter device 200. The counter offer request unit 161 identifies the member corresponding to the received member ID. The counter offer request unit 161 notifies the applicant device 300 of the member who is the target of the counter offer that it has received a request for a counter offer. This notification may include information on the recruitment case that is the target of the counter offer. The member who is the target of the counter offer receives the request for a counter offer via the applicant device 300. The "request" received here is an example of "information that encourages applicants to apply." The member who is the target of the counter offer decides whether or not to accept the request for a counter offer. The member who is the target of the counter offer can use the applicant device 300 to perform an operation to accept the request for a counter offer or an operation to reject the request for a counter offer. The applicant device 300, for example, accepts the request for a counter offer (step S24). The applicant device 300 that has accepted the request for a counter offer transmits application information to the counter offer approval request unit 162 .

[0392] The counter offer approval request unit 162 sends the application information of the subordinate to the applicant's superior. The counter offer approval request unit 162 identifies the member ID of the superior, who is the manager of the applicant, based on the relationship between the applicant's member ID and the superior's member ID registered in the member database 122. The applicant's superior checks the application information on his / her own applicant device 300 and approves the application (step S25).

[0393] The counter offer request acceptance notifying unit 163 receives approval information from the applicant's superior. On the condition that the approval information has been received, the counter offer request acceptance notifying unit 163 accepts the applicant's application. The counter offer request acceptance notifying unit 163 notifies the recruiter device 200 that the application from the member who made the counter offer has been accepted. Based on the notification, the recruiter device 200 notifies the recruiter that the counter offer has been accepted (step S26). More specifically, the recruiter device 200 displays information on the display 205 to notify the recruiter that the counter offer has been accepted.

[0394] Figure 36 is a diagram showing an example of member database 122A relating to Modification 1. Compared to member database 122 shown in Figure 4, member database 122A shown in Figure 36 has profile information and profile disclosure information indicating whether or not to make the profile public.

[0395] The matching system 1 gives members the authority to register and modify their own profile information in the member database 122A using the applicant device 300. The member registers various pieces of his / her profile information in the member database 122A using the applicant device 300. The profile information includes, for example, the member's Synthetic Personality Inventory (SPI) information, the member's work history, the member's achievements, the member's qualifications, and the like.

[0396] Members set profile public information using the applicant device 300. Profile information of members whose profile public information is set to allowed is provided to searchers. Profile information of members whose profile public information is set to not allowed is not provided to searchers. The sharing server 100 registers the profile public information in the member database 122A based on the settings selected by each member. In this way, the sharing server 100 accepts input of information from each of multiple members indicating whether or not they permit their profile information to be included in search results.

[0397] Here, an example has been described in which it is determined whether or not disclosure of the member's profile information is permitted based on the setting of the profile public information. However, the sharing server 100 may be configured to accept a setting operation for whether or not disclosure is permitted for each type of profile information. This allows, for example, a member to make achievements and qualifications public, while keeping SPI information private. Alternatively, when age is included in the profile information, the member can keep age private and make other profile information public. In this case, the sharing server 100 registers a plurality of pieces of profile information of each of a plurality of registrants (members) in the member database 122A. The sharing server 100 accepts an input from each of a plurality of registrants to set the range of the plurality of pieces of profile information to be made public as a search result.

[0398] 37 is a flowchart showing the procedure of a counter offer member search process according to Modification 1. The process based on this flowchart is executed by the sharing server 100.

[0399] First, the sharing server 100 accepts a search request by a searcher to search for members suitable for a recruitment request (step S211). Here, the searcher is a recruiter who has a recruitment request. The recruiter searches for members using his / her own recruiter device 200 to make a counter offer to members who have skills suitable for the recruitment request. The recruiter's search request is accepted by the sharing server 100 in step S211. The search request may include the member ID of the searcher and the request ID of the recruitment request.

[0400] Next, the sharing server 100 identifies the company to which the searcher belongs from the member database 122A and the company database 121 (step S212). Next, the sharing server 100 identifies the community to which the searcher belongs from the community database 123 (step S213).

[0401] Next, the sharing server 100 identifies the disclosure level and non-disclosure company ID list of the recruitment request registered in the recruitment request database 124 (step S214). Next, the sharing server 100 extracts members who can disclose to the searcher (step S215).

[0402] More specifically, the sharing server 100 identifies companies that should not disclose recruitment requests held by the searcher (recruiter) based on the non-disclosure company list and disclosure level in the recruitment request database 124. The sharing server 100 determines members belonging to such companies as members who cannot be disclosed to the searcher. The sharing server 100 extracts members other than those belonging to such companies as members who can be disclosed to the searcher.

[0403] Next, sharing server 100 refers to member database 122A and excludes the profile information of members who have set their profile information to non-disclosure from the extracted member information (step S216).

[0404] Next, the sharing server 100 transmits the extracted member information to the search request source (step S217), and ends the processing based on this flowchart. The recruiter device 200 that originated the search request receives the member information transmitted from the sharing server 100, and displays the information on the display 205. The information displayed on the display 205 displays the ID, name, and profile information of each extracted member. However, for members who have not disclosed their profile information, only the member's ID and name are displayed, and no profile information is displayed.

[0405] As explained above, according to the first modification, the recruiter can refer to the detailed profile information of the members, search for members who are considered to be the best candidates to apply for the job, and make a counteroffer to those members. Furthermore, members from companies that are in a rival relationship with the recruiter's company and community are excluded from the members displayed as search results. This prevents the recruiter from placing an order for work with members from such rival companies. Furthermore, since the members themselves can decide whether or not to make their profile information public, a system can be provided that respects the free will of each member.

[0406] In addition to the profile information, the member may be allowed to set whether or not to make his / her name public. Also, several categories may be provided for the profile information, and the member may be allowed to set whether or not to make the profile information public for each category.

[0407] By adding the offer function described above to the matching system 1, the recruiter can check the profile information of members who are permitted to view the recruitment case. Furthermore, the recruiter can encourage applications from members with whom the recruiter himself wants to place an order. Furthermore, members who are encouraged to apply by the recruiter can view the case information and accept or reject the application. Furthermore, when registering or editing member information, each member can decide whether or not to make their profile information public. This allows the recruiter to actively select who to offer to and to quickly engage the most suitable applicants in the business.

[0408] <Variation 2> Next, a second modified example will be described with reference to Fig. 38 to Fig. 42. In the second modified example, a member group application function that allows a plurality of members to apply for a recruitment operation as a group will be described.

[0409] [Background to proposing the member group application feature] In crowdsourcing, generally, recruiters disclose information about the job they are looking for, and individuals who are interested in the job apply for the job. However, there are many jobs that should be handled by a team of several people, or where it is preferable to handle them as a team, such as comprehensive tasks from business planning to acquiring intellectual property rights related to the plan. For this reason, if the number of people recruited is limited to one person, it is difficult for those who wish to accept the order to take on more work than they can handle individually.

[0410] In view of this background, in Modification 2, a member group application function is provided that enables a plurality of members to apply for a recruitment operation as a group. Modification 2 will be described in detail below.

[0411] Fig. 38 is a block diagram showing the configurations of the sharing server 100, recruiter device 200, and applicant device 300 relating to Modification 2. The block diagram shown in Fig. 38 has a member group database 128 added thereto, compared to the block diagram shown in Fig. 2. The recruiting request database 124A shown in Fig. 38 has a function added to the recruiting request database 124 shown in Fig. 6 that allows registration of recruiting requests that are open to applications from a member group.

[0412] Member groups consisting of multiple members are registered in member group database 128. The recruiter can use recruiter device 200 to register recruitment requests that allow application by member groups in recruiting request database 124A. The applicant can use applicant device 300 to apply for recruitment requests that allow application by member groups using a member group registered in member group database 128.

[0413] 39 is a diagram showing an example of member group database 128 relating to Modification 2. Member group information is registered in member group database 128. The member group information includes a group ID for identifying the member group, the company ID of the company to which each member of the member group belongs, and the member ID of each member of the member group.

[0414] Hereinafter, the membership groups corresponding to each group ID may be referred to as member group G1, member group G2, member group G3, . . . using the group ID.

[0415] Member group G1 is made up of three members identified by member IDs P1, P2, and P5. The company ID registered for member group G1 is 00A, so it can be seen that all three members belong to company A.

[0416] Member group G2 is composed of two members identified by member IDs P1 and P3. The company IDs registered corresponding to member group G2 are 00A and 00B, so it can be seen that one of the two members belongs to company A and the other belongs to company B. As can be seen by comparing member group G1 with member group G2, member ID P1 is registered in both member groups G1 and G2. Therefore, member P1 belongs to two member groups.

[0417] Member group G3 is made up of four members identified by member IDs P4, P7, P8, and P14. The company ID registered for member group G3 is 00C, so it can be seen that all four members belong to company C.

[0418] Member group database 128 is stored in storage 103 of sharing server 100, as shown in Fig. 38. A member forms a member group with the consent of other members who he or she has met through the same company or community, and registers the member group in member group database 128. A "member group" is an example of an "application group."

[0419] Fig. 40 is a diagram showing an example of the recruitment request database 124A according to the modified example 2. The recruitment request database 124A shown in Fig. 40 has information on the recruitment form added thereto, compared to the recruitment request database 124 shown in Fig. 6. The recruiter operates the recruiter device 200 to set the recruitment form. The sharing server 100 registers the recruitment form based on the setting in the recruitment request database 124A in association with the business information.

[0420] Recruiters can select the recruitment type from group and individual. If the recruiter does not select a recruitment type, the recruitment type of the recruitment case is considered to be not limited to group or individual. Cases with the recruitment type set to group can only be accepted by member groups. Cases with the recruitment type set to individual can only be accepted by individual members. Cases with no recruitment type restrictions can be accepted by either member groups or individuals. "Recruitment type information" is an example of "information that can identify that the job for which contractors are being recruited is a job to which multiple recruiters should jointly apply."

[0421] Fig. 41 is a diagram for explaining functions of the sharing server 100, the recruiter device 200, and the applicant device 300 relating to the modified example 2. In Fig. 41, compared to Fig. 11, a determination unit 145A is added to the sharing server 100. Also, compared to Fig. 11, in Fig. 41, step S7A is added after step S7, and step S8A of group application is adopted instead of step S8 of application.

[0422] Here, it is assumed that the applicant belongs to multiple member groups. The applicant operates the applicant device 300 to search for recruitment requests (step S6). The applicant device 300 transmits a search request to the request extraction unit 145 of the sharing server 100.

[0423] When the case extraction unit 145 receives a search request, it extracts cases that the applicant is permitted to view from among the recruitment cases registered in the recruitment case database 124, as explained using FIG. 11. The cases extracted by the case extraction unit 145 include cases whose recruitment type is either "group," "individual," or "unlimited." The case extraction unit 145 transmits the extracted recruitment cases to the applicant device 300. The applicant device 300 receives the recruitment cases from the case extraction unit 145. The applicant device 300 displays the received recruitment cases on the display 305 (step S7).

[0424] Display 305 displays the disclosure level, case title, estimated man-hours, estimated period, case contents, and recruitment type for each solicited case. If an applicant wishes to apply as a member group, the applicant uses operation unit 306 such as a mouse and keyboard to specify the member group and select a case for which the recruitment type is set to "group" or "unlimited." Applicant device 300 accepts the member group and the case to which the applicant wishes to apply based on the applicant's operation (step S7A). Applicant device 300 transmits the group ID of the accepted member group and the case ID of the accepted case to sharing server 100. Determination unit 145A of sharing server 100 acquires the group ID and case ID.

[0425] Determination unit 145A accesses member group database 128 and identifies a member ID registered corresponding to the acquired group ID. Determination unit 145A accesses member database 122 and identifies a company ID corresponding to the identified member ID.

[0426] The determination unit 145A accesses the community database 123 and identifies the community ID of the community to which the company with the identified company ID belongs. The determination unit 145A accesses the solicited job database 124A and identifies the company ID (the company ID of the recruiter), non-disclosure company ID, disclosure level, and solicitation form registered in correspondence with the acquired job ID.

[0427] Based on the information identified as above, the determination unit 145A determines whether or not the recruitment request accepted by the applicant device 300 is a request for which application by the member group designated by the applicant is permitted. In other words, the determination unit 145A determines whether or not application by the member group is permitted.

[0428] For example, if one of the members in the member group belongs to a company that is listed in the non-disclosure company ID list corresponding to the recruitment item, the determination unit 145A does not allow the member group to apply. Alternatively, if one of the members in the member group belongs to a company outside the community, even if the disclosure level of the recruitment item is "within the community," the determination unit 145A does not allow the member group to apply.

[0429] The determination unit 145A returns the determination result to the applicant device 300. FIG. 41 shows the flow when the application by the member group is permitted by the determination unit 145A. When the application by the member group is permitted by the determination unit 145A, the applicant device 300 accepts the application by the member group (step S8A). For example, the applicant device 300 displays on the display 305 a screen indicating that the application accepted in step S7A is permitted and a screen for confirming whether or not to apply. The applicant selects to apply using the operation unit 306 such as a mouse and keyboard.

[0430] When the applicant device 300 accepts an application from a member group (step S8A), it transmits application information to the sharing server 100. The application unit 146 of the sharing server 100 acquires the application information. The subsequent processing content is the same as that described using FIG. 11. However, the application unit 146 transmits the application information to the superiors of each member belonging to the member group. Therefore, the application approval processing of step S9 is executed for each superior of each member belonging to the member group. Therefore, the approval unit 147 receives approval information indicating that the subordinate's application is approved, or rejection information indicating whether the subordinate's application is rejected, from multiple superiors.

[0431] The approval unit 147 accepts an applicant's application only when approval information has been obtained from all of the superiors of each member belonging to the member group. After accepting an applicant's application, the approval unit 147 transmits the application information to the recruiter device 200. As already explained using FIG. 11, the recruiter device 200 displays the application details on the display 205 (step S10). The recruiter inputs the result of the hiring or rejection decision to the recruiter device 200. The recruiter device 200 accepts the input result (step S11) and transmits the accepted hiring or rejection result to the notification unit 148 of the sharing server 100.

[0432] The notification unit 148 transmits the application result (result of employment or non-employment) to the applicant's device 300 and the applicant's superior (manager) device 300. However, the notification unit 148 transmits the application result to the superior of each member belonging to the member group.

[0433] The applicant's device 300 and the applicant's device 300 of the superior of each member belonging to the member group display the application results on the display 305 (steps S12 and S13). The applicant and the superior of each member belonging to the member group check the application results by looking at the display 305.

[0434] Fig. 42 is a diagram for explaining the procedure for registering a recruitment request related to the modified example 2 in the recruitment request database 124A. In Fig. 42, compared to Fig. 13, a recruitment form is added to the business information input to the recruiter device 200.

[0435] In the second modification, when a recruiter who registers a recruitment request inputs the business information and disclosure information of the recruitment request into the recruiter device 200, the recruiting form of the recruitment request can be included in the business information. The recruitment form is either group or individual. The request registration unit 144 of the sharing server 100 registers the recruitment request including the recruitment form selected by the recruiter in the recruitment request database 124A (step S1442). If the recruiter does not select a recruitment form, the request registration unit 144 registers information indicating that the recruitment form is not limited in the recruitment request database 124A. The other contents shown in FIG. 42 are the same as those in FIG. 13 already described, and therefore the description will not be repeated here.

[0436] As explained above, according to the second modification, multiple members can apply for a job as a group. Moreover, according to the second modification, whether or not to accept an application from a member group is determined based on the relationship between the company and community to which the recruiter belongs and the company and community to which each member of the member group belongs. This makes it possible to prevent a member group that includes a member who belongs to an organization that is in competition with the applicant from accepting the job from that applicant.

[0437] By adding the member group application function described above to the matching system 1, it is possible to provide a system in which the recipient can view job postings and apply for them as a member group. This makes it possible for the matching system 1 to handle orders for large-scale work that is best done in teams.

[0438] <Variation 3> Fig. 43 is a diagram showing the configuration of a matching system 1A according to Modification 3. As shown in Fig. 43, the functions of the sharing server 100 may be distributed to systems within each company. That is, instead of the centralized management type matching system 1, a distributed management type matching system 1A may be adopted as the matching system 1.

[0439] The system configuration shown in Fig. 43 is common to companies A, B, C, D, .... Each company is provided with a user device 500, a database 520, and a storage 503 for storing the database. When a member operates the user device 500 as a recruiter, the user device 500 functions as the recruiter device 200. When a member operates the user device 500 as an applicant, the user device 500 functions as the applicant device 300.

[0440] The user device 500 is, for example, configured by a server. The user device 500 is an example of a computing device including the recruiter device 200 and the applicant device 300. Like the recruiter device 200 and the applicant device 300, the user device 500 includes a processor, a memory for storing programs and the like required for the processor's arithmetic processing, a communication interface, and the like.

[0441] 2, and includes a recruitment request database 524 replacing the recruitment request database 124, and various other databases. Recruitment requests proposed by employees of company A as recruiters are registered in company A's recruitment request database 524. Recruitment requests proposed by employees of company B as recruiters are registered in company B's recruitment request database 524. Recruitment requests proposed by employees of company B as recruiters are similarly registered in other companies' recruitment request databases 524.

[0442] A disclosure permission list 521 is registered in the database 520. The disclosure permission list 521 includes a list of groups (companies, communities, etc.) that are permitted to disclose recruitment requests. The disclosure permission list 521 includes information corresponding to the "non-disclosure company ID list" and "disclosure level" among the information registered in the recruitment request database 124 shown in Fig. 6. The user device 500 registers in the database 520 the disclosure permission list 521 (disclosure information) that indicates the recruitment request (business information) and the disclosure range of the recruitment request.

[0443] The user device 500 of company A determines which companies or communities to disclose the recruitment request to and which companies or communities not to disclose the recruitment request to, based on the disclosure permission list 521. The user device 500 of company A transmits the recruitment request to each company or community based on the determination. For example, when the user device 500 of company A determines to disclose a recruitment request to company C and not to companies B and D, it transmits the recruitment request to company C and does not transmit the recruitment request to companies B and D.

[0444] Each of the user devices 500 of companies B, C, D, etc. operates based on the disclosure permission list 521, similar to the user device 500 of company A. In this way, the user device 500 determines, from among the recruitment requests registered in the database 520, those for which disclosure to the applicant is permitted based on the disclosure permission list 521, and provides the applicant device 300 with the recruitment requests for which disclosure to the applicant is permitted.

[0445] According to the third modification, there is no need to provide a server for centrally managing the system within the matching system.

[0446] <Modification 4> Variation 4 will be described with reference to Fig. 44. Fig. 44 is a diagram showing an example (variation 4) in which Kerberos authentication is applied to matching system 1A. As shown in Fig. 44, Kerberos authentication may be applied to authentication between companies in matching system 1A. Kerberos authentication is one of the network authentication methods applied between a server and a client.

[0447] Here, variant example 4 will be described using companies A and C as examples of multiple companies. As shown in FIG. 44, authentication system 510A is disposed in company A, and authentication system 510C is disposed in company C. Authentication system 110 is a KDC (Key Distribution Center). Authentication system 110 is operated, for example, by an authentication authority. Authentication system 110 is configured by a server disposed in the authentication authority. Authentication systems 510A and 510C are configured, for example, by user device 500 (see FIG. 43).

[0448] The authentication system 110 has a function of issuing a Ticket Granting Ticket (TGT). The authentication system 110 includes an Authentication Server (AS) and a Ticket Granting Server (TGS). The AS issues the Ticket Granting Ticket (TGT). The TGT is a ticket required to obtain a service ticket. The TGS issues the service ticket. By obtaining the service ticket, company A becomes able to transmit data to company C.

[0449] Here, an example will be described in which company A performs Kerberos authentication and then transmits a recruitment request to company C. Thus, in this case, company A is the recruiter and company C is the applicant. First, authentication system 510A requests authentication system 110 for an authentication procedure (step Sk101). For example, authentication system 510A transmits information required for authentication, such as an ID and password for logging in, to the AS of authentication system 110. Authentication system 510A may use a public authentication key method for the authentication procedure.

[0450] The AS of the authentication system 110 performs authentication based on the information received from the authentication system 510A, and then transmits the TGT to the authentication system 510A (step Sk102). The authentication system 510A performs authorization authentication for the case, and obtains authorization to issue a service ticket (step Sk103).

[0451] Next, the authentication system 510A requests a service ticket for company C from the TGS of the authentication system 110 (step Sk104). At this time, the authentication system 510A presents the TGT issued by the AS to the TGS. The TGS checks the TGT and then transmits the service ticket for company C to the authentication system 510A (step Sk105).

[0452] Next, the authentication system 510A transmits the service ticket to the authentication system 510C of the company C to obtain transmission permission from the company C (step Sk106). The authentication system 510C obtains the service ticket. The authentication system 510C transmits data transmission permission to the authentication system 510A (step Sk107).

[0453] Thereafter, the authentication system 510A transmits to the authentication system 510C those recruitment requests that are permitted to be disclosed to company C by the disclosure permission list 521, among those registered in the recruitment request database 524. This allows company A to allow applicants from company C to view its recruitment requests. Note that instead of each company storing its own disclosure permission list 521, the authentication system 110 may store the disclosure permission list 521 of all companies. In this case, the authentication system 110 has a function of determining the viewing authority of recruitment requests.

[0454] When Kerberos authentication is applied to the matching system 1, company A can simplify the authentication procedure when sending a case to a company other than company C by using the already acquired TGT. For example, when company A wants to send a case to company D, authentication system 510A of company A presents the already acquired TGT and requests a service ticket for company D from the TGS. If there is no problem with the TGT, the TGS issues a service ticket for company D to authentication system 510A.

[0455] By using the Kerberos authentication as described above, a single sign-on technique can be implemented in the matching system 1. As a result, for example, when company A sends data such as recruitment requests to other companies, authentication is not required for each company. Note that companies A and C are shown here as an example of multiple companies. However, the Kerberos authentication as described above may also be applied as an authentication method between three or more multiple companies.

[0456] According to the present embodiment described above, the client company can provide the case information only to a limited number of companies, thereby preventing the leakage of confidential information. The contractor company can receive the case information from companies whose reliability is guaranteed by the matching system 1, 1A, thereby obtaining highly reliable case information.

[0457] According to this embodiment, the recruiter can set companies that are not subject to disclosure separately from the disclosure level (see FIG. 13). That is, in this embodiment, the recruiter device 200 accepts an operation to input a target group (companies that are not subject to disclosure) for which disclosure of business information is prohibited, and transmits information that can identify the accepted target group ("non-disclosure targets" of the "disclosure information") to the sharing server 100. The sharing server 100 prohibits disclosure of business information to applicants belonging to the target group even if the disclosure level is a level that permits disclosure of business information to the target group (disclosure level) (S1442). Therefore, according to this embodiment, companies for which disclosure of recruitment requests should be restricted can be individually set.

[0458] According to this embodiment, the manager of the company to which the employee belongs can confirm the content of the work that the employee has received, so that the leakage of confidential information can be prevented. Furthermore, according to this embodiment, the company that receives the order can know the hours that the employee works at his / her main job and the hours that he / she works at his / her side job. Therefore, the company that receives the order can manage the health of the employee.

[0459] As described above, according to this embodiment, it is possible to provide a matching system 1, 1A that functions as a crowdsourcing platform. In order to use crowdsourcing to find more suitable personnel, it is desirable to broaden the scope of crowdsourcing beyond a specific company or a small number of companies. In this case, it becomes necessary to consider the interests between the recruiter who is recruiting contractors and the applicants who apply for the recruitment. According to the matching system 1, 1A of this embodiment, it is possible to select a suitable applicant taking into consideration the interests between the recruiter and the applicant.

[0460] The sharing server 100 and the user device 500 are examples of computing devices that communicate with the applicant device and can access a database. The sharing server 100 and the user device 500 register business information and disclosure information indicating the disclosure range of the business information in the databases 120 and 520. The sharing server 100 and the user device 500 determine, based on the disclosure information, business information that is permitted to be disclosed to the applicant among the business information registered in the databases 120 and 520, and provide (transmit) the business information that is permitted to be disclosed to the applicant to the applicant device 300. The sharing server 100 and the user device 500 determine whether or not to permit disclosure for each of the first to third applicants according to the disclosure level (step S1452A).

[0461] A plurality of disclosure levels including "same company", "community", and "unlimited" are set for the disclosure information. The plurality of disclosure levels include a first level and a second level. The first level (e.g., "within the company") corresponds to permitting the disclosure of business information to a first applicant belonging to a first group, and prohibiting the disclosure of business information to applicants not belonging to the first group (see FIG. 22). The second level (e.g., "within the community") corresponds to permitting the disclosure of business information to applicants belonging to either the first group or a community group that has formed a community relationship with the first group, and prohibiting the disclosure of business information to applicants not belonging to either the first group or the community group (see FIG. 22). The third level corresponds to permitting the disclosure of business information to applicants belonging to a specific community group other than the first group and the second-level community group that has formed a community relationship with the first group, and prohibiting the disclosure of business information to applicants not belonging to either the first group or the specific community group (see the modified example of FIG. 22).

[0462] The multiple disclosure levels include a disclosure level (see FIG. 22) that corresponds to permitting disclosure of business information to an applicant regardless of the group to which the applicant belongs. Attribute data (community ID) capable of identifying a community group is registered in the databases 120 and 520, and the sharing server 100 and the user device 500 identify applicants to whom disclosure of business information is permitted based on the disclosure information and the attribute data.

[0463] When the sharing server 100 and the user device 500 receive input of a target group (company ID of a company not subject to disclosure) to which disclosure of business information is prohibited, they prohibit disclosure of the business information to applicants belonging to the target group even if the disclosure level is at a level that allows disclosure of business information to the target group.

[0464] The sharing server 100 receives a request from the recruiter device 200 to search for information on multiple registrants (members) registered in the database 120 (step S21), and provides the search results based on the received request to the recruiter device (step S22). The recruiter device 200 receives an operation by the recruiter to select an application recommended person who is recommended to apply as an applicant from the search results (step S23), and transmits identification information of the selected application recommended person (member ID of the member to be the target of the counter offer) to the sharing server 100. The sharing server 100 transmits information encouraging the application to the applicant device 300 of the selected application recommended person (step S24).

[0465] The sharing server 100 registers a plurality of profile information of each of a plurality of registrants (members) in the database 120 (see FIG. 36). The sharing server 100 accepts input from each of a plurality of registrants to set the range of the plurality of profile information to be made public as a search result (accepts a setting operation for whether to permit disclosure for each type of profile information). The sharing server 100 accepts input of recruitment form information (recruitment form shown in FIG. 42) that can specify whether the work for which contractors are being recruited is a group work that can be accepted when multiple applicants apply jointly, or a work that can be accepted for an application by a single applicant. The sharing server 100 registers the recruitment form information in the database 120 in association with the work information (step S1442).

[0466] The sharing server 100 registers an application group (member group) consisting of multiple applicants in the database 120. The sharing server 100 accepts an application from the application group for business information that is permitted to be disclosed to all applicants belonging to the application group (determination unit 145A).

[0467] This embodiment has the following configurations. (a-1) An evaluation system for evaluating contractors who apply for a job, comprising: a first evaluator device operated by one or more evaluators belonging to a first group; and a computing device that communicates with the first evaluator device and can access a database, wherein the first evaluator device accepts input of an evaluation of a contractor and transmits the accepted evaluation to the computing device, and the computing device registers first evaluation information based on the evaluation received from the first evaluator device in the database for each contractor, and when the computing device receives a viewing request in a first communication established by identification information that can identify the applicant as belonging to the first group, it transmits the first evaluation information to the sender that sent the viewing request in the first communication.

[0468] (a-2) Further comprising a second evaluator device operated by one or more evaluators belonging to a second group different from the first group, the second evaluator device accepts input of an evaluation for a contractor and transmits the accepted evaluation to a computing device, the computing device registers second evaluation information based on the evaluation received from the second evaluator device in a database for each contractor, and when the computing device receives a viewing request in a second communication established by identification information that can identify the contractor as belonging to the second group, it transmits the second evaluation information to the sender that sent the viewing request in the second communication.

[0469] (a-3) A first group is constituted by a first company, and a second group is constituted by a second company different from the first company.

[0470] (a-4) The first group is composed of the first division of the first company, and the second group is composed of the second division of the first company.

[0471] (a-5) When the compute device receives evaluations of a specified contractor from multiple evaluators belonging to the first group, it calculates an average of the evaluations of the specified contractor by the multiple evaluators, and transmits the average value as first evaluation information of the specified contractor to the sender that sent the viewing request in the first communication.

[0472] (a-6) The first group includes one or more evaluators belonging to the first divided group and one or more evaluators belonging to a second divided group different from the first divided group, and the computing device calculates a first average value which is an average value of the evaluations for the specified contractor based on the evaluations for the specified contractor received from the multiple evaluators belonging to the first divided group, and the computing device calculates a second average value which is an average value of the evaluations for the specified contractor based on the evaluations for the specified contractor received from the multiple evaluators belonging to the second divided group, and the computing device calculates a second average value which is an average value of the evaluations for the specified contractor received from the multiple evaluators belonging to the first group. based on the above, calculates a third average value, which is the average value of the evaluations for a specified contractor, and when the compute device receives a viewing request in a third communication established by identification information that can identify the person as belonging to the first divided group, transmits the first average value and the third average value to the sender that sent the viewing request in the third communication as the first evaluation information for the specified contractor, and when the compute device receives a viewing request in a fourth communication established by identification information that can identify the person as belonging to the second divided group, transmits the second average value and the third average value to the sender that sent the viewing request in the fourth communication as the first evaluation information for the specified contractor.

[0473] (a-7) A list of contractors is registered in the database, and when the first evaluator device receives an operation to search the list, it sends a search request to the computing device, and when the computing device receives the search request, it sends the search result, in which contractors whose evaluation level does not meet the criteria specified by the first evaluation information, are excluded from the list, to the sender that sent the viewing request in the first communication.

[0474] (a-8) The database has multiple pieces of business information registered together with disclosure information indicating the range of disclosure to the applicant, and the evaluation system further includes an applicant device operated by an applicant belonging to the second group, and the computing device determines, from the multiple pieces of business information registered in the database, which pieces of business information are permitted to be disclosed to applicants belonging to the second group based on the disclosure information, and provides the business information that is permitted to be disclosed to applicants belonging to the second group to the applicant device.

[0475] (a-9) An evaluator device operated by one or more evaluators belonging to a first group, the evaluator device comprising: an interface that accepts an operation to input an evaluation of a contractor who has applied for a job; a reception unit that accepts a viewing request; a display; and a processor that transmits the evaluations accepted by the interface and the viewing request accepted by the reception unit to a computing device that can access a database, wherein when a viewing request is received, the processor displays the evaluations by the one or more evaluators belonging to the first group on the display.

[0476] (a-10) A method for evaluating a contractor who has applied for a job, the method comprising the steps of: communicating with a first evaluator device operated by one or more evaluators belonging to a first group; receiving an evaluation of the contractor from the first evaluator device; registering first evaluation information based on the evaluation received from the first evaluator device in a database; and, when a viewing request is received in a first communication established by identification information that can identify the applicant as belonging to the first group, transmitting the first evaluation information to a sender that sent the viewing request in the first communication.

[0477] (b-1) An evaluation system for evaluating recruiters who are recruiting applicants for a job, comprising: a first evaluator device operated by one or more evaluators belonging to a first group; and a computing device that communicates with the first evaluator device and can access a database, wherein the first evaluator device accepts input of an evaluation of the recruiter and transmits the accepted evaluation to the computing device, the computing device registers first evaluation information based on the evaluation received from the first evaluator device in the database for each recruiter, and when the computing device receives a viewing request in a first communication established by identification information that can identify the applicant as belonging to the first group, it transmits the first evaluation information to the sender that sent the viewing request in the first communication.

[0478] (b-2) Further comprising a second evaluator device operated by one or more evaluators belonging to a second group different from the first group, the second evaluator device accepts input of an evaluation for the recruiter and transmits the accepted evaluation to a computing device, the computing device registers second evaluation information based on the evaluation received from the second evaluator device in a database for each recruiter, and when the computing device receives a viewing request in a second communication established by identification information that can identify the recruiter as belonging to the second group, it transmits the second evaluation information to the sender that sent the viewing request in the second communication.

[0479] (b-3) A first group is constituted by a first company, and a second group is constituted by a second company different from the first company.

[0480] (b-4) The first group is composed of the first division of the first company, and the second group is composed of the second division of the first company.

[0481] (b-5) When the computing device receives evaluations of a specified recruiter from multiple evaluators belonging to the first group, it calculates an average of the evaluations of the specified recruiter by the multiple evaluators, and the computing device transmits the average value as first evaluation information of the specified recruiter to the sender that sent the viewing request in the first communication.

[0482] (b-6) The first group includes one or more evaluators belonging to the first divided group and one or more evaluators belonging to a second divided group different from the first divided group, and the computing device calculates a first average value which is an average value of the evaluations for the specified recruiter based on the evaluations for the specified recruiter received from the multiple evaluators belonging to the first divided group, and the computing device calculates a second average value which is an average value of the evaluations for the specified recruiter based on the evaluations for the specified recruiter received from the multiple evaluators belonging to the second divided group, and the computing device calculates a second average value which is an average value of the evaluations for the specified recruiter received from the multiple evaluators belonging to the first group. Based on this, the computing device calculates a third average value, which is the average value of the evaluations for the specified recruiter, and when the computing device receives a viewing request in a third communication established by identification information that can identify the person as belonging to the first divided group, it transmits the first average value and the third average value to the sender that sent the viewing request in the third communication as first evaluation information for the specified recruiter, and when the computing device receives a viewing request in a fourth communication established by identification information that can identify the person as belonging to the second divided group, it transmits the second average value and the third average value to the sender that sent the viewing request in the fourth communication as first evaluation information for the specified recruiter.

[0483] (b-7) A list of recruits is registered in the database, and when the first evaluator device receives an operation to search the list, it sends a search request to the computing device, and when the computing device receives the search request, it sends the search results, which exclude recruits from the list whose rating does not meet the criteria specified by the first evaluation information, to the sender that sent the viewing request in the first communication.

[0484] (b-8) The database has multiple pieces of business information registered together with disclosure information indicating the range of disclosure to the applicant, and the evaluation system further includes an applicant device operated by an applicant belonging to the second group, and the computing device determines, from the multiple pieces of business information registered in the database, which pieces of business information are permitted to be disclosed to applicants belonging to the second group based on the disclosure information, and provides the business information that is permitted to be disclosed to applicants belonging to the second group to the applicant device.

[0485] (b-9) An evaluator device operated by one or more evaluators belonging to a first group, the evaluator device comprising: an interface that accepts an operation to input an evaluation of a recruiter who is recruiting applicants for a job; a reception unit that accepts a viewing request; a display; and a processor that transmits the evaluations accepted by the interface and the viewing request accepted by the reception unit to a computing device that can access the database, wherein when a viewing request is received, the processor displays the evaluations by the one or more evaluators belonging to the first group on the display.

[0486] (b-10) A method for evaluating a recruiter who is recruiting applicants for a job, the method comprising the steps of communicating with a first evaluator device operated by one or more evaluators belonging to a first group, receiving an evaluation of the recruiter from the first evaluator device, registering first evaluation information based on the evaluation received from the first evaluator device in a database, and, when a viewing request is received in a first communication established by identification information that can identify the person as belonging to the first group, transmitting the first evaluation information to a sender that sent the viewing request in the first communication.

[0487] (c-1) A matching system that matches applicants with recruiters who are seeking contractors for a job, the matching system comprising: a first applicant device operated by a first applicant; and a computing device that communicates with the first applicant device and can access a database, the computing device registers in the database business information for which contractors are being recruited and disclosure information indicating the scope of disclosure of the business information, the computing device determines, based on the disclosure information, business information that is permitted to be disclosed to the first applicant from the business information registered in the database, the business information includes detailed information regarding the content of the job, and the computing device displays, on the first applicant device, the business information that is permitted to be disclosed to the first applicant and terms included in the detailed information.

[0488] (c-2) The terms contained in the detailed information are in-house terms commonly used within the group to which the recruiter belongs.

[0489] (c-3) The computing device registers the in-house terms and the meanings of the in-house terms in the database.

[0490] (c-4) The computing device registers the in-house terms in a database according to the group to which the recruiter belongs.

[0491] (c-5) When an operation of the first applicant on the in-house term is detected on the first applicant device, the computing device transmits information capable of identifying the meaning of the in-house term registered in the database to the first applicant device.

[0492] (c-6) The computing device searches for in-house terms included in the detailed information, and registers the business information in the database with the detected in-house terms associated with the meanings of the in-house terms.

[0493] (c-7) A computing device included in a matching system that matches applicants with recruits who are seeking contractors for a business, the computing device having a communication interface that communicates with a first applicant device operated by a first applicant, and a processor that accesses a database, wherein the processor registers in the database business information for which contractors are sought and disclosure information indicating the range of disclosure of the business information, the processor determines, based on the disclosure information, business information from the business information registered in the database that is permitted to be disclosed to the first applicant, the business information including detailed information regarding the content of the business, and the processor displays on the first applicant device the business information that is permitted to be disclosed to the first applicant and the meanings of terms included in the detailed information.

[0494] (c-8) A method for matching a recruiter seeking contractors for a job with an applicant, the method comprising the steps of: communicating with a first applicant device operated by a first applicant; registering in a database business information for which contractors are being recruited and disclosure information indicating the range of disclosure of the business information; and determining, from the business information registered in the database, business information that is permitted to be disclosed to the first applicant based on the disclosure information, wherein the business information includes detailed information regarding the content of the job; and the method further comprises the step of displaying on the first applicant device the business information that is permitted to be disclosed to the first applicant and the meanings of terms included in the detailed information.

[0495] (d-1) The user device includes a second applicant device operated by a second applicant different from the first applicant, and the computing device determines, from among the business cases registered in the database, business cases that are permitted to be disclosed to the second applicant based on the disclosure information, and provides the business cases that are permitted to be disclosed to the second applicant to the second applicant device.

[0496] (d-2) The user device includes a third applicant device operated by a third applicant different from the first applicant and the second applicant, and a plurality of disclosure levels are set for the disclosure information, and the computing device determines whether or not to allow disclosure for each of the first to third applicants depending on the disclosure level.

[0497] (d-3) The first applicant belongs to a first group, and the second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level and a second level, the first level corresponds to permitting disclosure of the business case to the first applicant and prohibiting disclosure of the business case to applicants who do not belong to the first group, and the second level corresponds to permitting disclosure of the business case to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and prohibiting disclosure of the business case to applicants who do not belong to either the first group or the community group.

[0498] (d-4) The first applicant belongs to a first group, and the second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level, a second level, and a third level, the first level corresponding to permitting disclosure of the business case to the first applicant and prohibiting disclosure of the business case to applicants who do not belong to the first group, the second level corresponding to permitting disclosure of the business case to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and the third level corresponding to permitting disclosure of the business case to applicants who belong to the first group and a specific community group that is different from the second-level community group that has formed a community relationship with the first group, and prohibiting disclosure of the business case to applicants who do not belong to either the first group or the specific community group.

[0499] (d-5) The multiple disclosure levels include a disclosure level that corresponds to permitting disclosure of the business case to an applicant regardless of the group to which the applicant belongs.

[0500] (d-6) In the database, attribute data capable of identifying a community group is registered, and the computing device identifies applicants who are permitted to disclose the business case based on the disclosure information and the attribute data.

[0501] (d-7) When the computing device receives an input of a target group for which disclosure of the business case is prohibited, the computing device prohibits disclosure of the business case to applicants who belong to the target group, even if the disclosure level is at a level that allows disclosure of the business case to the target group.

[0502] (d-8) The computing device receives a request from the recruiter device to search for information on multiple registrants registered in the database, and provides the recruiter device with search results based on the received request. The recruiter device receives an operation by the recruiter to select from the search results an applicant recommender who is recommended to apply as an applicant, and transmits identification information of the selected application recommender to the computing device. The computing device transmits information encouraging the applicant device of the selected application recommender to apply.

[0503] (d-9) The computing device registers multiple pieces of profile information for each of the multiple registrants in the database, and the computing device accepts input from each of the multiple registrants to set the scope of the multiple pieces of profile information to be made public as search results.

[0504] (d-10) When the computing device receives input of recruitment type information that can identify whether the job for which contractors are being recruited is a group job that can be accepted when multiple applicants apply jointly, or a job that can be accepted for a single applicant, the computing device registers the recruitment type information in a database in association with the job case.

[0505] (d-11) The computing device registers an application group consisting of multiple applicants in a database, and the computing device is capable of accepting applications from the application group for business cases in which disclosure to all applicants belonging to the application group is permitted.

[0506] [Aspects] Aspects of the present disclosure are listed below.

[0507] (Paragraph 1) The matching system described in paragraph 1 is a matching system for matching business cases, and includes a user device operated by a user, and a computing device configured to access a database in which business cases are registered and transmit business information related to the business cases to the user device, wherein the computing device selects candidates to whom the business information is to be notified from among a plurality of users based on selection criteria, and transmits the business information to a user device operated by the selected candidate or to a user device operated by some of the selected candidates, wherein the selection criteria include inclusion criteria for including users as targets for notifying the business information.

[0508] (Paragraph 2) The matching system described in paragraph 2 is the matching system described in paragraph 1, wherein the selection criteria include exclusion criteria for excluding users from the targets for notifying business information, and the computing device selects candidates by excluding users selected based on the exclusion criteria from among the users selected based on the inclusion criteria.

[0509] (Item 3) The matching system according to item 3, in which the exclusion criteria includes information about the user's work history.

[0510] (Section 4) The matching system described in Section 4 is the matching system described in Section 2 or 3, in which the user device includes an applicant device operated by an applicant applying for a job, and the computing device receives restriction information from the applicant device that restricts the applicant from being selected as a candidate, and the exclusion criteria include the restriction information.

[0511] (Item 5) The matching system according to item 5 is the matching system according to any one of items 1 to 4, wherein the inclusion criteria includes information about the user's work history.

[0512] (Clause 6) The matching system described in clause 6 is a matching system described in any one of clauses 1 to 5, in which the user device includes a recruiter device operated by a recruiter who initiates a business case, and the recruiter device transmits business information and selection criteria to a computing device based on the recruiter's operation, and the computing device associates the business information with the inclusion criteria and registers them in a database.

[0513] (Clause 7) The matching system described in clause 7 is the matching system described in clause 6, in which the recruiter device has a display unit and a control unit that controls the display unit, and the computing device transmits candidate information indicating the candidates to the recruiter device, the control unit displays the candidates on the display unit, the control unit transmits user information indicating a user selected from the candidates by the operation of the recruiter to the computing device, and the computing device determines a user to be notified of the business information based on the user information received from the recruiter device.

[0514] (Clause 8) The matching system described in clause 8 is the matching system described in clause 7, in which the control unit displays the candidate's profile information on the display unit based on the recruiter's operation when the candidate is displayed on the display unit.

[0515] (Item 9) The recruiter device described in item 9 is a recruiter device that communicates with a computing device that matches business cases and is operated by a recruiter, and the computing device is configured to access a database in which business cases are registered, select candidates from a plurality of applicants to whom business information related to the business cases will be notified based on selection criteria, and transmit the business information to an applicant device operated by the selected candidate or to an applicant device operated by some of the selected candidates, and the recruiter device has a reception unit that accepts operations by the recruiter to set the business information and the selection criteria, and a transmission unit that transmits the selection criteria accepted in the reception unit to the computing device, and the selection criteria include inclusion criteria for including applicants as targets for notifying business information.

[0516] (Clause 10) The computing device described in clause 10 is a computing device that communicates with a user device and matches business cases, and includes a transmission unit that accesses a database in which business cases are registered and transmits business information related to the business cases to the user device, and a selection unit that selects candidates to be notified of the business information from among a plurality of users based on selection criteria, wherein the transmission unit transmits the business information to a user device operated by the candidate selected by the selection unit, or to a user device of a user operated by some of the candidates selected by the selection unit, and the selection criteria include inclusion criteria for including users as targets for notifying of the business information.

[0517] (Clause 11) The method described in clause 11 is a method for matching business cases, and includes the steps of accessing a database in which business cases are registered, selecting candidates from a plurality of users to be notified of business information related to the business case based on selection criteria, and transmitting the business information to a user device operated by the candidate selected in the selection step, or to a user device operated by some of the selected candidates, wherein the selection criteria include inclusion criteria for including users as targets for notifying the business information.

[0518] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0519] 1 Matching system, 50 Internet, 100 Sharing server, 101 Processor, 102 Memory, 103, 503 Storage, 104 Communication interface, 120, 520 Database (DB), 121 Company database (Company DB), 122, 122A Member database (Member DB), 123 Community database (Community DB), 124, 124A, 524 Recruitment case database (Recruitment case DB), 125 Side job database (Side job DB), 126 Evaluation input database (Evaluation input DB), 126A Recruiter evaluation section, 126B Applicant evaluation section, 127 Evaluation summary database (Evaluation summary DB), 127A Recruiter evaluation summary section, 127B Applicant evaluation summary section, 128 Member group database (Member group DB), 129 Profile database (Profile DB), 137 In-house terminology database (In-house terminology DB), 140 Community registration unit, 141, company registration unit, 142, member registration unit, 143, member search unit, 144, case registration unit, 145, case extraction unit, 145A, member group information acquisition unit, 146, application unit, 147, approval unit, 148, notification unit, 149, performance reception unit, 150, performance output unit, 151, evaluation reception unit, 152, evaluation output unit, 161, counter offer request unit, 162, counter offer approval request unit, 163, counter offer request acceptance notification unit, 200, 200A, 200B, 200C, recruiter device, 201, processor, 202, memory, 203, communication interface, 204, input / output interface, 205, display, 206, operation unit, 206A, keyboard, 206B, mouse, 300, 300A, 300B, 300C, applicant device, 301 Processor, 302 memory, 303 communication interface, 304 input / output interface, 305 display, 306 operation unit, 306A keyboard, 306B mouse, 307A to 307C tabs, 308 cursor, 401, 402 table, 500 user device, 521 disclosure permission list, screens 551 to 555, 1271, 1272 data group, 5551 detailed information button, 5552 check box, 5553 offer button.

Claims

1. A matching system for matching business cases, A user device operated by a user; a computing device configured to access the database of business cases and to transmit business information related to the business cases to the user device; The computing device selects candidates to whom the business information is to be notified from among a plurality of users based on a selection criterion, and transmits the business information to a user device operated by the selected candidate or to a user device operated by a portion of the selected candidates; A matching system, wherein the selection criteria include inclusion criteria for including a user as a recipient of notification of the business information.

2. the selection criteria include exclusion criteria for excluding users from targets for notifying the business information; The matching system of claim 1 , wherein the computing device selects the candidates by excluding users selected based on the exclusion criteria from users selected based on the inclusion criteria.

3. The matching system of claim 2 , wherein the exclusion criteria includes information about a user's work history.

4. the user device includes an applicant device operated by an applicant who applies for the job, the computing device receives restriction information from the applicant device that restricts the applicant from being selected as the candidate; The matching system according to claim 2 or 3, wherein the exclusion criteria includes the restriction information.

5. The matching system according to any one of claims 1 to 3, wherein the inclusion criteria includes information about the user's work history.

6. The user device includes a recruiter device operated by a recruiter who initiates the business case; The recruiter device transmits the business information and the selection criteria to the computing device based on an operation of the recruiter; 4. The matching system according to claim 1, wherein the computing device registers the business information and the inclusion criteria in the database in association with each other.

7. The recruiter device comprises: A display unit; A control unit that controls the display unit, the computing device transmits candidate information indicative of the candidate to the recruiter device; The control unit displays the candidates on the display unit, The control unit transmits user information indicating a user selected by an operation of a recruiter from among the candidates to the computing device; The matching system according to claim 6 , wherein the computing device determines the user to whom the business information is to be notified based on user information received from the recruiter device.

8. The matching system according to claim 7 , wherein the control unit, when displaying the candidate on the display unit, displays profile information of the candidate on the display unit based on an operation of the recruiter.

9. a recruiter device in communication with a computing device that matches business jobs and operated by a recruiter, the computing device is configured to access a database in which the job applications are registered, select candidates to be notified of job information related to the job application from among a plurality of applicants based on a selection criterion, and transmit the job information to an applicant device operated by the selected candidate or to an applicant device operated by a portion of the selected candidates; The recruiter device includes: a reception unit that receives an operation for the recruiter to set the job information and the selection criteria; a transmission unit that transmits the selection criteria received by the reception unit to the computing device; The selection criteria include inclusion criteria for including applicants as targets for notification of the business information.

10. A computing device that communicates with a user device and matches business cases, a transmission unit that accesses a database in which the business case is registered and transmits business information related to the business case to the user device; A selection unit that selects candidates to whom the business information is to be notified from among a plurality of users based on a selection criterion; The transmission unit transmits the task information to a user device operated by the candidate selected by the selection unit or a user device of a user operated by a part of the candidates selected by the selection unit; The selection criteria includes inclusion criteria for inclusion of a user as a recipient of notification of the business information.

11. 1. A method for matching business cases, comprising: accessing a database of said business cases; selecting candidates to be notified of business information related to the business case from among a plurality of users based on a selection criterion; and transmitting the task information to a user device operated by the candidate selected in the selecting step or to a user device operated by a part of the selected candidates; The method, wherein the selection criteria includes inclusion criteria for inclusion of a user for notification of the business information.

Images