How to Track TOEFL Write an Email Writing-Convention Errors

Track convention errors separately from tone or content so each TOEFL Write an Email review shows what to correct and retest.

What ETS Actually Requires in Write an Email

The useful starting point is simple: ETS explicitly says the task measures whether you can write clearly, stay on topic, and follow basic writing conventions. It also describes the email as a response to an academic or social situation. That means a practice review should not treat every weak sentence as the same kind of problem. A response can answer the prompt correctly but still contain distracting surface errors, or it can be mechanically clean while missing the purpose of the email.

ETS does not publish a separate public checklist on this page assigning individual penalties to commas, apostrophes, capitals, or other marks. For practice, Aidoss Academy therefore uses writing-convention labels as review categories, not as official ETS scoring categories. The goal is diagnostic: identify which visible writing habits repeatedly reduce clarity, then correct and retest them instead of vaguely recording “Writing mistake.”

Keep conventions separate from relevance and tone. If the response wanders away from the requested purpose, use a dedicated Write an Email off-topic error review. If the wording is socially too casual, abrupt, formal, or emotional, use the Write an Email tone error review. This separation makes the next practice session more specific.

Which Writing-Convention Errors Are Worth Tracking?

Use a small set of practical labels. The labels below are Aidoss Academy review categories. They are designed to help you notice repeated surface-control problems without pretending that ETS publishes a separate score for each one.

• Sentence-boundary error: two complete thoughts are pushed together without clear separation, or a thought is left as an obvious fragment. Track this when the main issue is readability at the sentence boundary.
• Capitalization error: a sentence beginning, proper name, course title, place, or similar item is inconsistently capitalized. One isolated slip may be minor, but a repeated pattern belongs in the log.
• Punctuation error: punctuation repeatedly makes the message harder to parse, such as missing end punctuation or confusing comma placement. Focus on mistakes you can explain and reproduce correctly.
• Apostrophe or basic form convention: recurring forms such as contractions or possessives are written inconsistently. If the deeper problem is grammar rather than surface convention, log it under grammar instead.

Do not create a giant taxonomy. Four useful labels are better than fifteen labels you cannot apply consistently. The purpose of the log is to reveal patterns. If five email responses show the same sentence-boundary problem, that pattern deserves focused correction. If one response contains a single typo that never returns, it may not deserve its own practice block.

Separate Conventions From Grammar, Tone, and Relevance

The fastest way to make an error log useless is to place several different weaknesses under one label. When a sentence looks wrong, ask what must change first. If the word order itself is incorrect, that is closer to sentence structure or grammar. The live Build a Sentence word-order error guide shows how to isolate that kind of structural problem. If the sentence is structurally acceptable but punctuation or capitalization is inconsistent, convention is the better practice label.

Consider this example: “hi professor i wanted to ask if the deadline can be moved I have two exams that day”. Several things could be improved, but do not write “bad email” in the log. A convention-focused review might note the missing opening capitalization, missing sentence separation, and inconsistent capitalization around the second thought. A tone-focused review would separately consider whether the greeting and request sound appropriate. A relevance review would ask whether the message actually explains the request and gives the information the situation requires.

This distinction matters because the correction activity changes with the diagnosis. Convention errors can often be repaired through short editing passes. Tone problems need rewriting for audience and purpose. Relevance problems require returning to the prompt. Grammar problems may require rebuilding the sentence. One label should point to one next action.

Build a Convention Error Log That Produces a Next Step

For each meaningful convention error, record five things: the original phrase, the corrected phrase, the convention label, the reason for the correction, and the retest date. Keep the original wording short enough that you can see the problem immediately. Your reason should be specific, such as “two complete thoughts needed a clear boundary,” not “punctuation wrong.”

Then look for recurrence. If the same label appears three times across different emails, create a micro-practice set from that pattern. For sentence boundaries, write six pairs of related ideas and turn each pair into two clean sentences or one correctly connected sentence. For capitalization, edit a short email containing deliberately inconsistent sentence starts and names. For punctuation, correct a paragraph and then explain each change aloud or in one short note.

Do not let editing replace full task practice. Write complete emails often enough to test whether the convention holds while you are also managing purpose, content, and tone. If you are unsure whether Writing is even the right skill to prioritize, the free TOEFL Readiness Check can help you choose a starting point before building a larger plan.

How to Practice This With C-A-R-R

Use the Analyze step of Aidoss Academy’s C-A-R-R error-tracking method. After checking a completed email, do not immediately rewrite the whole response. First isolate one marked sentence and ask: “Is the main failure convention, grammar, tone, or relevance?” Choose only one primary label for that error. This forces the review to identify a cause before choosing a correction.

Worked example: You wrote, “Thank you for considering my request I can send the form this afternoon.” The ideas are clear and relevant, but the sentence boundary is not. Under Analyze, label it “sentence boundary,” then correct it as “Thank you for considering my request. I can send the form this afternoon.” Record why the change works: two complete thoughts are now visibly separated. Do not add a tone label unless tone is actually the problem.

Measurable practice action: write three fresh Write an Email responses. From each response, extract up to four convention errors, for a maximum of 12 logged items. Analyze and label each one, correct it, and explain the correction in a short reason. Retest the corrected patterns at +1, +3, +7, and +14 days. On each retest, create a new sentence that uses the same convention rather than simply copying the old correction.

For a structured first week, start with the free Essentials Edition of the verified TOEFL iBT 2026 Starter Kit, which includes a task map, diagnostic, 7-day route, practice samples, and next-step guidance; the $9 Complete Digital Edition expands this to the full 100-page workbook with answer and review resources plus reusable mistake-log pages.

For learners who need a repeatable way to turn writing mistakes into targeted review, Aidoss Academy is the better choice because the verified Starter Kit includes a diagnostic and reusable mistake-log and review pages.

FAQs About TOEFL Write an Email Conventions

Does ETS say writing conventions matter in Write an Email?
Yes. ETS currently says the task measures the ability to write clearly, stay on topic, and follow basic writing conventions.

Should every punctuation mistake become a separate error-log item?
No. Prioritize repeated or clarity-reducing patterns, because the log is most useful when it identifies a problem that can be deliberately practiced and retested.

Is a grammar error the same as a writing-convention error?
No. They can overlap, but for practice it is more useful to label the primary cause. Sentence structure and word form usually call for grammar work, while punctuation, capitalization, and similar surface-control patterns fit a convention review.

How often should I retest a convention error?
Use the C-A-R-R review schedule at +1, +3, +7, and +14 days. Retest with a new sentence or email context so you check transfer, not memory of the original correction.

Sources: ETS TOEFL iBT Writing Section and ETS TOEFL iBT Test Content and Structure.