MSP — Editflow — Key Advantages

<!DOCTYPE HTML> <html lang="en"> <head> <title> MSP — Editflow — Key Advantages </title> <meta charset="utf-8"> <meta name="viewport" content="width=500, initial-scale=1.0"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <link href="/msp_org/static/img/favicon.ico" type="image/vnd.microsoft.icon" rel="icon"> <link href="/msp_org/static/img/favicon.ico" rel="shortcut icon"> <script type="text/javascript" src="//use.typekit.net/lqn0uwr.js"></script> <script type="text/javascript">try{Typekit.load();}catch(e){}</script>  <link href="/msp_org/static/css/glyphicons.css" type="text/css" rel="stylesheet"> <link href="/msp_org/static/css/style.min.css?v=2024-12-14" type="text/css" rel="stylesheet">  <script type="text/javascript" src="/msp_org/static/js/respond.min.js"></script> <script type="text/javascript" src="/msp_org/static/js/collapser.js"></script> <script type="text/javascript" src="/msp_org/static/js/copypasta.js"></script> </head> <body> <div id="upjump" title="Jump to Top of Page" onclick="javascript:window.location.href='#page';">⇧</div> <div id="body-double"> <div id="page-wrapper"> <div id="page">  <div id="head"> <div id="h1-wrapper"> <h1> <a href="/"> <span><span>MSP</span></span> </a> </h1> </div> <a href="/"> <div id="tagline"> nonprofit scientific publishing </div> </a> <nav id="top-menu"> <table cellpadding="0" cellspacing="0"> <tr> <td > <a href="/publications/main/" class="menu-item" >  Publications  </a> <div class="submenu"> <p> <a href="/publications/main/" class="submenu-item" >  Our Publications  </a> </p> <p> <a href="/publications/journals/" class="submenu-item spaced " >  Journals  </a> </p> <p> <a href="/publications/books/" class="submenu-item " >  Books  </a> </p> <p> <a href="/publications/websites/" class="submenu-item " >  Celebratio Mathematica  </a> </p> <p> <a href="/publications/subs/" class="submenu-item spaced " >  Subscriptions  </a> </p> <p> <a href="/publications/s2o/" class="submenu-item " >  Subscribe to Open  </a> </p> <p> <a href="/publications/oa/" class="submenu-item " >  Open Access  </a> </p> <p> <a href="/publications/ethics/" class="submenu-item spaced " >  Principles and Ethics  </a> </p> <p> <a href="/publications/policies/" class="submenu-item " >  Author Policies  </a> </p> <p> <a href="/publications/authquotes/" class="submenu-item " >  Author Testimonials  </a> </p> </div> </td> <td class="current" > <a href="/editflow/main/" class="menu-item" >  EditFlow  </a> <div class="submenu"> <p> <a href="/editflow/main/" class="submenu-item" >  What is EditFlow?  </a> </p> <p> <a href="/editflow/key/" class="submenu-item spaced " >  Key Advantages  </a> </p> <p> <a href="/editflow/setup/" class="submenu-item " >  Setup Options  </a> </p> <p> <a href="/editflow/video/" class="submenu-item " >  Demo Videos  </a> </p> <p> <a href="/editflow/journals/" class="submenu-item spaced " >  Client Journals  </a> </p> <p> <a href="/editflow/quotes/" class="submenu-item " >  User Testimonials  </a> </p> </div> </td> <td > <a href="/services/main/" class="menu-item" >  Services  </a> <div class="submenu"> <p> <a href="/services/main/" class="submenu-item" >  Our Services  </a> </p> <p> <a href="/services/jprod/" class="submenu-item " >  Journal Production  </a> </p> <p> <a href="/services/editflow/" class="submenu-item " >  EditFlow  </a> </p> </div> </td> <td > <a href="/blog/main/" class="menu-item" >  Blog  </a> <div class="submenu"> <p> <a href="/blog/main/" class="submenu-item" >  The Blazing Papyrus  </a> </p> </div> </td> <td > <a href="/about/main/" class="menu-item" >  About Us  </a> <div class="submenu"> <p> <a href="/about/main/" class="submenu-item" >  About MSP  </a> </p> <p> <a href="/about/staff/" class="submenu-item " >  Staff Members  </a> </p> <p> <a href="/about/board/" class="submenu-item " >  Board of Directors  </a> </p> <p> <a href="/about/culture/" class="submenu-item spaced " >  Work Culture  </a> </p> <p> <a href="/about/jobs/" class="submenu-item " >  Work Opportunities  </a> </p> <p> <a href="/about/privacy/" class="submenu-item " >  Privacy Policy  </a> </p> <p> <a href="/about/contacts/" class="submenu-item spaced " >  Contact Us  </a> </p> </div> </td> </tr> </table> </nav> </div>  <div id="content-wrapper"> <div id="content">  <header> <h2 class="pagetitle"> <u>EditFlow® — Key Advantages</u> </h2> </header>     <aside> <div class="floatbox global "><h5> Quick Links: </h5><p><h6><a href='/editflow/' >Introduction</a></h6><h6><a href='/editflow/key/' >Key Advantages</a></h6><h6><a href='/editflow/quotes/' >Testimonials from users</a></h6><h6><a href='/editflow/journals/' >Publications using EF</a></h6><h6><a href='/editflow/setup/' >Standard setup options</a></h6><h6><a href='/editflow/video/' >Demo videos</a></h6><h6><a href='/editflow/screen/' >Screenshots</a></h6><h6><a href='/forms/editflow/' >Get EditFlow</a></h6></div> </aside> <section id="s575" class="titledbox pushdown " >   <div id="seg-575" class="justifiedtext textbox pushright " >    <p><p> EditFlow saves you time by keeping information organized and available, and making it easy to act on that information. </div>  </section>   <section id="s576" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-576');" class="active triangled" > Powerful overview — lots of information, few clicks <span class="x1 halflings halflings-play rotate180" id="seg-576-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-576-co" style="display:none" ></span></a></h5></header>   <div id="seg-576" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow’s interface is tailor-made for journals of the size that’s typical in mathematics, allowing you to first survey at a glance the whole pipeline of the journal, then dive straight into working on an article, eliminating extraneous clicks and obstacles in between. </div>  </section>   <section id="s581" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-581');" class="active triangled" > Qualified help is always at hand <span class="x1 halflings halflings-play rotate180" id="seg-581-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-581-co" style="display:none" ></span></a></h5></header>   <div id="seg-581" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> Switching to new software can be intimidating. That’s why we’re with you and your users every step of the way, with quick hands-on support via email or video-chat. <p> Support inquiries are handled directly by programmers and other people deeply familiar with EditFlow, who are knowledgeable about it and able to influence its direction, or explore and fix a bug. Issues are resolved quickly and competently, and you’re not subjected to several layers before reaching somebody who can help you. </div>  </section>   <section id="s577" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-577');" class="active triangled" > Authors and referees: not yet another username and password <span class="x1 halflings halflings-play rotate180" id="seg-577-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-577-co" style="display:none" ></span></a></h5></header>   <div id="seg-577" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> Infrequent users of the system (authors and referees) are not asked to register and then remember yet another login and password; instead, EditFlow allows their access by authenticating with unique tokens they receive by email. (Of course, staff and editors can only access the system by using a username and password.) </div>  </section>   <section id="s580" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-580');" class="active triangled" > First, get a quick opinion <span class="x1 halflings halflings-play rotate180" id="seg-580-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-580-co" style="display:none" ></span></a></h5></header>   <div id="seg-580" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow gives the option of first requesting fast advice about an article from an outside expert, before committing to requesting full referee reports, and keeps the two types of requests separate. This allows editors to efficiently filter out submissions that are not a good fit (and can be part of more involved workflows). Continuing an advice request with a full-report referee request is straightforward. </div>  </section>   <section id="s231" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-231');" class="active triangled" > Find referees from a curated database of mathematicians <span class="x1 halflings halflings-play rotate180" id="seg-231-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-231-co" style="display:none" ></span></a></h5></header>   <div id="seg-231" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> As a standard option, editors can be given access to an extensive “address book” of mathematicians, most useful when seeking reviewers. These names and email addresses are not just shared and refreshed by most journals using EditFlow, but also actively curated by our staff, who eliminate duplications and investigate bounced email messages. (This data is governed by <a href='/about/privacy/' >our privacy policy</a>, and is compliant with privacy regulations, including Europe’s GDPR.) </div>  </section>   <section id="s578" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-578');" class="active triangled" > Collect a complete record <span class="x1 halflings halflings-play rotate180" id="seg-578-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-578-co" style="display:none" ></span></a></h5></header>   <div id="seg-578" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow makes it easy to record the inevitable interactions that happen outside the system: a referee request made by phone, a report received directly by email. Relevant outside email messages can be added to an article’s record. <p> Editors can act on behalf of their referees, chief editors can act on behalf of their editors, and staff can seamlessly assist along the way. </div>  </section>   <section id="s484" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-484');" class="active triangled" > Your data still belongs to you <span class="x1 halflings halflings-play rotate180" id="seg-484-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-484-co" style="display:none" ></span></a></h5></header>   <div id="seg-484" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> We don’t hold your data hostage. While we do securely store all journal records, you are the owner of your data and can even store backups on your own servers. This makes it easier for you to take your journal history with you if you ever decide to leave EditFlow, but we’re confident you won’t want to. </div>  </section>   <section id="s579" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-579');" class="active triangled" > Templates — write in your voice <span class="x1 halflings halflings-play rotate180" id="seg-579-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-579-co" style="display:none" ></span></a></h5></header>   <div id="seg-579" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow allows editors to not only modify the text of each outgoing email, but also personalize and save for future use the template itself that generates that class of emails (e.g., the several acceptance, rejection and referee-request variants). Additional journal-wide templates can be added as needed. </div>  </section>   <section id="s601" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-601');" class="active triangled" > Collective or independent decisions <span class="x1 halflings halflings-play rotate180" id="seg-601-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-601-co" style="display:none" ></span></a></h5></header>   <div id="seg-601" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> Editors can make decisions independently, submit to the review of a chief editor, make recommendations to an executive committee, or collect votes from the whole editorial board. The process can be set up to be flexible or have strict rules and deadines. </div>  </section>   <section id="s582" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-582');" class="active triangled" > Visibility to editors, as transparent as you want <span class="x1 halflings halflings-play rotate180" id="seg-582-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-582-co" style="display:none" ></span></a></h5></header>   <div id="seg-582" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow can be configured so that a regular editor can see only the articles they handle, or also see articles that have been recommended for a decision, or see all articles in process. <p> If shown an article they’re not handling, an editor can see the manuscripts, or also see the referee report but not the identity of the reviewers, or see everything: reports, identities and discussions. <p> We can also configure EditFlow so that an editor, while not shown some given article in the journal listing, could nonetheless access its page and data if explicitly sent the article’s URL (this can be useful, for example, if the chief editor wants to consult only a specific editor before assigning the article to a handling editor). <p> Of course, editors can never see any details of an article that they authored. </div>  </section>   <section id="s584" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-584');" class="active triangled" > Programmable flexibility <span class="x1 halflings halflings-play rotate180" id="seg-584-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-584-co" style="display:none" ></span></a></h5></header>   <div id="seg-584" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow can accommodate all manner of workflows and decision models, from the simplest editor-decides-alone models to multi-stage/multi-layered processes, including votes and gatekeepers. <p> We can freely configure which actions are available to whom and for which article-states. <p> To give you an example of a complicated workflow that’s made easy with EditFlow, here’s one that is being adopted by some journals: <blockquote class="small"> A submitted article is assigned to a handing editor, who first requests quick opinions from outside experts to gauge fit and interest. Then, after collecting such quick opinions in EditFlow, the editor makes a recommendation to the chief editors, either to reject the article or to proceed to full-blown peer review. If a chief editor agrees, the article goes back to the care of the handling editor, who sends the article to referees for full review reports. After collecting the full reports, the handling editor makes a recommendation as to whether to accept, request a revision of, or reject the article. </blockquote> This is just one example of the possible combinations and trajectories that can be enabled in EditFlow. </div>  </section>   <section id="s586" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-586');" class="active triangled" > Multiple roles <span class="x1 halflings halflings-play rotate180" id="seg-586-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-586-co" style="display:none" ></span></a></h5></header>   <div id="seg-586" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> Three layers of standard editorial roles are available (chief editor, senior editor, regular editor), with their titles, visibility permissions and available actions configurable. A role can be journal-wide or restricted to a section or special issue, and can be further subdivided functionally, starting with the assignment of distinct titles. <p> A viewer role is available for an inactive academic supervisor. A preferred-referee role is available for “editors” whose role is only to give advice or reports on specific articles. Several staff roles are also available. </div>  </section>   <section id="s585" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-585');" class="active triangled" > Sections and special issues <span class="x1 halflings halflings-play rotate180" id="seg-585-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-585-co" style="display:none" ></span></a></h5></header>   <div id="seg-585" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> A journal can be sliced into sections (for example, to separate areas or subfields, or types of articles), even with their own section-specific editors and workflows. <p> Similarly for special issues, which can each have their own guest editor and procedures. As an option, submission to a special issue could be allowed only from the invited authors that follow a secret URL. </div>  </section>   <section id="s232" class="titledbox pushright " > <header><h5><a onclick="CollapseExpand('seg-232');" class="active triangled" > Statistics and reports <span class="x1 halflings halflings-play rotate180" id="seg-232-xp" ></span><span class="x1 halflings halflings-play rotate90" id="seg-232-co" style="display:none" ></span></a></h5></header>   <div id="seg-232" class="justifiedtext textbox-hidden " style="display:none;" >    <p><p> EditFlow provides a direct interface to a good number of aggregated reports, collecting both raw data and computed statistics. Adding to the interface a new journal-specific custom report is as routine for our staff as adding a custom email template. All reports are downloadable as CSV files and thus easily opened by Excel. </div>  </section>   <section id="s587" class="titledbox pushdown pushright " > <a href="#s587" class="para-selflink intext" >¶</a> <header><h5> Be our partner</h5></header>   <div id="seg-587" class="justifiedtext textbox " >    <p><p> Our publisher clients are important partners in the direction and development of EditFlow. Many features are developed in collaboration with our partners, to serve their evolving needs. This is one of the advantages we offer as a smaller, agile firm. </div>  </section>   <section id="s631" class="titledbox pushright " > <a href="#s631" class="para-selflink intext" >¶</a> <header><h5><a href="/forms/editflow/" > Contact us  <span class="x1 halflings halflings-menu-right"></span></a></h5></header>   <div id="seg-631" class="justifiedtext textbox " >    <p><p> <a href='/forms/editflow/' >Send us an email</a> and we’ll be happy to offer you a tour of EditFlow, or set up a demo instance so you can try it yourself. </div>  </section>   <section id="s477" class="titledbox pushright " > <a href="#s477" class="para-selflink intext" >¶</a> <header><h5><a href="/editflow/quotes/" > Testimonials from users  <span class="x1 halflings halflings-menu-right"></span></a></h5></header>   </section>   <section id="s596" class="titledbox pushright " > <a href="#s596" class="para-selflink intext" >¶</a> <header><h5><a href="/editflow/journals/" > List of journals using EditFlow  <span class="x1 halflings halflings-menu-right"></span></a></h5></header>   </section>     <footer class="pushright"> <nav> <ul class="flat"> <li> <a href="/about/main/" > About Us </a> </li> <li> <a href="/about/main/"> This is MSP </a> </li> <li> <a href="/about/staff/"> Staff Members </a> </li> <li> <a href="/about/board/"> Board of Directors </a> </li> <li> <a href="/about/culture/"> Work Culture </a> </li> <li> <a href="/about/jobs/"> Work Opportunities </a> </li> <li> <a href="/about/privacy/"> Privacy Policy </a> </li> <li> <a href="/about/contacts/"> Contact Us </a> </li> </ul> <ul class="flat"> <li> <a href="/publications/main/" > Publications </a> </li> <li> <a href="/publications/journals/"> Journals </a> </li> <li> <a href="/publications/books/"> Books </a> </li> <li> <a href="/publications/websites/"> Celebratio Mathematica </a> </li> <li> <a href="/publications/subs/"> Subscriptions </a> </li> <li> <a href="/publications/s2o/"> Subscribe to Open </a> </li> <li> <a href="/publications/oa/"> Open Access </a> </li> <li> <a href="/publications/ethics/"> Principles and Ethics </a> </li> <li> <a href="/publications/policies/"> Author Policies </a> </li> <li> <a href="/publications/authquotes/"> Author Testimonials </a> </li> </ul> <ul class="flat"> <li> <a href="/editflow/main/" > EditFlow </a> </li> <li> <a href="/editflow/main/"> This is EditFlow </a> </li> <li> <a href="/editflow/key/"> Key Advantages </a> </li> <li> <a href="/editflow/setup/"> Setup Options </a> </li> <li> <a href="/editflow/video/"> Demo Videos </a> </li> <li> <a href="/editflow/journals/"> Client Journals </a> </li> <li> <a href="/editflow/quotes/"> User Testimonials </a> </li> </ul> <ul class="flat"> <li> <a href="/services/main/" > Services </a> </li> <li> <a href="/services/jprod/"> Journal Production </a> </li> <li> <a href="/services/editflow/"> EditFlow </a> </li> </ul> <ul class="flat"> <li> <a href="/blog/main/" > Blog </a> </li> <li> <a href="/blog/main/"> The Blazing Papyrus </a> </li> </ul> </nav> <p class="clear"> <a href="/"><img width="235" height="23" src="/msp_org/static/img/msp-logo.png" alt="Mathematical Sciences Publishers"></a> <br> © 2012–2025 MSP.  All rights reserved. </p> </footer>  </div>  </div>  </div>  </div>  </div>  <script async defer src="https://eye.msp.org/app.js"></script> <noscript><img src="https://eye.msp.org/image.gif" alt=""></noscript> </body> </html>

CINXE.COM

MSP — Editflow — Key Advantages