Work on a Mercor project can stop for four different reasons, and Mercor treats them as four different things. Two say nothing about you at all. One comes with a stated chance to fix the problem. Only one can cost you money and your access to the platform.
Everything below is Mercor’s own published policy, stated by Mercor rather than measured by this site. What to look for in the list is the left edge: only the marked entries touch your standing.
- Paused Not an ending Your weekly cap goes to zero and no new work is assigned. Everyone on the project is paused, not just you, and you stay in the pool. Nobody can request a restart.
- Project ended Says nothing about you The engagement finished, the scope changed, or the budget ran out. Tool access is revoked soon after. Submit your final hours before the deadline.
- Performance offboarding Says something about the work Missed deadlines, repeated revisions, or going quiet. Your project lead may run a trial sprint with stated expectations first.
- Policy violation Says something about conduct Falsified work, misused AI, or shared confidential material. Payment can be withheld and platform access suspended.
Only the bottom two touch your standing. Mercor is explicit that a project simply ending does not.
Paused is not an ending
From the inside a pause looks exactly like being dropped, which is why it gets read that way. Work stops, no new tasks arrive, and the weekly hour cap goes to 0 hours. Mercor says a project can be paused because the workload dried up, because the client changed what it needs, or because of internal planning. It applies to everyone on the project, and you stay in the project pool.
A pause cannot be lifted on request: Mercor says the decision sits at project and client level and that individual escalations to restart the work are not accommodated. And there is no published duration, only Mercor’s statement that pause lengths vary widely.
What Mercor asks of you is small. Submit hours already worked before the pause takes effect, keep your payment details current so pending payouts are not held up, and watch email and Slack, where Mercor says a restart would be announced.
A worked example of reading a pause wrongly
Imagine a data annotator, six weeks in, who opens Insightful on a Monday and finds her weekly cap at zero. No task list, no message yet. She reads it as a quiet firing.
So she does three things. She asks support to reinstate her hours, which support cannot do, because caps sit with the project point of contact and a pause is not a cap adjustment anyway. She asks her point of contact to restart her on the project, a request Mercor has said is not accommodated. Then she logs out of the tools and stops reading her contractor inbox, on the grounds that it is over.
The pause ends eleven days later. The restart notice goes to the email she stopped reading, and the first new tasks go to whoever is watching Slack. Nothing about her standing had changed. The right read on a zero cap is that it is probably project-wide and has no timeline, so the useful move is to stay reachable and apply elsewhere meanwhile.
A project ending says nothing about you
When a contract concludes normally, Mercor says access to Slack, Airtable and the rest is revoked shortly after the end date, so submit your final hours and deliverables before the stated deadline rather than after.
Mercor lists three ordinary causes: the work was completed, the scope changed, or the budget ran out. It says directly that a project ending does not affect your standing unless it is tied to fraud or performance. In most cases every contract on a project ends on the same date, which is another sign it was never about any one person. Advance notice is given where Mercor can give it, though it warns that client requirements can change with little notice.
Your payout follows the normal schedule, and a first Mercor payout still sits behind Stripe’s seven-day hold. How that last week’s hours are checked before they are paid is covered in the guide to Mercor hours and quality.
Performance offboarding comes with a remedy
This ending is about your work, and Mercor names the signals: missed deadlines, work that needs repeated revisions, and poor communication or slow responses.
The remedy comes first, and knowing that in advance changes what you do. Mercor says a project lead may run a trial sprint with expectations and timelines set out explicitly. That is a real second chance with a stated bar, though the project team can end the contract if nothing improves across it. Mercor’s own advice is to ask earlier rather than later: if you are unsure how your work is landing, raise it with the lead before a sprint is needed.
Policy violation is the one that costs
The behaviours Mercor names here are faking work, using AI where the project forbids it, and passing confidential material outside the project. How far the consequence goes depends on how bad and how repeated the conduct was. Mercor says pay can be cut or clawed back, you can be taken off the project, and at the severe end your access to the platform itself can be suspended. This is the only one of the four where money already earned is at risk, and the only one that follows you off the project.
Offboarding decisions are final
Mercor states that offboarding decisions are made by the project team and are conclusive, and that support cannot overturn them. What your point of contact can do is give you context on the decision.
If you were offboarded and nobody told you why, Mercor asks you to contact support with the project name, your last working day, and any prior communication. That is a request for an explanation, not an appeal. To end a contract yourself, Mercor points you to your point of contact rather than support.
Nobody is moved to a new project automatically
The mistake here comes after the ending rather than during it. Mercor says contributors are not automatically moved to another project when one concludes, and that the next contract comes from applying again through the platform.
Expired contracts are not reactivated and cannot be extended, before or after the end date, so there is nothing to renew. Keep your profile, skills and availability current, since Mercor’s matching system reads those when deciding who to surface as prequalified for an instant offer. Then browse what is open and apply.
The rate is fixed, so the next offer can pay less
Pay rates are fixed for the duration of a project and, in Mercor’s words, not open to renegotiation once work begins. They are set from the role, the project’s requirements, the budget and evaluation outcomes. Because those inputs differ between projects, a follow-up offer can pay less than the engagement you just finished. That is not a downgrade applied to you; it is a different project priced on its own terms.
Separately, a project can change its pay structure mid-project, switching hourly to task-based or the other way. Mercor says this is announced officially, that your contract on the dashboard is updated to show the new terms, and that work already completed is paid under the terms it was done under. It is set at project level and cannot be opted out of individually.
If an offer does not work for you, declining it is safe: Mercor states that declining does not reduce your consideration for future roles. The Mercor guide covers the rest of how the platform works.
Two things Mercor does not publish, so nobody should guess at them: how long a pause lasts, and how many missed deadlines trigger a performance review.
Red Pen Jobs is an independent directory, not affiliated with Mercor, and has no part in any of these decisions.