# Author Brief/Introduction

When authors' frameworks have been accepted and editors are assigned, the lead editor will send an Author Brief to help guide the shape of the article and communicate important deadlines and information about voice and audience. The lead editor may do this alone, but should include contact information for the co-editor and, if available, technical editor (although they are often assigned later). Briefs should be sent as soon as possible after accepting the framework so that authors can begin working on a first draft with proper guidance. 

Editors should also introduce themselves, which will help create a better working relationship and accountability for both author and editor. 

Here are some templates for the [author brief](https://sftpmag.gitbook.io/sftp-publishing/cfp-submissions-acceptances/author-brief/author-brief-template) and [introduction letter](https://sftpmag.gitbook.io/sftp-publishing/cfp-submissions-acceptances/author-brief/author-editor-introduction). JoEllen's [Guide to Accessible Writing](https://sftpmag.gitbook.io/sftp-publishing/editing-resources-1/our-editors-advice/untitled) has some great pointers on how to structure feedback to authors!


---

# 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/author-brief.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.