> For the complete documentation index, see [llms.txt](https://docs.code4rena.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.code4rena.com/platform-guide/platform-guide-for-wardens/comments-on-submissions.md).

# Comments on submissions

{% hint style="info" %}
This page is about comments on audit submissions. Documentation about sponsor Q\&A can be viewed here.
{% endhint %}

To view comments for an audit, start from the audit dashboard, and click the `View all comments` button.

<figure><img src="/files/AWM3a0n38sGcCGyBUsbI" alt=""><figcaption><p>The comment list is grouped by the date of the most recent comment in the thread, and shows the number of comments.</p></figcaption></figure>

Clicking on a thread will take you to the comment section on the relevant submission:

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

SR wardens will see a comment form that can be used to add comments during the Post-judging QA phase of the audit. SR wardens may also leave a private comment for the judge and sponsor.

## Who can comment?

Comment privileges vary depending on the phase of the audit:

* From launch through completion:
  * Sponsor team members
  * Judge(s) assigned to the audit
* [Post-judging QA](/competitions/judging-criteria.md#post-judging-qa-pjqa) phase:
  * Wardens may comment during this 48-hour period only.

The Post‑judging QA (PJQA) comment window is the official place to raise clarifications, disputes, or escalation requests about a judge's assessment. Do not contact judges individually.


---

# 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://docs.code4rena.com/platform-guide/platform-guide-for-wardens/comments-on-submissions.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.
