# Rejections & Kills/Cuts Emails

There are two instances where we send rejections: 

1. during the selection process, if a pitch is not chosen
2. after the framework is submitted, if we have decided not to accept the pitch. 

In the first case, the email below is sent to the submitting authors. In the second case, the ME can reach out to the authors to provide more detailed reasoning behind rejecting the pitch or modify the email for this instance.

### REJECTION EMAIL TEMPLATE

Dear \_\_\_\_,

Thank you for your submission on \_\_\_\_\_\_\_\_ for Volume X, no. X of Science for the People magazine, \_\_\_\_\_. We received a high volume \[#] of fantastic submissions, and we are only able to accept \_\_\_\_\_ features for this issue \[due to budget and printing constraints]. Our editorial collective enjoyed reading your proposal, but unfortunately, has chosen not to publish your submission in this issue. \[Optional: Boilerplate feedback or feedback from the EC is available upon request.] \
\
We encourage you to stay in touch and let us know about other article ideas you have in the future. We publish our calls for proposals periodically on our [website](https://magazine.scienceforthepeople.org/), as well as on our [Twitter feed](https://twitter.com/sftpmag). If you are interested in becoming a part of the editing process by joining a future editorial collective, please let us know. Likewise, if you have any questions or comments feel free to reach out. We hope to have the opportunity to work with you!\
\
Finally, we are collecting demographic information on everyone who submits ideas to Science for the People to help us stay accountable to the social justice mission of Science for the People. If you have not already done so, please fill out our questionnaire,[ here](https://airtable.com/shrAqWlf8g2cLQuHW). Any responses shared publicly will be anonymized; your responses will not be shared outside the editorial collective.

In solidarity,

Vol. XXX, No. XXX Editorial Collective

\[Name]

Managing Editor, Science for the People

**Boilerplate reasons for rejection**

Was great but didn't fit (as we received close to X submissions), did not respond to the theme of the issue\
\ <br>


---

# 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://sftpmag.gitbook.io/sftp-publishing/cfp-submissions-acceptances/accepting-articles/rejections-and-kills-cuts.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.