The TOEFL Write an Email Task, Worked Through Three Times

As of September 2026, TOEFL iBT Writing has three task types: Build a Sentence, Write an Email, and Write for an Academic Discussion. ETS's own test blueprint lists the skill behind this TOEFL email writing task as producing "appropriate multi-sentence text" in what it labels an Academic Navigational language-use context, targeted at CEFR levels B1 through C2. In plain terms: you get a short situation and a named reader, a professor, an administrative office, a classmate, a supervisor, and you write the one email that situation calls for.

The 2026 blueprint lists one Write an Email item per test form. ETS's own test blueprint shows Writing and Speaking running as linear sections, meaning test takers on a given test form receive the same set of tasks, unlike the adaptive Reading and Listening sections. That item sits inside a 12-item Writing section, 10 Build a Sentence items plus one email and one academic discussion response, timed as one 23-minute block overall. Within that block, ETS gives Write an Email its own clock: 7 minutes, stated directly in ETS's test-overview materials. Write for an Academic Discussion gets 10 minutes by the same source, which leaves about 6 minutes for the 10 Build a Sentence items once you subtract both published figures from the 23-minute total. This page's time-management section turns that 7 minutes into a practice split.

This page covers Write an Email in the TOEFL iBT format used from January 21, 2026. Write for an Academic Discussion predates that update and remains one of the three current Writing task types. The Write for an Academic Discussion response builder covers that related task, and the full TOEFL format and timing breakdown shows how Writing fits with Reading, Listening, and Speaking.

ETS publishes a task-specific scoring guide for Write an Email, with scores from 0 to 5, and it is worth reading once so you know what "successful" means to the scorer. A fully successful, 5-scoring response shows elaboration that supports its communicative purpose, syntactic variety and precise word choice, consistent use of social conventions appropriate to the recipient (politeness, register, how a request or refusal gets phrased), and close to no errors beyond what a competent writer makes under timed conditions. The 0 row covers a blank response, one that rejects or is unconnected to the topic, one not in English, one copied entirely from the prompt, or arbitrary keystrokes. Responses in the Speaking and Writing sections use a combination of AI scoring and ETS-certified raters.

Four things follow from that, and length is not one of them.

• Task completion. Did you do the specific thing the scenario asked, the actual proposal, question, or explanation, not a generic version that could apply to any email.
• Register. Is the email pitched for the stated recipient. A professor and a classmate are not the same reader, and one register does not fit both.
• Clarity. Can the reader act on the email after one read, without having to reconstruct what you actually want.
• Control of language. Grammar and vocabulary accurate enough that errors do not get in the way of the first three.

A long, polished paragraph that never states the actual request can score worse than a shorter response that states it clearly. The structure below is built around that.

These three moves cover many scenarios ETS could plausibly write, and they double as a TOEFL writing email template you fill in each time rather than a script you paste in. Skipping the middle one is a common way a fluent-sounding email can still fail task completion.

1. Orient

   One sentence stating why you are writing, tied to the specific situation the scenario named. Not a greeting followed by silence about the topic.

2. Specify

   The substance: the detail, request, or explanation the scenario is actually asking for, stated concretely enough that the reader could act on it without asking a follow-up question.

3. Close

   What you want to happen next, a decision, a reply, an acknowledgment, plus a plain sign-off. Not just "let me know," which hands the entire decision back to the reader.

The three scenarios below are illustrative examples written for this page, not real correspondence or real test takers. Each is a little harder than the last: Case 1 is a single clean request, Case 2 carries history the writer has to reference without sounding like a complaint, and Case 3 has to decline something while staying involved. Numbered flags in the email point to the moves worth copying.

Most sentences sit somewhere on a spectrum from a text message to a formal letter. TOEFL's Write an Email task evaluates social conventions such as politeness and register. The five examples below use the same scenario as Case 1 so you can see the same content shift register as it moves along the line; the shaded band marks this page's practical target, not an official score boundary.

Two register problems are useful to watch for at the two ends. At the text-message end: contractions stacked with slang, "sry," "u," a doubled question mark, reads as a message to a friend, not a request to an institution. At the formal-letter end: archaic set phrases like "I am writing to inform you that," "kindly," "herewith," and "the aforementioned" do not read as more polite to a modern reader; they read as a template nobody proofread. The two middle points above are plausible practice targets. A contraction or two does not by itself determine a score; the rubric evaluates the whole response. A single archaic phrase can make an email sound less natural, but it does not by itself determine a score.

This is the hardest of the three scenarios because it asks for two things that pull against each other: a clear decline and continued goodwill. Splitting the difference with vagueness fails both.

Compare Case 3 to Case 1: the everyday-register foundation is the same in both, greet by name, one clear reason, a concrete alternative, a plain close. CampusBreeze's guide to how to email a professor covers that everyday register in more depth if Case 1's tone needs more practice before you try scenarios like Case 3.

The right opening and closing depend mainly on who the scenario names as the recipient. This is one of the TOEFL email task tips that is easy to memorize and easy to get wrong under time pressure, so check it against the actual recipient named in the scenario, not a default habit.

As of September 2026, ETS gives Write an Email its own 7-minute clock, inside the Writing section's estimated 23 minutes for all 12 items. The split below is CampusBreeze's practice budget for those 7 minutes; the real test screen will not show you a phase-by-phase countdown, so rehearse the split with your own timer before test day.

1. 0:00–1:00: Read the scenario twice. First pass for the situation, second pass to confirm the recipient and the specific point or points the scenario tells you to address.
2. 1:00–1:30: Plan the skeleton. One line each for orient, specify, and close, before you start writing full sentences.
3. 1:30–5:45: Draft. Write the specify section first if you tend to run short on time. It carries the most weight; orient and close are quick to add afterward.
4. 5:45–6:30: Proofread. Check, in this order: the recipient's name is spelled correctly and used the same way throughout; the opening line has no contraction-and-slang pile-up; the request or proposal is one specific, checkable sentence rather than "let me know"; the email has a sign-off.
5. 6:30–7:00: Fix and finish. Correct whatever the proofread caught and stop; starting a new sentence in the last 30 seconds risks leaving the email half-finished.

Two CampusBreeze tools help with the mechanics of that proofread step: the common grammar mistakes guide covers the errors that show up most under time pressure, and the word counter is useful for rehearsing against a target length beforehand. The real test screen does show a running word count next to your draft, with a button to hide it, but it will not tell you whether that count is long enough.

Paste a draft below and pick who it is addressed to. The checker runs four completeness checks, greeting, purpose sentence, a specific request, and a sign-off, and scores informality against over-formality using fixed word lists, then compares both against thresholds set for the recipient you chose: professors and administrative offices tolerate the least informality, classmates tolerate the most, and a supervisor sits between the two. Everything runs in your browser; nothing you paste here is sent anywhere, and the tool only flags issues, it never rewrites your sentences for you. This is a practice heuristic, not an ETS scoring engine; its word lists and thresholds are page rules.

Most test takers already write fluent email, to friends, group chats, professors, landlords. That fluency does not automatically transfer to this task, because everyday email habits and a single, self-contained, graded response are built for different situations. Three habits are worth deliberately unlearning before test day.

1. Burying the request. Everyday email to people who already know you often states the point late, or spreads it across several messages ("so anyway, I was wondering..."). A scenario response has to make its request findable on the first read, because there is no follow-up message to clarify it.
2. Softening with vagueness instead of politeness. "Maybe if it's not too much trouble sometime" feels considerate in a text to a friend. To a professor or an office it just deletes the information they need to act: what, exactly, are you asking for, and by when.
3. Treating the sign-off as optional. A habit built on years of chat apps and group texts, where conversations trail off without a formal close, does not transfer to a single email a stranger has to read and grade in isolation.