> For the complete documentation index, see [llms.txt](https://sftpmag.gitbook.io/sftp-publishing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sftpmag.gitbook.io/sftp-publishing/editorial-collectives-1/master-working-spreadsheet.md). # Master Working Spreadsheet ### What is the master spreadsheet? Currently, we manage the editorial process using a Google Sheets spreadsheet. It contains all the information you need to know about who is assigned for each piece, what the deadlines are, author payment information, and article status. See below for an example from the PGND collective (click to expand): ![The big master spreadsheet in all its glory - click to zoom, or see insets below.](/files/-MBaxQMa55hNJwGggYoN) Yes, it's huge, but fairly simple if we break it down into parts! Each **row** of the spreadsheet corresponds to a specific article. In this section of the spreadsheet, you'll the names of everybody associated with that particular article: lead and co-editors, proofreaders, fact-checkers, and so on. To find their contact information, check out the [roster](/sftp-publishing/editorial-collectives-1/roster.md). This is your team! Get to know them well, **and communicate early and often.** ![Who's who for each article](/files/-MBazG92vCjrs0i3FjYH) If the article has been selected for translation, you'll find information on who will be translating the article in the rightmost column shown above. Translations are decided upon collaboratively by the editorial collective, the translation working group, and authors. Typically, we aim to have 3-4 translations of features per issue. Articles can be sent to translators once the fact-checking process has finished. Lead editors are responsible for keeping their article's row up-to-date. This is done by updating the detailed status column and the status drop-down menu as the article progresses through the editorial pipeline. The drop-down menu has options like "in edits", "sent to EAL review", or "in proofreading". The detailed status cell is the place to write updates like "sent second draft to authors on 6/27" or "waiting for edits due 5/23". Remember, if you have any problems during the editing process, always contact the EAL and ME in addition to updating the detailed status. ![Status section](/files/-MBaxjSnQeJzYfAHk9SZ) The ME will work with the collective to set initial deadlines for each article. Sometimes articles are delayed (or, if we're lucky, early!). In this case, the lead editor should check with the ME or EAL in order to set appropriate deadlines and update the spreadsheet. This is **very important** as it helps the ME keep tabs of how articles are progressing in order to coordinate between the different stages of the editorial process. ![Deadlines! We love them!](/files/-MBayF_7YKfEB45HmnTD) In this spreadsheet, you'll also find details on article types and lengths. It is very important that authors adhere to the word limits, **especially** if we're going into print. Word counts set the number of pages each article takes, so the page count of each issue depends on word counts for individual articles, as well as the number of articles we're publishing in total. ![](/files/-MBayX0D0o3sE8byIN0-) Articles are typically grouped by type (working group/chapter reports, features, etc). For more information on the magazine departments, see [here.](/sftp-publishing/magazine-departments/overview.md) ![For more info, see the magazine departments page.](/files/-MBb--VM0FwrJSqGlC65) We are always looking to improve this part of the process. If you have any suggestions on how to make this more clear, email the ME (). --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sftpmag.gitbook.io/sftp-publishing/editorial-collectives-1/master-working-spreadsheet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.