Computers in Human Behavior Submission Process

The searcher job here is procedural: what happens when an author starts the Elsevier record, what the record asks for, what can stall the file, and how to interpret the early decision path. It is not a broad verdict on whether CHB is the best target.

Use the split this way:

The boundary matters because CHB process intent is narrower than broad submission intent. This page assumes the author has already chosen CHB and now needs the generated record to show a psychological or behavioral paper, not merely a technology-adoption study.

These figures are journal-level ScienceDirect insights, not promises for one manuscript. The 6-day first-decision number mostly tells authors that CHB has a fast early screen. It does not mean a paper sent to external reviewers has completed peer review in six days.

Use 6 days as the early-screen planning point. Use 62 to 153 days for complex or delayed externally reviewed cases while reviewer matching settles across psychology, communication, education, HCI, AI interaction, social-media behavior, online learning, digital well-being, or behavioral-methods expertise.

The calibrated range is straightforward: administrative returns and desk-screen decisions can happen quickly, while externally reviewed technology-behavior papers can move over months. A CHB paper needing one behavioral-science reviewer, one application-domain reviewer, and one method reviewer is more likely to behave like the 62-to-153-day path than the 6-day first screen.

Elsevier Editorial Manager can delay the record before a scientific editor evaluates the contribution. The routine checks include authorship details, file type, source-file editability, figure captions, table integrity, supplementary files, references, permissions, competing interests, funding, AI-use declaration, human-subjects ethics, data availability, and double-anonymized file separation.

For CHB, the early process check has a second layer: the generated record must look like a CHB manuscript. A complete upload is not enough if the abstract reads like platform adoption, algorithm evaluation, dashboard usability, education technology, or information-systems implementation without a psychological or behavioral mechanism.

The first 48 hours should not ask the editor to reconcile mismatched artifacts:

• the abstract should name the behavior, psychological process, population, technology setting, method, and central evidence
• the Highlights should state behavioral findings rather than generic technology benefits
• the methods should map constructs to validated measures, sampling choices, exclusions, statistical model, and robustness checks
• figures and tables should make the behavior-theory connection auditable
• supplementary files should support instruments, codebooks, model settings, stimuli, survey items, preregistration links, or de-identified data where possible

These are process issues because the editor sees the generated record, not the author's private intent. If the record makes the technology louder than the behavior, CHB triage becomes harder.

The editor's first screen asks whether the paper is genuinely a Computers in Human Behavior paper.

Three tests matter most:

1. Human-behavior primacy. Does the manuscript study psychological or behavioral processes connected to computer use, rather than computers as objects?
2. Theory-to-measure alignment. Do the hypotheses, constructs, measures, sample, and analysis match the psychological or behavioral claim?
3. CHB conversation fit. Does the paper belong with current CHB topics such as online communication, social media, human-AI interaction, digital well-being, gaming, online learning, technology-mediated work, or computer-mediated social interaction?

A fast first decision should be read as a screen signal. It can mean the record was returned administratively, the manuscript did not sit inside the journal's aims and scope, or the editor did not see enough behavioral contribution to justify reviewers. It should not be read as proof that all CHB decisions happen in six days.

The strongest process package makes the first screen easy. The title names the human-behavior object. The abstract identifies the psychological mechanism. The methods justify the constructs and measures. The figures or tables show evidence that the behavior claim is not just a platform description. The discussion explains what changes for psychology, communication, education, HCI, digital health, social interaction, or human-AI behavior.

The current ScienceDirect page is useful because it shows what the process record has to make visible before the editor spends reviewer capacity. Professor Matthieu Guitton is listed as editor, and recent June 2026 CHB articles include work on algorithm oversight in social decision-making, human and large-language-model content analysis, human-AI input representation, collaborative behavior in League of Legends, social-media notification attention effects, AI-agent apology framing, AI second opinions, and generative-AI-supported learning competence. The DOI examples shown on ScienceDirect include 10.1016/j.chb.2026.108924, 10.1016/j.chb.2026.108904, 10.1016/j.chb.2026.108927, 10.1016/j.chb.2026.108928, and 10.1016/j.chb.2026.108926.

That calibration matters for the upload process. CHB is not asking authors to prove that a technology exists or that users clicked something. The record has to identify a behavior, a psychological or communication mechanism, a population, a technology-mediated context, and a method capable of supporting the claim. A manuscript about generative AI, gaming, social media, educational technology, recommender systems, or platform behavior can still be process-weak if the generated PDF leaves the editor asking what the human-behavior contribution is.

Use those current-issue signals as a practical self-check before final submission:

Once a CHB manuscript clears the first screen, reviewer selection usually follows the behavior claim rather than the technology label alone.

Reviewer routing often depends on:

• psychological or behavioral-theory reviewers for motivation, cognition, affect, personality, social interaction, well-being, trust, decision-making, or development
• application-domain reviewers for social media, gaming, online learning, digital mental health, human-AI interaction, online communication, virtual reality, or platform behavior
• method reviewers when the paper relies on surveys, experiments, longitudinal data, computational text analysis, psychometrics, structural models, field data, mixed methods, or preregistered analysis
• HCI or communication reviewers when the technology interaction, interface, mediation channel, or communication context is central to the claim

CHB uses double-anonymized peer review, which authors should treat as double-blind preparation for every reviewer-facing file. Suggested reviewer logic, if requested in the portal, should cover the behavior theory, method, and technology setting. Do not list only researchers who study the same platform or only methodologists who cannot evaluate the CHB contribution.

The response from review usually turns on whether the process package made the behavioral claim auditable. A manuscript can be topical and still receive a difficult decision if reviewers decide the theory is thin, measures are ad hoc, the sample does not support the claim, the technology setting is overemphasized, or the work fits a neighboring venue better.

In our pre-submission review work with CHB manuscripts, we treat the process package as one connected behavioral record: title, abstract, Highlights, introduction, method, figures, tables, data statement, ethics material, supplementary files, references, and reviewer-routing logic. A paper can be complete and still process-weak if those pieces make the editor reconstruct why the work is psychological or behavioral.

Technology-first framing. The most common pattern is a manuscript that opens with a platform, app, AI system, game, learning tool, or digital environment and only later names the behavior. The first screen should reverse that priority: behavior question first, technology context second.

Theory appears after the results. Some papers cite psychology or communication theory but do not let it shape hypotheses, measures, analysis, or interpretation. CHB reviewers are likely to read that as decorative theory rather than a behavioral contribution.

Construct measurement is too loose. Ad hoc scales, single-item constructs, unclear manipulation checks, weak reliability reporting, and missing validity logic create review risk even when the topic fits.

Neighboring-venue confusion. A manuscript may be stronger for Computers & Education, Information Systems Research, Technology in Society, Behaviour and Information Technology, Cyberpsychology, Behavior, and Social Networking, or Journal of Computer-Mediated Communication if the central contribution is learning-outcome design, IS theory, policy/society mechanism, usability practice, cyberpsychology community, or communication theory rather than broad CHB behavior.

These patterns are process-relevant because editors do not evaluate the author's intention. They evaluate the generated submission record. In our checks, the weak record usually has a predictable shape: the title names an app or platform, the abstract reports usage or intention, the Highlights repeat outcome labels, the methods section lists survey items without construct logic, the tables show coefficients without effect interpretation, and the data statement is generic.

The stronger record is different: the title names a behavior, the abstract states the theory and mechanism, the first figure maps constructs, the methods justify sample and measurement decisions, the tables report reliability and effect sizes, the supplementary files include instruments or codebooks, and the references show where the paper enters CHB's psychology-of-technology conversation.

That is why our process review reads the upload package as an editor-facing artifact, not as a formatting checklist. We look for the exact moment where an editor can say "this is a CHB paper" without reconstructing the contribution from scattered pieces. If that moment is missing, the author should revise the record before final submission, even if every mandatory field in Editorial Manager is technically complete.

Watch for these named process failures before uploading:

• Technology-first record. The title, abstract, Highlights, and first figure make the platform or system primary while the behavior is vague.
• Theory-to-measure gap. The manuscript cites theory but uses measures or models that do not test the theoretical mechanism.
• Double-anonymized identity leak. The anonymized file, acknowledgments, self-citations, data links, supplementary files, or document metadata reveal author identity.
• Human-subjects statement gap. Ethics approval, consent, privacy, participant protection, or sex/gender reporting is unclear for studies involving people.
• Wrong neighboring venue. The process package reads more like education technology, IS, HCI practice, platform policy, or communication research than broad psychology-of-computer-use research.

Check whether your CHB record is technology-first →

Check whether your CHB measures support the theory →

Check whether your CHB package is ready for double-anonymized review →

CHB decisions are easier to interpret if you separate process, fit, method, and peer-review outcome.

The important distinction is between "fix the process record" and "change the paper." A missing anonymized file is a process repair. A decision saying the manuscript is descriptive technology adoption is a manuscript-positioning problem.

Method note: we reviewed the official ScienceDirect CHB journal page, ScienceDirect Guide for Authors, current ScienceDirect timing/APC/journal-metric snippets, the existing Manusights CHB fit owner, and adjacent venue owners before creating this process page. Source limitation: ScienceDirect provides current journal-level timing and APC metrics, but it does not publish a stable desk-rejection rate by subfield or method.

The evidence boundary is deliberate. Elsevier and ScienceDirect set the current public facts: CHB's scope, article types, double-anonymized review model, title-page and anonymized-file requirements, abstract and Highlights rules, online-submission route, Article Transfer Service, proofing, APC, and timing insights. Manusights adds the author-side process layer: whether the generated record makes the behavior, theory, measures, method, data statement, and journal choice obvious before the editor spends reviewer capacity.

Use this page for the judgment layer, not as a substitute portal. ScienceDirect remains the source for mandatory fields and current policy text. The Manusights contribution is the CHB-specific interpretation of what those fields need to show when the manuscript is trying to look like psychology-of-technology research rather than a generic technology-use report.

Last verified: July 17, 2026 against ScienceDirect and Editorial Manager source URLs.