Submissions and Enquiries

Security Dialogue publishes regular fully double-blind peer-reviewed articles of 8,000-10,000 words.

All submissions and resubmissions should be made via the online system Manuscript Central.

All submitting authors should consult Security Dialogue’s Notes for Authors below for details on style. You may also wish to download this Endnote template.

1. Submissions

Authors should send all regular article submissions and resubmissions to Security Dialogue via Sagetrack, which provides step by step instructions on how to submit. Content for our digital platform may be submitted to

The Managing Editor can be contacted at if you have any difficulties or queries with your submission.

All submissions are initially read and evaluated by the Editorial Team. We aim to make an initial decision on each submission with regards to sending for external review within 6 weeks.

As a general rule, Security Dialogue operates a double-blind peer review process in which the reviewers’ names are withheld from the author, and the authors’ names are withheld from the reviewers. We aim to complete the external peer-review process and make a decision on a submission within 12 weeks.

2. Types of articles

Security Dialogue publishes regular, fully double-blind peer reviewed, articles.

Articles that are submitted for a special issue are classed as regular articles but may sometimes have additional restrictions for word count. This will in case have been stated in the call for submissions.

Regular articles should be 8,000-10,000 words in length, including the abstract, references and endnotes. See further details on requirements for regular articles below.

Rejoinder (to another article) and book reviews are published in electronic format only on our digital platform, and should normally not exceed 500-1,500 words. These submissions will not undergo external peer-review, but may receive feedback and revision requests from our digital editor. The digital editor can be reached at

3. The manuscript (‘regular article’)

The final version of a manuscript (ms) should contain:

  • The actual manuscript with title, abstract, main text, and a list of references (in Harvard style) with notes (footnotes or endnotes are acceptable at submission stage). An EndNote template is available from our website. Please note that the author(s) name(s) should not appear on the final ms, apart from in the references (if any).
  • Title page with name(s) of the author(s), affiliation, author biography (80 words) with author email address, and acknowledgements (if any), in a separate document.
  • Table(s)/figure(s)/graph(s) should be uploaded in a separate document.

Authors must check that this information is included before submitting the final version of their manuscript via the online system. Failure to send a correct manuscript can result in a delay.

The final manuscript should be submitted in MS Word for Windows. The text in the ms should be left justified, with an ample left margin. Line spacing should be set to 1.5 or double.

Please ensure that the information in your Sagetrack author / co-author account(s) is correct and that your email address is up to date.

Our publisher, Sage, requires authors to disclose information on any specific funding which supports the article, including name of funder and, where applicable, grant number. Please notify the Managing Editor at if you experience any problems entering or updating your account details.

We do not accept double submissions, and we assume all submissions to be original. We may exceptionally accept articles that are extracts from or summaries of books published at about the same time, as well as articles that have appeared in other languages.

The author’s name is not disclosed to the reviewers. It is the author’s responsibility to remove first-person references and other clues elsewhere in the article that may reveal the author’s identity. Security Dialogue prefers that articles be anonymized by referring to previous publications by the authors in the third person. This option is particularly important where the absence of reference to authors’ previous publications would be suggestive of the authors’ identities, e.g.

As _author name_ (2007) has previously argued, …

The reviewers’ comments will be anonymous when sent to the author. We expect all articles to be fully anonymized upon submission. Failure to anonymize the article might result in delays.

4. Abstract

The abstract should be 150–200 words. The abstract should be added in the box marked ‘abstract’ in the online system during the Sagetrack submission process.

The abstract is an important part of the article. It is intended for use as an instrument for selection, and upon publication attracts readers, and search engines, to the full text. It should summarize the actual content of the article, rather than merely relate the subject the article deals with. It is useful to strategically include the most important keywords in the text of the abstract. The abstract should be written in the present tense and in the third person or passive; use of the first person is discouraged.

The abstract is included in the final word count of articles and review articles.

5. Keywords

All regular articles should have five-six keywords that adequately reflect their content. Keywords are meant for cataloguing, and to make the articles easily searchable online. The keywords should be added to the box marked ‘keywords’ in the online system during the Sagetrack submission process. It is worth including at least one keyword or key phrase that describes the broad discipline within which the article sits, e.g. ‘sociology’ or ‘critical security studies’.

6. Searchability

The vast majority of readers find articles online by searching rather than browsing. Most searching is done using clusters of keywords or key phrases (e.g. ‘youth justice’, rather than simply ‘youth’). Including key phrases that people searching are likely to use should make your article more discoverable. To ensure that you maximize the searchability of your article, you should:

  1. try to make the title of the article as clear as possible in describing its content;
  2. ensure that the abstract spells out clearly what the article covers and mentions any terms that people searching for such an article might be likely to use;
  3. make sure that you include appropriate key phrases or keywords

7. Language

The main objective of an academic journal is to communicate clearly with an international audience. Elegance in style is a secondary aim. The basic criterion should be clarity of expression.

We allow both UK and US spelling, as long as there is consistency within the article. You are welcome to indicate on the front page whether you prefer UK or US spelling.

For UK spelling, we use -ize (standardize, normalize) but -yse (analyse, paralyse).

For US spelling, -ize/-yze are the standard (civilize/analyze).

Note also that with the US standard, we use the serial comma (e.g. ‘red, white, and blue’).

Security Dialogue uses gender-neutral language wherever possible.

Authors should avoid colloquialisms, acronyms and abbreviations particularly if linked to a particular national culture.

However, the acronyms: UN, USA, EU and UK (no full stops) will be readily understood, as will ‘the ABM treaty’ (in an article on arms control).

Otherwise, an acronym or abbreviation should be spelled out the first time it occurs.

Italics for emphasis should be used sparingly.

We prefer ‘the USA’ or ‘the United States’ (not ‘America’) for the name of that country, and ‘US’ as an adjective.

All articles will be subject to editing by the editor and the language editor. Manuscripts that will require heavy editing may be returned to the author for correction, clarification of misunderstandings and possibly additional rounds of word processing prior to copy-editing. When corrections are made in the final version, there is usually no time for further consultation with the author, but the proofs (see below) provide the author an opportunity to correct any misunderstandings.

8. Title and headings

All sections of the article (including the beginning) should have principal headings. Regular articles can include up to three levels of headings. The author should ensure that the heading hierarchy is clear, consistent and logical. If two or three levels are used, they must be typographically differentiated clearly. For example:

Main Heading

Text.Text.Text.Text. Text.Text.Text.Text


Text.Text.Text.Text. Text.Text.text.Text

Sub-subheading. Text.Text.text.Text Text.


9. Notes

Notes should be used only where substantive information is conveyed to the reader. Literature references should normally not necessitate separate notes (see the section on References). However, non-standard references, such as to press conferences, political statements, hearings, interviews etc., are best provided as notes.

Notes will appear as endnotes in the journal. In the manuscript they may be either footnotes or endnotes.

Acknowledgements and credits to funding agencies should not be given in a note but rather appear in separate paragraphs at the end of the main text. This information should be included in the final version of the manuscript only.

For articles with replication data, the URL(s) where the data will be posted should be provided immediately following the main text; see section 18, below.

Notes to tables/figures must not be incorporated into the main notes section but placed immediately below the relevant table or figure. The note should not be preceded by the word ‘Note’.

10. Tables and figures

Each table/figure should be self-explanatory, as far as possible.

The table/figure heading will appear below the table. The table/figure heading should be brief, but additional explanatory material may be added in ‘notes’.

Each table/figure should also contain a full reference to the source(s) used. The source reference should appear below the table/figure and in the reference section of the manuscript, not in the ‘notes’ section.

Authors should indicate where the table/figure is to appear in their manuscript by adding a text indicator; this should be inserted after the paragraph where the table/figure is first mentioned, in the following manner:


Table I in here


We cannot guarantee that a table will be printed exactly where indicated in the ms.

11. Maps and graphs

Maps and graphs may be inserted in Security Dialogue articles, provided they can be supplied in a suitable format and resolution and, if necessary, with permission to reprint.

12. References

References should be provided in a separate alphabetical list; they should not be incorporated in the notes. When citing books or articles in the text or in notes, use the following form:

  • See Smith (1997); Brem and Rutherford (2001); Taylor (1996, 1999)
  • or: See Smith (1997: 22)
  • or: (Smith, 1997: 22)
  • or: (Smith, 1997; Taylor, 1996)
  • or: (Smith, 1997: 22; Taylor, 1996: 6)
  • or: For further discussion, see Smith (1997).

Commas are used to separate the author from the year, colons to separate the year from the page number, and semicolons to separate two references. References to two publications by the same author are written as follows:

  • Wallensteen (1995, 1996)
  • or: Wallensteen (1995a,b)

All direct quotes must be accompanied by page numbers.

When there are three authors or more, ‘et al.’ is used in text references, but not in the reference list, where a full list of authors should be provided.

All references quoted in the text must appear in the reference list, and vice versa. This should be checked carefully. Please ensure also that spellings and dates match in all cases.

Although books, articles and other citations should be listed together in the references, they are:

Articles from periodicals

Stepputat F (2012) Knowledge production in the security-development nexus: An ethnographic reflection. Security Dialogue 43(5): 439-455.


Wibben ATR (2010) Feminist Security Studies: A Narrative Approach. Abingdon, Oxon: Routledge.

Foreign-language works

Greilsammer I (1998) La nouvelle histoire: Essai sur une nouvelle identité nationale [The New History: Reflections on a New National Identity]. Paris: Gallimard.

Works with translator

Agamben G (1998) Homo Sacer: Sovereign Power and Bare Life. Heller-Roazen D. Trans. Stanford, CA: Stanford University Press.

Chapters/articles from books

Meek S (2000) Combating arms trafficking: progress and prospects. In: Lumpe L (ed.) Running Guns: The Global Black Market in Small Arms. London: Zed, 183-206.


European Commission (2009) Commission staff working document on health security in the European Union and internationally. 23 November. Available at:

UN reports

Include the authorizing body, year, topic or title of the paper, series and publication numbers, place of publication, and a page reference when applicable. For references in the text, use, for example:

(United Nations, 2002), followed by full reference in the list of references;

United Nations (2002) On the situation in the Middle East. Security Council Resolution 1428, S/RES/1428 (2002), New York.

However, we accept alternative styles for UN documents, provided that they are complete and consistent.

Newspaper articles

Articles with author byline:

Finnonian A (1990) The Iron Curtain rises. Wilberton Journal, 7 February.

Articles without author byline:

The Guardian (London) (2002) Croatia sparks showdown with UN. The Guardian, 25 September.

Please note that the city of publication should be provided where this is not included in the title of the newspaper.

Internet references

Internet references should generally be regarded as supplementary. Unless the work cited exists only on the Internet, a URL alone does not suffice. The author must verify the accuracy of all URLs. The date on which the page was accessed should be provided.

Providing supplementary information on magazine, journal or newspaper article

Stillman S (2011) The invisible army. New Yorker, 6 June. Available at:

Providing links to general web pages

Prime Minister’s Office, Israel (2002). Weekly Cabinet meeting Tuesday 10.9.2002. Press release. Available at: (accessed 18 September 2002).

Referencing interviews

When interviews are cited in-text, these should be listed separately at the end of the reference list under the heading ‘Interviews cited’. As much detail as possible should be provided in this list, though this will vary according to the need to protect the anonymity of interviewees. As far as possible, information provided should include: the name of the interviewee, the position or title of the interviewee, the organization or institution with which the interviewee is affiliated, and the location and date of the interview. In all but the most exceptional cases, a numbering system should be used to ensure that in-text citations from interviews can be correlated with the information provided in this list.

In-text references should follow the following format: ‘Interview 1’, ‘Interview 2’, etc. Footnotes or endnotes should not be used unless to convey additional substantive information to the reader.

Listings under ‘Interviews cited’ should without compromising the identity of interviewees follow the following format as closely as possible:

‘Number. Name of interviewee, position of interviewee, institutional affiliation of interviewee, location of interview, date of interview.’

13. Biographical statement

A brief author biographical statement can be followed by a separate paragraph with any acknowledgements the author wishes to include. Authors are encouraged to add their e-mail address(es) to their biographical statement. Please try to keep the statement within 80 words.

The biographical statement, acknowledgements, and funding information will be added as separate paragraphs in the printed version of the article.

14. Proofs and reprints

A first round of proofs will be sent from Security Dialogue’s dedicated language editors. A second author’s proofs will be e-mailed as PDFs directly from SAGE (in London, UK) after copy editing, and typesetting. If the article is co-authored, the proofs will normally be sent to the author who submitted the manuscript (corresponding author in Sagetrack).

Authors should ensure that their e-mail addresses are correct in Sagetrack so that they can be contacted at short notice if any urgent queries arise during copy-editing. A limited number of offprints will be made available to the author(s) electronically post publication.

15. Copyright

The responsibility for respecting copyright in the quotations of a published article rests with the author(s).

It is not necessary to obtain permission for a brief quote from a work in the social sciences. However, with a long quote, a figure or a table, written permission must be obtained. Due references to the original source must always be provided.

The author must consult the original source to determine whether the copyright is held by the author, the journal or the publisher, and seek the permission of the appropriate person or institution. In the event that reprinting requires a fee, written confirmation that the author is prepared to cover those expenses must be furnished.

Regulations for quotation of literary material are much stricter. Even a single verse from a poem may require permission.

When publishing an article in Security Dialogue, authors retain copyright of their work, but agree to publish under an exclusive license with Security Dialogue and the publisher.

Authors retain their right to reuse the material in other publications written or edited by themselves and due to be published at least one year after initial publication in Security Dialogue.

After an article is accepted, the author will be required to fill out and return a Journal Contributor Agreement.

For more information regarding copyright and permissions, please consult Sage’s guidelines.

16. Resubmissions and Accepted Articles

The following guidelines should be adhered to closely for revised manuscripts. Resubmissions that are likely to require undue editorial attention because of neglect of these instructions or poor presentation or language may be suspended from further consideration.

17. Revised Manuscript Submission

A revised submission should contain:

  1. The actual manuscript with footnotes and a list of references, but without any details revealing the name(s) of the author(s).
  2. A memo outlining the changes made and how the reviewers’ points have been met – or, if disregarded, why.
  3. A Track Changes version of the manuscript clearly showing what changes have been made to the previous version, and where.

And, if applicable:

4.  Revised versions of: the author biographical statement; keywords; name(s) of the author(s) and affiliation(s); tables and figures.

18. Online Submission Instructions

All submissions should be made online at the Security Dialogue Sagetrack website.

New users will first need to create an account by pressing the 'Create Account' button. If an error message appears stating that the e-mail address already exists in the system, it is because information from our old database has been transferred to Sagetrack. Enter the e-mail address as requested and use the ‘forgot your password?’ function.

The manuscript should be submitted in a separate file in Microsoft Word format.

The abstract should be entered when prompted by Sagetrack during the submission procedure.

Please do not include a title page or insert page numbers on your final manuscript, the Sagetrack system will create them automatically. Full instructions for uploading the manuscript are provided on the Sagetrack website.

The author can follow the status of the submission through the author center in Sagetrack:

  • Awaiting initial decision - the article has not gone out for external review, but may have gone out for internal review to the Editorial team
  • In external review process - the external peer review process has been initiated
  • Out for review - the article is in external peer review