Rejected from Computers in Human Behavior? Where to Submit Next
A decision-led post-rejection guide for Computers in Human Behavior manuscripts, with a 72-hour repair plan, six evidence-matched routes, and safe resubmission rules.
Next step
Choose the next useful decision step first.
Use the guide or checklist that matches this page's intent before you ask for a manuscript-level diagnostic.
Quick answer: If you were rejected from Computers in Human Behavior, first decide whether the outcome was a desk rejection, a rejection after peer review, or a transfer or referral option. The journal's center is psychological knowledge about how computers shape and express human behavior. Extract the controlling concern, fix evidence problems that will follow the paper, and select the next venue from the revised contribution. Do not route by impact factor proximity or assume a transfer guarantees acceptance.
This page answers “rejected from Computers in Human Behavior: where should I submit next?”. It does not replace the submission guide, which owns first-submission preparation.
Last reviewed: July 13, 2026.
From our manuscript review practice
In our pre-submission review work with Computers in Human Behavior manuscripts, the next-journal decision improves only after the team converts the rejection letter into specific repairs across the abstract, methods, evidence, figures, discussion, and submission package.
72-hour action plan after the rejection
First 24 hours: freeze the exact CHB submission: manuscript, supplement, figures, tables, data and code versions, cover letter, editor letter, reviews, and portal status. Do not revise from memory. Record whether external reviewers participated and whether the Computers in Human Behavior decision offers transfer, referral, or appeal instructions.
Hours 24 to 48: convert every CHB decision sentence into one of five buckets: scope and audience, contribution and novelty, methods and controls, evidence and interpretation, or presentation and policy. Name the section, figure, table, analysis, dataset, or claim affected by each item.
Hours 48 to 72: create a Computers in Human Behavior repair ledger and two destination abstracts. One should preserve psychological knowledge about how computers shape and express human behavior; the second should recenter the strongest application or disciplinary contribution. Compare both with the six routes below before changing formatting.
Preserve the CHB rejection as data. Coauthors may disagree with a reviewer, but they should still ask whether another qualified reader could reach the same conclusion from the present psychological knowledge about how computers shape and express human behavior artifact.
Readiness check
Run the scan while the topic is in front of you.
See score, top issues, and journal-fit signals before you submit.
Triage the CHB decision letter
Rejection signal | Likely diagnosis | Required next action |
|---|---|---|
The computer is the topic rather than the medium | The paper describes a platform or model without advancing behavioral knowledge | Route to HCI, information systems, or education, or rebuild the psychological contribution |
Theory is decorative | Construct names appear but do not generate predictions or interpretation | Specify mechanism, alternatives, and theoretical boundary conditions |
Self-report supports a behavioral claim | Intentions or perceptions are generalized to use, performance, or well-being | Add behavior or narrow the outcome language |
Common-method or cross-sectional design | One survey at one time point cannot establish the proposed direction | Use temporal, experimental, multi-source, or cautious associational framing |
Sample and context limit transport | One platform, course, country, or convenience panel is treated as universal | Model heterogeneity and state the population boundary |
The contribution belongs to another audience | Learning, communication, clinical, IS, or interface design is the real center | Route to the discipline that owns the reader decision |
Audit the Computers in Human Behavior rejection before choosing another journal.
Desk rejection, post-review rejection, and transfer are different
A desk rejection from Computers in Human Behavior usually says the editor could not justify external review for its audience, contribution threshold, visible evidence, or article type. That can be a routing problem, but it can also expose a weak abstract, hidden contribution, incomplete controls, or unsupported framing.
A post-review CHB rejection after external review is deeper evidence. Comments on assumptions, design, measurement, baselines, figures, reporting, interpretation, and limitations are portable. Another masthead will not erase them. Resolve the strongest repeated or editor-endorsed concern before resubmission.
A CHB transfer offer or referral, when available, identifies a possible destination rather than an acceptance path. The receiving editor decides independently. Compare the offered title with the alternatives below, revise first, and follow the live Computers in Human Behavior decision instructions.
Reconstruct the manuscript's evidence chain
For this field, the paper should make the following chain inspectable: technology exposure -> psychological construct -> design and measurement -> behavioral evidence -> bounded mechanism -> human consequence. Mark each connection as directly measured, validated, inferred, hypothesized, or absent. The destination should match the strongest demonstrated link, not the most ambitious sentence.
Read the CHB title, abstract, first figure or table, methods, central result, discussion, limitations, data statement, and supplement as one package. If those components do not jointly support psychological knowledge about how computers shape and express human behavior, repair the inconsistency before selecting a venue.
Route by the revised contribution
Journal or venue | Best fit after revision | Think twice when |
|---|---|---|
Computers in Human Behavior Reports | interdisciplinary human-computer behavior studies with a sound and transparent empirical contribution | the study still lacks a meaningful human-behavior result |
Behaviour & Information Technology | human factors, usability, adoption, work, interaction, and behavioral technology research | the paper is primarily clinical, educational, or communication research |
International Journal of Human-Computer Studies | theory-rich HCI, cognition, interaction, user studies, and design implications | the interface or interaction contribution is incidental |
Journal of Computer-Mediated Communication | communication theory and digitally mediated social behavior | communication processes are not the central theoretical object |
Internet Research | digital platforms, online behavior, organizations, markets, and societal implications | the work is a narrow lab study without an internet or platform contribution |
Computers & Education | learning, instruction, educational technology, and demonstrable educational outcomes | the sample is educational but the outcome is general technology attitude |
Computers in Human Behavior Reports
Best for: Interdisciplinary human-computer behavior studies with a sound and transparent empirical contribution. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.
Think twice if: the study still lacks a meaningful human-behavior result. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.
Behaviour & Information Technology
Best for: Human factors, usability, adoption, work, interaction, and behavioral technology research. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.
Think twice if: the paper is primarily clinical, educational, or communication research. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.
International Journal of Human-Computer Studies
Best for: Theory-rich hci, cognition, interaction, user studies, and design implications. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.
Think twice if: the interface or interaction contribution is incidental. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.
Journal of Computer-Mediated Communication
Best for: Communication theory and digitally mediated social behavior. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.
Think twice if: communication processes are not the central theoretical object. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.
Internet Research
Best for: Digital platforms, online behavior, organizations, markets, and societal implications. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.
Think twice if: the work is a narrow lab study without an internet or platform contribution. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.
Computers & Education
Best for: Learning, instruction, educational technology, and demonstrable educational outcomes. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.
Think twice if: the sample is educational but the outcome is general technology attitude. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.
Extract the decision letter into a routing artifact
Use one row per Computers in Human Behavior editor or reviewer concern. Quote only enough to preserve meaning, then record the affected claim and evidence. The minimum CHB extraction dimensions are:
- Psychological construct: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
- Technology role: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
- Causal ordering: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
- Measurement validity: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
- Behavioral outcome: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
- Population and context: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
- Theoretical boundary: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
Add CHB ledger columns for owner, required work, dependency, expected artifact, and completion evidence. A concern is resolved only when its figure, method, analysis, source, or bounded claim changes and the revision can be located.
What to revise before resubmitting
- CHB title: name the demonstrated contribution without prestige language, unsupported causality, or breadth the sample cannot carry.
- CHB abstract: align the question, data, method, decisive result, uncertainty, and bounded implication. Remove claims absent from the evidence.
- CHB introduction: identify the reader's decision and precise gap. Distinguish missing knowledge from a missing application.
- CHB related work or theory: compare the nearest alternatives, define constructs and assumptions, and explain what changes.
- CHB data and sampling: document inclusion, exclusion, provenance, missingness, observation unit, leakage, and context boundary.
- CHB methods: expose assumptions, controls, preprocessing, parameter choices, software, validation units, and reproducibility details.
- CHB results: report effect size or performance with uncertainty, negative findings, sensitivity checks, and failure cases.
- CHB figures and tables: make denominators, units, sample sizes, legends, exclusions, baselines, and uncertainty readable.
- CHB discussion and limitations: separate observation from mechanism, test alternatives, and state where transport or application stops.
- CHB supplement, data, and code: provide a testable audit trail with ethical, privacy, license, and access limits.
- Next-journal cover letter: explain why the revised Computers in Human Behavior paper belongs to the destination and list substantive repairs.
Run a clean read from each CHB claim to its artifact. Every use of “novel,” “robust,” “general,” “effective,” “causal,” or “practical” should point to evidence proportional to that word.
Check the repaired manuscript and destination fit before resubmitting.
Transfer, appeal, or submit fresh?
Use a CHB transfer when the offered journal matches the revised psychological knowledge about how computers shape and express human behavior contribution, the current publisher process is acceptable, and the team can address prior advice before evaluation. Treat reviewer reports as part of the record unless the instructions say otherwise.
Appeal a Computers in Human Behavior decision only when a specific factual or procedural error could alter it. Follow the publisher policy linked below. Disagreement with novelty, significance, scope, or editorial judgment is normally better handled through revision and a new destination.
Submit the revised CHB paper fresh when its audience lies elsewhere, major changes alter it, or the offered venue is convenient but wrong. Do not submit elsewhere while a Computers in Human Behavior appeal, transfer, or parallel evaluation remains active. Never make a simultaneous submission.
Stress-test the next journal choice
Before uploading the former CHB manuscript, write a 150-word editor test naming its problem, intended readers, contribution, design, strongest evidence, uncertainty, consequence, and limitation. Then answer four questions:
- Would the destination publish this CHB article type and scientific center according to its current scope?
- Does the revised first page reveal why its readers care without inheriting Computers in Human Behavior prestige framing?
- Did the revision resolve the controlling CHB rejection reason in evidence, not only prose?
- Can the next editor identify the former Computers in Human Behavior paper's contribution and boundary without the supplement?
If the same CHB editor test fits every destination unchanged, routing is unfinished. Rewrite it until the audience and evidence obligations become specific to psychological knowledge about how computers shape and express human behavior.
In our pre-submission review work with Computers in Human Behavior manuscripts
We audit each Computers in Human Behavior claim across the components its editor and reviewers can inspect. These are not acceptance-rate estimates; they are CHB repair patterns that determine whether a rejected paper becomes coherent.
Pattern 1: Computers in Human Behavior and technology adoption substitutes for psychological explanation
We observe this in Computers in Human Behavior manuscripts when reviewers question construct definitions, competing mechanisms, temporal ordering, discriminant validity, and behavior. We audit the Introduction, hypotheses, measures, model, and Discussion. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.
For the technology adoption substitutes for psychological explanation pattern, we compare the strongest CHB claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.
Pattern 2: Computers in Human Behavior and one self-report instrument supplies predictor and outcome
We observe this in Computers in Human Behavior manuscripts when reviewers question common-method bias, source separation, objective traces, timing, reverse causality, and response quality. We audit the design, measures, ethics, analysis, and limitations. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.
For the one self-report instrument supplies predictor and outcome pattern, we compare the strongest CHB claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.
Pattern 3: Computers in Human Behavior and platform-specific findings become claims about people
We observe this in Computers in Human Behavior manuscripts when reviewers question affordances, algorithmic exposure, user selection, culture, age, task, and historical period. We audit the sampling, context table, robustness checks, Discussion, and abstract. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.
For the platform-specific findings become claims about people pattern, we compare the strongest CHB claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.
Pattern 4: Computers in Human Behavior and statistical significance is presented as human consequence
We observe this in Computers in Human Behavior manuscripts when reviewers question effect size, uncertainty, baseline risk, practical threshold, heterogeneity, and plausible harm or benefit. We audit the Results, figures, tables, conclusion, and policy or design implications. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.
For the statistical significance is presented as human consequence pattern, we compare the strongest CHB claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.
Across CHB reviews, we inspect contradictions between the clean manuscript, supplement, figures, reporting statements, code or data availability, and cover letter. A repaired analysis absent from the abstract, or a narrowed conclusion paired with an unchanged title, leaves two versions of the Computers in Human Behavior contribution.
We observe that the strongest CHB rerouting decisions often lower one claim while increasing trust. A paper improves when it states a narrower population, mechanism boundary, application-stage result, or specialist readership. The goal is to make psychological knowledge about how computers shape and express human behavior evidence and audience agree.
Final routing rule
Choose the next journal only when the revised manuscript can state technology exposure -> psychological construct -> design and measurement -> behavioral evidence -> bounded mechanism -> human consequence without skipping an unsupported link. Recheck live scopes and author instructions immediately before submission because policies and article types can change.
How this page was created
For Computers in Human Behavior, we checked current publisher pages, official author and appeal guidance, destination scopes, the Manusights URL inventory, and live exact-query results on July 13, 2026. Official sources establish policy and scope; the CHB matrices and review patterns are Manusights analysis.
The Computers in Human Behavior source cluster recorded 0 impressions and 2 preview starts in available demand evidence. That is a journal-level or product-intent proxy, not proof of exact rejected-from query volume. Read final Search Console data after 14 complete days; at 21 days, keep, revise, consolidate, or stop the CHB owner.
Frequently asked questions
Classify the decision as desk rejection, rejection after review, or a transfer or referral outcome. Extract the controlling scope, contribution, methods, audience, and evidence concerns; repair portable defects; then route the revised paper by its real contribution.
Plausible routes include Computers in Human Behavior Reports, Behaviour & Information Technology, International Journal of Human-Computer Studies, but the correct destination depends on the decision letter, revised contribution, evidence, and intended readers. A nearby journal is not automatically an easier journal.
Appeal only when a specific factual or procedural error could change the decision. Disagreement about novelty, significance, scope, or editorial judgment normally calls for revision and rerouting.
Yes after the original process and any appeal or transfer choice are closed. Do not make a parallel or simultaneous submission. Address portable reviewer concerns before uploading elsewhere.
Sources
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Anthropic Privacy Partner. Zero-retention manuscript processing.