@Liz B wrote:
Also, why would someone have 38% job success, but I don't see any negatives at all in her feedback...?
Liz, without seeing the freelancer's profile, there's no way of knowing, but one possibility is that the freelancer had many unsuccessful assignments, so rather than risk having negatives in the profile, she refunded all money paid for the unsuccessful jobs, because feedback is only displayed for jobs for which the freelancer was paid, but clients *can* leave private feedback even when all money is refunded, and private feedback is factored into Job Success.
"No good deed goes unpunished." -- Clare Boothe Luce
why would someone have 38% job success, but I don't see any negatives at all in her feedback...?
There is another possible reason of that. If any freelancer was out of Upwork (means did not even open his/her profile) for a long time (say 1 year or more), then his/her job success rate decreases automatically. I personally know one of my friends having the same problem. She was not in Upwork for a year because of her physical illness. She was a top rated freelancer with 100% job success. When she came back after a year her job success score was 58%.
So better not judge anyone by seeing only job score.
Being absent from the platform doesn't decrease the Job Success score automatically. Yes, since the score is based on the outcomes of contracts in the last 2 years, it can change as older outcomes fall off of the calculation. However, having a low score would mean that some contracts of this freelancer had unsuccessful outcomes according to public and private feedback as well as other information the system collected about contracts the freelancer worked on.
Being absent from the platform doesn't decrease the Job Success score automatically.
May be I was not able to clarify my point last time. For example, if someone has a top rated badge with 90% job success. And he was out of the platform for a year, generated no income. And as a result, his last 12 months earning going down to less than 1k,.
Then is it not obvious, that he lost his top rated badge and job success score rate? As the calculation process did not find any data (last one year) to calculate.
That was my point.
Your JSS may have a slight downfall but due to old contracts that are not calculated any more. Example if the 2 year window was from January 2015 to 2017, today it will be September 2015 - September 2017.
But for the top rated badge yes it will be lost. One of the requirements for top rated is: Freelancer needs to have 1k earnings in the past 12 months.
Just joined Upwork,
Sent a freelancer an invite to look at the job and respond, then later, I checked in messages - nothing - so I checked the saved freeelancers and it still shows "send invite " (Shouldnt it say "invitation sent" )
Click on the invite button (I got the strangely worded interview in progress message , I thought it would say something practical like "invitation sent" - I think any hallway testing in code tests would have picked up that type of work flow as communication errors in how the software should work for the end user.
Also, nothing appears in my messages.. I would have expected to something like , the actual invitation sent, but it just says ;"no messages"
So if the invitee does not respond, then the inviter has no way of knowing if they received the invitaion, as written English saying "interview in progress doesnt mean that I am interviewing them , because I am not in invterview with the freelancer, they havent even responsed to any message, and so far as I can tell, I havent sent them one as no messages are in my messages.
all very strange. Simply go and ask employers if they find it an easy system as a first timer. Thats how you do hallway testing in software.
Needs to be worked on .
I am having the same challenge (problem?) as you. I sent an invite, did not recieve a reply. On the "Invite Freelancer's" tab --- it shows for this single freelancer "Invite Sent."
I then go to the "Invited Freelancer's" tab ----- and the invite that I sent does not show. This is clearly a programming/process issue that needs to be solved.