Editorial Support

Highly specialised requests are first checked for feasibility from this information. Please do not send confidential data through the public form; describe it first and agree secure transfer afterwards.

1. 01Enquiry and requirement assessment
2. 02Technical scoping and proposal
3. 03Execution
4. 04Quality review and delivery, with an agreed round of revisions

Read the full project workflow.

In depth: how the work is done

1. Defining the theme and purpose

   The editorial begins with the theme: what is the topic, why does it matter and what was the call for papers? A clear statement of purpose helps readers decide which papers to read. We help editors write an opening that is specific and avoids generic statements about importance.

2. Synthesising contributions

   A good editorial groups papers by theme and explains how they relate, not merely listing them. It identifies agreement, differences in approach and complementary results. We help editors build a map of contributions, drawing on abstracts and papers, and write paragraphs that connect them.

3. Fair and accurate summaries

   Each paper should be summarised in a few sentences that reflect its content and contribution. Over-praise or misstatement is avoided. We check summaries against the abstracts and papers and ask editors to confirm claims. Authors of accepted papers are often shown the text about their contribution.

4. Identifying gaps and future directions

   Beyond summarising, the editorial can indicate what remains unsolved and where research should go. Gaps should arise from the collection and the wider literature, not just editors' preferences. We help editors express them with evidence.

5. Tone and structure

   Editorials are written in a more personal voice than research papers but should be professional. A clear structure with an opening, thematic sections and a closing helps. We edit for flow and consistency.

6. Attribution and references

   Each paper is cited accurately with authors and titles; other cited works must be verified. We help editors check that names, affiliations and citations are correct and consistently formatted.

7. Transparency about the editorial process

   Special issues should describe how papers were handled, including who managed peer review and any conflicts of interest where editors contributed papers. Journals increasingly require such statements. We help editors write transparent process notes.

8. Managing timeline

   Editorials are often the last piece prepared, and delays can hold up publication. Preparing a skeleton early and filling in as papers are accepted saves time. We help editors schedule drafts and review.

9. Acknowledging reviewers, authors and the community

   Editorials should acknowledge the people who made the issue possible: authors, reviewers and the editorial team. Thanks should be accurate and specific without disclosing confidential review information. Mentioning the call for papers, the number of submissions and the acceptance process gives transparency. We help editors prepare acknowledgements that are accurate and respect confidentiality norms.

10. Relating the issue to the journal and field

    A special-issue editorial can connect the collection to the journal's aims and to wider developments, such as new standards or funding programmes. It can also suggest how readers might use the issue, for example in teaching or as a reference for method choice. We help editors add this wider context briefly so the editorial serves as a guide and not merely a preface.

11. Keeping the editorial useful after publication

    An editorial can serve as an entry point to the issue for years if it is written with longevity in mind. Using descriptive section headings, explicit links to each paper and a concise statement of the open questions makes it easy to cite and to use in teaching. We help editors write with that in mind and check that links and identifiers are correct when the issue goes online.

Common pitfalls this service helps avoid

• List of abstracts. An editorial should connect, not just list.
• Inaccurate summaries. Errors embarrass editors and authors.
• Undeclared conflicts. Editors with papers in the issue should say so.
• Generic importance statements. Be specific about why the theme matters.

What good reporting looks like

Support for editorials is documented with a contribution map, a summary accuracy check against the papers, a reference check and a process-transparency note. The editors approve the final text. We do not fabricate contributions, quotations or statistics, and the editorial remains the editors' own.

An illustrative scenario

Hypothetical example written for explanation. It is not a client case, a result or a testimonial.

Imagine guest editors introducing a special issue on energy storage. The first draft lists twelve abstracts. The revised editorial groups papers into materials, system integration and policy, shows which contributions address the same question with different methods, notes that none of the papers examined recycling, and proposes that as a future topic. Each summary is checked against the paper.

Questions to settle before you begin

• What is the theme and why does it matter now?
• How do the papers relate to each other?
• Are summaries accurate?
• What gaps remain?
• Have I declared conflicts of interest?

Key terms

Guest editor

An editor invited to manage a special issue.

Special issue

A collection of papers on a theme.

Contribution map

A summary of how papers relate.

Call for papers

An invitation to submit on a theme.

Process note

A statement of how papers were handled.

Working together on Specialised Scholarly Article Formats projects

Specialised article engagements begin by confirming which format suits your material, since short communications, methods, data, software, protocol and replication papers each have conventions and length limits. We ask for the results, code or datasets that the article describes, the target journal's guidelines and your deadline. Drafting follows the format's structure, and reporting checklists are applied where they exist. Statements about data and code availability reflect what you can actually share. We do not fabricate results, and we do not promise acceptance.

Few projects need a single service in isolation. These are the services most often combined with this one.

• Technical Perspectives

  Support for perspective and viewpoint articles that offer an informed, forward-looking position on a technical topic.

• Commentary & Correspondence

  Support for commentaries and correspondence responding to published work or discussing issues, with respectful, evidence-based argument.

• Short Communications

  Support for short communications that report a focused, timely finding in a compact format, with disciplined selection of data and a tight argument.