> For the complete documentation index, see [llms.txt](https://docs.scholars.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scholars.net/how-to/accept-or-reject-a-job-offer.md).

# Accept or reject a job offer

Learn here how to accept or reject job offers on Scholars.

If you've received an offer, congratulations – you've been selected to work on a job on Scholars.

The next step is to look at the offer and accept or reject it.

## What is in an offer?

The offer will contain all of the details regarding the job: the job description, start and end dates, and the hourly rate at which you'll be paid.

### Payment rates and categories

If the job pays different rates for different timesheet categories, the offer also shows how each category's multiplier changes the base rate. For example, you may see the base rate next to the final training or assessment rate before you accept.

These categories and rates are saved with the offer and resulting contract, so later changes to the job do not change the terms you accepted.

### Payment schedule

The offer can also show a payment schedule. This schedule explains the work period, when your timesheet should be submitted, when it should be approved, and when payment is expected to be sent.

## When does an offer expire?

If you have not responded to an offer yet, Scholars may send reminder emails with a link back to the offer.

Offers do not remain available indefinitely. A pending offer expires on the earlier of its proposed end date and 30 days after it was created. The offer email shows the expiration date. Respond before that date; after the offer expires, it can no longer be accepted or rejected.

## Video guide

{% embed url="<https://youtu.be/1i0fhqs_T2U>" %}

## How to respond to an offer

{% stepper %}
{% step %}

### Click on the banner in the home page

When you have a pending offer, you'll see it at the top of the home page. Click on it to see it and respond to it.

You can also go to the *Offers* tab and respond from there.

<figure><img src="https://620615177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcMVr1tcqZLg9WCEj5GgZ%2Fuploads%2Fgit-blob-ed2cb4e2270fc641b5d5c827018ab92bbd5d3aa3%2Floreshot-20260113-112428%402x.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### (Optional) Reject the offer

At this stage, you may reject the offer by clicking on the *Reject Offer* button.

<figure><img src="https://620615177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcMVr1tcqZLg9WCEj5GgZ%2Fuploads%2Fgit-blob-90a8bd7e498579a254224a55a4e368ec2c018731%2Floreshot-20260113-112627%402x.png?alt=media" alt=""><figcaption></figcaption></figure>

The offer will disappear from the home page. There is nothing else you should do at this time, and you do not need to continue reading this guide.
{% endstep %}

{% step %}

### Complete the compliance requirements

If you wish to instead accept the offer, you must first complete the compliance requirements.

Essentially, you click on each of the compliance requirements on the right and follow the steps on screen to complete them.

The message above the offer buttons tells you what happens next:

* If you still need to complete a requirement, finish the listed steps. *Accept Offer* stays disabled.
* If you have completed everything available to you but an item needs company review, wait for the review. Scholars will email you when the offer is ready.
* When every requirement is complete, you can accept the offer.
  {% endstep %}

{% step %}

### Accept the offer

Once all of the compliance requirements are completed, you may click on *Accept Offer* to accept the offer.
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scholars.net/how-to/accept-or-reject-a-job-offer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.