A task management system based on flexible employment and management method thereof
By distinguishing between ordinary tasks and fast tasks in a flexible employment system and providing multiple winning bid and settlement modes, the problem that existing systems are difficult to compatible with different needs is solved, and the interaction efficiency and work efficiency between enterprises and individuals are improved.
Patent Information
- Application Number
- CN202210654000.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-10
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing flexible employment system is difficult to compatible with different types of business needs and settlement methods, and cannot meet the personalized needs of enterprises and individuals.
A task management system based on flexible employment is designed. By distinguishing between ordinary tasks and fast tasks, it provides manual and automatic winning methods, supports prepayment, completion of checkout, bargainable mode and piece-based mode, and realizes the review of task content and delivery results and Settlement.
It improves the interaction efficiency between enterprises and individuals, meets the needs of different task scales and business types, saves the company's manpower and material resources, and achieves a balance between general tasks and personalized needs, which is in line with the characteristics of flexible employment.
Smart Images

Figure CN114936792B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of enterprise employment, and in particular to a task management system based on flexible employment and a management method thereof. Background Art
[0002] At present, with the changes in employment forms and people's demand for personalized employment, the advantages of flexible employment are highlighted. It not only meets the needs of enterprises to save costs, but also meets the needs of individuals who are not convenient for full-time employment or want flexible employment. It is in line with the current social and economic situation and has been continuously developed and supported.
[0003] However, the needs of enterprises and individuals using flexible employment are also relatively flexible. The same enterprise may have different types of businesses, and each business requires different types of individuals. This also involves issues such as how to settle accounts. How to reconcile these needs has become a big problem. The single model of issuing tasks, receiving tasks, handing in tasks, and settling accounts can no longer meet the needs.
[0004] Therefore, there is an urgent need for a solution that can meet both general tasks and personalized needs. Summary of the invention
[0005] The purpose of the embodiments of the present invention is to provide a task management system based on flexible employment and a management method thereof, so as to meet both general tasks and personalized needs to fit the characteristics of flexible employment.
[0006] To achieve the above objectives, in a first aspect, an embodiment of the present invention provides a task management system based on flexible employment, the system comprising a service platform and a user terminal;
[0007] The user terminal is used for:
[0008] When logging in, select the required user role; wherein, the user roles include enterprise users and individual users, and different user roles correspond to different system functions and system pages;
[0009] When the user role is an enterprise user, the enterprise task is published on the corresponding system page; the types of enterprise tasks include ordinary tasks and fast tasks, and different task types correspond to their own task content and personal commissions. The ordinary tasks include prepayment, checkout completion, negotiable mode and piecework mode;
[0010] According to different task types, the corresponding bidding method is called to obtain the bidding information; wherein the bidding information is associated with the information of the contractor, and the bidding methods include manual bidding registration and automatic bidding;
[0011] Receive deliverables uploaded by individual users;
[0012] The enterprise task type, winning bid information and received deliverables are transmitted to the service platform for review; wherein, in the case of ordinary tasks, the enterprise user performs acceptance operation on the deliverables uploaded by the individual user on its corresponding system page;
[0013] The service platform is used for:
[0014] Conduct an audit based on the content of the task;
[0015] Conducting review based on the information of the undertaker;
[0016] Conduct reviews based on the stated deliverables;
[0017] If the review is passed, the individual user will be sent a confirmation message or the enterprise user will be triggered to directly conduct enterprise acceptance;
[0018] Pay commissions based on the acceptance operations or settlement requests generated;
[0019] When the user role is an individual user, the user can view tasks, register, win bids, upload task deliverables and collect payments on the corresponding system page; in the case of express tasks, the user is also required to sign a personal commitment letter and confirm the task information; the confirmation of task information includes viewing the received information to be confirmed, determining whether the user has participated in the completion and whether to confirm the task;
[0020] After confirming the task, the task is reconfirmed based on the operational feedback. If the confirmation is passed again, the settlement request is generated and the payment is collected; wherein, the reconfirmation includes confirming whether the individual has been authenticated, signing the agreement and setting the payment method.
[0021] Preferably, when the user role is an enterprise user, it is also used for enterprise authentication, agreement signing and enterprise recharge.
[0022] Preferably, for ordinary tasks, the corresponding bidding method is manual bidding, including self-registration and enterprise invitation. If it is self-registration, the bid will be won after the enterprise's review and approval; if it is an enterprise invitation, the individual will automatically win the bid;
[0023] For extremely fast tasks, the corresponding bidding method is automatic bidding.
[0024] Preferably, for ordinary tasks, individual users need to manually upload the task deliverables;
[0025] For express tasks, enterprise users need to manually upload or batch upload the information of the task assignee and the received task delivery results.
[0026] Preferably, before issuing a task, the speed task also determines the balance in the enterprise user account. If the balance meets the requirement, the task is successfully issued and the payment is made.
[0027] When the ordinary task is released, no balance check is performed, but there must be sufficient balance in the account before the enterprise pays.
[0028] In a second aspect, an embodiment of the present application further provides a task management method based on flexible employment, which is applied to a task management system based on flexible employment described in the first aspect, and the method includes:
[0029] When logging in through the user terminal, select the required user role; wherein the user roles include enterprise users and individual users, and different user roles correspond to different system functions and system pages;
[0030] Utilize enterprise users to publish enterprise tasks on their corresponding system pages; the types of enterprise tasks include ordinary tasks and fast tasks, and ordinary tasks include prepayment, checkout completion, negotiable mode and piecework mode;
[0031] According to different task types, the corresponding bidding method is called to obtain the bidding information; wherein the bidding information is associated with the information of the contractor, and the bidding methods include manual bidding registration and automatic bidding;
[0032] Receive deliverables uploaded by individual users;
[0033] The enterprise task type, winning bid information and received deliverables are transmitted to the service platform for review; in the case of ordinary tasks, the enterprise user performs acceptance operations on the deliverables uploaded by the individual user on its corresponding system page;
[0034] Through the service platform, the content of the task, the information of the undertaker and the deliverables are reviewed respectively;
[0035] If the review is passed and it is a normal task, the enterprise user will be triggered to directly conduct enterprise acceptance;
[0036] If the review is passed and it is a high-speed task, a confirmation message will be sent to the individual user;
[0037] and make commission payments based on said acceptance operations or resulting settlement requests;
[0038] Then, individual users can view tasks, sign up, win bids, upload task deliverables and collect payments on their corresponding system pages; in the case of express tasks, they are also required to sign a personal commitment letter and confirm the task information; the confirmation of task information includes viewing the received information to be confirmed, determining whether the individual has participated in the completion and whether to confirm the task;
[0039] After confirming the task, the task is reconfirmed based on the operational feedback. If the confirmation is passed again, the settlement request is generated and the payment is collected; wherein the reconfirmation includes confirming whether the individual has been authenticated, signing the agreement and setting the payment method.
[0040] Preferably, the method further comprises:
[0041] When the user role is an enterprise user, enterprise authentication, agreement signing and enterprise recharge are also performed.
[0042] Preferably, for ordinary tasks, the corresponding bidding method is manual bidding, including self-registration and enterprise invitation. If it is self-registration, the bid will be won after the enterprise's review and approval; if it is an enterprise invitation, the individual will automatically win the bid;
[0043] For extremely fast tasks, the corresponding bidding method is automatic bidding.
[0044] Preferably, for ordinary tasks, individual users need to manually upload the task deliverables;
[0045] For express tasks, enterprise users need to manually upload or batch upload the information of the task assignee and the received task delivery results.
[0046] Preferably, the extreme speed task also determines the balance in the enterprise user account before issuing the task. If the balance meets the requirement, the task is successfully issued and the payment is made.
[0047] When the ordinary task is released, no balance check is performed, but there must be sufficient balance in the account before the enterprise pays.
[0048] By implementing the embodiment of the present invention, the needs of enterprises under different task scales are met through the division of ordinary tasks and extreme-speed tasks. Enterprises can flexibly choose, meet the needs of different types of business of enterprises, and improve the adaptability of enterprise business;
[0049] Ordinary tasks include many different types, meeting the needs of freelancers in different flexible employment scenarios, greatly improving the efficiency of interaction between enterprises and individuals, and achieving both general tasks and personalized needs.
[0050] At the same time, extremely fast tasks can meet the needs of a large number of task undertakers. Individuals can automatically win bids and successfully deliver work, eliminating the tedious operations of manual registration and uploading task delivery results. It is in line with the fast work pace of flexible employment individuals, and greatly saves the company's manpower and material resources, improving the company's work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] In order to more clearly illustrate the specific implementation of the present invention or the technical solution in the prior art, the drawings required for use in the specific implementation or the description of the prior art are briefly introduced below.
[0052] Figure 1 It is a structural diagram of a task management system based on flexible employment provided by an embodiment of the present invention;
[0053] Figure 2 This is a schematic diagram of the interaction of the system when performing a common task provided by an embodiment of the present invention;
[0054] Figure 3 This is a schematic diagram of the interaction between an enterprise user, a service platform and an individual user during an extreme speed task provided by an embodiment of the present invention;
[0055] Figure 4 It is a flowchart of a task management method based on flexible employment provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0056] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0057] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.
[0058] Please refer to Figures 1 to 3 , is a task management system based on flexible employment provided by the first embodiment of the present invention, the task management system includes a service platform and a user terminal;
[0059] The user terminal is used for:
[0060] When logging in, select the required user role; wherein, the user roles include enterprise users and individual users, and different user roles correspond to different system functions and system pages;
[0061] When the user role is an enterprise user, the enterprise task is published on the corresponding system page; the types of enterprise tasks include ordinary tasks and fast tasks, and different task types correspond to their own task content and personal commissions. The ordinary tasks include prepayment, checkout completion, negotiable mode and piecework mode;
[0062] According to different task types, the corresponding bidding method is called to obtain the bidding information; wherein the bidding information is associated with the information of the contractor, and the bidding methods include manual bidding registration and automatic bidding;
[0063] Receive deliverables uploaded by individual users;
[0064] The enterprise task type, winning bid information and received deliverables are transmitted to the service platform for review; wherein, in the case of ordinary tasks, the enterprise user performs acceptance operation on the deliverables uploaded by the individual user on its corresponding system page;
[0065] The service platform is used for:
[0066] Conduct an audit based on the content of the task;
[0067] Conducting review based on the information of the undertaker;
[0068] Conduct reviews based on the stated deliverables;
[0069] If the review is passed, the individual user will be sent a confirmation message or the enterprise user will be triggered to directly conduct enterprise acceptance; specifically, it includes:
[0070] If the review is passed and it is a normal task, the enterprise user will be triggered to directly conduct enterprise acceptance;
[0071] If the review is passed and it is an extremely fast task, a confirmation message will be sent to the individual user.
[0072] Pay commissions based on the acceptance operations or settlement requests generated;
[0073] When the user role is an individual user, the user can view tasks, register, win bids, upload task deliverables and collect payments on the corresponding system page; in the case of express tasks, the user is also required to sign a personal commitment letter and confirm the task information; the confirmation of task information includes viewing the received information to be confirmed, determining whether the user has participated in the completion and whether to confirm the task;
[0074] After confirming the task, the task is reconfirmed based on the operational feedback. If the confirmation is passed again, the settlement request is generated and the payment is collected; wherein, the reconfirmation includes confirming whether the individual has been authenticated, signing the agreement and setting the payment method.
[0075] In this embodiment, tasks are divided into two categories: ordinary tasks and fast tasks. In this embodiment, individuals, individual users, freelancers, and task undertakers all have the same meaning.
[0076] Reference Figure 2For ordinary tasks, the corresponding bidding method is manual bidding, including self-registration and company invitation. If it is self-registration, the bid will be won after the company's review and approval; if it is a company invitation, the individual will automatically win the bid;
[0077] For extremely fast tasks, the corresponding bidding method is automatic bidding.
[0078] During implementation, priority will be given to determining whether there is an enterprise invitation, that is, whether the enterprise has invited the individual; if not, the individual needs to register on his own. If the enterprise passes the review, the individual will win the bid; otherwise, if the enterprise fails the review, the individual's registration will fail;
[0079] Then, after the individual delivers the results, they will be reviewed through the service platform. The review content includes the task content, the information of the undertaker and the information of the delivered results, etc.
[0080] If the review is passed, the enterprise will then review and accept the individual deliverables of the task;
[0081] If this step of acceptance is passed, the commission will be paid based on the acceptance operation generated by the corporate user.
[0082] Furthermore, before issuing a task, the Extreme Speed Task also determines the balance in the enterprise user's account. If the balance meets the requirement, the task is successfully issued and the payment is made.
[0083] When the ordinary task is released, no balance check is performed, but there must be sufficient balance in the account before the enterprise pays.
[0084] When the application is in use, if the balance is insufficient, enterprise recharge is performed; when the user role is an enterprise user, it is also used for enterprise authentication, agreement signing and enterprise recharge; and enterprise authentication and agreement signing are used to enhance the credibility of the settled enterprises.
[0085] Reference Figure 3 When publishing an ultra-fast task, first select the task scenario on the enterprise side, then edit the task information, so that the task scenario and the edited task information are used as the task content, and then invite the task undertaker, fill in the personal commission and upload the task delivery results, click to confirm the release, and determine whether the company's balance is sufficient, if not, recharge; if sufficient, the release is successful and transmitted to the service platform for review, at the same time, the enterprise pays and the platform receives the payment; it should be noted that the characteristics of ultra-fast tasks are: freelancers have delivered the task delivery results to the enterprise, and the enterprise can directly upload the delivery results, eliminating the need for individuals to repeat operations.
[0086] The platform audit includes review, review 1 and review 2. If all the reviews are passed, the confirmation information will be sent to the user end. It should be noted that the review is reviewed by the junior operation staff, review 1 is reviewed by the senior operation specialist, and review 2 is reviewed by the operation manager. At each review node, all task information (i.e., the task content, the information of the undertaker and the deliverables) will be reviewed. Different personnel have different focuses.
[0087] After logging in, individual users can view tasks on their corresponding system pages, that is, view tasks to be confirmed, including:
[0088] Confirm whether you have participated in the task. If you do not confirm the task, return to the system page corresponding to the enterprise user to re-edit or cancel the task;
[0089] If the individual has confirmed that he / she is the one who completed the task and is not a formal employee of the enterprise, he / she shall sign a personal commitment letter and then confirm the task. If not, he / she shall return to the system page corresponding to the enterprise user and re-edit or cancel the task.
[0090] If yes, it means that the individual has confirmed that the task has been passed. Before the individual has confirmed that the task has been passed, it is necessary to do authentication, sign an agreement, and set up a payment method. Only after the individual has completed all of these, can the task be confirmed;
[0091] If all the above judgments are passed, it means that the individual has confirmed successfully, thereby triggering the generation of the settlement request, and then the platform pays out the money and the individual receives the money.
[0092] For example, Zhang San undertakes a drawing design task from an enterprise with a commission of 100 yuan. The enterprise can then publish a drawing design task, write the task content, upload Zhang San's information, drawing design results, etc. After the task is successfully published and the service platform reviews it, the task will be displayed to the individual for confirmation, and after confirmation, the individual can receive the payment.
[0093] The above technical solution meets the needs of enterprises at different task scales by dividing ordinary tasks and high-speed tasks. Enterprises can flexibly choose to meet the needs of different types of businesses and improve the adaptability of their businesses.
[0094] Ordinary tasks include many different types, meeting the needs of freelancers in different flexible employment scenarios, greatly improving the efficiency of interaction between enterprises and individuals, and achieving both general tasks and personalized needs.
[0095] At the same time, the fast task can meet the needs of a large number of task undertakers. Individuals can automatically win the bid and automatically deliver the work successfully, which is in line with the fast work pace of flexible employment individuals, and greatly saves the manpower and material resources of the enterprise and improves the work efficiency of the enterprise.
[0096] Finally, all task processes of this plan can be operated online and fully digitized, making operations for enterprises and individuals more convenient and traceable, in line with the characteristics of flexible employment.
[0097] Based on the same inventive concept, an embodiment of the present invention also provides a task management method based on flexible employment, which is applied to the task management system based on flexible employment described above. Figure 4 As shown, the method may include the following steps:
[0098] S101, when logging in, the user terminal selects a required user role; wherein the user roles include enterprise users and individual users, and different user roles correspond to different system functions and system pages;
[0099] S102, using enterprise users to publish enterprise tasks on their corresponding system pages; wherein the types of enterprise tasks include ordinary tasks and fast tasks, and different task types correspond to their own task content and personal commissions, and the ordinary tasks include prepayment, completed checkout, negotiable mode and piecework mode.
[0100] Specifically, when an enterprise logs in with an enterprise account, it needs to be authenticated and have the agreement signed. After signing the agreement and passing the authentication, the enterprise can publish enterprise tasks.
[0101] At the same time, when the user role is an enterprise user, in addition to enterprise authentication and agreement signing, enterprise recharge can also be performed.
[0102] S103, according to different task types, calling corresponding bidding methods to obtain bidding information; wherein the bidding information is associated with the information of the contractor, and the bidding methods include manual bidding registration and automatic bidding.
[0103] Specifically, in this embodiment, for ordinary tasks, the corresponding bidding method is manual bidding, including self-registration and enterprise invitation; if it is self-registration, the bid will be won after the enterprise's review and approval; if it is an enterprise invitation, the individual will automatically win the bid;
[0104] For extremely fast tasks, the corresponding bidding method is automatic bidding.
[0105] S104, receiving deliverables uploaded by individual users;
[0106] The type of the enterprise task, the winning bid information and the received delivery results are transmitted to the service platform for review; wherein, in the case of ordinary tasks, the enterprise user performs acceptance operations on the delivery results uploaded by the individual user on the corresponding system page.
[0107] Specifically, when applying,for ordinary tasks, individual users need to manually upload the,task deliverables;
[0108] For express tasks, enterprise users need to manually upload or batch upload the information of the task assignee and the received task delivery results.
[0109] S105, reviewing the content of the task, the information of the undertaker and the deliverables through the service platform;
[0110] If the review is passed and it is a normal task, the enterprise user will be triggered to directly conduct enterprise acceptance;
[0111] If the review is passed and it is an extremely fast task, a confirmation message will be sent to the individual user.
[0112] Specifically, it should be noted that when the enterprise task type is an ordinary task, the task content, contractor information and delivery results are also reviewed. The difference is that no confirmation information is sent to individual users, and the delivery results are directly accepted by the enterprise.
[0113] S106, paying a commission according to the acceptance operation or the settlement request generated;
[0114] Then, individual users can view tasks, sign up, win bids, upload task deliverables and collect payments on their corresponding system pages; in the case of express tasks, they are also required to sign a personal commitment letter and confirm the task information; the confirmation of task information includes viewing the received information to be confirmed, determining whether the individual has participated in the completion and whether to confirm the task;
[0115] After confirming the task, the task is reconfirmed based on the operational feedback. If the confirmation is passed again, the settlement request is generated and the payment is collected; wherein the reconfirmation includes confirming whether the individual has been authenticated, signing the agreement and setting the payment method.
[0116] In this embodiment, when the enterprise task type is an extreme speed task, a judgment will be made in the subsequent process as to whether the person has participated in the completion and whether the task has been confirmed.
[0117] When applied, the extreme speed task also determines the balance in the enterprise user account before issuing the task. If the balance meets the requirement, the task is successfully issued and the payment is made;
[0118] When the ordinary task is released, no balance check is performed, but there must be sufficient balance in the account before the enterprise pays.
[0119] It should be noted that for more specific work processes in the method embodiments, please refer to the records in the aforementioned system embodiments, which will not be repeated here.
[0120] The implementation of a task management method based on flexible employment in the embodiment of the present invention meets the needs of enterprises under different task scales by dividing ordinary tasks and extreme-speed tasks. Enterprises can flexibly choose to meet the needs of different types of business of the enterprise, thereby improving the adaptability of the enterprise's business.
[0121] Ordinary tasks include many different types, meeting the needs of freelancers in different flexible employment scenarios, greatly improving the efficiency of interaction between enterprises and individuals, and achieving both general tasks and personalized needs.
[0122] At the same time, extremely fast tasks can meet the needs of a large number of task undertakers. Individuals can automatically win bids and successfully deliver work, which is in line with the fast work pace of flexible employment individuals, and greatly saves the company's manpower and material resources and improves the company's work efficiency.
[0123] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0124] In the several embodiments provided in the present application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.
[0125] In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional modules.
[0126] If the integrated module is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0127] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.
Claims
1. A task management system based on flexible employment, characterized in that: The task management system includes a service platform and a user terminal; The user terminal is used for: When logging in, select the required user role; wherein, the user roles include enterprise users and individual users, and different user roles correspond to different system functions and system pages; When the user role is an enterprise user, the enterprise task is published on the corresponding system page; the types of enterprise tasks include ordinary tasks and fast tasks, and different task types correspond to their own task content and personal commissions. The ordinary tasks include prepayment, checkout completion, negotiable mode and piecework mode; According to different task types, the corresponding bidding method is called to obtain the bidding information; wherein the bidding information is associated with the information of the contractor, and the bidding methods include manual bidding registration and automatic bidding; Receive deliverables uploaded by individual users; The enterprise task type, winning bid information and received deliverables are transmitted to the service platform for review; wherein, in the case of ordinary tasks, the enterprise user performs acceptance operation on the deliverables uploaded by the individual user on its corresponding system page; The service platform is used for: Conduct an audit based on the content of the task; Conducting review based on the information of the undertaker; Conduct reviews based on the stated deliverables; If the review is passed, the confirmation information is sent to the individual user or the enterprise user is triggered to directly conduct enterprise acceptance; the commission is paid according to the acceptance operation or the settlement request generated; When the user role is an individual user, the user can view tasks, register, win bids, upload task deliverables and collect payments on the corresponding system page; in the case of express tasks, the user is also required to sign a personal commitment letter and confirm the task information; the confirmation of task information includes viewing the received information to be confirmed, determining whether the user has participated in the completion and whether to confirm the task; After confirming the task, the task is reconfirmed based on the operational feedback. If the confirmation is passed again, the settlement request is generated and the payment is collected; wherein, the reconfirmation includes confirming whether the individual has been authenticated, signing the agreement and setting the payment method.
2. A task management system based on flexible employment as claimed in claim 1, characterized in that: When the user role is an enterprise user, it is also used for enterprise authentication, agreement signing and enterprise recharge.
3. A task management system based on flexible employment as claimed in claim 1, characterized in that: For ordinary tasks, the corresponding bidding method is manual bidding, including self-registration and company invitation. If it is self-registration, the bid will be awarded only after the company's review and approval; if it is a company invitation, the individual will automatically win the bid; For extremely fast tasks, the corresponding bidding method is automatic bidding.
4. A task management system based on flexible employment as claimed in claim 3, characterized in that: For ordinary tasks, individual users need to manually upload the task deliverables; For express tasks, enterprise users need to manually upload or batch upload the information of the task assignee and the received task delivery results.
5. A task management system based on flexible employment as claimed in claim 3, characterized in that: Before issuing a task, the Extreme Task also checks the balance in the enterprise user's account. If the balance meets the requirement, the task is successfully issued and the payment is made. When the ordinary task is released, no balance check is performed, but there must be sufficient balance in the account before the enterprise pays.
6. A task management method based on flexible employment, characterized in that: The method applied to a task management system based on flexible employment as described in claim 1 comprises: When logging in through the user terminal, select the required user role; wherein the user roles include enterprise users and individual users, and different user roles correspond to different system functions and system pages; Utilize enterprise users to publish enterprise tasks on their corresponding system pages; the types of enterprise tasks include ordinary tasks and fast tasks, and ordinary tasks include prepayment, checkout completion, negotiable mode and piecework mode; According to different task types, the corresponding bidding method is called to obtain the bidding information; wherein the bidding information is associated with the information of the contractor, and the bidding methods include manual bidding registration and automatic bidding; Receive deliverables uploaded by individual users; The type of the enterprise task, the winning bid information and the received deliverables are transmitted to the service platform for review; in the case of ordinary tasks, the enterprise user performs acceptance operations on the deliverables uploaded by the individual user on its corresponding system page; Through the service platform, the content of the task, the information of the undertaker and the deliverables are reviewed respectively; If the review is passed and it is a normal task, the enterprise user will be triggered to directly conduct enterprise acceptance; If the review is passed and it is a high-speed task, a confirmation message will be sent to the individual user; and make commission payments based on said acceptance operations or resulting settlement requests; Then, individual users can view tasks, sign up, win bids, upload task deliverables and collect payments on their corresponding system pages; in the case of express tasks, they are also required to sign a personal commitment letter and confirm the task information; the confirmation of task information includes viewing the received information to be confirmed, determining whether the individual has participated in the completion and whether to confirm the task; After confirming the task, the task is reconfirmed based on the operational feedback. If the confirmation is passed again, the settlement request is generated and the payment is collected; wherein the reconfirmation includes confirming whether the individual has been authenticated, signing the agreement and setting the payment method.
7. A task management method based on flexible employment as claimed in claim 6, characterized in that: The method further comprises: When the user role is an enterprise user, enterprise authentication, agreement signing and enterprise recharge are also performed.
8. A task management method based on flexible employment as claimed in claim 7, characterized in that: For ordinary tasks, the corresponding bidding method is manual bidding, including self-registration and company invitation. If it is self-registration, the bid will be awarded only after the company's review and approval; if it is a company invitation, the individual will automatically win the bid; For extremely fast tasks, the corresponding bidding method is automatic bidding.
9. A task management method based on flexible employment as claimed in claim 8, characterized in that: For ordinary tasks, individual users need to manually upload the task deliverables; For express tasks, enterprise users need to manually upload or batch upload the information of the task assignee and the received task delivery results.
10. A task management method based on flexible employment as claimed in claim 9, characterized in that: Before issuing a task, the Extreme Task also checks the balance in the enterprise user's account. If the balance meets the requirement, the task is successfully issued and the payment is made. When the ordinary task is released, no balance check is performed, but there must be sufficient balance in the account before the enterprise pays.
