Valeria K wrote:
As always, clients should communicate with freelancers and agree in advance before making any changes. Freelancers can still propose changes and additions to contract milestones and submit them to the client for review. If a freelancer had not already agreed with a change, they can use this functionality. This can be done by clicking the “Add or Edit Milestones” button in the Contract Room. We hope with the additional functionalities for clients, this will continue to improve the contract management experience.
You conclude by referring to "additional functionalities for clients"—not for freelancers. It's not at all clear what you mean by "If a freelancer had not already agreed with a change, they can use this functionality. This can be done by clicking the 'Add or Edit Milestones' button in the Contract Room." Will clicking the button allow us to delete milestones not previously discussed or agreed to? Or, as Phyllis asks, does our only means of rejection remain closing the contract?
It's great to hear about these new features, but it seems like there's still an important problem that hasn't been fixed on the freelancer end. As far as I'm aware, a client with an existing contract can set up a new milestone without the freelancer's approval. If the freelancer does not agree to it and ends the contract without completing it, the freelancer will end up taking a hit to their JSS score.
Is this still the case?
As before, freelancers should only start working on a milestone once it's funded if they want to benefit from Upwork Fixed-Price Protection. With this new feature clients will be able to easily edit upcoming milestone, but they will still need to fund them in order for the freelancer to start working on them.
Renata S wrote:
As far as I'm aware, a client with an existing contract can set up a new milestone without the freelancer's approval. If the freelancer does not agree to it and ends the contract without completing it, the freelancer will end up taking a hit to their JSS score.
In this case, the JSS won't be impacted by the mere action of closing the contract, since at least one milestone, the first one, has already been approved by the said freelancer and released.
The first milestone is funded when the offer is sent to the freelancer for them to approve. It is the subsequent milestones that can be created by the client without the freelancer being asked anything. When a milestone is
assigned imposed that way, the freelancer can close the contract, yes, and this will be a contract with money paid. However, closing the contract abruptly may trigger an angry feedback from the client. Which is why discussing the matter with them should be the first thing to do when they assign a milestone out of the blue.
In all honesty, having an option to decline an assigned milestone in an existing contract would be nice, but wouldn't do that much with respect to client/freelancer communication.
Valeria, thanks for your responses. I have another question: what is an "upcoming milestone" exactly? Is that one that has not been funded yet? Or one that may/may not be funded but isn't due yet?