Because from my point of view - Client/Worker relationship is a bit unbalanced from the start.



Let's take a look at the things both sides have at stake in both situations - BadClient and BadWorker:



A) BadClient:

If the Client is bad, Worker risks just one thing - spending his time, and not getting any monetary reward for this.

But the BadClient itself has a full set of risks if he acts maliciously:

1) Lose a contractor to finish the project and need to seek a new one.

2) Wasted time, missed deadlines and project plans.

3) Money is worth its every cent, but 1 day of code usually is useless, if the project is longer-term.

4) It's not so easy to be a BadClient as it is to be a BadWorker - you need to have a real project to earn gains from this fraud, and projects usually value reputation much more than anonymous Workers.



B) BadWorker:

If the Worker is bad and "takes the money and runs" - BadWorker risks nothing but his reputation. But there are much more Workers out there than clients, so the reputation is harder to track.



But the Client has all the same risks as above from his ruined project, wasted time, no work done and missed deadlines. Plus - he loses real money.



Thus, it's harder to cheat when you're a Client, and especially if the PayDay Periods are so small that no meaningful work can be done within the period.



That's why I've decided to allow clients to refund the work done in current PayDay Period.

