Matching system and method

Abstract

To select an appropriate applicant in consideration of a relation of interest between a group of seekers and a group of applicants.SOLUTION: A matching system (1) for matching a recruiter who recruits an order receiver of a task with an applicant, the matching system including a first applicant device (300) operated by a first applicant and a compute device (100) capable of communicating with the first applicant device (300) and accessing a database (120), the compute device (100) registering, in the database (120), task information for recruiting an order receiver and disclosure information indicating a disclosure range of the task information, the compute device (100) determines the business information permitted to be disclosed to the first applicant among the business information registered in the database (120) on the basis of the disclosure information, and provides the business information permitted to be disclosed to the first applicant to the first applicant device (300).SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a matching system, a recruiter device, and a method for matching a recruiter who is seeking contractors for a job with an applicant. [Background technology]

[0002] Crowdsourcing has been used by businesses for some time. Generally, crowdsourcing refers to the process of acquiring needed services, ideas, or content by soliciting contributions from an unspecified number of people. Crowdsourcing involves finding people with the best skills to perform the required tasks.

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

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-44642 Summary of the Invention [Problem to be solved by the invention]

[0005] The crowdsourcing described in Patent Document 1 is implemented within a single group, namely a company. However, in order to find more suitable personnel, it is desirable to further expand the scope of crowdsourcing. In this case, it becomes necessary to consider the conflict of interest between the recruiter who is recruiting contractors for the work and the applicants who apply for the job.

[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to make it possible to select appropriate applicants taking into consideration the interests of the recruiter and the applicant. [Means for solving the problem]

[0007] A matching system according to a first aspect of the present disclosure is a matching system that matches applicants with recruiters seeking contractors for a job, and includes a first applicant device operated by the first applicant, and a computing device that communicates with the first applicant device and can access a database, wherein the computing device registers in the database business information for which contractors are sought and disclosure information indicating the scope of disclosure of the business information, and the computing device determines, based on the disclosure information, which business information registered in the database is permitted to be disclosed to the first applicant, and provides the business information that is permitted to be disclosed to the first applicant to the first applicant device.

[0008] A recruiter device according to a second aspect of the present disclosure is a recruiter device operated by a recruiter, which communicates with a computing device that matches applicants with recruiters who are recruiting contractors for work, and is equipped with an interface that accepts operations to input business information and disclosure information indicating the scope of disclosure of the business information, and a processor that transmits the business information and disclosure information accepted by the interface to the computing device, and the disclosure information includes information that instructs the computing device to allow disclosure of the business information to a first applicant and to prohibit disclosure of the business information to a second applicant different from the first applicant.

[0009] A method according to a third aspect of the present disclosure is a method for matching applicants with recruiters seeking contractors for a business, and includes the steps of communicating with a first applicant device operated by the first applicant, registering in a database business information for which contractors are sought and disclosure information indicating the scope of disclosure of the business information, and determining, based on the disclosure information, which business information registered in the database is permitted to be disclosed to the first applicant, and providing the business information that is permitted to be disclosed to the first applicant to the first applicant device. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to select an appropriate applicant taking into consideration the conflict of interest between the recruiter who is recruiting contractors for a job and the applicants who apply for that job. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing an overview of a matching system. [Figure 2] FIG. 2 is a block diagram showing the configurations of a sharing server, a recruiter device, and an applicant device. [Figure 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. [Figure 5] FIG. 2 is a diagram illustrating an example of a community database. [Figure 6] FIG. 10 is a diagram illustrating an example of a recruitment request database. [Figure 7] FIG. 10 is a diagram illustrating 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. 10 is a diagram illustrating an example of an evaluation summary database. [Figure 10] FIG. 2 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device. [Figure 11]FIG. 2 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device. [Figure 12] FIG. 2 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device. [Figure 13] FIG. 10 is a diagram for explaining a procedure for registering a job posting in a job posting database. [Figure 14] FIG. 10 is a diagram for explaining a procedure for searching for a job posting from a database. [Figure 15] FIG. 10 is a diagram for explaining the procedure for registering side job plans and results in a database. [Figure 16] FIG. 10 is a diagram for explaining the procedure for registering an evaluation of an applicant in a database. [Figure 17] FIG. 10 is a diagram for explaining the procedure for displaying the evaluation of an applicant and the search results of members on a display. [Figure 18] FIG. 10 is a diagram for explaining the viewable range of the evaluation summary database. [Figure 19] FIG. 10 is a diagram showing an example in which the disclosure range is set according to the disclosure level. [Figure 20] FIG. 10 is a diagram showing a screen displayed on the applicant device of a manager (applicant's boss) when the manager checks the side job status of his / her subordinates. [Figure 21] FIG. 10 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device according to the first modification. [Figure 22] FIG. 10 is a diagram showing an example of a member database according to the first modification. [Figure 23] 10 is a flowchart showing the processing steps of a counter offer member search process according to the first modification. [Figure 24] FIG. 10 is a block diagram showing the configurations of a sharing server, a recruiter device, and an applicant device according to Modification 2. [Figure 25] FIG. 11 is a diagram showing an example of a member group database according to the second modification. [Figure 26] FIG. 10 is a diagram showing an example of a recruitment request database according to the second modification. [Figure 27] FIG. 10 is a diagram for explaining the functions of a sharing server, a recruiter device, and an applicant device according to Modification 2. [Figure 28] FIG. 10 is a diagram for explaining the procedure for registering a job posting related to the second modification in the job posting database. [Figure 29] FIG. 10 is a diagram showing the configuration of a matching system according to Modification 3. [Figure 30] FIG. 10 is a diagram showing an example (fourth modification) in which Kerberos authentication is applied to a matching system. DETAILED DESCRIPTION OF THE INVENTION

[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 numerals, and description thereof will not be repeated.

[0013] [Background for 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 employees to have side jobs in order to make effective use of their human resources. By using crowdsourcing between companies, the capabilities of employees can be utilized.

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

[0017] [Possibility of confidential information being leaked] With typical crowdsourcing methods, the relationship between the client company and the recipient company is not taken into consideration, so adopting crowdsourcing involves both 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 traditional crowdsourcing methods, managers cannot ensure that employees are not taking on 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 their working hours will become excessively long. To eliminate the risk of overwork, companies could set a limit on overtime hours, including for their main job and side job. However, as long as employees are free to take on side jobs, it will be difficult for companies to control the amount of time 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] There are currently crowdsourcing systems that request clients to evaluate contractors. If appropriate evaluations made by clients are shared on the crowdsourcing system, those seeking contractors for work can refer to those evaluations to select highly capable individuals from among the many applicants for work.

[0020] However, a client of a certain company may be so concerned about the contractors of other companies being evaluated that they enter a higher rating into the system than they should. Also, a client of a certain company may avoid giving a low rating to a contractor of another company, fearing that this could worsen the relationship between the companies. Furthermore, a client may not see any benefit in providing a rating and enter a rating that is far from their true rating into the system. Considering these possibilities, the reliability of the ratings provided by the system may be reduced. In this case, even if the ratings of contractors are shared, the client of the work cannot use the ratings as reference data when selecting a contractor.

[0021] [Special features of matching with companies] Generally, in order to match talent with jobs across companies, a close relationship such as trust between the companies matching talent and jobs is required. Therefore, for example, it is extremely difficult to match talent with jobs across companies that have no capital relationship. In addition, large companies such as listed companies are prone to competing with other companies from the perspective of diversified management, etc., and cannibalization occurs between other companies, so they have a unique situation in which they cannot match talent with jobs across a large number of companies.

[0022] In this embodiment, a matching system 1, which will be described in detail below, is proposed in order to solve 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, etc., and applicant devices 300A, 300B, 300C, etc.

[0024] 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 matching system 1. Employees of company A, company B, company C, etc. who use matching system 1 are also individually registered as members of matching system 1.

[0025] The work arranged by the matching system 1 is, for example, temporary work that is expected to be completed within a predetermined period of time. Therefore, a person who accepts a work arranged by the matching system 1 will work in the specific department to which they belong within the company as their main job, and will engage in the work arranged by the matching system 1 as a side job, respectively. Note that in the matching system 1, for example, an applicant from company A can also accept an order for 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 an order for work from department X of company A.

[0026] Hereinafter, work for which contractors are being recruited in the matching system 1 may be referred to as a "recruited work" or a "recruited case," a person who provides a recruited case may be referred to as a "recruiter," and a person who applies to receive an order for a recruited case may be referred to as an "applicant." Applying for a recruited work may be referred to as an "application for the recruited work" or an "application for the recruited case."

[0027] An applicant who accepts a job offer is referred to as the "contractor," and a recruiter who places an order with a contractor is referred to as the "orderer." However, in the following, the term "contractor" may be used to refer to the "applicant," and the term "orderer" may be used to refer to the "contractor."

[0028] The sharing server 100 has a database 120 necessary for the matching service. The database 120 includes various databases in which information necessary for providing the matching service is registered. For example, the database 120 registers information about members and recruitment operations. The sharing server 100 is managed and operated by a company separate from the companies that use the matching service. Any of the companies that use the matching service may manage and operate the sharing server 100.

[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, etc. 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, etc. may be collectively referred to as "applicant devices 300." Although FIG. 1 shows two applicants for each company, 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 act as recruiters. Therefore, hereinafter, the managers of each company will be referred to as "recruiters." Recruiters can also act as applicants for jobs that other recruiters are recruiting for. In this 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 administrators. When company A has administrators, each administrator may be given a recruiter device 200, or one recruiter device 200 may be shared by multiple administrators. The same applies to company B, company 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 recruiter and applicant 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 (requested work) in the database 120 in response to an operation to input the recruitment request, registers an evaluation of the target applicant (contractor) in the database 120 in response to an operation to input an evaluation, and provides member information to the recruiter device 200 in response to an operation to search for members.

[0037] Applicant device 300 accepts various operations by applicants. For example, applicant device 300 accepts operations such as searching for job postings, applying for job postings, and inputting work performance.

[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 job postings in response to an operation to search for job postings, issues a notice of employment or rejection to the applicant device 300 in response to an operation to apply for the job posting, 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 job posting 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 job posting 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.

[0042] [Configuration of Sharing Server 100] 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 required 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, etc. The storage 103 stores a database 120. The database 120 includes multiple types of databases. The multiple 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, an evaluation input database (evaluation input) 126, and an evaluation summary database (evaluation summary DB) 127.

[0045] Some of these multiple types of databases may be stored in 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] Processor 101 connects to Internet 50 via communication interface 104 in accordance with a program stored in memory 102. Processor 101 connects to Internet 50 and communicates with recruiter device 200 and applicant device 300. Processor 101 accesses database 120 and executes processes such as extracting necessary data, registering new data in database 120, and updating data registered in database 120.

[0047] [Configuration of recruiter device 200] The recruiter device 200 comprises 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 configured with a mouse, a keyboard, and the like.

[0048] The memory 202 may include 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 job offer, displaying information about applicant members on the display 205, placing an order for work with a contractor selected from the applicants, and sending the details 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] Applicant device 300 comprises a processor 301, memory 302, a communication interface 303, an input / output interface 304, a display 305, and an operation unit 306. Operation unit 306 is made up of a mouse, a keyboard, and the like.

[0052] The memory 302 may include 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 notification of whether the applied job has been accepted or rejected on the display 305, and transmitting the results of the work ordered 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 Overview] An overview of the database 120 will be explained below. The company database 121 stores information about companies that are members of the matching system 1. The member database 122 stores information about members who use the matching system 1. Many of the members are employees of companies that are members of the matching system 1.

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

[0057] The community database 123 stores information for identifying companies that belong to a community. A community is formed by agreement between companies. Therefore, multiple communities can be formed depending on how the companies agree. The number of companies that belong to one community can also be set in various ways. Companies that have a community relationship form a relationship of trust within the scope determined by how they agree to form the community. The community database 123 registers information for each community that identifies companies that belong to the community.

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

[0059] Data indicating the status of a side job is registered for each member in the side job database 125. The data indicating 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. By using the matching system 1, a job recruiter (orderer) can evaluate the work performance of an applicant (contractor) who has completed a job as an evaluator. The evaluations made by each evaluator are registered in the evaluation input database 126.

[0061] Evaluation summaries are registered in the evaluation summary database 127. 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 job and select a member who is deemed appropriate as the 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, the company name, the company address, and the maximum side job hours are registered for each company. The maximum side job hours is the maximum amount of time an employee is permitted to work as a side job in addition to their main job. The maximum side job hours is set for each company. For example, the maximum side job hours can be calculated by subtracting the overtime hours at the main job other than the side job. The "prescribed overtime hours" vary from company to company. Note that while FIG. 3 shows the maximum side job hours in monthly units, the maximum hours may also be set in weekly units. The unit of the maximum side job hours 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 the side job time limit set by the company to which the member belongs is not exceeded.

[0064] [Member Database 122] 4 is a diagram showing an example of the member database 122. Various information about members is registered in the 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 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 member authority include administrator and applicant. A member with administrator authority is given the authority to use the matching system 1 as both a recruiter and an applicant. A member with applicant authority is given the authority to use the matching system 1 as an applicant, but not 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 his or her subordinate applicants. Therefore, a manager functions as an approver.

[0066] The side job available time is the remaining time available for a side job. The side job available time is calculated by "side job maximum 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 estimated man-hours registered in the job posting database 124. Figure 4 shows the available side job time on a monthly basis. When an applicant searches for available jobs using the matching system 1, only jobs that can be completed with man-hours within the available side job time are offered as jobs for which they can apply.

[0067] [Community Database 123] FIG. 5 is a diagram showing an example of the community database 123. Information about 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 that belong to the community. Each company can form various communities by agreeing with other companies. A company that belongs to a community can change the companies that belong to the community by agreeing with the other companies.

[0068] [Recruitment Database 124] 6 is a diagram showing an example of the job listing database 124. Information about job listings is registered in the job listing database 124. The job listing information includes a job listing ID for identifying the job listing, the ID of the company to which the recruiter who registered the job listing belongs, a list of non-disclosure company IDs, a disclosure level, a job listing title, estimated man-hours, estimated period, and job listing details.

[0069] The non-disclosure company ID list registers the IDs of companies that prohibit disclosure of job postings. 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 recruitment request corresponding to request ID=001 has the disclosure level set to "our company." In this case, only members who belong to the company that registered the recruitment request (company ID=00A) can view the recruitment request corresponding to request ID=001.

[0071] Hereinafter, the recruitment projects corresponding to each project ID may be referred to as project 001, project 002, project 003, etc., using the project 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 part of the company ID.

[0072] The disclosure level for case 002 is set to "within the community." According to the community database 123 shown in Fig. 5, the 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 job postings with a disclosure level set to "All," all members can view the job posting. This is the case for job posting 005 shown in Figure 6. If one or more company IDs are registered in the non-disclosure company ID list for job posting 005, members belonging to the companies with those company IDs will not be granted permission to view job posting 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 status of a member's side job is registered for each side job case in side job database 125. The information showing the status of a side job includes the ID of the member engaged in the side job, the case ID, the month (duration of engagement in the side job), planned time for the side job, actual time for the side job, expected time for the side job, and progress rate.

[0077] The planned side job time is the time a member is expected to need to process an order for a job. Members who have ordered a side job input their planned side job time each month from their applicant device 300. The input planned side job time is reflected in the side job database 125. For example, the estimated man-hours for job 001 are set to 5 hours / person / month in the job listing database 124. This means that the workload is 5 hours per person per month. Usually, members input their planned side job time using the estimated man-hours for the job listing as a guide.

[0078] The side job performance time is the time that a member has actually worked on an order-received project. In other words, the side job performance time is the time that a member has already worked as an actual result. Each time a member works on an order-received project until the work is completed, the member inputs the time spent working on the project into their own applicant device 300 at any timing. The cumulative value of the time input into the applicant device 300 is registered in the side job database 125 as the side job performance time for each month.

[0079] The expected side job time is the time estimated to be required for the work of the target project. In other words, the expected side job time is the time estimated as the member's future working hours. The sharing server 100 automatically sets the expected side job time, taking into account the planned side job time and the actual side job time. Members may be allowed to input the expected side job time on their own applicant device 300 at any time until the work of the target project is completed. Alternatively, members may be allowed to modify the automatically set expected side job time. It is desirable that the expected side job time be equal to or less than the planned side job time. However, depending on the status of the project, the expected side job time may be longer than the planned side job time. Members engaged in a project may be able to update their expected side job time at any time until the work of the project 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 initially accepts a 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 are the same. As the member progresses with the project and inputs the actual side job time and progress rate, the expected side job time changes.

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

[0083] The side job database 125 stores the following data for October for project 001: planned side job hours = 5, actual side job hours = 10, and expected side job hours = 10. This shows that member P2 worked on project 001 in October beyond the planned side job hours.

[0084] The data for November of case 002 is registered in side job database 125 as planned side job hours = 10, actual side job hours = 4, and expected side job hours = 8. From this, it can be seen that member P2 worked on case 002 in November without exceeding the set expected side job hours. Since the progress rate is 50, it can be seen 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 shows that planned side job hours = 5 and estimated side job hours = 5, but no actual side job hours are registered. Similarly, the December data for case 002 also shows that no actual side job hours are registered. This means that the system is waiting for member P2 to input actual side job hours.

[0086] Sharing server 100 calculates the member's available capacity for additional side jobs using the expected side job time and actual side job time in side job database 125. If a member is engaged in multiple side jobs, sharing server 100 calculates the "total expected side job time," which is the sum of the expected side job times corresponding to those multiple side jobs, and the "total actual side job time," which is the sum of the actual side job times corresponding to those multiple side jobs. Sharing server 100 calculates the available capacity for side jobs by calculating "side job upper limit time - (total expected side job time + total actual side job time)." If "total side job time" is defined as "total expected side job time + total actual side job time," then the available capacity for side jobs, i.e., "available side job time," is calculated as "side job upper limit time - total side job time." For example, in the side job database 125 shown in Figure 7, member P2's total expected side job time, which is the sum of his or her expected side job hours in December, is 15 hours (5 hours + 10 hours). Additionally, the total number of hours worked by member P2 on a side job 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 time for a side job) is calculated as 15 hours (30 hours - 15 hours).

[0087] Here, we will explain an example of a more specific calculation procedure for the expected side job time. For example, the "expected side job time" may be calculated based on the 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 time for the side job is 10 hours and the actual time for the side job is 2 hours, the man-hour progress rate is calculated as 20%. Now, let's assume the progress rate is 40%. In this case, the expected time for the side job is calculated as "(20% / 40%) x 10 hours - 2 hours" = 3 hours. In other words, according to this calculation result, the expected time for the side job in question 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 results.

[0090] The person being evaluated is the applicant for the job and the person who receives the job. The evaluator is the person who solicits the job (the person who orders the job). 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 as the maximum value and 0 as 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 (contractor), he / she uses the recruiter device 200 to evaluate the applicant (appraisee) 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 requested 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 each evaluator's evaluation of 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 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. Department-specific evaluation information for the person being evaluated is registered in the evaluation summary database 127. The evaluation information 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] Referring 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 systems department within company A, and evaluation of the planning department within company A. The evaluation summary registers the average value of the evaluation corresponding to each classified category.

[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 are members of the system department and who evaluated member P7.

[0097] Similarly, a data group 127B representing the evaluation of company B for member P7 is registered in the evaluation summary database 127, including an evaluation summary for company B as a whole and an evaluation summary 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 the person being evaluated, other members P1 to P6, member P8, member P9, . . . are also registered in the evaluation summary database 127 as people being evaluated.

[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 into 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 input by the system administrator (step S1). The community registration unit 140 further has a function of updating the information about the community registered in the community database 123.

[0104] The company registration unit 141 has a function for registering new companies that will join the matching system 1. A system administrator inputs information about the company into 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, maximum side job hours, 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 has a function to update information about companies that have already been registered.

[0106] The member registration unit 142 has a function of registering (signing up) new members 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 a person who belongs to a company that is a member of the matching system 1. A person who wishes to become a member executes the sign-up process using a personal computer or the like (step S3).

[0107] Specifically, a person wishing to become a member enters information such as their name, the company they belong to, and the department they belong to into a personal computer or the like, and transmits the entered information to the sharing server 100. The member registration unit 142 registers the entered information in the member database 122. New members can sign in to the sharing server 100 using the personal computer they 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 intended to be operated by a manager of the applying company. The other is a device intended to be operated by someone other than the manager at the applying company. The manager of the applying company is a managerial position such as a department head, and corresponds to the superior of the applicants who are his or her subordinates. In this embodiment, the manager of the applying company plays the role of an approver who approves applications for recruitment jobs from his or her subordinates.

[0109] The member search unit 143 has a function to search for members of the matching system 1. When the recruiter device 200 receives a search operation for a recruiter, it executes a member search process (step S4). Similarly, when the applicant device 200 receives a search operation for a manager who is the superior of an applicant, it executes a member search process (step S4). The member search unit 143 provides information on members registered in the member database 122 to the recruiter device 200 and the applicant device 300 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 request registration unit 144 has a function of registering a recruitment request in the recruitment request database 124. When the recruiter device 200 receives an operation to input a recruitment request, it executes a process to register the recruitment request (step S5). In the process of registering the recruitment request, the recruiter device 200 transmits information about the recruitment request to the sharing server 100. The request registration unit 144 registers the received information about the recruitment request in the recruitment request 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 hire the applicant from the recruiter, and notifying the applicant and the manager of the result.

[0115] The application unit 146, approval unit 147, and notification unit 148 realize, by means of 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 allowed to view from 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 allowed 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 are permitted for viewing by the applicant. Therefore, the case extraction unit 145 extracts cases that are permitted for disclosure 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 are permitted for viewing by the applicant to the applicant device 300.

[0119] The case extraction unit 145 may be configured to accept an operation to set criteria for extracting cases. For example, a function may be added to the sharing server 100 that allows the system administrator to select one of a first setting that enables only the first criteria, a second setting that enables only the second criteria, 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 the recruitment requests 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 request for the application target 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 transmits the application information received from the applicant device 30 to the applicant device 300 of the manager (the applicant's superior). The application unit 146 identifies the member ID of the applicant's superior, who is the manager, based on, for example, the relationship between the applicant's member ID and the superior's member ID registered in the member database 122. The application unit 146 transmits the subordinate's application information to the applicant device 300 corresponding to the identified superior's member ID. The manager checks the job for which the subordinate has applied on his / her own applicant device 300. The manager performs an operation to approve the application on the applicant device 300. The applicant device 300 accepts the approval operation and executes application approval processing (step S9). In the application approval processing, the applicant device 300 transmits approval information to the approval unit 147 of the sharing server 100. As a result, 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 an applicant's application on the condition that approval information has been received from the applicant device 300. In this way, in this embodiment, an applicant's application is accepted on the condition that it is approved 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, confidential information can be prevented from leaking outside the company through an employee's side job.

[0125] 11 shows the flow when the administrator 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 administrator to the approval unit 147. If 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 application details 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 decision on whether to hire or not to the recruiter device 200. The recruiter device 200 accepts the input result (step S11). The recruiter device 200 transmits the accepted result of hire or not to the notification unit 148 of the sharing server 100.

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

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

[0130] 12, the sharing server 100 functionally includes a performance result receiving unit 149, a performance 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 to receive 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 to output information including the applicant's planned side job hours and actual side job hours to the recruiter device 200 or the manager's applicant device 300.

[0132] The evaluation receiving unit 151 has a function of receiving an evaluation of an applicant (contractor) 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, the applicant inputs the planned side job hours and the actual side job hours into applicant device 300. An applicant typically inputs the planned side job hours into applicant device 300 when receiving an order for a new side job, and inputs the actual side job hours into applicant device 300 at any time while engaging in the side job. For example, if an applicant receives an order for a side job that is expected to last multiple months, the applicant inputs the actual side job hours into applicant device 300 for each month.

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

[0135] The achievement receiving unit 149 registers the received planned side job hours and achieved side job hours in the side job database 125. The processing of step S14 executed by the applicant device 300 and the processing of the achievement receiving unit 149 will be described in detail later with reference to FIG.

[0136] The result output unit 150 transmits the planned side job time and actual side job 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 planned side job time and actual side job time on the display 205, and the manager's applicant device 300 displays the received information including the planned side job time and actual side job time on the display 305 (step S15). However, when the information transmitted to the recruiter device 200 is compared with the information transmitted to the manager's applicant device 300, the cases to be transmitted are different.

[0137] Data corresponding to the cases that the subordinates are 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 subordinates 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 subordinates will be explained later using FIG. 20.

[0138] Data corresponding to the job that the recruiter has recruited from among the many jobs registered in the side job database 125 is transmitted from the achievement receiving unit 149 to the recruiter device 200. For example, consider a case in which, in the side job database 125 shown in Fig. 7, among multiple recruiters, a first recruiter has recruited for job 001 and a second recruiter has recruited for job 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 hours and actual side job hours displayed on the display 305 of the recruiter device 200.

[0141] When the side job is completed, the recruiter inputs an evaluation of the applicant into 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 processing of steps S17 and S18 executed by the recruiter device 200 and the processing of the evaluation output unit 152 will be described in detail later with reference to FIG.

[0146] [Details of the processing by the offer 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 request 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 business information and disclosure information for the recruitment request into the recruiter device 200 using the operation unit 206, such as a mouse and keyboard.

[0148] The information input 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 content of the business and an operation to input disclosure information that specifies the target to whom the business will be disclosed.

[0149] The business information for 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 subject to disclosure, depending on the employer's choice.

[0150] The recruiter device 200 receives input of the business information and disclosure information of the recruitment request, and executes a process to register 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 using 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 for 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, member database 122, and 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, disclosure level, case title, estimated man-hours, estimated period, case content, and the like in the solicited case database 124 in association with the generated case ID.

[0155] According to this embodiment, the recruiter can freely control the scope of disclosure of the recruitment request at the level of "within his own company," "within the community," or "without restriction." As a result, the recruiter can prevent the recruitment request from being disclosed to a specific company that the recruiter does not intend.

[0156] According to this embodiment, companies that are not to be disclosed 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 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 ID of that member to the sharing server 100. The sharing server 100 may not provide recruitment requests corresponding to a member whose member ID is listed on the non-disclosure member ID list. In this way, the recruiter device 200 may accept either a company or a member as a target for which disclosure of business requests is prohibited.

[0158] Fig. 14 is a diagram for explaining the procedure for searching for recruitment requests from the database 120. The processing of steps S6 and S7 in Fig. 11 and the function of the request extraction unit 145 will be explained in more detail using 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 a 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 jobs that are permitted for viewing by applicants based on the disclosure scope set for the job. In step S1451, the applicant's company and the company's community are determined. In step S1452, jobs that can be disclosed are extracted.

[0162] Step S1453 is a process for extracting jobs that the applicant is allowed 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 company to which the applicant belongs 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 job listings are extracted from job listing database 124 based on the community to which the applicant's company belongs and the disclosure level.

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

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

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

[0170] The total side job time is calculated using 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 work is calculated for each job. Time T2 is calculated based on the estimated man-hours (man-months) and estimated period registered in the job database 124. For example, the estimated man-hours (months) may be used as time T2. For example, for the job corresponding to job ID 001, 5 hours per month may be set as time T2.

[0172] In step S1453C, job offers that satisfy the condition "time T2≦time available for side job T1" are extracted from job offer database 124. Here, the job offer extracted by the processing in step S1453C is referred to as job offer Y.

[0173] [Process to extract projects 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 can be completed within the applicant's side job limit. 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 hours into the applicant device 300, and inputs the actual side job hours into the applicant device 300 at any timing while engaged in the side job. The applicant device 300 accepts the input of the planned side job hours (step S14). The applicant device 300 transmits the accepted planned side job hours and actual side job hours 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 received 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 hours for a side job, the applicant inputs the actual hours for the side job at the end of the month. For this reason, side job database 125 may include cases in which the planned hours for the side job are registered but the actual hours for the side job are not. For example, when an applicant who has received an order for a side job inputs the planned hours for the side job, the planned hours for the side job are registered as data corresponding to that side job, but the actual hours for the side job are not registered.

[0180] Next, the result receiving unit 149 automatically calculates the expected side job time for the current month (step S1512). The result receiving unit 149 calculates the expected side job time based on the planned side job time and the actual side job time. Specifically, as already explained, the "expected side job time" is calculated based on the calculation formula "(man-hour progress rate / progress rate) × planned side job time - actual side job time." Note that the result receiving unit 149 may also calculate the "expected side job time" using the calculation formula "planned side job time - actual side job time." The result receiving unit 149 registers the calculated expected side job time in the side job database 125. As shown in the side job database 125 in FIG. 7, the expected side job time is registered for each project 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 delivery and completion to the recruiter and undergoes inspection by the recruiter. The recruiter then operates the recruiter device 200 to input an evaluation of the applicant into 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 acceptance unit 151 of the sharing server 100. The information transmitted from the recruiter device 200 to the sharing server 100 includes the member ID and evaluation value (0 to 10) of the applicant who is to be evaluated.

[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 ratee are already registered in the evaluation input database 126, the evaluation receiving unit 151 calculates the average value of the evaluation results of the evaluators for the ratee, including the evaluation value received this time. 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 ratee 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. Based on the evaluation information received in step S1513, the company database 121, and the member database 122, 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. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) of a person who has accessed the sharing server 100."

[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 listed. 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 person being evaluated, P7, the ID of the company to which the person being evaluated belongs, 00C, and the ID of the company to which the evaluator belongs, 00A. When a member belonging to the systems 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, the evaluation receiving unit 151 sets the average value of the evaluations of the entire company C, including the evaluations received in step S1513, as the evaluation summary corresponding to "Overall" in the data group 127A. Similarly, the evaluation receiving unit 151 sets the average value of the evaluations of the system part, including the evaluations received in step S1513, as the evaluation summary corresponding to "System part" in the 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 applicant evaluation summary] When the recruiter's device 200 receives an operation to view the applicant's evaluation from the recruiter, 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 selects, from the evaluation summary database 127, an evaluation summary that the recruiter (view requester) has permission to view (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 sent the viewing request, the company database 121, and the member database 122. The "member ID" is an example of "identification information that allows the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) and viewing authority of the 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 the evaluation summary as well as the member ID of the applicant (person being evaluated), information about the company to which the applicant belongs, information about the department to which the applicant belongs, etc. If there are selection targets for the evaluation output unit 152, the transmitted data includes evaluation summaries corresponding to each of multiple applicants (persons being evaluated).

[0195] Upon receiving the evaluation summary, the recruiter device 200 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 using 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 that sent the viewing request.

[0197] [Member search process] When the recruiter device 200 receives a search operation for a person recruiting contractors for a job, it 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] Upon receiving the search request, the member search unit 143 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 uses the company database 121 and the member database 122 to identify the company X to which the recruiter belongs.

[0200] Next, the member search unit 143 extracts from the evaluation summary database 127 members whose evaluation summary value for the identified company X as a whole exceeds a reference value (step S1432). In other words, the member search unit 143 extracts search results by excluding members who have a low evaluation for company X as a whole. 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 who have a low evaluation 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 issued 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 companies have low overall ratings on the display 205. Therefore, when selecting an order recipient from among applicants, the recruiter can save the trouble of visually excluding members whose companies have low overall ratings.

[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] [Viewable range 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] The right to view the evaluation summary calculated from the evaluation of Company A's Systems Department is granted to members (recruiters) of Company A's Systems Department, but not to members (recruiters) other than the Systems Department of Company A. The right to view the evaluation summary calculated from the evaluation of Company A's Planning Department is granted to members (recruiters) of Company A's Planning Department, but not to members (recruiters) other than the Planning Department of Company A.

[0206] The right to view the evaluation summary calculated from the overall evaluation of Company B is granted to all members (recruiters) belonging to Company B. The right to view the evaluation summary calculated from the evaluation of the Planning Department of Company B is granted to members (recruiters) of Company B's Planning Department, but not to members (recruiters) other than those of Company B's Planning Department.

[0207] If the viewers are members (recruiters) of Company X's first division and members (recruiters) of Company X's second division, the viewers' permissions for 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 Company X as a whole, the evaluation summary of Company X's first division, and the evaluation summary of Company X's second division are shared within Company X, but are not made public to members of companies other than Company X. Therefore, for example, even if the work performance of an employee of Company Y who has been contracted to handle recruitment work for Company X is not satisfactory, the recruiter of Company X can evaluate the employee of Company Y using objective criteria 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 motivates the evaluators to make accurate evaluations. As a result, the accuracy of the evaluation summary improves. This makes it possible to use the evaluation summary as useful 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 results excluding members with low ratings are provided to the recruiter (step S1432). In other words, the matching system 1 has a filtering function that provides search results excluding members with low ratings.

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

[0212] A command signal instructing which of filtering using the evaluation summary for the entire company or filtering using the evaluation summary for each department to use 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 to change the evaluation summary used for filtering in response to the command signal.

[0213] [Example of setting the scope of disclosure according to the disclosure level] Figure 19 is a diagram showing an example in which the disclosure range is set according to the disclosure level. Here, as shown in Figure 19, consider a case in which companies A to E form a community relationship, and company F does not form a community relationship with any company. In this case, the disclosure range of the recruitment job 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 "Level 1" to "Level 3" shown in FIG. 19 correspond to the three levels of "Company," "Within Community," and "All" already explained. Therefore, at Level 1, the recruiter's job posting is disclosed only to applicants who belong to the same company as the recruiter's company. At Level 2, the recruiter's job posting is disclosed to applicants who belong to companies that have a community relationship with the recruiter's company, in addition to the scope of Level 1. At Level 3, the recruiter's job posting 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. Of the disclosure levels in this embodiment, "Level 1" corresponds 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 business 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 business information to applicants who do not belong to either the first group or a community group." "Level 3" corresponds to "allowing the disclosure of business information to applicants regardless of the group to which the applicant belongs."

[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 community may be divided into multiple small communities, and whether or not to disclose recruitment services 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, the recruiter of company D may be able to select whether to disclose the scope of his or her recruitment services within 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 a different disclosure range for each solicited case. For example, among the many solicited cases, cases 001 to 003 will be taken as examples to explain a specific example in which a different disclosure range is set for each solicited case.

[0217] For example, the disclosure scope of job 001 may be limited to only companies A and C that belong to the community identified by community ID=03. Alternatively, the disclosure scope of job 002 may be limited to only companies C, D, and C that belong to the community identified by community ID=02. Alternatively, the disclosure scope of job 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] Company A may form a community separate from the community identified by community ID=01 or 02. For example, as shown by the dashed line in FIG. 19, company A may form a community identified by community ID=Z with company Z. For example, if a recruiter belongs to company A, the recruiter's job postings may be disclosed to applicants belonging to company A and applicants belonging to company Z. This level of disclosure may be adopted as a variation of "Level 3" as shown in FIG. 19.

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

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

[0221] In this example, 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, etc. with keyboard 306A or mouse 306B. This allows the manager to 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.

[0222] In this 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 a single "group." A "company group" may also be formed by multiple companies.

[0223] In this embodiment, a "company forming a community relationship" is an example of a "community group."

[0224] In this embodiment, the information of "non-disclosure targets" included in the disclosure information is an example of "information that can identify targets to whom disclosure of business information is prohibited."

[0225] The communication (S9 in FIG. 11) for transmitting approval information from the applicant device 300 of the manager functioning as the 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 that includes the identification information of the approver of the first applicant."

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

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

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

[0229] 18 illustrates a systems department and a planning department as examples of departments of company A. In this embodiment, "one of the systems 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.

[0230] Based on the estimated man-hours registered in the job posting database 124, the side job limit hours registered in the company database 121, the actual side job hours registered in the side job database 125, and the expected side job hours registered in the side job database 125, the sharing server 100 extracts from the list of job postings database 124 job information for which the applicant's working hours do not exceed the upper limit hours. Specifically, for example, if the applicant is engaged in multiple side jobs, the sharing server 100 calculates the sum of the actual side job hours for each side job to determine the total actual side job hours, and the sum of the expected side job hours for each side job to determine the total expected side job hours. The sharing server 100 adds the calculated total actual side job hours and the calculated total expected side job hours to determine 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 job postings 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 complete each job posting based on the estimated man-hours in the job posting database 124, and searches for job postings that fall within the range of available side job 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 "actual side job time" is an example of "actual time that is the actual time the applicant has already worked," and the "expected side job time" is an example of "expected time that is expected to be the applicant's working hours." The upper limit time may be not only for the side job, but also for the total time set for the main job and side job. The first upper limit time may not be the side job upper limit time, but may also be the upper limit time for all work, including the main job and side job. The first actual time and first expected time may not only be for the side job time, but also for the total time for all work, including the side job and main job.

[0231] 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 VDI (Virtual Desktop Infrastructure). A thin client system using 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, applicant device 300, and sharing server 100 do not necessarily have to be independent devices. When using a thin client system such as the one described above, the functions of the recruiter device 200, applicant device 300, and sharing server 100 can be provided on the same aggregation server.

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

[0233] The sharing server 100 is an example of a computing device. A computing device may be configured using a server (such as an on-premise server or a cloud server) or a serverless system. Here, an on-premise server is a server installed and managed in facilities managed within a company. A cloud server is a server (a rented server) provided by another business 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.

[0234] <Variation 1> Next, Modification 1 will be described with reference to Figures 21 to 23. In Modification 1, a counter offer function will be described that allows a recruiter to encourage selected members from a large number of members to recruit for the recruiting business.

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

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

[0237] 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 that are rivals to the recruiter's company is excluded from the search results. Variation 1 will be explained in detail below using the drawings.

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

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

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

[0241] The recruiter device 200 receives member information (search results) from the member search unit 143 and displays the member information as search results on the display 205 (step S22). Thereafter, the recruiter device 200 accepts an operation by the recruiter to select an applicant from the search results. That is, the recruiter selects a member to whom to make a counter offer based on the search results and makes the 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.

[0242] 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 about the recruitment job 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 encouraging an applicant to apply." The member who is the target of the counter offer decides whether 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 the application information to the counter offer approval request unit 162.

[0243] The counter offer approval request unit 162 sends the subordinate's application information to the applicant's superior. The counter offer approval request unit 162 identifies the member ID of the applicant's 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 or her own applicant device 300 and approves the application (step S25).

[0244] The counter offer request acceptance notifying unit 163 receives approval information from the applicant's superior. The counter offer request acceptance notifying unit 163 accepts the applicant's application on the condition that it has received the approval information. 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 this 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.

[0245] 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 added profile information and profile disclosure information indicating whether or not the profile is to be made public.

[0246] 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. Members register various pieces of their own profile information in the member database 122A using the applicant device 300. The profile information includes, for example, the member's Synthetic Personality Inventory (SPI) information, the member's work history, the member's achievements, the member's qualifications, and the like.

[0247] Members set their profile public information using the applicant device 300. The profile information of members whose profile public information is set to "allowed" is provided to searchers. The profile information of members whose profile public information is set to "disallowed" 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 from each of multiple members of information indicating whether or not they permit their profile information to be included in search results.

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

[0249] 23 is a flowchart showing the processing steps of the counter offer member search processing according to Modification 1. The processing based on this flowchart is executed by the sharing server 100.

[0250] First, the sharing server 100 receives a search request from 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 uses his / her own recruiter device 200 to search for members who have skills suitable for the recruitment request. The recruiter's search request is received by the sharing server 100 in step S211. The search request may include the searcher's member ID and the request ID of the recruitment request.

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

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

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

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

[0255] 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 whose profile information has not been disclosed, only the member's ID and name are displayed, and no profile information is displayed.

[0256] As explained above, according to the first modification, a recruiter can refer to detailed member profile information to 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 rivals to the recruiter's company or community are excluded from the members displayed as search results. This prevents the recruiter from placing an order with members from such rival companies. Furthermore, because 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.

[0257] In addition to the profile information, members may be able to set whether or not to make their name public. Also, several categories of profile information may be provided, and members may be able to set whether or not to make their profile information public for each category.

[0258] By adding the offer function described above to the matching system 1, recruiters can check the profile information of members who are permitted to view the job postings. Furthermore, recruiters can encourage applications from members with whom they wish to place orders. Members who are encouraged to apply by recruiters can view job 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 recruiters to actively select recipients of offers and quickly put the most suitable applicants to work.

[0259] <Variation 2> Next, Modification 2 will be described with reference to Figures 24 to 28. In Modification 2, a member group application function will be described, which allows a plurality of members to apply for a recruitment operation as a group.

[0260] [Background for proposing the member group application feature] In crowdsourcing, typically, the recruiter discloses information about the job they are looking for, and individuals who are interested in the job apply for it. However, there are many jobs that require or are best handled by a team of multiple people, such as comprehensive tasks ranging from business planning to acquiring intellectual property rights related to the project. For this reason, if the number of people recruited is limited to one, it is difficult for the person seeking the order to take on more work than they can handle individually.

[0261] In view of this background, Modification 2 provides a member group application function that allows multiple members to apply for recruitment services as a group. Modification 2 will be described in detail below.

[0262] 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. Compared to the block diagram shown in Fig. 2, the block diagram shown in Fig. 24 adds a member group database 128. The recruiting request database 124A shown in Fig. 24 adds a function to the recruiting request database 124 shown in Fig. 6 that enables registration of recruiting requests that allow applications from member groups.

[0263] Member groups consisting of multiple members are registered in member group database 128. Using recruiter device 200, recruiters can register recruitment jobs that allow applications by member groups in recruitment job database 124A. Using applicant device 300, applicants can apply for recruitment jobs that allow applications by member groups using a member group registered in member group database 128.

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

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

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

[0267] Member group G2 is made up 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 to company B. As can be seen by comparing member group G1 and member group G2, member ID P1 is registered in both member groups G1 and G2. Therefore, member P1 belongs to two member groups.

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

[0269] As shown in FIG. 24, the member group database 128 is stored in the storage 103 of the sharing server 100. A member forms a member group with the consent of other members they have met through the same company or community, and registers the member group in the member group database 128. A "member group" is an example of an "application group."

[0270] Fig. 26 is a diagram showing an example of the recruitment request database 124A related to Modification 2. Compared to the recruitment request database 124 shown in Fig. 6, the recruitment request database 124A shown in Fig. 26 has added information on the recruitment type. The recruiter operates the recruiter device 200 to set the recruitment type. The sharing server 100 associates the recruitment type based on the setting with the business information and registers it in the recruitment request database 124A.

[0271] Recruiters can select the recruitment type from group and individual. If the recruiter does not select a recruitment type, the recruitment type of the job is considered to be not limited to either group or individual. Jobs with a recruitment type set to group can only be accepted by member groups. Jobs with a recruitment type set to individual can only be accepted by individual members. Jobs 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 that should be applied for jointly by multiple recruiters."

[0272] Fig. 27 is a diagram for explaining the functions of the sharing server 100, recruiter device 200, and applicant device 300 according to Modification 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 group application step S8A is adopted instead of application step S8.

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

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

[0275] Display 305 displays the disclosure level, project title, estimated man-hours, estimated period, project content, and recruitment type for each solicited project. 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 project for which the recruitment type is set to "group" or "unlimited." Based on the applicant's operation, applicant device 300 accepts the member group and the project for which the applicant wishes to apply (step S7A). Applicant device 300 transmits the group ID of the accepted member group and the project ID of the accepted project to sharing server 100. Determination unit 145A of sharing server 100 acquires the group ID and project ID.

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

[0277] 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-disclosed company ID, disclosure level, and solicitation type registered in correspondence with the acquired job ID.

[0278] Based on the information identified as described 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.

[0279] For example, if one of the members in the member group belongs to a company that is listed on the non-disclosure company ID list corresponding to the job posting, the determination unit 145A will 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 though the disclosure level of the job posting is "within the community," the determination unit 145A will not allow the member group to apply.

[0280] The determination unit 145A returns the determination result to the applicant device 300. FIG. 27 shows the flow when the determination unit 145A permits the application by the member group. When the determination unit 145A permits the application by the member group, 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.

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

[0282] 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. Having accepted the 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 decision on whether to hire or reject the applicant to the recruiter device 200. The recruiter device 200 accepts the input result (step S11) and transmits the accepted result of hire or rejection to the notification unit 148 of the sharing server 100.

[0283] The notification unit 148 transmits the application result (result of whether the applicant was hired or not) to the applicant's applicant device 300 and the applicant's superior (manager's) applicant device 300. However, the notification unit 148 transmits the application result to the superior of each member belonging to the member group.

[0284] The applicant device 300 of the applicant and the applicant 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.

[0285] 28 is a diagram for explaining the procedure for registering a recruitment request related to Modification 2 in the recruitment request database 124A. In FIG. 28, compared to FIG. 13, a recruitment type is added to the business information input to the recruiter device 200.

[0286] In the second modification, when a recruiter who registers a recruitment request inputs 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 thereof will not be repeated here.

[0287] 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 approve an application from a member group is determined based on the relationship between the company and community to which the recruiter belongs and the companies and communities to which each member of the member group belongs. This prevents 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.

[0288] By adding the member group application function described above to the matching system 1, it is possible to provide a system in which the order-receiving party 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.

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

[0290] The system configuration shown in FIG. 29 is common to companies A, B, C, D, etc. Each company is provided with a user device 500, a database 520, and a storage 503 for storing the database. When a member operates the user device 500 as a recruiter, the user device 500 functions as a recruiter device 200. When a member operates the user device 500 as an applicant, the user device 500 functions as an applicant device 300. Hereinafter, a member may be referred to as a "user."

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

[0292] Database 520 has the functions of database 120 shown in Fig. 2, and includes a job posting database 524 that replaces job posting database 124, as well as various other databases. Job postings proposed by employees of company A as recruiters are registered in company A's job posting database 524. Job postings proposed by employees of company B as recruiters are registered in company B's job posting database 524. Similarly, job postings proposed by employees of each company as recruiters are registered in other companies' job posting databases 524.

[0293] Database 520 has disclosure permission list 521 registered therein. Disclosure permission list 521 includes a list of groups (companies, communities, etc.) that are permitted to disclose job postings. Disclosure permission list 521 includes information corresponding to the "non-disclosure company ID list" and "disclosure level" among the information registered in job posting database 124 shown in FIG. 6. User device 500 registers job postings (business information) and disclosure permission list 521 (disclosure information) that indicates the disclosure range of the job postings in database 520.

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

[0295] Like the user device 500 of company A, the user device 500 of each of companies B, C, D, etc. operates based on the disclosure permission list 521. In this way, the user device 500 determines, from among the recruitment requests registered in the database 520, which recruitment requests are permitted to be disclosed to the applicant based on the disclosure permission list 521, and provides the applicant device 300 with the recruitment requests that are permitted to be disclosed to the applicant.

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

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

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

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

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

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

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

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

[0304] Thereafter, authentication system 510A transmits to authentication system 510C, from among the job listings registered in job listing database 524, those for which disclosure to company C is permitted by disclosure permission list 521. This allows company A to allow applicants from company C to view its job listings. Note that instead of each company storing its own disclosure permission list 521, the authentication system 110 may store the disclosure permission list 521 for all companies. In this case, authentication system 110 has a function to determine the viewing authority for job listings.

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

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

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

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

[0309] According to this embodiment, the details of the work ordered by an employee can be confirmed by the manager of the company to which the employee belongs, thereby preventing the leakage of confidential information. Furthermore, according to this embodiment, the company that receives the order can understand the time that the employee spends on their main job and the time that the employee spends on their side job. This allows the company that receives the order to manage the health of their employees.

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

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

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

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

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

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

[0316] The sharing server 100 registers a plurality of pieces of profile information for each of a plurality of registrants (members) in the database 120 (see FIG. 22). The sharing server 100 accepts 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 search results (the setting operation for whether to permit disclosure is accepted for each type of profile information). The sharing server 100 accepts input of solicitation form information (the solicitation form shown in FIG. 28) that can identify whether the work for which contractors are being recruited is a group work that can be accepted when multiple applicants apply jointly, or a work that can be accepted for an application by a single applicant. The sharing server 100 associates the solicitation form information with the work information and registers it in the database 120 (step S1442).

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

[0318] [Aspect] Aspects of the present disclosure are listed below.

[0319] (Item 1) The matching system described in item 1 is a matching system that matches applicants with recruiters who are seeking contractors for a job, and includes a first applicant device operated by the first applicant, and a computing device that communicates with the first applicant device and can access a database, the computing device registers in the database business information for which contractors are sought and disclosure information indicating the scope of disclosure of the business information, and the computing device determines, based on the disclosure information, which business information is permitted to be disclosed to the first applicant from the business information registered in the database, and provides the business information that is permitted to be disclosed to the first applicant to the first applicant device.

[0320] (Section 2) The matching system described in Section 2 is the matching system described in Section 1, further comprising a recruiter device operated by the recruiter, and the recruiter device transmits business information and disclosure information to the computing device.

[0321] (Item 3) The matching system described in item 3 is the matching system described in item 1, wherein the computing device includes a recruiter device operated by a recruiter.

[0322] (4) The matching system described in paragraph 4 is a matching system described in any one of paragraphs 1 to 3, further comprising a second applicant device operated by a second applicant different from the first applicant, and the computing device determines, based on the disclosure information, business information registered in the database that is permitted to be disclosed to the second applicant, and provides the business information that is permitted to be disclosed to the second applicant to the second applicant device.

[0323] (Item 5) The matching system described in item 5 is the matching system described in item 4, further comprising a third applicant device operated by a third applicant different from the first applicant and the second applicant, wherein multiple disclosure levels are set for the disclosure information, and the computing device determines whether or not to allow disclosure for each of the first to third applicants depending on the disclosure level.

[0324] (Section 6) The matching system described in Section 6 is the matching system described in Section 5, wherein the first applicant belongs to a first group and the second applicant belongs to a second group different from the first group, the multiple disclosure levels include a first level and a second level, the first level corresponds to allowing disclosure of business information to the first applicant and prohibiting disclosure of business information to applicants who do not belong to the first group, and the second level corresponds to allowing disclosure of business 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 disclosure of business information to applicants who do not belong to either the first group or the community group.

[0325] (Section 7) The matching system described in Section 7 is the matching system described in Section 5, wherein the first applicant belongs to a first group and the second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level, a second level, and a third level, the first level corresponding to allowing disclosure of business information to the first applicant and prohibiting disclosure of business information to applicants who do not belong to the first group, the second level corresponding to allowing disclosure of business 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 the third level corresponding to allowing disclosure of business information to applicants who belong to a specific community group that is different from the first group and the second-level community group that has formed a community relationship with the first group, and prohibiting disclosure of business information to applicants who do not belong to either the first group or the specific community group.

[0326] (Section 8) The matching system described in Section 8 is the matching system described in Section 6, wherein the multiple disclosure levels include a disclosure level corresponding to allowing disclosure of business information to applicants regardless of the group to which the applicant belongs.

[0327] (Item 9) The matching system described in item 9 is a matching system described in any one of items 6 to 8, in which attribute data that can identify a community group is registered in the database, and the computing device identifies applicants who are permitted to disclose their business information based on the disclosure information and the attribute data.

[0328] (Clause 10) The matching system described in clause 10 is a matching system described in any one of clauses 5 to 7, in which the recruiter device accepts an operation to input a target group to which disclosure of business information is prohibited, and transmits information that can identify the accepted target group to the computing device, and the computing device prohibits disclosure of business information to applicants belonging to the target group even if the disclosure level is a level that allows disclosure of business information to the target group.

[0329] (Clause 11) The matching system described in clause 11 is a matching system described in any one of clauses 4 to 10, in which the first applicant belongs to a first company and the second applicant belongs to a second company different from the first company.

[0330] (Section 12) The matching system described in Section 12 is the matching system described in Section 2, in which the computing device receives a request from a recruiter device to search for information on multiple registrants registered in a database, provides search results based on the received request to the recruiter device, the recruiter device receives an operation from the recruiter to select an applicant recommender who is recommended to apply as an applicant from the search results, transmits identification information of the selected applicant recommender to the computing device, and the computing device transmits information to the applicant device of the selected applicant recommender encouraging them to apply.

[0331] (Item 13) The matching system described in Item 13 is the matching system described in Item 12, in which a computing device registers multiple pieces of profile information for each of multiple registered individuals in a database, and the computing device accepts input from each of the multiple registered individuals to set the range of the multiple pieces of profile information to be made public as search results.

[0332] (Item 14) The matching system described in item 14 is a matching system described in any one of items 1 to 13, in which the recruiter device transmits recruitment type information to the computing device that can identify whether the job for which contractors are being recruited is a group job that can be accepted when multiple applicants apply jointly, or a job that can be accepted for an application by a single applicant, and the computing device registers the recruitment type information in the database in association with the job information.

[0333] (Item 15) The matching system described in Item 15 is the matching system described in Item 14, in which the computing device registers an application group consisting of multiple applicants in a database, and the computing device is capable of accepting applications from the application group regarding business information that is permitted to be disclosed to all applicants belonging to the application group.

[0334] (Clause 16) The recruiter device described in clause 16 is a recruiter device operated by a recruiter, which communicates with a computing device that matches recruiters who are recruiting contractors with applicants, and is equipped with an interface that accepts operations to input business information and disclosure information that indicates the scope of disclosure of the business information, and a processor that transmits the business information and disclosure information accepted by the interface to the computing device, and the disclosure information includes information that instructs the computing device to allow disclosure of business information to a first applicant and to prohibit disclosure of business information to a second applicant different from the first applicant.

[0335] (Item 17) The method described in item 17 is a method for matching applicants with a recruiter seeking contractors for a job, and includes the steps of communicating with a first applicant device operated by the first applicant, registering in a database business information for which contractors are sought and disclosure information indicating the scope of disclosure of the business information, and determining, based on the disclosure information, which business information is permitted to be disclosed to the first applicant from the business information registered in the database, and providing the business information permitted to be disclosed to the first applicant to the first applicant device.

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

[0337] 1 Matching system, 50 Internet, 100 Sharing server, 101 Processor, 102 Memory, 103, 503 Storage, 104 Communication interface, 120, 520 Database (DB), 121 Company database (Company DB), 122, 122A Member database (Member DB), 123 Community database (Community DB), 124, 124A, 524 Recruitment job database (Recruitment job 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 Job registration unit, 145 Job extraction unit, 145A Member group information acquisition unit, 146 Application unit, 147 Approval unit, 148 Notification unit, 149 Performance reception unit, 150 Performance output unit, 151 Evaluation reception unit, 152 Evaluation output unit, 161 Counteroffer request unit, 162 Counteroffer approval request unit, 163 Counteroffer request acceptance notification unit, 200, 200A, 200B, 200C Recruiter device, 201 Processor, 202 Memory, 203 Communication interface, 204 Input / output interface, 205 Display, 206 Operation unit, 206A Keyboard, 206B Mouse, 207 Screen, 300, 300A, 300B, 300C Applicant device, 301 Processor, 302 Memory, 303 Communication interface, 304 Input / output interface, 305 Display, 306 Operation unit, 306A Keyboard, 306B Mouse, 307A-307C Tab, 401, 402 Table, 500 User device, 521 Disclosure permission list.

Claims

1. A matching system that matches a recruiter who is looking for a contractor for a job with an applicant, a first applicant device operated by a first applicant; a computing device in communication with the first applicant device and capable of accessing a database; The computing device registers business information for soliciting contractors and disclosure information indicating the scope of disclosure of the business information in the database; A matching system in which the computing device determines, based on the disclosure information, business information that is permitted to be disclosed to the first applicant from the business information registered in the database, and provides the business information that is permitted to be disclosed to the first applicant to the first applicant device.

2. further comprising a recruiter device operated by a recruiter; The matching system according to claim 1 , wherein the recruiter device transmits the business information and the disclosure information to a computing device.

3. The matching system of claim 1 , wherein the computing device comprises a recruiter device operated by a recruiter.

4. a second applicant device operated by a second applicant different from the first applicant; A matching system as described in any one of claims 1 to 3, wherein the computing device determines, based on the disclosure information, business information that is permitted to be disclosed to the second applicant from the business information registered in the database, and provides the business information that is permitted to be disclosed to the second applicant to the second applicant device.

5. the matching system further comprises a third applicant device operated by a third applicant different from the first applicant and the second applicant; A plurality of disclosure levels are set for the disclosure information, The matching system according to claim 4 , wherein the computing device determines whether or not to permit disclosure for each of the first to third applicants according to the disclosure level.

6. The first applicant belongs to a first group, and the second applicant belongs to a second group different from the first group; the plurality of disclosure levels includes a first level and a second level; the first level corresponds to permitting disclosure of the business information to the first applicant and prohibiting disclosure of the business information to applicants not belonging to the first group; The matching system of claim 5, wherein the second level corresponds to allowing disclosure of the business 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 disclosure of the business information to applicants who do not belong to either the first group or the community group.

7. The first applicant belongs to a first group, and the second applicant belongs to a second group different from the first group; the plurality of disclosure levels includes a first level, a second level, and a third level; the first level corresponds to permitting disclosure of the business information to the first applicant and prohibiting disclosure of the business information to applicants not belonging to the first group; The second level allows disclosure of the business information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group; The matching system of claim 5, wherein the third level corresponds to allowing disclosure of the business information to applicants who belong to a specific community group other than the first group and the second-level community group that has formed a community relationship with the first group, and prohibiting disclosure of the business information to applicants who do not belong to either the first group or the specific community group.

8. The matching system according to claim 6 , wherein the plurality of disclosure levels includes a disclosure level corresponding to allowing disclosure of the business information to an applicant regardless of the group to which the applicant belongs.

9. The database has registered therein attribute data that can identify the community group, The matching system according to any one of claims 6 to 8, wherein the computing device identifies applicants who are permitted to disclose their business information based on the disclosure information and the attribute data.

10. A matching system as described in any one of claims 5 to 7, wherein when the computing device receives input of a target group to which disclosure of the business information is prohibited, it prohibits disclosure of the business information to applicants belonging to the target group, even if the disclosure level is a level that allows disclosure of the business information to the target group.

11. The matching system according to any one of claims 4 to 10, wherein the first applicant belongs to a first company, and the second applicant belongs to a second company different from the first company.

12. The computing device receives a request from the recruiter device to search for information on a plurality of registrants registered in the database, and provides the recruiter device with a search result based on the received request; The recruiter device accepts an operation by the recruiter to select a recommended applicant who is recommended to apply as an applicant from the search results, and transmits identification information of the selected recommended applicant to the computing device; The matching system according to claim 2 , wherein the computing device transmits information encouraging the applicant to apply to the applicant device of the selected applicant recommended.

13. The computing device registers a plurality of pieces of profile information of each of the plurality of registrants in the database; The matching system according to claim 12 , wherein the computing device receives an input from each of the plurality of registrants to set a range of the plurality of profile information to be made public as the search result.

14. The matching system of any one of claims 1 to 13, wherein when the computing device receives input of recruitment type information that can identify whether the job for which the contractor is being recruited is a group job that can be accepted when multiple applicants apply jointly, or a job that can be accepted for an application by a single applicant, the computing device associates the recruitment type information with the job information and registers it in the database.

15. The computing device registers an application group consisting of a plurality of applicants in the database; The matching system of claim 14 , wherein the computing device is capable of accepting applications from the application group regarding business information that is permitted to be disclosed to all applicants belonging to the application group.

16. a recruiter device that communicates with a computing device that matches recruiters who are recruiting contractors with applicants and is operated by a recruiter, an interface that accepts an operation to input business information and disclosure information indicating the disclosure range of the business information; a processor that transmits the business information and the disclosure information received by the interface to the computing device; The disclosure information includes information instructing the computing device to allow disclosure of the business information to a first applicant and to prohibit disclosure of the business information to a second applicant different from the first applicant, on a recruiter device.

17. A method for matching a recruiter who is seeking contractors for a job with an applicant, comprising: communicating with a first applicant device operated by a first applicant; A step of registering business information for which contractors are being recruited and disclosure information indicating the disclosure range of the business information in a database; A method comprising a step of determining, from among the business information registered in the database, business information that is permitted to be disclosed to the first applicant based on the disclosure information, and providing the business information that is permitted to be disclosed to the first applicant to the first applicant device.

Images