# Guidelines

Consider the following guidelines when verifying.

### Check the resolution source

Make sure the **evidence matches the resolution source**. 

*Example:* In *2026 NBA Champion*, the resolution source is information from the NBA. Evidence from outlets such as ESPN would not count.

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

### Review proposals that are about to finalize

Prioritize reviewing proposals whose **challenge periods are about to end**.

*Example:* In the UMA Oracle, prioritize proposals with less time remaining in their challenge period over those just submitted.

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

### Collaborate with others

Verification is a **team effort.** Work with others to determine whether a proposal is accurate. By collaborating, you can **learn from experienced verifiers** and markets you may be unfamiliar with.

*Example:* In *Any Tesla arsonist found guilty in 2025?*, several users collaborated by reviewing court documents to confirm whether a Tesla arsonist had been found guilty.

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


---

# 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://polymarketguide.gitbook.io/polymarketguide/resolution/how-to-participate/verify/guidelines.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.