# How Reviewers Works

The reviewing phase begins immediately after the submission period for a coding competition ends. At this time, all eligible  reviewers will receive an email informing them of the start of the judging phase. Each project will have 3 judges which one of the 3 will be randomly selected as lead judge that will review the code and create a document for the business.

This guide provides instructions on how to participate in the  judging phase, where you can evaluate others' submissions and earn additional rewards.

### Reviewer Control

Navigate to the reviewing Page by clicking on the "reviewer" button on the navbar to view all projects currently being reviewed.

<figure><img src="/files/UwugrXnH1uLgzfWYrHmd" alt=""><figcaption></figcaption></figure>

### Contributing to projects during Reviewer Phase

Once you find the project you want to contribute to through the reviewing phase, you can visit our discord to get your reviewer role or engineer appeal role and gain access to the channels regarding the projects.\
\
Each reviewer will receive a list of submissions they will review, each submission that passed will then be included in a pool along with the accepted submissions the other reviewers have added.

### Reviewers Assessment

Once all submissions have been reviewed, the lead reviewer will allow the engineers to appeal for any wrong assessments, before agreeing as to which submissions to present to the business.&#x20;

### XP

Reviewers earned XP based on the number of submissions they have assessed which successfully passed the final stage.\
The XP varies based on the type of submission they have reviewed and passed (e.g. Feature, Optimization, Bug)


---

# Agent Instructions: 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:

```
GET https://codecall.gitbook.io/code-call/reviewer-docs/how-reviewers-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.