[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-378208-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-378208-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","em-editorial-office-checklist","EM-Editorial-Office-Checklist","","Editorial Office Functionality Checklist outlines the capabilities of an online editorial management environment for journal operations. It covers authentication and role-based administration, security rules for login and record editing, and template letter setup with merge fields and event-triggered sending. The checklist also describes manuscript workflow controls including flags, editor searches, submission routing, desk rejections, bouncing, user registration and duplicate merging, editor availability visibility, and configurable submission and reviewer-capture question formats.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/forms/","Forms",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/em-editorial-office-checklist/378208/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/em-editorial-office-checklist/378208.png","ImageObject",442,249,{"name":42,"@type":43},"Hazel","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-21","2026-09-24",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",6,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What login and access controls are covered in the checklist?","Question",{"text":63,"@type":64},"The checklist includes system login across web pages, single-sign-on using ORCID credentials, web-based administration for role permissions, and security rules based on publisher policy.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does the checklist describe handling letters and communications?",{"text":68,"@type":64},"It covers configuring template letters with merge fields, triggering letters via specific system events, and sending communications to authors directly within author portal or manuscript service interfaces.",{"name":70,"@type":61,"acceptedAnswer":71},"What workflow features for submissions and editor assignment are listed?",{"text":72,"@type":64},"It includes submission flags and metadata associations, editor searches and history tracking for flag on/off, assignment to editors by section or role, editor chains for multi-editor steps, desk reject decisions without assignment, and bouncing submissions back for resubmission or cleanup.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},378208,1791025105,{"code":4,"msg":82,"data":83},"success",[84,89,94,99,104,109,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":86,"show_sort_weight":87,"slug":88},11,"Presentations",90,"presentations",{"id":90,"doc_module":22,"doc_module_name":25,"category_name":91,"show_sort_weight":92,"slug":93},12,"Resumes",80,"resumes",{"id":95,"doc_module":22,"doc_module_name":25,"category_name":96,"show_sort_weight":97,"slug":98},14,"Invoices",70,"invoices",{"id":100,"doc_module":22,"doc_module_name":25,"category_name":101,"show_sort_weight":102,"slug":103},15,"Posters",60,"posters",{"id":105,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},16,"Social Media",50,"social-media",{"id":110,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":111,"slug":112},17,40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":110,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":136,"language":137,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":12,"update_tm":141,"read_time":30},137441390410,"https://ap-avatar.wpscdn.com/avatar/2000252f4ab5702993?_k=1776741390130283984","Editorial Office Functionality Checklist  \n\n| | Editorial Office can display system login box on any web page, such as the journal online site. |\n| --- | --- |\n| | For convenience, Editorial Office staff can use their ORCID username and password for single-sign-on (SSO) across multiple journals. |\n| | Editorial Office uses web-based administration tools to control user roles and permissions. |\n| | Journal office can select security rules for log-in and user record editing based on publisher policy. |\n| | Editorial Office uses web-based tools to set up template letters with appropriate merge fields. |\n| | Editorial Office can “trigger” letters by associating template letters with specific system events. |\n| | Editorial Office can configure dozens of graphical “flags” to display next to the manuscript which indicate action items and idiosyncrasies at-a-glance. |\n| | Submission “flags” can be associated with specific metadata entries, including custom question responses. |\n| | Editors can create and save searches for submissions with specific “flags.” |\n| | Editors can view when a particular flag was turned on or off within submission history. |\n| | Editorial Office sees “Search Submissions – Results” and “Saved Search Results”, in the modern, streamlined, PowerGrid. PowerGrid allows users to resize, re-order, lock, and include/exclude data columns according to personal preference. |\n| | Editorial Office can receive new manuscript submissions from Authors, or manuscripts can be automatically assigned to Editors based on journal section or Editorial role. |\n| | Editorial Office can “bounce” submissions back to Authors for resubmission (for clean-up, missing materials, etc. ) . |\n| | Editorial Office can edit submissions prior to assignment to an Editor, or “bouncing” them back to the Author. |\n| | Editorial Office can remove spurious or test submissions and no submission charge is made for such removed submissions. |\n| | Early decisions (“desk reject”) can be made without Editor assignment. |\n| | Editorial Office can easily “proxy” transactions on behalf of Authors, Reviewers, and Editors. |\n| | Authors can be required to explicitly agree to configurable Editorial Office policies and terms via an “I accept” checkbox. |\n| | Editorial Office can easily register new users. Editorial Office has tools to identify and merge duplicate user records. |\n| | When assigning manuscripts to Editors, the Editorial Office can see information about the Editor’s availability and current assignments. |\n| | Editorial Office can configure submission steps to capture Author recommended and/or opposed Reviewers. |\n\n\n| | Editorial Office can configure Editor chains, thereby allowing assignment to multiple Editors in a single step. Configurable by article type. |\n| --- | --- |\n| | Editorial Office can swap one Editor for another without disrupting the rest of the configured multi-Editor chains. |\n| | Editorial Office can prevent an Editor from having access to a submission, if that Editor was a contributing Author for that submission. |\n| | Editorial Office can filter Editor searches by unavailable dates. |\n| | Editorial Office can configure Author submission questions that include radio buttons, drop-down lists, dates, free text, check boxes. Questions can be mandatory for new or revised manuscripts and can be limited by word or character count. Questionnaires are configurable by article type. Two Author questionnaires can be used during the workflow of a manuscript: one containing submissionrelated questions and one containing Author-and Co-Author questions. |\n| | Editorial Office can associate metadata identifiers with data elements, such as custom questions and submission types to facilitate\u003Cbr>smooth transfer of manuscript data between journals and platforms (such as publisher portals or third-party author services and tools) . |\n| | If Authors are using an Author Portal or Manuscript Service provider for submission, Editorial Office can send communi","cbCaig1cDyYKTsPD","https://ap.wps.com/l/cbCaig1cDyYKTsPD","pdf",264793,7,"English","# Editorial Office Functionality Checklist\n## Authentication, roles, and security controls\n## Templates, event-triggered letters, and flags\n## Submission workflow, assignment, and editor chains\n## User registration and identifier management\n## Manuscript numbering, status configuration, and article types","[{\"question\":\"What login and access controls are covered in the checklist?\",\"answer\":\"The checklist includes system login across web pages, single-sign-on using ORCID credentials, web-based administration for role permissions, and security rules based on publisher policy.\"},{\"question\":\"How does the checklist describe handling letters and communications?\",\"answer\":\"It covers configuring template letters with merge fields, triggering letters via specific system events, and sending communications to authors directly within author portal or manuscript service interfaces.\"},{\"question\":\"What workflow features for submissions and editor assignment are listed?\",\"answer\":\"It includes submission flags and metadata associations, editor searches and history tracking for flag on/off, assignment to editors by section or role, editor chains for multi-editor steps, desk reject decisions without assignment, and bouncing submissions back for resubmission or cleanup.\"}]","EM-Editorial-Office-Checklist | PDF",1790228959]