العربية
A practical guide to preparing a proposal and manuscript for scholarly assessment and reducing avoidable revision rounds. These guidelines are supplemented by discipline- or call-specific requirements; the approved project instructions take precedence where they differ.
Title page and authorship
The title page should give the full title and subtitle, authors or editors in the agreed order, and academic titles and affiliations in their intended publication form. Identify the corresponding author and email address; include ORCID identifiers where available. Do not add non-contributing authors or omit eligible contributors, and obtain co-author approval before submission.
Proposal, abstract and readership
Explain the central research question, the need addressed, sources or methods, expected contribution and intended audience. Describe the relationship to comparable works without dismissing prior scholarship, and supply a contents list that shows the chapter sequence. Arabic and English abstracts support bibliographic presentation, while the language of the book is recorded separately.
Manuscript structure
Organise the file into clear units: title, introduction, chapters or sections, conclusions, references and any appendices. Use consistent heading levels and traceable numbering; do not align text with repeated spaces. A clean Word manuscript is appropriate before professional typesetting. At this stage, structural and substantive clarity matter more than imitating the final printed layout.
Sources, citations and references
Follow a referencing style appropriate to the discipline or specified in the call and apply it consistently. Check that in-text citations match the bibliography, and verify author names, titles, dates, pages and DOI identifiers where available. Do not include unverified sources or machine-generated references without checking them. Distinguish quotations from paraphrases and acknowledge the source in both cases.
Tables, figures and images
Number tables and figures separately, provide informative captions and sources, and cite them in the text. Submit editable tables wherever possible and retain high-quality originals of images and diagrams. A figure intended for monochrome printing should not rely on colour alone. Document permissions and permitted uses for reproduced images, maps and other third-party materials.
Research requiring ethical documentation
Where research involves human participants, health information, animal studies or sensitive data, the editorial office may request relevant approvals and evidence of privacy safeguards or informed consent appropriate to the study. Remove unnecessary identifiers and do not upload personal records or images without an appropriate basis. Responsibility for the conduct of the research remains with the author and research team.
Use of artificial-intelligence tools
Authors should disclose material use of AI tools in drafting, analysis or image creation and explain the checks they performed. An AI tool is not listed as an author and must not be used to fabricate data, results or citations. Third-party manuscripts or confidential data should not be uploaded to external services without permission. Authors remain accountable for the submitted work regardless of the tools used.
Revisions, proofs and approval
When revision is requested, provide a revised manuscript and a structured response addressing each comment or explaining any reasoned disagreement. At proof stage, check names, titles, contents, tables, notes, pagination and publication details, and consolidate corrections into a clear response. Proof review is not normally an opportunity to rewrite the entire book; substantial changes require discussion of their scheduling and cost implications.
Before you submit
Check author details, consistency between the form and manuscript title, the abstract, contents and bibliography, permissions, and the correct submission route. Keep original copies of all files, record the application reference after submission, and use the tracking link for updates rather than creating duplicate applications for the same project.