How to Write a Computers and Education Cover Letter (With Template)

Source: Computers & Education guide for authors and Elsevier cover-letter guidance, accessed June 2026.

The order matters. The handling editor scans for educational signal density, not literary polish. A letter that names the contribution, the learning evidence, the theory, and the fit in that sequence is faster to read and easier to route to double-anonymized review.

Computers & Education, like every reputable Elsevier title, expects an explicit originality and approval statement. Use language this direct, verbatim:

This manuscript is original, has not been published previously, and is not under consideration for publication elsewhere. All authors have read and approved the final manuscript and agree to its submission to Computers & Education.

That single declaration covers the two things the desk screen checks first: that the work is not a duplicate submission, and that every author has approved it. Vague phrasing here ("we think this is new") reads as carelessness, and carelessness in the letter primes the editor to expect it in the manuscript.

The opener is the unique signal of a Computers & Education letter. It must put the learning change first and the technology second. Compare the contrastive pair below, and avoid the weak shape:

Weak opener (avoid this): "We present a novel LLM-based feedback system built on a fine-tuned retrieval pipeline and evaluate it in an undergraduate programming course."

Strong opener (use this): "We show that automated, theory-grounded feedback restructures how novice programmers self-regulate their debugging, improving delayed conceptual-knowledge retention over a worked-example control; the AI design is the mechanism, not the contribution."

The weak version fails because the contribution is the architecture, the outcome is unstated, and there is no learning claim an education editor can route. The strong version works because the learning change is the load-bearing claim, the outcome is a validated retention measure, and the editor can already see why this belongs in an education journal rather than a systems venue.

Computers & Education submits through Elsevier Editorial Manager (the portal you reach from submit.elsevier.com, routed to the journal's submission site), and the system collects several declarations during submission. Stating them in the cover letter signals a careful author and prevents the desk screen from bouncing the package back for a missing element.

For reference, the journal lists a 250 word abstract limit and an optional open-access article publishing charge of USD 4,930 excluding taxes, so the cover letter is the place to flag a funder mandate or a read-and-publish agreement if one applies.

Suggested reviewers: name 3 to 5 reviewers who are genuine edtech researchers, with affiliations and institutional emails. Exclude reviewers who are recent collaborators, co-authors from the last few years, or same-institution colleagues. If you need a referee excluded for a real conflict, say so and give the reason. Editorial Manager may collect reviewers in a separate step; if it does, keep the letter brief rather than duplicating the full list.

Declaration of competing interest: required even when none exist. State it plainly. Elsevier's Declaration Tool produces an ICMJE-compliant statement you can upload alongside the manuscript.

Data availability statement: name where the data live (a repository DOI is strongest) or state the access condition. Human-subjects (student) data also needs an ethics-approval statement.

Funding statement: name the grant and funder, or state that there was no external funding.

Preprint disclosure: if the work is on a preprint server, disclose the link in the letter so the editor is not surprised at screening.

A clean declarations block does not rescue a weak study, but a messy one makes a borderline study easier to decline.

Here is the part authors rarely picture. Computers & Education editors screen the cover letter against three questions before they invite a single reviewer. When the handling editor opens your submission, they are not reading for elegance. They are asking, in order: is this education research or a technology demo? Is there a learning outcome I can defend to reviewers, or only satisfaction and clicks? Does the contribution reach beyond one course or institution?

If the cover letter answers those three in its first half, the editor keeps reading and starts thinking about which reviewers to invite. If it leads with model architecture and buries the learning claim in paragraph three, the editor has already seen the venue mismatch and can act on it before lunch. The letter is not a courtesy.

It is the first triage document the editor reads, and at Computers & Education it is read against a fast clock.

In our pre-submission review work with Computers and Education submissions, three cover-letter failure patterns predict a desk redirect more reliably than anything in the manuscript body, and each is testable against your own letter before you open Editorial Manager.

(Per Elsevier's published medians, Computers & Education issues a first decision in about 7 days, so the cover letter is read against a fast triage clock, and a letter that does not surface a learning-outcome connection can be returned before external review.) These patterns are specific to how Computers & Education reads a letter, which is why a generic Elsevier cover-letter template will not catch them.

The abstract-in-disguise letter that never names the learning outcome. The most common Computers and Education cover-letter pattern we see restates the 250-word abstract: it lists the study design, the platform, and the results, but never makes the editorial argument that the work changes learning. The handling editor's question is not "what did you build?" but "what does it change about learning, and can I defend that to reviewers?"

When the letter's outcome language stops at a satisfaction scale, an intention-to-use construct (TAM or UTAUT2 behavioral-intention items), or click-stream engagement, the editor reads a venue mismatch.

The fix is to name one validated learning-outcome measure in the letter itself, a pre/post conceptual-knowledge test with reported reliability, a delayed-retention task, or a real performance result such as grade or pass rate, and to put that learning result ahead of the satisfaction findings in the opening sentence.

The architecture-first letter that inverts the contribution. For Computers and Education submissions built on generative AI, intelligent tutoring, or automated feedback, we repeatedly see the letter lead with the model novelty (a fine-tuning approach, a retrieval pipeline, a prompting scheme) and treat the educational consequence as a downstream demonstration.

Computers & Education's published criterion is that technology must change learning, teaching, feedback, self-regulation, or assessment, not that it is novel in computer-science terms, so this inversion reads as a venue mismatch at the desk screen.

The fix touches two manuscript components the letter must reference: rewrite the contribution statement so the educational change is the load-bearing claim, and signal in the letter that the architecture detail sits in the methods or supplementary section, grounded in a learning theory (cognitive load, ICAP, self-regulated learning, productive failure) that predicts why the design should produce the effect.

The single-context letter with no generalizability or theory claim. The third pattern we see across Computers and Education cover letters is a well-run study at one institution, one course, or one cohort whose letter never tells an editor what readers outside that setting should take from it.

Computers & Education reviewers, drawn from an international edtech community, check the discussion for explicit boundary conditions, a named theory contribution (which framework the results extend or refine, not merely cite), and design implications stated as transferable patterns. When the cover letter frames the study as a local case, the editor anticipates a parochial manuscript and routes accordingly.

The fix is to add one sentence to the letter naming two or three contexts where the design should and should not transfer, state one concrete way the theory moves forward, and own the single-context limitation honestly rather than implying broader reach than the sample supports.

Check whether your Computers and Education cover letter surfaces a learning-outcome claim before you commit to the Elsevier submission route.

These are the recurring letter-level errors that draw a desk redirect at Computers & Education, distilled into a checklist you can run against your own draft.

• The journal-flattery opener. "Computers & Education is the leading edtech journal, so we are delighted to submit" wastes the most valuable line. The editor knows the journal's standing; the useful sentence is why this manuscript belongs here.

• The buried learning claim. The educational consequence appears in paragraph three after a paragraph on the platform and a paragraph on the dataset.

By then the editor has already read a technology demo.

• The unbounded significance pitch. "This work has broad implications for education worldwide" with no named transfer contexts reads as inflation, not generalizability.

• The silent declarations. A letter with no originality statement, no all-author-approval line, and no competing-interest declaration forces the desk screen to bounce the package back before it is even read on merit.

If you cannot write a convincing learning-outcome sentence without reaching past your data, that is useful information. It usually means the study measured engagement and satisfaction but not learning, and Computers & Education will read that gap immediately. If your strongest contribution sentence is really about the model and not the pedagogy, the honest next step is to compare Computers & Education: Artificial Intelligence or another AI-in-education venue, or to consult our pre-submission review for education research guide before you write the letter.