Evaluation system and method

Abstract

An evaluation system (1) for evaluating a contractor who has applied for a job comprises a first evaluator device (200) that is operated by an evaluator belonging to a first group, and a computing device (100) that communicates with the first evaluator device (200) and is capable of accessing a database (120). The first evaluator device (200) accepts input of evaluation pertaining to the contractor and transmits the accepted evaluation to the computing device (100). The computing device (100) registers first evaluation information based on the evaluation received from the first evaluator device (200) to the database (120). When a browsing request is received in first communication established using identification information by which it can be identified that a person belongs to the first group, the computing device (100) transmits the first evaluation information to the sender who transmitted the browsing request in the first communication.

Description

[Technical field]

[0001] The present disclosure relates to an evaluation system for evaluating contractors who apply for work. ,oh and methods. [Background technology]

[0002] Crowdsourcing has been used by companies for some time. In general, crowdsourcing refers to the process of acquiring needed services, ideas, or content by collecting contributions from an unspecified number of people. In crowdsourcing, the person who orders the work usually prepares an evaluation report for the person who receives the work.

[0003] Patent Document 1 describes that when an evaluator inputs an evaluation report on the skills of a dispatched personnel from an input device after the dispatch period of the dispatched personnel is completed, the evaluation report is transmitted to a dispatch information server. [Prior art documents] [Patent documents]

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

[0005] Evaluation reports are useful as criteria for job seekers when selecting applicants. Therefore, it is desirable to share evaluation reports widely among many job seekers. However, if the scope of sharing evaluation reports is expanded without limit, there is a risk that evaluators will not prepare appropriate evaluation reports due to excessive concern that the contents of the evaluation will be leaked to the applicants themselves. In such a case, the reliability of the evaluation report will decrease.

[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to encourage evaluators to appropriately evaluate contractors. [Means for solving the problem]

[0007] An evaluation system according to a first aspect of the present disclosure is an evaluation system that evaluates contractors who apply for a job, and includes 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 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 contractor as belonging to the first group, it transmits the first evaluation information to the sender that sent the viewing request in the first communication.

[0008] An evaluator device according to a second aspect of the present disclosure is an evaluator device operated by one or more evaluators belonging to a first group, and includes 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 the database, and 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.

[0009] A method according to a third aspect of the present disclosure is a method for evaluating a contractor who has applied for a job, the method including 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. Effect of the Invention

[0010] According to the present disclosure, it is possible to encourage evaluators to appropriately evaluate contractors. [Brief description of the drawings]

[0011] [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. 10 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. 13 is a diagram for explaining a procedure for registering a recruitment request in a recruitment request database. [Figure 14] FIG. 13 is a diagram for explaining a procedure for searching for recruitment requests from a database. [Figure 15] 13 is a diagram for explaining the procedure for registering side job plans and results in a database. FIG. [Figure 16] FIG. 13 is a diagram for explaining the procedure for registering an evaluation of an applicant in a database. [Figure 17] 13 is a diagram for explaining a procedure for displaying evaluations of applicants and search results of members on a display. FIG. [Figure 18] FIG. 13 is a diagram for explaining the viewable range of the evaluation summary database. [Figure 19] FIG. 13 is a diagram showing an example in which a disclosure range is set according to a disclosure level. [Figure 20] 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 21] 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. [Figure 22] FIG. 13 is a diagram showing an example of a member database according to the first modified example. [Figure 23] 13 is a flowchart showing the processing steps of a counter offer member search process according to the first modification. [Figure 24] 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. [Diagram 25] FIG. 13 is a diagram showing an example of a member group database according to the second modified example. [Figure 26] FIG. 11 is a diagram showing an example of a recruitment request database according to the second modified example. [Figure 27] 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. [Figure 28] 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 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.

[0013] [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.

[0014] 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.

[0015] 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.

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

[0017] [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.

[0018] [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.

[0019] [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.

[0020] 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.

[0021] [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.

[0022] 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.

[0023] [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....

[0024] 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.

[0025] 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.

[0026] Hereinafter, a job for which contractors are being recruited in the matching system 1 may be referred to as a "recruited job" or a "recruited case", a person providing a recruited case may be referred to as a "recruiter", and a person applying to receive an order for 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".

[0027] 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."

[0028] 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.

[0029] 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."

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

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

[0043] 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.

[0044] The storage 103 is configured with a hard disk drive, a solid state drive, and the like. 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 include 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, and an evaluation input database (evaluation input DB ) 126 and an evaluation summary database (evaluation summary DB) 127 .

[0045] 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.

[0046] 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.

[0047] [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.

[0048] 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.

[0049] 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.

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

[0051] [Configuration of applicant device 300] The applicant device 300 comprises a processor 301, a memory 302, a communication interface 303, an input / output interface 304, a display 305, and an operation unit 306. The operation unit 306 is made up of a mouse, a keyboard, and the like.

[0052] 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.

[0053] 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.

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

[0055] [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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] [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.

[0063] 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.

[0064] [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.

[0065] 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.

[0066] 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.

[0067] [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.

[0068] [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, a disclosure level, a request title, an expected number of man-hours, an expected period, and a request content.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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.

[0076] [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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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(%).

[0081] 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.

[0082] 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.

[0083] 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.

[0084] As data for case 002 in November, the 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 expected side job hours that were set. % This shows that member P2 completed half of the total work for case 002 in November.

[0085] 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.

[0086] 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).

[0087] 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.

[0088] 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.

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

[0090] The person being evaluated is one who applies for a job and receives the job. The evaluator is the person who solicits the job (the person placing the order). Evaluations of the person being evaluated are registered for each evaluator in the evaluation input database 126. The evaluation result is expressed as a numerical value, with 10 being the maximum value and 0 being the minimum value. Figure 8 shows an example where member P7 is the person being evaluated.

[0091] When a job solicitor (orderer) completes a job requested of an applicant (recipient), he / she uses the solicitor device 200 to evaluate the applicant (evaluatee) as an evaluator. The evaluator's evaluation results are registered in the evaluation input database 126. When a certain recruiter requests a different job from an applicant who has previously been requested to do a job, 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.

[0092] 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 or a standard deviation value may be used. Evaluation results by case ID may also be registered in the evaluation input database 126.

[0093] [Evaluation Summary Database 127] 9 is a diagram showing an example of the evaluation summary database 127. Departmental evaluation information for the person being evaluated is registered in the evaluation summary database 127. The information on the evaluation by organization includes the member ID of the person being evaluated, the ID of the company to which the person being evaluated belongs, the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, and an evaluation summary.

[0094] FIG. 9 shows an example 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 FIG. 9, data group 127A represents company A's evaluation of member P7, and data group 127B represents company B's evaluation of member P7.

[0095] With reference to data group 127A, it can be seen that the evaluation of company A is classified into the categories of evaluation of the entire company, evaluation of the system department of company A, and evaluation of the planning department of company A. In the evaluation summary, the average value of the evaluation corresponding to each classified category is registered.

[0096] For example, the evaluation summary corresponding to the entire company A is registered with the average evaluation results of the members of company A who evaluated member P7. The evaluation summary corresponding to the system department is registered with the average evaluation results of the members of company A who evaluated member P7 and who belong to the system department.

[0097] Similarly, a data group 127B showing the evaluation of company B with respect to member P7 is registered in the evaluation summary database 127, which includes an evaluation summary of company B as a whole and evaluation summaries for each department within company B.

[0098] 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.

[0099] Although FIG. 9 shows only member P7 as an assessee, the other members P1 to P6, member P8, and member P9 . . . are also registered in the evaluation summary database 127 as assessees in the same manner.

[0100] [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.

[0101] 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.

[0102] 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).

[0103] 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.

[0104] 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.

[0105] 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 for updating the information about a company that has already been registered.

[0106] 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 a member of 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).

[0107] Specifically, a person who wishes to become a member inputs information such as his / her name, company, and department into a personal computer, and transmits the input information to the sharing server 100. The member registration unit 142 registers the input information in the member database 122. A new member 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.

[0108] 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 position 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.

[0109] The member search unit 143 has a function of searching for members of the matching system 1. When the recruiter's device 200 receives a search operation from the recruiter, it executes a member search process (step S4). 300 When the member search unit 143 receives a search operation for a manager who is the superior of an applicant, the member search unit 143 executes a member search process (step S4). The member search unit 143 provides the information of the members registered in the member database 122 to the recruiter device 200 and the applicant device 300 of the manager.

[0110] The member search process (step S4) 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.

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] 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.

[0116] 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.

[0117] 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. 13. The spare capacity for a side job is calculated as the available time for a side job shown in FIG. 14.

[0118] 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.

[0119] 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.

[0120] 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).

[0121] 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.

[0122] 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.

[0123] The application unit 146 is an applicant device 300 The application unit 146 transmits the application information received from the applicant device 300 to the applicant device 300 of the manager (the manager of the applicant). The application unit 146 identifies the member ID of the manager who is the manager of the applicant, based on the relationship between the member ID of the applicant and the member ID of the manager, which are registered in the member database 122, for example. The application unit 146 transmits the application information of the subordinate to the applicant device 300 corresponding to the identified member ID of the manager. 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.

[0124] 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.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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.

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

[0133] 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.

[0134] 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.

[0135] 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.

[0136] 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.

[0137] 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 Figure 20.

[0138] 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.

[0139] 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.

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

[0141] 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 evaluation (step S16). Therefore, when accepting the input evaluation, the recruiter device 200 functions as an evaluator device operated by an evaluator.

[0142] 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.

[0143] The process of step S16 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.

[0144] When the recruiter accepts an operation to view the evaluation of the applicant, the recruiter device 200 executes a view request process (step S17). In the view request process, the recruiter 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 transmits the evaluation of the applicant 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 S18).

[0145] The processes of steps S17 and S18 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.

[0146] [Details of the processing by the case registration unit 144 and the recruiter device 200] Fig. 13 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. 13.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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 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, and the case content in the solicited case database 124 in association with the generated case ID.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] Fig. 14 is a diagram for explaining the procedure for searching for recruitment requests from the database 120. The processes of 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. 14.

[0159] 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.

[0160] 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.

[0161] 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.

[0162] 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.

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

[0164] 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.

[0165] 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.

[0166] 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.

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

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

[0169] 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.

[0170] 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.

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

[0172] 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.

[0173] [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).

[0174] [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).

[0175] 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.

[0176] [Process to register planned and actual side job hours] Fig. 15 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. 15.

[0177] 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.

[0178] 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.

[0179] 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.

[0180] 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.

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

[0182] 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 S16). 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).

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

[0184] If the evaluation results of the recruiter (evaluator) for the evaluatee are already registered in the evaluation input database 126, the evaluation receiving unit 151 calculates the average value of the evaluator's evaluation results for the evaluatee, 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 evaluatee are registered in the evaluation input database 126 for each evaluator.

[0185] Next, the evaluation receiving unit 151 executes an evaluation summary process (step S1514). In the evaluation summary process, the evaluation receiving unit 151 calculates the average value of the evaluation results for the evaluatees by company and department, and registers the calculation results in the evaluation summary database 127.

[0186] For example, the evaluation receiving unit 151 identifies the evaluator using the member ID used by the recruiter device 200 to sign in to execute step S16. 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 S1513, 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 accessing the sharing server 100."

[0187] 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 evaluation summary corresponding to the detected data row.

[0188] For example, data group 127A in Fig. 9 includes the member ID of the appraisee, P7, the ID of the company to which the appraisee belongs, 00C, and the ID of the company to which the evaluator belongs, 00A. When a member belonging to the system department of company A evaluates member P7, the evaluation is accepted in step S1513.

[0189] In this case, in step S1514, the evaluation received in step S1513 is reflected in the evaluation summary corresponding to the "whole" and the evaluation summary corresponding to the "system part" of data group 127A.

[0190] More specifically, evaluation receiving unit 151 sets the average value of the evaluations of company C as a whole, including the evaluations received in step S1513, as an evaluation summary corresponding to “whole” in data group 127A. Similarly, evaluation receiving unit 151 sets the average value of the evaluations of the system part, including the evaluations received in step S1513, as an evaluation summary corresponding to “system part” in data group 127A.

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

[0192] [Process to output the applicant's evaluation summary] When the recruiter's device 200 receives an operation for the recruiter to view the evaluations of the applicant, the recruiter's device 200 executes a view request process (step S17). 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 an evaluation summary that the recruiter (view requester) has permission to view from the evaluation summary database 127 (step S1521).

[0193] The recruiter who made the viewing request is authorized to view the evaluation summary of the entire company to which the recruiter belongs and the evaluation summary of 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 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."

[0194] The evaluation output unit 152 selects an evaluation summary corresponding to the viewing authority from the evaluation summary database 127. The evaluation output unit 152 transmits data including the selected evaluation summary to the recruiter device 200 (step S1522). The transmitted data includes, in addition to the evaluation summary, the member ID of the applicant (person being evaluated), information on the company to which the applicant belongs, information on the department to which the applicant belongs, and the like. If there are selection options for the evaluation output unit 152, the transmitted data includes evaluation summaries corresponding to each of multiple applicants (persons being evaluated).

[0195] The recruiter device 200, which has received the evaluation summary, displays the applicant's 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 S18). When evaluation summaries corresponding to multiple applicants (evaluated persons) are received, the recruiter device 200 displays the evaluation summaries in a list of multiple applicants (evaluated persons).

[0196] 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 sends an evaluation summary, which is an example of evaluation information, to the recruiter device 200 of the recruiter who sent the viewing request.

[0197] [Member search process] When the recruiter device 200 receives a search operation of a person recruiting contractors for a job, the recruiter device 200 executes a member search process (step S4). In the member search process, the recruiter device 200 transmits a search request to the member search unit 143 of the sharing server 100. For example, the search request includes a reference value for excluding members with low evaluations in the member search.

[0198] 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 S1431). Here, the company identified in step S1431 is referred to as "company X."

[0199] 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 X to which the recruiter belongs by using the company database 121 and the member database 122.

[0200] Next, the member search unit 143 extracts members whose evaluation summary value for the identified company X as a whole exceeds a reference value from the evaluation summary database 127 (step S1432). In other words, the member search unit 143 extracts search results excluding members whose evaluation for the company X as a whole is low. The sharing server 100 may be provided with a function for receiving setting information for the reference value from the recruiter device 200 of each company. This allows each company to exclude members whose evaluation is low based on their own reference value from the search results.

[0201] 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 S1433). The recruiter device 200 displays the received search results in a list on the display 205 (step S19).

[0202] As a result, the recruiter can view the search results excluding members whose company has a low overall rating on the display 205. Therefore, when selecting an order recipient from among applicants, the recruiter can save the trouble of visually excluding members whose company has a low overall rating.

[0203] 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.

[0204] [Availability of evaluation summary database 127] Fig. 18 is a diagram for explaining the viewable range of the evaluation summary database 127. As shown in Fig. 18, the right to view the evaluation summary calculated from the overall evaluation of company A is granted to all members (recruiters) belonging to company A.

[0205] Viewing rights for the evaluation summary calculated from the evaluation of Company A's System Department are granted to members (recruiters) of Company A's System Department, but are not granted to members (recruiters) other than the System Department of Company A. Viewing rights for the evaluation summary calculated from the evaluation of Company A's Planning Department are granted to members (recruiters) of Company A's Planning Department, but are not granted to members (recruiters) other than Company A's Planning Department.

[0206] Viewing authority for the evaluation summary calculated from the overall evaluation of Company B is granted to all members (recruiters) belonging to Company B. Viewing authority for the evaluation summary calculated from the evaluation of the planning department of Company B is granted to members (recruiters) of the planning department of Company B, but not to members (recruiters) other than those of the planning department of Company B.

[0207] If the viewers are members (recruiters) of Company X's first division and members (recruiters) of Company X's second division, the viewers' authority to view the overall evaluation summary of Company X, 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 18.

[0208] The evaluation summary of the entire company X, the evaluation summary of the first division of company X, and the evaluation summary of the second division of company X are shared within company X, but are not made public to members of companies other than company X. Therefore, for example, even if the performance of an employee of company Y who has been contracted to recruit for company X is not satisfactory, the recruiter of company X can evaluate the employee of company Y on an objective basis without considering the relationship between the companies.

[0209] Furthermore, because the evaluations are shared within Company X as an evaluation summary, the evaluators are made aware that the accumulation of each evaluation produces useful information. This gives the evaluators an incentive to make accurate evaluations. As a result, the accuracy of the evaluation summary improves. This makes it possible to use the evaluation summary effectively as reference data when selecting contractors.

[0210] Furthermore, according to this embodiment, when the recruiter device 200 executes the member search process (step S4), the search result excluding low-rated members is provided to the recruiter (step S1432). In other words, the matching system 1 has a filtering function that provides the search result excluding low-rated members.

[0211] Therefore, when deciding on a contractor for the job, the recruiter can prevent the erroneous hiring of a member with a low evaluation on a company-by-company basis. The sharing server 100 may perform filtering using the evaluation summary on a department-by-department basis.

[0212] 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.

[0213] [Example of how the scope of disclosure is set according to the disclosure level] Fig. 19 is a diagram showing an example in which the disclosure range is set according to the disclosure level. Here, as shown in Fig. 19, 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.

[0214] The disclosure levels of "Level 1" to "Level 3" shown in FIG. 19 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 recruiter's company. At level 3, the recruitment job of the recruiter is disclosed to applicants who belong to all companies including the recruiter's company. 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."

[0215] 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.

[0216] 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.

[0217] For example, the disclosure range of the recruitment job 001 may be limited to only companies A and C belonging to the community identified by the community ID=03. Alternatively, the disclosure range of the recruitment job 002 may be limited to only companies C and D belonging to the community identified by the community ID=02. D Alternatively, the disclosure scope of case 003 may be limited to companies C, D, and C 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.

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

[0219] 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.

[0220] 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.

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

[0222] 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."

[0223] 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."

[0224] 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."

[0225] 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."

[0226] 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."

[0227] 18 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.

[0228] 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.

[0229] 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.

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

[0231] 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.

[0232] <Variation 1> Next, a first modification will be described with reference to Fig. 21 to Fig. 23. 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.

[0233] [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.

[0234] 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.

[0235] 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.

[0236] FIG. 21 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.

[0237] 21, 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.

[0238] 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.

[0239] 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.

[0240] 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 .

[0241] 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).

[0242] 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.

[0243] Fig. 22 is a diagram showing an example of member database 122A relating to Modification 1. Compared to member database 122 shown in Fig. 4, member database 122A shown in Fig. 22 has profile information and profile disclosure information indicating whether or not to make the profile publicly available added thereto.

[0244] 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 track record, the member's qualifications, and the like.

[0245] 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.

[0246] 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.

[0247] 23 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.

[0248] 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.

[0249] 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).

[0250] 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).

[0251] 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.

[0252] 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).

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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.

[0257] <Variation 2> Next, a second modified example will be described with reference to Fig. 24 to Fig. 28. 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.

[0258] [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.

[0259] 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.

[0260] Fig. 24 is a block diagram showing the configurations of the sharing server 100, recruiter device 200, and applicant device 300 relating to Modification 2. In the block diagram shown in Fig. 24, a member group database 128 is added to the block diagram shown in Fig. 2. In the recruiting request database 124A shown in Fig. 24, a function of registering a recruiting request that allows application by a member group is added to the recruiting request database 124 shown in Fig. 6.

[0261] 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.

[0262] 25 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.

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

[0264] 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.

[0265] 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.

[0266] 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.

[0267] Member group database 128 is stored in storage 103 of sharing server 100, as shown in Fig. 24. 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."

[0268] Fig. 26 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. 26 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.

[0269] 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."

[0270] Fig. 27 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. 27, compared to Fig. 11, a determination unit 145A is added to the sharing server 100. Also, compared to Fig. 11, in Fig. 27, step S7A is added after step S7, and step S8A of group application is adopted instead of step S8 of application.

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

[0272] 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).

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] 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.

[0278] The determination unit 145A returns the determination result to the applicant device 300. FIG. 27 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.

[0279] 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 is similar to 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. For this reason, the application approval processing in step S9 is executed for each superior of each member belonging to the member group. Therefore, the approval unit 147 transmits approval information indicating that the subordinate's application is approved, or information indicating that the subordinate's application is rejected. Sukiyaki The following information is received from multiple superiors.

[0280] 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.

[0281] 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.

[0282] 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.

[0283] Fig. 28 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. 28, compared to Fig. 13, a recruitment form is added to the business information input to the recruiter device 200.

[0284] 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. 28 are the same as those in FIG. 13 already described, and therefore the description will not be repeated here.

[0285] 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.

[0286] 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.

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

[0288] (Paragraph 1) The evaluation system described in paragraph 1 is an evaluation system that evaluates contractors who apply for a job, and includes 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 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 contractor as belonging to the first group, it transmits the first evaluation information to the sender that sent the viewing request in the first communication.

[0289] (Paragraph 2) The evaluation system described in paragraph 2 is the evaluation system described in paragraph 1, further comprising a second evaluator device operated by one or more evaluators belonging to a second group different from the first group, wherein 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.

[0290] (Item 3) The evaluation system described in item 3 is the evaluation system described in item 2, in which a first group is constituted by a first company, and a second group is constituted by a second company different from the first company.

[0291] (4) The evaluation system described in paragraph 4 is the evaluation system described in paragraph 2, wherein the first group is composed of a first division of a first company, and the second group is composed of a second division of the first company.

[0292] (Clause 5) The evaluation system described in clause 5 is an evaluation system described in any one of clauses 1 to 4, in which when the computing device receives evaluations of a specific contractor from a plurality of evaluators belonging to a first group, the computing device calculates an average value of the evaluations of the specific contractor by the plurality of evaluators, and transmits the average value as first evaluation information of the specific contractor to the sender that sent the viewing request in the first communication.

[0293] (Item 6) The evaluation system described in item 6 is the evaluation system described in any one of items 1 to 3, wherein 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 evaluations for a specific contractor based on evaluations for the specific 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 evaluations for the specific contractor based on evaluations for the specific 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 evaluations for the specific contractor based on evaluations for the specific contractor received from the multiple evaluators belonging to the first group. based on the evaluations of the specified contractor received from the evaluators, calculates a third average value, which is the average value of the evaluations for the specified contractor, 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 division 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 of the specified contractor, 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 division 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 of the specified contractor.

[0294] (Clause 7) The evaluation system described in clause 7 is an evaluation system described in any one of clauses 1 to 6, in which a list of contractors is registered in a database, and when the first evaluator device receives an operation to search the list, it sends a search request to a computing device, and when the computing device receives the search request, it sends a search result to the sender that sent the viewing request in the first communication, excluding contractors from the list whose level of evaluation identified by the first evaluation information does not meet the criteria.

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

[0296] (Item 9) The evaluator device described in item 9 is an evaluator device operated by one or more evaluators belonging to a first group, and comprises 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 the database, and 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.

[0297] (Item 10) The method described in item 10 is a method for evaluating contractors who have applied for a job, and includes 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.

[0298] 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]

[0299] 1 Matching system, 50 Internet, 100 Sharing server, 101 Processor, 102 Memory, 103 Storage, 104 Communication interface, 120 Database (DB), 121 Company database (Company DB), 122, 122A Member database (Member DB), 123 Community database (Community DB), 124, 124A Recruitment case database (Recruitment case DB), 125 Side job database (Side job DB), 126 Evaluation input database (Evaluation input DB), 127 Evaluation summary database (Evaluation summary DB), 127A, 127B Data group, 128 Member group database (Member group 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 judgementsection, 146 application section, 147 approval section, 148 notification section, 149 performance reception section, 150 performance output section, 151 evaluation reception section, 152 evaluation output section, 161 counter offer request section, 162 counter offer approval request section, 163 counter offer request acceptance notification section, 200, 200A, 200B, 200C recruiter device, 201 processor, 202 memory, 203 communication interface, 204 input / output interface, 205 display, 206 operation section, 206A keyboard, 206B mouse, 207 screen, 300, 300A, 300B, 300C applicant device, 301 processor, 302 memory, 303 communication interface, 304 input / output interface, 305 display, 306 operation section, 306A keyboard, 306B Mouse, 307A-307C Tabs, 401,402 Tables.

Claims

1. An evaluation system for evaluating contractors who apply for a job, a first evaluator device operated by one or more evaluators belonging to a first group; a second evaluator device operated by one or more evaluators belonging to a second group different from the first group; a computing device in communication with the first evaluator device and capable of accessing a database; The first evaluator device receives an input of an evaluation of a contractor and transmits the received evaluation to the computing device; The second evaluator device receives an input of an evaluation of the contractor and transmits the received 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 contractor; The computing device registers second evaluation information based on the evaluation received from the second evaluator device in the database for each contractor; the first evaluator device and the second evaluator device are capable of receiving an input of an evaluation for a first contractor; When the computing device receives a browsing request in a first communication established by identification information that can identify the person as belonging to the first group, the computing device transmits the first evaluation information regarding the first contractor to a source that transmitted the browsing request in the first communication, and does not transmit the second evaluation information regarding the first contractor; An evaluation system in which, when the computing device receives a viewing request in a second communication established by identification information that can identify the person as belonging to the second group, the computing device transmits the second evaluation information regarding the first contractor to the sender that sent the viewing request in the second communication, and does not transmit the first evaluation information regarding the first contractor.

2. The evaluation system according to claim 1 , wherein the first group is constituted by a first company, and the second group is constituted by a second company different from the first company.

3. 2. The evaluation system according to claim 1, wherein the first group is made up of a first division of a first company, and the second group is made up of a second division of the first company.

4. When the computing device receives evaluations of a specific contractor from a plurality of evaluators belonging to the first group, the computing device calculates an average value of the evaluations of the specific contractor by the plurality of evaluators; The evaluation system according to any one of claims 1 to 3, wherein the computing device transmits the average value as the first evaluation information of the specified contractor to a sender that transmitted the viewing request in the first communication.

5. 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; a computing device in communication with the first evaluator device and capable of accessing a database; The first evaluator device receives an input of an evaluation of a contractor and transmits the received 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 contractor; when the computing device receives a browsing request in a first communication established by identification information that can identify the computing device as belonging to the first group, the computing device transmits the first evaluation information to a transmission source that transmitted the browsing request in the first communication; The first group includes one or more evaluators belonging to a first divided group and one or more evaluators belonging to a second divided group different from the first divided group, The computing device calculates a first average value, which is an average value of the evaluations for the specific contractor, based on the evaluations for the specific contractor received from the multiple evaluators belonging to the first divided group; 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 a plurality of evaluators belonging to the second divided group; The computing device calculates a third 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 group; When the computing device receives a browsing request in a third communication established by identification information that can identify the person as belonging to the first divided group, the computing device transmits the first average value and the third average value to a source that transmitted the browsing request in the third communication as the first evaluation information of the specified contractor; An evaluation system in which, 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 division group, the computing device 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 of the specified contractor.

6. The database has a list of contractors registered therein, When the first evaluator device receives an operation to search the list, the first evaluator device transmits a search request to the computing device; The evaluation system of claim 1, wherein when the computing device receives the search request, the computing device transmits a search result to the sender that sent the viewing request in the first communication, the search result excluding from the list contractors whose evaluation level specified by the first evaluation information does not meet the standard.

7. In the database, a plurality of pieces of business information are registered together with disclosure information indicating the scope of disclosure to applicants, the evaluation system further comprises an applicant device operated by an applicant belonging to the second group; The evaluation system described in claim 1 or claim 2, wherein the computing device determines, based on the disclosure information, which of the multiple business information registered in the database is permitted to be disclosed to applicants belonging to the second group, and provides the business information that is permitted to be disclosed to applicants belonging to the second group to the applicant device.

8. A method for evaluating contractors who apply for a job, comprising: a first evaluator device operated by one or more evaluators belonging to a first group; a computing device in communication with the first evaluator device and capable of accessing a database; a second evaluator device operated by one or more evaluators belonging to a second group different from the first group, The method comprises: receiving an input of an evaluation of a contractor in the first evaluator device and transmitting the received evaluation to the computing device; receiving, in the second evaluator device, an input of an evaluation of the contractor and transmitting the received evaluation to the computing device; a step of registering, in the computing device, first evaluation information based on the evaluation received from the first evaluator device in the database for each contractor; and registering, in the computing device, second evaluation information based on the evaluation received from the second evaluator device in the database for each contractor; the first evaluator device and the second evaluator device are capable of receiving an input of an evaluation for a first contractor; The method comprises: When the computing device receives a viewing request in a first communication established by identification information that can identify the first contractor as belonging to the first group, the computing device transmits the first evaluation information regarding the first contractor to a source that transmitted the viewing request in the first communication, and does not transmit the second evaluation information regarding the first contractor; The method further includes a step in which, when the computing device receives a viewing request in a second communication established by identification information that can identify the first contractor as belonging to the second group, the computing device transmits the second evaluation information regarding the first contractor to a sender that transmitted the viewing request in the second communication, and the computing device does not transmit the first evaluation information regarding the first contractor.

Images