> 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/policies-projects-evaluation-workflow/considering-projects/applied-and-policy-track.md). # "Applied and Policy" Track > See some of the output of this stream [here](https://unjournal.pubpub.org/search?q=%22applied+stream%22+%2Bsummary). ## Why have an “[Applied & Policy Stream](#user-content-fn-1)[^1]”? Much of the most impactful research is not aimed at academic audiences and may never be submitted to academic journals. It is written in formats that are very different from traditional academic outputs, and cannot be easily judged by academics using the same standards. Nonetheless, this work may use technical approaches developed in academia, making it important to gain expert feedback and evaluation. The Unjournal can help here. However, to avoid confusion, we want to make this clearly distinct from our main agenda, which focuses on impactful academically-aimed research. Our “Applied & Policy Stream” will be clearly labeled as separate from our main stream. This may constitute roughly 10 or 15% of the work that we cover. Below, we refer to this as the “applied stream” for brevity. ## What should be included in the Policy stream? Our considerations for prioritizing this work are generally the same as for our academic stream – is it in the fields that we are focused on, using approaches that enable meaningful evaluation and rating? Is it already having impact (e.g., influencing grant funding in globally-important areas)? Does it have the potential for impact, and if so, is it high-quality enough that we should consider boosting its signal? We will particularly prioritize policy and applied work that uses technical methods that need evaluation by research experts, often academics. [This could include ](#user-content-fn-2)[^2]a range of applied research from EA/GP/LT linked organizations such as GPI, Rethink Priorities, Open Philanthropy, FLI, HLI, Faunalytics, etc., as well as EA-adjacent organizations and relevant government white papers. \\ ## How should our (evaluation etc.) policies differ here? *Ratings/metrics*: As in the academic stream, this work will be evaluated for its credibility, usefulness, communication/logic, etc. However, we are not seeking to have this work assessed by the standards of academia in a way that yields a comparison to traditional journal tiers. Evaluators: Please ignore these parts of our interface; if you are unsure if it is relevant feel free to ask. *Evaluator selection, number, pay:* Generally we want to continue to select academic research experts or non-academic researchers with strong academic and methodological background to do these evaluations. [A key purpose of this applied stream is largely to bring research expertise](#user-content-fn-3)[^3], particularly from academia, to work that is not normally scrutinized by such experts. The compensation may be flexible as well; in some cases the work may be more involved than for the academic stream and in some cases less involved. As a starting point we will begin by offering the same compensation as for the academic stream. *Careful flagging and signposting:* To preserve the reputation of our academic-stream evaluations we need to make it clear, wherever people might see this work, that it is not being evaluated by the same standards as the academic stream and doesn't “count” towards those metrics. ### Authors' permission in the Applied Stream This research is more likely to fall into the category of ["Direct evaluation" track](/the-unjournal-project-and-communication-space/policies-projects-evaluation-workflow/considering-projects/direct-evaluation-track.md#direct-evaluation-of-impactful-work), "already influencing a substantial amount of funding in impact-relevant areas, or substantially influencing policy considerations". If the research itself is being funded by a global-impact focused foundation or donor, this will also constitute a strong *prima facie* reason to commission an evaluation (without requiring the authors' consent). See [this post on the EA Forum](https://forum.effectivealtruism.org/posts/N3hsGxSPNMQS4wADy/should-the-unjournal-evaluate-1-research-outputs-per). [^1]: Note: we mostly called this the ‘Non-academic stream’ in the past. We’re revising this term to be clearer and more descriptive. [^2]: It could also include the strongest work published or link-posted on the EA Forum, where it is written in the style of a long-form research report. [^3]: While non career researchers and non-academics have a lot to offer in terms of this feedback, this is largely already provided by places like the Effective Altruism Forum. --- # 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://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/policies-projects-evaluation-workflow/considering-projects/applied-and-policy-track.md?ask=&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.