TOEFL Write an Email Practice

What Write an Email actually tests

The task gives you a situation and a reader, and asks for an email that does something: request an extension, decline an invitation, report a problem, follow up on an application. What is being scored is whether the register fits the reader, whether the reason is supported, and whether the message is organized so the reader can act on it.

The reader is the hinge. The same content sent to a professor, an administrator and a roommate needs three different registers, and the most common cause of a low band on this task is not grammar but a register that misses the relationship.

Where students lose marks on this task

Writing a formal letter to a peer is the first leak, and it reads as strange rather than polite. The second is burying the request. If a reader has to reach the third sentence to learn what you want, the email has failed a job it was set to do, whatever else it does well.

The third is a reason with no example behind it. Saying you have a scheduling conflict is a claim; saying you have a lab section that runs until six on Thursdays is a reason. The fourth is length. Seven minutes for 130 to 140 words means one draft and a quick check, so students who plan for three minutes end up submitting an unfinished second half.

How the 20 levels drill it

Most levels are five micro-drills rotated across the moves the task is built from: matching register to the reader, choosing an opening and a closing that fit the ask, phrasing a request directly or with a hedge, completing a reason with the example that actually supports it, ordering information for a purpose, repairing a line that is too blunt or too vague, and judging whether a sentence belongs in this email at all.

Levels 5, 10, 15 and 20 are different: those are a full timed email, 7 minutes for 130 to 140 words, graded by the same engine that scores the writing practice tests. So the ladder alternates between taking the task apart and putting it back together under exam conditions.

How the required points decide your score

Every email prompt has two halves. The situation sets the scene, and then a short instruction lists what your email has to do: explain why you are writing, describe what went wrong, ask about a specific alternative. Three of them, in every email task on this site. Students read that list as a suggestion about content. The rubric treats it as the first check, ahead of organization, grammar and anything to do with tone.

The scale these are graded on runs from 0 to 5, and the bands are written in terms of those points rather than language quality. Leaving one point out is described at band 2. Leaving two out is described at band 1. The rule cuts the other way too: an email that covers all three and stays understandable does not fall below a 3, however many article and spelling errors it carries. That one fact should change how you spend your last ninety seconds. A clumsy sentence that answers the third point is worth more than a polished version of the first.

The subtler failure is a point that is present but not answered. If the instruction says describe the problem and your email says you have had trouble with the system, you have named a topic, not described a problem. A point counts as covered when the reader could repeat it back as a fact: the upload stops at ninety percent and returns the same error code every time. So count the points before you write and give each one its own sentence or two. At 130 to 140 words, a greeting and a closing leave roughly forty words per point, which is room for a claim and the detail that makes it checkable, and none for a paragraph of apology. The full band descriptors are in our lesson on how TOEFL Writing is scored.

What a strong email looks like, line by line

Take a case from the upper levels of this ladder. The archive you need for a term paper closed for repairs on Monday, the paper is due Friday, and you are writing to the professor who set it. Four sentences do the whole job, and the order they go in is not a matter of taste.

The first line names the request and what it applies to: you are writing to ask for a short extension on the term paper due Friday. Not your registration number, which is already on the account you are sending from, and not how worried you are. The second gives the cause, and it has to be second, because a sentence beginning with the reason only makes sense once a request exists for it to explain. The third supplies the measure. The archive reopens on the fourteenth, so three extra days would be enough. That number is what turns a difficulty into something a professor can approve or refuse in one reply. The fourth asks for a decision and signs off.

The weak version is not shorter, and rarely less polite. It opens with identity and apology, gives the cause without a date, asks for an extension without saying how long, and closes with a second round of thanks. Several criteria drop at once. The reader cannot act, so the request reads as vague and the reason as unsupported, even though every word is true. Fixing that costs no extra words, only different ones. Test any draft by reading back only the sentences that carry a date, a number or a named thing. If none of them do, you have written your feelings rather than your case. A full response at the bottom of the range, with a critique of what holds it there, is in this band 3 email sample.