> For the complete documentation index, see [llms.txt](https://codecall.gitbook.io/code-call/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codecall.gitbook.io/code-call/engineers-docs/appeals.md).

# Appeals

At CodeCall, we are committed to ensuring a transparent and fair project environment. Our Appeals Period is designed to uphold this commitment.

### Appeals Period

For 24 hours following the review phase, participants may submit appeals to contest judgments. This period will be clearly announced across all channels. During the Appeals Period, you can interact with your submissions directly on the platform and leave comments detailing your appeal for re-assessment.

### Eligibility for Appeals

To maintain a fair competition environment, participants who wish to appeal judgments on submissions (including those by other engineers) must:

* Have at least one active submission in the current contest, ensuring they are familiar with the codebase.
* Have earned at least $100 from previous CodeCall porjects, which helps ensure the credibility of the participants.

### Review of Results

Results are released immediately after the conclusion of the reviewers process. This initial release provides an overview of submission standings and participant performance.

Once preliminary results are public, a 24-hour Appeals Period begins. During this time, participants can:

* Raise concerns about their own submissions.
* Provide additional insights or clarifications.
* Challenge the preliminary findings if discrepancies are believed to exist.

### How to Submit an Appeal

To submit an appeal, follow these steps on the CodeCall portal:

1. **Locate reviewed Submission:** Navigate to your reviewed submission on out Discord server.
2. **Review Comments:** Carefully read the comments provided by the reviewers.
3. **Detail Your Appeal:** If you disagree with the reviewers decision or have questions about the results, open a ticket explaining in detail why you believe the judgment is incorrect. If challenging other entries, provide clear reasoning for any discrepancies identified.

**Note:** Low-effort appeals that lack substantial evidence or clear reasoning may be disregarded.

### Key Considerations

* **Substantial Evidence Required:** Appeals must be well-reasoned and supported by substantial evidence. Hasty or unclear appeals will be promptly closed.
* **Thoughtful Submissions:** While valid concerns are encouraged, excessive appeals with little merit may lead to disqualification of even valid points. Participants should be discerning and thoughtful in their approach.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://codecall.gitbook.io/code-call/engineers-docs/appeals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.