Manuscript template
Prepare the main manuscript and keep author identities in the separate title page.
Download manuscript templateFor authors
A practical route through scope, manuscript files, scientific reporting and the declarations needed for a fair review.
Prepare an accurate AI-use declaration, verify references and explain the provenance of figures, data and code.
Recommended before submission. Check sections, declarations, citations and references, then prepare a Word draft with this journal’s template.
Submissions are currently closed while the editorial board is formed and the submission workflow is prepared. You may use the guidance and Manuscript Pre-check to prepare your work; preparation is not a journal submission. The opening date and authorised submission route will be announced here.
Downloading a template or preparing evidence does not submit a manuscript. The formal submission route will be announced when the journal opens.
Use these editable files alongside the instructions below. They are preparation resources; they do not create an active submission.
Prepare the main manuscript and keep author identities in the separate title page.
Download manuscript templateRecord the author list, affiliations, contributions and relevant declarations separately.
Download title pageExplain the contribution, journal fit and related work for editorial assessment.
Download cover letterAddress each review point and identify revisions or explain a reasoned disagreement.
Download response to reviewersPrepare an anonymised manuscript, a separate title page, a cover letter and any supporting files needed to assess the work. The title page should give the full journal title, manuscript title, article type, author names and affiliations, corresponding author details, contribution statement and relevant declarations. Keep identities and identifying acknowledgements out of the review manuscript. Anonymise document properties and explain any repository link that could reveal authorship. Ethics, data-access and methodological declarations needed to assess the science must remain in anonymised form in the review manuscript. Provide identifying approvals or other confidential evidence separately through the authorised editorial route.
Prepare an editable DOCX manuscript using the journal structure; a review PDF may accompany it. Authors using LaTeX or another specialist format should seek an agreed alternative route before submission and provide a compiled review PDF and source when requested. Supply original figure files and an accurate reference list for production. Initial submissions may use a consistent readable reference style. The final house style is specified during production. References to data and software should identify the version or release and a persistent identifier where available.
Use a specific title, an informative abstract and descriptive keywords. State the research question, its relationship to prior work, the methods and assumptions, the evidence, limitations and conclusions. For empirical work, distinguish results from interpretation. For theoretical, conceptual or qualitative work, use a structure that makes the reasoning and evidence traceable. Include all applicable declarations and cite supplementary material in the manuscript.
There is no fixed initial-submission word limit in this guide. Provide a word count and use the length needed for a complete, focused account. The editor may request shortening or restructuring. A later published article-type limit will apply to submissions received after its stated effective date; any exceptional change for a manuscript already under consideration must be communicated to its authors.
A preparation file or saved evidence record does not constitute a journal submission. Formal submission requires the journal's announced submission route, author approval and completion of the required declarations. Authors should use the manuscript reference in subsequent correspondence and identify the version to which a query relates.
A revised submission should include an updated anonymised manuscript, any revised supporting files and a response addressing every editorial and reviewer point. Identify where changes were made and explain any reasoned disagreement. Keep the response professional and provide evidence for disputed technical issues. Do not silently substitute datasets, analyses or author lists; disclose consequential changes for editorial assessment.
Journal-specific standards
Use the guidance relevant to your design. A formal, conceptual or behavioural study should not add unrelated experiments merely to resemble another article type.
The abstract should state the task, proposed contribution, evaluation setting and principal conclusion without implying operating conditions that were not tested. Introduce the research problem in relation to the relevant robotics literature. Explain the gap in capability, understanding or evidence rather than relying on the novelty of a component's name.
A suitable manuscript explains system or problem formulation, design or method, evaluation, results and limitations. Adapt that structure to the study. Provide diagrams and notation that make sensing, decision and actuation relationships clear. Keep essential assumptions, safety limitations and findings in the main text; supplementary materials should extend the explanation rather than replace it.
Identify the platform, configuration, mechanism, sensing, actuation and computational components relevant to the contribution. Report dimensions, payloads, constraints and units where they affect interpretation. Explain control rates, communication dependencies, latency and offboard computation when these influence system behaviour. Distinguish autonomous operation from teleoperation, remote supervision and manual intervention.
Define the task and the intended operating conditions. Describe terrain, lighting, obstacles, object properties, environmental variability, connectivity or other factors that materially affect the result. State relevant assumptions about what the robot knows, observes or can control. Explain how the evaluation represents the conditions claimed in the conclusion, and identify conditions outside that evidence.
State the unit of evaluation, trial-selection procedure and success or failure criteria before interpreting performance. Report the number of attempts and explain exclusions, resets and aborted trials. Distinguish repeated measurements on one configuration from independent trials across conditions. Describe interventions and recovery procedures so readers can assess the level of autonomy demonstrated.
Select comparisons that address the same task and constraints. Explain parameter tuning, implementation differences, computational resources and information available to each method. Consider ablations when they clarify which component accounts for a claimed advance. Report relevant distributions or uncertainty rather than relying on a single best run or a visually impressive demonstration.
Choose metrics appropriate to the research question. Depending on the study, these may include task completion, precision, stability, latency, reliability, energy use, human effort or operating cost. Define denominators, measurement procedures and trade-offs. A speed improvement obtained through reduced safety margins or increased intervention should be reported as such.
Describe calibration, alignment, synchronisation and ground-truth construction when they affect results. Identify measurement resolution, reference instruments or estimation procedures, and uncertainty relevant to the conclusions. Explain how missing sensor values, drift, saturation and communication loss were handled. Distinguish measured outcomes from values inferred through the proposed method itself.
For learned perception or control, describe data provenance, training and evaluation separation, preprocessing and model selection. Prevent leakage between repeated trajectories, objects, environments or participants where those dependencies matter. Identify software and model versions and document stochastic variation. Generalisation claims should reflect the independent conditions actually tested.
Simulation-only submissions are eligible when the question and claims are appropriately grounded. Identify the simulator, physics assumptions, numerical settings, robot and environment models, noise and relevant limitations. Explain why the model is suitable for examining the proposed phenomenon. Compare against analytical expectations, established results or physical observations where appropriate to the claim.
Describe domain randomisation, parameter identification and adaptation when transferring methods between simulation and physical operation. Separate results observed in simulation from evidence obtained on hardware. A policy that succeeds in a model should not be described as deployment-ready without supporting evidence about the intended physical conditions.
For analytical work, state assumptions and the precise meaning of stability, convergence, observability, feasibility or optimality. Distinguish guarantees from approximations and heuristic behaviour. Numerical examples can illustrate a result but do not establish a general theorem. Hardware is not required solely to decorate a theoretical contribution.
Explain safeguards appropriate to the system and setting, including operating limits, supervision, emergency stopping and containment where relevant. Report safety-relevant events and interventions that affect the interpretation of performance. Identify hazards that the evaluation could not address. Research demonstrations must not imply certification, regulatory approval or unrestricted safety unless those claims are supported by the actual arrangements and evidence.
Analyse failures and operating boundaries with the same care as successful trials. Describe collisions, loss of tracking, unstable behaviour, degraded sensing or recovery failures when relevant. Explain whether observed faults are repeatable and how they affect the claims. A carefully investigated failure can offer more useful knowledge than a selected sequence of successful demonstrations.
For human–robot interaction studies, describe participants, recruitment, tasks, exposure, instruments and the rationale for the study design. Explain training, researcher involvement and any assistance given during trials. Identify ethics approval or exemption and relevant consent through the shared research-ethics policy. Protect identifiable video, speech, motion and behavioural data.
Interpret usability, trust, workload and acceptance measures within their context and limits. Distinguish participant perceptions from evidence of technical safety or reliability. Where deployment may affect vulnerable users, workers, bystanders or public spaces, discuss plausible consequences and safeguards proportionate to the research. Address potentially harmful uses when they are a meaningful feature of the work.
Document the equipment, software versions, configurations and instructions needed to examine reusable materials. Hardware resources should identify relevant drawings, components, assembly tolerances and test or calibration procedures. Explain access restrictions and substitute materials where full sharing is prevented by rights, safety or confidentiality. Provide a clear statement of what is available and which version supports the reported results.
Videos should distinguish real-time footage from accelerated, edited or simulated sequences and identify interventions essential to understanding the demonstration. Supply an informative caption or transcript and a short content summary. Explain playback or execution requirements in a README. Materials supporting technical claims should accompany the manuscript for review; promotional additions after acceptance must not change the evidence base without editorial assessment.
Adapt these examples to what actually occurred. Keep science-relevant information in the anonymised manuscript and provide identifying evidence separately when needed.
Evaluation used [platform and configuration] to perform [task] under [defined conditions]. The reported results cover [tested range]. Operation outside [limits] was not evaluated. [Type and frequency of intervention] occurred during [specified trials] and was handled in the analysis by [procedure].
The reported evaluation in [section] was conducted in [simulator and version] using [models and assumptions]. Parameters were obtained through [source or procedure]. The results establish performance within [modelled conditions]; transfer to [physical setting] remains [evaluated through specified evidence or not evaluated].
Materials supporting [specified results] are available at [repository and identifier], version [version]. These include [design files, code, configurations, data or videos]. Required equipment and execution instructions are described in [README or documentation]. Restrictions on [material] arise from [reason] and access is managed through [authorised route].
Publishing information
Read the journal’s publication frequency, charges, editorial policies and discovery information.