Project building and execution
Each project is structured the same. The structure has proven itself to be very efficient and leaves the least possible room for misunderstanding between you and the performer. Creating your project, you only need to follow the preset steps. Once you have created a project you can save it as your custom-template. Creating a similar project becomes extremely easy. You can also use templates created by the administrator.
Your project is specified in products and sub- products. (Sub)-Products explain what the final result looks like, rather then what the tasks are that need to be executed. This takes away the main misunderstanding in project management: the performer thinks he/she performed all tasks; while the assigner is left with a useless end-result.
The project is separated into phases based on the different sub-products. Each phase consists of a draft and a final deadline. During project creation you have specified all features/characteristic. During project execution you’ll give feedback based on these features/characteristics. You can directly give feedback to the (draft) uploads. On top, there is a chatting function.
Each project ends with a closing phase. This phase functions as a back-up and review. You’ll review if the overall project has been successful and if anything is still missing or needs to be fixed before the complete finishing of the project.
Project control and payment
Due to the clear project structure, the feedback and the closing phase bad deliveries rarely happen. However, there needs to be a safety net in place.
You have specified two types of features: essential and with a percentage value. While giving feedback you’ll rate these as pass or fail. Obviously, the performer tries to have all passed by phase ending and especially project ending.
In case essential features are missing, the whole project would be useless. Therefore, project execution can never move to the next phase as long as these are rated as fail.
Failing percentage-features reduce the value of the project. However, the project can still move to the next phase, the performer can fix these during the closing phase. Both happen rarely due to feedback and the distinction between draft and final. If you fail a feature, feedback is obliged.
Once a project has started, it can only be withdrawn after deadlines are not met. This can be a phase deadline with a failed essential feature or the deadline of the full project. In these cases withdrawals are optional, not obliged.
If at project completion, (non-essential) features are still failed, this reduces the pay-out to the performer (equivalently to the rated percentage). However, the payment can never be below 55% of the initial value (exception: at project withdrawal it will be 0).
After you have created your project and selected your candidate, you need to have the project value in your account before project start. At project start, this money is frozen in your account. At project ending this is released to the performer (or back to you in case of project failure).