# Gender Contacts by Critical Issue

#### Location

This panel appears on the following dashboards:

* [Contacts by Critical Issues](/analyze/impact-dashboards/contacts-by-critical-issues.md)

#### Modules Included

* Quarterly Efforts (Grand Challenge Totals)

#### Filters

**Applied Filters**

* **Viewable records** — Only Quarterly Effort records the current user has permission to view are included.

**Non-Applicable Filters**

* **Units** — Quarterly Efforts do not directly reference Extension units.
* **Sites** — Quarterly Efforts do not have a site field.
* **Interventions** — Quarterly Efforts do not have an intervention field.
* **Projects** — Quarterly Efforts do not have a project field.
* **Action Plans** — Quarterly Efforts do not have an action plan field.
* **Settings** — Quarterly Efforts do not have a setting field.
* **Verified** — Quarterly Efforts do not have a verification status field.
* **Session Date Range** — Quarterly Efforts do not have session occurrences.
* **Primary Curriculum** — Quarterly Efforts do not have a curriculum field.
* **Collaborator** — Quarterly Efforts do not have collaborators.

#### Calculations

1. PEARS retrieves all viewable Quarterly Effort records that match the current dashboard filters.
2. Grand Challenge Total records are grouped by their critical issue (grand challenge) name.
3. For each critical issue, the panel sums gender demographic fields: Female, Male, Non-Binary, Prefer Not to Respond, and Unknown.
4. A stacked bar chart is displayed where:
   * The x-axis shows the critical issue names.
   * Each stacked segment represents a gender category.
   * The segment height represents the contact count for that gender.

#### Additional Notes

* Grand Challenge Totals are a component of the Quarterly Effort module and represent aggregate contact counts by demographic group.


---

# 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://support.pears.io/analyze/impact-dashboards/panels/gender-contacts-by-critical-issue.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.