As an Editor, how do I send and receive chapters in the workflow for review?

Last updated on June 12, 2025

If you are an Editor on a project, you will know a chapter is ready for you to review because you will receive an email notification that the chapter has been sent to you in the workflow. If there are multiple editors on your project, you will all be notified simultaneously.

Similarly, if you are ready to return a chapter to a contributor or to an Elsevier staff member, you will do this by sending the chapter in the workflow.

To send a chapter from the Project Overview page and view more information regarding workflow:

To Send a chapter, select 'Send to Stage' to populate the Send window.

From here, select the workflow stage to which you would like to send the chapter.

Chapters can be sent both forward and backward in the workflow. You can also skip stages and return to them at a later time. A full list of the workflow stages can be found at the bottom of this page.

Once you have selected a stage, you can enter additional information in the Note field if needed and press 'Send'. All recipients with access to the chapter at that stage will be notified. i.e. all contributors will be notified at Contributor Draft stage, all Editors at Initial and Final Editor Review stages, etc.

      

What are the workflow stages?

Workflows can be customized by an Elsevier staff member depending on the best set-up for your project so the below stages may appear in a different sequence or have added or fewer steps. Workflow stage names can also be customized and may vary according to project. We recommend looking at the top banner of the Dates and Milestones section of the project overview page to confirm the workflow for your project.

Edited Title Workflow

  • Not Started/Ready: This stage indicates a chapter is not currently in a workflow stage. Once a chapter has been moved out of this stage of the workflow, it is generally not recommended to send it back here as this removes all associated due dates and can indicate that no one has started working in the chapter.
  • Contributor Draft: Contributors submit a draft of their chapter for submission, then send to Initial Editor Review.
  • Initial Editor Review:: Editor reviews the chapter and provides feedback for the Contributor, then sends to Revised Draft.
  • Review: an external reviewer or another project member other than an Editor or Elsevier staff member provides a review of the chapter. Can be blind or non-blind.
  • Revised Draft: Contributor corrects any feedback from Editor and finalizes chapter, then sends to Final Editor Review.
  • Final Editor Review: Editor reviews the revised chapter (sending it back for additional edits if necessary) and confirms that it is complete, sending it to Staff Review.
  • Staff Review: Elsevier staff member reviews the chapter, sending back to Editor if changes are necessary. Once finalized, Elsevier staff member sends on to Production. Once a chapter has been sent to Staff Review, you will not have access to it unless an Elsevier staff member returns it to you.
  • Production: Production are where post-authoring and editing steps – like copyediting and indexing – take place before the book is transmitted for publication.

Monograph Title Workflow

  • Not Started/Ready: This stage indicates a chapter is not currently in a workflow stage. Once a chapter has been moved out of this stage of the workflow, it is generally not recommended to send it back here as this removes all associated due dates and can indicate that no one has started working in the chapter.
  • Draft: Author submits a draft of their chapter then sends to Staff Review.
  • Staff Review: An Elsevier staff member reviews the chapter, sending back to the Author if changes are necessary. Once finalized, Elsevier staff send the chapter on to Production.
  • Production: Production are where post-authoring and editing steps – like copyediting and indexing – take place before the book is transmitted for publication.

Did we answer your question?

Related answers

Recently viewed answers

Functionality disabled due to your cookie preferences

For further assistance: