# Follow submission results


After submitting work, check the result of that Submission. A Campaign's running state does not tell you whether your work has been reviewed. Contributors use **Contributions** to follow their submissions; Developers use the corresponding Campaign to inspect work and participant results.

## Find your submission

Open **Contributions** in the Contributor sidebar. Find the work, using the status filter if helpful, and open its details. In **Overview**, check the Campaign, Task, submission time, and Submission ID. These identify the exact attempt you are reading. Then read the review result, grade, and feedback against the task's requirements.

**Submitted content** contains the answers or files you handed in. **Activity** contains recorded events such as submission, review, and rewards. **Awarded** shows reward records for this contribution. **Elapsed** includes time spent away from the task, so it is not a measure of active working time.

After acceptance, choose the next view according to your question. Use **Track record** for subsequent provenance and data processing. Use **Earnings** for earnings and withdrawal conditions. **Next → Complete** means the contribution has an acceptance result and reward record; it does not establish that data delivery, on-chain anchoring, and wallet payment have all finished.

## Interpret the result

| What you see | What it means | What to do next |
| --- | --- | --- |
| Submitted and processing or under review | Your work has entered the next stage | Read the current stage and any feedback |
| Accepted | The work received an acceptance result | Follow data delivery and earnings separately |
| Rejected or Duplicate | The work was not accepted, or was identified as a duplicate | Read the reason and the actions offered for this record |
| No result, or a loading error | The current view does not establish an outcome | Keep the original record and reload it |
| **Integrity review pending** | The submission is paused for an integrity check. Nothing has been decided and the work has not been removed | Wait for the review. To add context, send support the Submission ID |
| **Further review requested** or **Further review under way** | Someone asked for another review of this submission. It is not a penalty and nothing has been taken away | Wait for the outcome on the same record |

Different Steps in one Campaign can use different review criteria. Use your Submission's result and reward records to understand your work.

## Follow an on-chain record

**Anchored on-chain** describes a contribution's anchoring stage. XnY uses a **Contribution Fingerprint**, or **CF**, to associate identity, task, review information, and a content digest with a contribution. A CF and a Humanbased Submission are related records with different identifiers.

Open **Track record**: once the contribution is anchored, its **Anchored on-chain** step shows the block number and a shortened transaction hash (`ContributionRecord · tx …`). Look that block up in [XnY Explorer](https://explorer.xny.ai) to inspect the record. Public contribution details can include the author, task, review result, metadata address, and transaction links.

Anchoring records identifiers, digests, and references. It does not mean the entire image, text, or video is stored on the blockchain. Dataset membership and earnings have their own records. If the step shows no block or transaction yet, retain its reported state instead of inferring a completed chain transaction from a list label.

<a id="availability-appeals"></a>
## Respond to rejection or duplicate feedback

Start by comparing the recorded result with the work you actually submitted:

1. Find the original record in **Contributions**. Use the **Rejected** or **Duplicate** filter if appropriate.
2. Open **Overview** and read the result and feedback.
3. Open **Submitted content** and compare the content with the task requirements. A duplicate finding and a quality rejection call for different corrections.
4. To contest the decision, select **Appeal** on the record. **Appeal this decision** shows what the review said; add a note if it helps the reviewer, then select **File appeal**.
5. To fix the work instead, select **Correct and resubmit** where it is offered.

**Appeal** is offered on a result that was not accepted, while no other appeal on that submission is open. A note supplements the review; it does not change how the decision is classified. After you file, the record shows **Appealed**, its next step reads **Appeal under review**, and a person decides. The decision appears on the same record as **Appeal upheld** or **Original rejection upheld**; when an appeal against a rejection is upheld, the submission and your reputation are corrected, and the record says so once both corrections are verified; **Earnings** shows any change to what you are paid. If a correction cannot be verified yet, because verification is still running or a service is briefly unavailable, the record reads **Human ruling recorded; execution needs attention**: the ruling is recorded and the correction is not finished. An upheld appeal against a duplicate finding is recorded with the same message, because no correction is applied automatically. Whichever the original result, that message means the appeal stays open while Humanbased follows up. If **Appeal** is missing or filing fails, send [hello@humanbased.ai](mailto:hello@humanbased.ai) the Submission ID, rejection time, feedback and the point you dispute.

**Correct and resubmit** revises the work and submits it again. The original Task must still be available, and the Campaign state, quota, task supply, and participation requirements still apply. Use the record's action rather than creating a duplicate submission yourself.

For any dispute deadline, read the version of **Contributor Payout Terms** applicable to your account in **Agreements**. Rejection disputes and payment disputes can have different deadlines. Contact support promptly if the record's action cannot be completed.

## Review work as a Developer

Open the Campaign and select **Reviews**. Find the submission and select **Review** on its row. **Submitted content** shows the work, and **Review outcome** shows its result. Review is a record action, not a separate navigation section.

When the item has reached the acceptance step, decide it with **Approve** or **Reject**; a rejection needs a **Reason for rejection**, and a scored step asks you to **Pick a score** first. **Change verdict** can overturn the decision until the award starts settling; once it is settling or paid, the control is no longer offered. A paid award cannot be taken back: to flag a problem with data already paid for, open **Dispute this submission?** from the Submissions table, which opens a case for the operations team without reversing the payment. When a contributor's appeal needs a person, **Fill out human review request** asks Humanbased operations to review it; the verdict stays unchanged until they rule.

Use **People** for participants. Submissions are listed by step in **Reviews**, which is also where **View records** on **Overview** leads. Aggregate acceptance rates help explain a Campaign's progress; an individual decision should be based on that Submission's content and criteria. Confirm the target record, reason, and your permissions before changing a review or a participant's access.

## When a Campaign pauses or closes

Pausing work, stopping new submissions, and completing all processing are separate states. Existing submissions may still be under review or awaiting settlement. If the Campaign is **Closing**, inspect the outstanding work before concluding that every submission or refund is complete.