> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow.md).

# Our policies: evaluation & workflow

See links below accessing current policies of The Unjournal, accompanied by discussion and including templates for managers and editors.

### 1. Project submission, selection and prioritization

People and organizations submit their own research or suggest research they believe may be high-impact. The Unjournal also directly monitors key sources of research and research agendas. Our team then systematically *prioritizes* this research for evaluation.  *See the link below for further details.*

{% content-ref url="/pages/CF6lfFSZeOJ5u44sLYZJ" %}
[Project submission, selection and prioritization](/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow/considering-projects.md)
{% endcontent-ref %}

### 2.  Evaluation 

2. We choose an *evaluation manager* for each research paper or project. They commission and compensate expert *evaluators* to rate and discuss the research, following our evaluation template and [guidelines](/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow/evaluation/guidelines-for-evaluators.md). The original research authors are given a chance to publicly respond before we post  these evaluations. *See the link below for further details.*

{% content-ref url="/pages/be11bR0reZtpAtIya4N6" %}
[Evaluation](/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow/evaluation.md)
{% endcontent-ref %}

### 3. Communicating results

We make all of this evaluation work public on [our PubPub page](https://unjournal.pubpub.org/), along with an *evaluation summary.* We create DOIs for each element and submit this work to scholarly search engines. We also present a summary and analysis of our [evaluation ratings data](https://unjournal.shinyapps.io/DataExplorer/). 

\
*We outline some further details in the link below.*

[Communicating results](/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow/communicating-results.md) 

### Flowchart

*See the link below for a full 'flowchart' map of our evaluation workflow*

{% content-ref url="/pages/RvqKciylkdQHvZ8FxPtd" %}
[Mapping evaluation workflow](/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow/mapping-evaluation-workflow.md)
{% endcontent-ref %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/~/changes/531/policies-projects-evaluation-workflow.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 `build a script that syncs our docs to a CMS` 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.