TOEIC Link Writing — Parallel Structure in Coordinated and Listed Items: How Grammatical Symmetry Across Conjoined Elements Recovers 3 to 4 Rubric Points on the Structure Sub-Score
Parallel structure is the discipline of keeping conjoined elements in the same grammatical form. When a candidate writes "the training improved accuracy, response time, and it raised confidence," the three items joined by and are not in the same form — the first two are noun phrases, the third is a clause. Each fragment is grammatical read alone. The fault exists only in the relationship between them, and that is exactly why candidates who are otherwise strong on grammar accuracy keep losing points here: they proofread each clause in isolation and never audit the coordination that ties the clauses together.
Faulty parallelism is the most common structural error in TOEIC Link writing responses at band 22 and above. It rarely shows up in the beginner bands because beginners write short, single-clause sentences with nothing to coordinate. It emerges precisely when a candidate starts to write ambitiously — combining ideas with and, or, but, and building lists — because ambition creates coordination, and coordination is where parallelism breaks. The structure sub-score carries roughly 20% of the rubric weight at band 24 and above, and a response riddled with asymmetric coordination reads as unpolished even when every individual clause is correct. Fixing parallelism recovers 3 to 4 points on that sub-score without adding a single new grammar structure or vocabulary item. For the adjacent structural levers, see the clausal subordination and syntactic complexity calibration guide and the foundational parallel structure and balanced constructions grammar guide.
Why raters penalize asymmetry they cannot name
A rater does not stop mid-response and label a sentence "faulty parallelism." What happens is faster and less conscious: the reader's eye expects the third item in a list to arrive in the same shape as the first two, and when it arrives in a different shape, the reader stumbles for a fraction of a second. That micro-stumble registers as roughness. Multiply it across a response with six or seven coordinated structures and the whole piece reads as uncontrolled, even though the rater could not point to a single ungrammatical clause.
This is why parallelism punishes strong candidates specifically. A weak response has few coordinations, so it has few chances to break parallelism. A strong, ambitious response coordinates constantly — and each coordination is a fresh opportunity for the shapes to fall out of alignment. The skill does not scale automatically with grammar knowledge; it has to be trained as its own audit.
The four parallelism failure modes
Failure 1 — The mixed-category list
The classic error: a list of three or more items where the items belong to different grammatical categories. "The role requires attention to detail, being organized, and to communicate clearly" mixes a noun phrase, a gerund phrase, and an infinitive phrase. The fix is to choose one category and convert all items to it: "attention to detail, organization, and clear communication" (all noun phrases), or "paying attention to detail, staying organized, and communicating clearly" (all gerund phrases). Pick the category that reads most naturally for the head noun, then force every item into it.
Failure 2 — The correlative mismatch
Correlative conjunctions — both … and, either … or, neither … nor, not only … but also — demand that the element after the first half matches the element after the second half. "The plan not only reduces cost but also it improves quality" is faulty because reduces cost (verb phrase) does not match it improves quality (clause). The fix: "The plan not only reduces cost but also improves quality." The rule is mechanical — whatever grammatical unit follows the first correlative must be the exact unit that follows the second.
Failure 3 — The dropped auxiliary or preposition
When a shared auxiliary verb or preposition governs multiple items, it must either be repeated for every item or stated once and validly shared by all. "The report was reviewed, corrected, and sent to the client" is fine — was validly governs all three past participles. But "The candidate was interviewed and offered the position" quietly changes voice: was interviewed is passive, was offered is passive, so this one is actually fine — the trap is "The candidate was interviewed and then accepted the offer," where was cannot govern accepted. Audit every shared auxiliary by testing it against each item individually.
Failure 4 — The comparison asymmetry
Comparisons with than or as … as require the two compared elements to be the same kind of thing. "Writing a clear email is more effective than to schedule a meeting" compares a gerund phrase to an infinitive phrase. The fix: "Writing a clear email is more effective than scheduling a meeting." Comparisons are coordination in disguise — the two sides of the comparison are conjoined elements and must be parallel.
The coordinator-and-list audit
The reliable way to catch parallelism errors is not to read for meaning — meaning reads fine, which is the trap — but to run a targeted structural pass. After drafting, do a dedicated sweep that does only this:
- Find every coordinator. Circle every and, or, but, nor, and every correlative pair. Each one marks a coordination that must be checked.
- Bracket the conjoined elements. For each coordinator, identify exactly which units it joins. This is the step candidates skip, and skipping it is why the error survives.
- Name the category of each unit. Noun phrase, verb phrase, gerund, infinitive, clause, adjective. Write the category label above each bracketed unit if you have to.
- Confirm the categories match. If they do not, rewrite the outlier to match the majority — usually the first item sets the pattern.
This audit takes about ninety seconds on a typical response and catches the overwhelming majority of parallelism faults. Because it is mechanical, it works even under exam pressure when reading-for-meaning fails.
The six-week rewrite routine
Parallelism is a proofreading reflex, and reflexes are built by repetition on your own output, not by reading rules.
- Weeks 1–2 — Detection. Take ten of your past writing responses and run the coordinator-and-list audit on each. Do not rewrite yet; just find and mark every faulty coordination. The goal is to train your eye to stop at coordinators automatically. Most candidates find two to four faults per response and are surprised, because the responses read fine.
- Weeks 3–4 — Repair. Now rewrite each marked fault three different ways — once forcing all items to noun phrases, once to gerunds, once to full clauses. This builds the flexibility to choose the category that reads best rather than defaulting to whichever category the first item happened to land in.
- Weeks 5–6 — Prevention. Write fresh responses and run the audit as the final step before submitting. The target is zero faults caught on the audit — not because you stopped making them while drafting, but because you now catch them reliably in the sweep. Fluent writers break parallelism while drafting all the time; the difference is they catch it on review.
The one habit that fixes most of it
If you internalize a single rule, make it this: whenever you write a coordinator, immediately check that both sides are the same grammatical shape before you continue the sentence. Most parallelism faults happen because the writer starts a coordination, gets pulled forward by the idea, and completes the second element in whatever form the thought arrived in — not the form the first element established. Pausing for half a second at each and to confirm the shapes match is the entire discipline. It costs almost nothing in drafting time and recovers structure-sub-score points that no amount of additional vocabulary will buy. For how parallelism interacts with information ordering, see the end-weight and given-new information ordering guide.
Parallelism is not an advanced flourish. It is basic structural hygiene that becomes visible precisely when a candidate is good enough to coordinate ambitiously — and that is exactly when the rubric starts rewarding the candidates who keep their coordinations clean.