Manuscript & Publication Services

Specialised Scholarly Article Formats

Support for short communications, brief reports, research letters, technical notes, methods, protocol, data and software papers, replication studies, registered reports and perspectives.

  • Services in this pathway15
  • DivisionManuscript & Publication
  • Journal acceptanceNever guaranteed

Specialised formats have their own conventions, length limits and reviewer expectations. Support covers scope reduction, structure, reporting checklists and venue fit.

Integrity note. All manuscript support is based on genuine research, author-provided data, documented methods and appropriate expert input. We never invent results, citations or author contributions, and we do not guarantee acceptance.

Services

Services in this pathway (15)

  • #119

    Short Communications

    Support for short communications that report a focused, timely finding in a compact format, with disciplined selection…

  • #120

    Brief Reports

    Support for brief reports presenting concise studies or findings in a condensed IMRaD structure.

  • #121

    Research Letters

    Support for research letters, which communicate significant findings quickly to a specialist readership in a highly…

  • #122

    Technical Notes

    Support for technical notes that describe a technique, correction, improvement or practical finding too brief or narrow…

  • #123

    Methods Papers

    Support for methods papers that present a new or improved method, with clear algorithm or protocol description…

  • #124

    Protocol Papers

    Support for protocol papers that describe planned studies or reviews before results exist, so that methods are…

  • #125

    Data Papers

    Support for data papers that describe a dataset, its collection, quality and reuse potential, so that others can find…

  • #126

    Software Papers

    Support for software papers that describe research software, its functionality, design, usage and validation, in the…

  • #127

    Replication Studies

    Support for reporting replication studies that re-test previously published findings, including departures from the…

  • #128

    Negative Results Articles

    Support for articles reporting results that did not confirm expectations, framed so that other researchers can learn…

  • #129

    Registered Reports

    Support for registered-report formats in which hypotheses and methods are peer-reviewed before data collection.

  • #130

    Engineering Design & Innovation Papers

    Support for papers presenting engineering designs or innovations, including the design problem, novelty, evaluation and…

  • #131

    Technical Perspectives

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

  • #132

    Commentary & Correspondence

    Support for commentaries and correspondence responding to published work or discussing issues, with respectful…

  • #133

    Editorial Support

    Support for editorials, introductions to special issues and similar editorial pieces, including synthesis of…

Why specialised formats

Choosing a specialised format

Why specialised formats exist

Not every contribution is a full original research article. Technical notes report a method, a result or a correction concisely; brief reports present preliminary but sound findings; data papers describe datasets and how they were collected; registered reports peer review the study design before results exist; commentaries and perspectives offer argument or viewpoint; and some journals publish software, method or protocol articles. Each format has its own length, structure and expectations, and choosing the right one increases the chance that the paper is judged on its merits. We help authors select and execute the format that fits.

Choosing the format

Match the format to the contribution: if the main value is the data, write a data paper; if it is a small, complete result, a brief report or note; if it is a viewpoint, a perspective; if you want design-stage review, a registered report. Check the journal's article-type list and word limits.

Submit a presubmission enquiry if the journal accepts them. We help prepare enquiries.

Examples of judging fit for a short format

Suppose a team has developed a modification to a standard test method and validated it on a handful of materials. A technical note may suit if the modification is the main contribution; a full article suits if the modification yields new understanding. Suppose another team has built a labelled dataset of vibration signals from a test rig. A data paper suits, provided the rig, the faults and the labels are well documented. Suppose a third team wants to test a hypothesis about a control algorithm on hardware. A registered report may suit if the design is sound and the venue offers it.

These are illustrative scenarios. The right choice depends on the target journal's article types and on the maturity of the results.

Peer review expectations for different formats

Reviewers apply format-specific criteria. For technical notes, they ask whether the point is correct, new and useful. For data papers, they test whether the data are accessible, well described and of adequate quality. For registered reports, they assess whether the design can answer the question and whether the analysis plan is complete. For commentaries, they ask whether the argument is well founded and fair.

Aligning the manuscript with these criteria and answering the likely questions in the text shortens review. We help authors read the journal's reviewer guidelines and respond to them.

Always check the journal's current article-type definitions, since they vary between publishers and change over time.

Format guides

Guides to individual formats

Technical notes and brief reports

A technical note focuses on a single idea, such as an improved calculation, a corrected formula, a new apparatus detail or a concise validation. It usually has a short introduction, a focused method, a limited set of results and a brief conclusion, with a strict word limit. Brief reports present results from a small study or preliminary finding with enough detail to be useful.

The key challenge is concision without losing the essentials. We help trim, prioritise the key figure and make sure the contribution is clear in the first paragraph.

Data papers and dataset documentation

A data paper describes a dataset: why it was created, how data were collected and processed, quality control, structure, formats, licences and potential uses. It does not need to present scientific conclusions, but it must provide enough information for others to reuse the data. Deposit the data in a recognised repository with a persistent identifier and provide metadata following community standards.

We help structure the description, create data dictionaries and check that units, versions and licences are clear.

Registered reports

In a registered report, the introduction, hypotheses and methods are peer reviewed before data collection, and acceptance in principle depends on the quality of the design rather than on the results. This reduces publication bias and encourages rigorous planning. Authors must follow the registered plan and report deviations transparently.

Engineering use is growing in areas such as machine-learning evaluation and experimental studies with clear hypotheses. We help prepare the stage-one manuscript, including analysis plans and power considerations.

Commentary, correspondence and technical perspectives

These formats present an argument or viewpoint, respond to a published paper or discuss emerging directions. They require clear reasoning, balanced engagement with literature and constructive tone. Responses to published work should be factual, specific and respectful, and the original authors may be invited to reply.

We help authors structure arguments, check factual accuracy and maintain a professional tone, but we do not write on behalf of authors to settle disputes.

Software, method and protocol papers

Method and software papers document tools so that others can use them. They should describe the problem addressed, the design, validation against known results, performance and limitations, with the software archived in a repository and licensed. Protocol papers describe step-by-step procedures with troubleshooting notes.

We help with structure and documentation but do not write code or validate software.

Length limits, structure and style in short formats

Short formats have strict limits, often in the range of a few thousand words, a limited number of figures and a restricted reference list. Plan the content around one central message. Use a compact introduction, a precise methods paragraph, results with one or two key figures and a short discussion. Move peripheral material to supplementary files.

Editors of short formats value clarity and immediate usefulness. We help authors decide what to keep and what to cut without damaging the evidence.

Quality and submission

Quality, governance and submission

Quality expectations for short formats

Short does not mean low rigour. Reviewers expect the same standards for evidence, with space limits forcing precision. Use supplementary information for detailed derivations, extra data or code, and make sure the main text stands alone.

Check that figures are essential, tables are compact and references are focused.

Ethics, licensing and data governance

For data papers and software papers, confirm that you have the right to share the data or code, that personal or sensitive data are protected and that licences are specified. Cite the datasets and software that you use.

We help prepare data availability and licence statements.

Preparing supplementary material and repositories

Supplementary files should be numbered, cited in the main text and described in captions. Provide code with a readme, a licence and a version tag, and data with a data dictionary and a persistent identifier. Avoid hosting only on personal websites that may disappear.

Check the journal's policy on supplementary file formats and size.

Final checks for short-format submissions

Re-read the instructions for authors and confirm word count, abstract limit, number of figures and reference style. Make sure that the title states the contribution, the first paragraph states why the note is worth reading, and the conclusion states what the reader can now do. Check that all supplementary files are cited and that data and code links work.

Getting started

Tell us what you have: a dataset, a method, a short result or an argument. We will suggest suitable formats, check the target journals' requirements and agree on a plan.

Starting a specialised-format project

Tell us what you have and the journals you are considering. We will compare the article types they offer, check word limits and structure, and propose a plan for drafting, figures and supplementary material.

Working together

What we need from you

What to bring to the first conversation

  • Your data, results and methods, or the analysis outputs the manuscript will report
  • Your draft or notes, and the target journal or audience
  • Author roles and contribution details, which remain your decision
  • Your deadline and any journal-specific requirements

See also all manuscript & publication services and the research integrity principles.

Discuss your project

Share your objectives, data situation and target outcome. We will assess the scope and suggest sensible next steps.