Good answers don’t just contain the right ideas—they flow. Cohesion is the glue that helps the reader/listener move from A to B without friction. Use the right marker at the right time, keep reference words clear, and build paragraphs that guide the eye.
Register choices (formal ↔ neutral ↔ friendly)
- Formal: however, therefore, in addition, consequently, whereas, provided that
- Neutral: but, so, also, meanwhile, once, next
- Friendly: by the way, anyway, then, so (avoid in formal tasks)
Tip: Use one clear marker per sentence. Over-marking sounds mechanical.
Cohesion is more than markers: five invisible tools
1) Given → New ordering
Start with what the reader already knows, end with the new info.
- Your application was received yesterday. The missing item is the signed consent form.
2) Reference words (this/that/it/they) with clear anchors
- Good: The delivery was late. This delay affected our schedule.
- Ambiguous: The delivery was late. This affected us. (What is “this”?)
3) Lexical chains (repeat key terms with small variation)
Keep the topic noun steady with near-repeats: inspection → safety inspection → scheduled inspection rather than hopping terms.
4) Parallel structure
Match grammar in lists and comparisons for smooth rhythm.
- We will inspect, document, and repair. (not: inspect, documentation, and repair)
5) Signposted paragraphs (topic sentence → support → action)
One main point per paragraph, then details, then a next step or result.
Natural-sounding bundles (plug into sentences)
Reason/Result: because, as a result, therefore, consequently
Contrast/Concession: however, that said, although, even though
Ordering: first, next, then, finally
Condition/Timing: if, once, as soon as, no later than
Clarifying/Focus: specifically, in other words, in particular, importantly
Summary/Decision: overall, in short, ultimately, we will…
Email & message flow templates (swap your details)
Problem → impact → ask (formal)
The elevator has been out since June 3. As a result, residents on upper floors have difficulty accessing their units. Therefore, we’re requesting an update on the repair timeline and temporary accommodations for deliveries.
Update with clear steps (neutral)
The technician inspected the unit this morning. Next, the part will arrive on Thursday; afterwards, we’ll schedule installation for Friday 2–4 p.m..
Recommendation with concession (formal)
The current budget is limited. Nevertheless, replacing the router now will reduce outages. In summary, we recommend authorizing the purchase this week.
Friendly coordination (keep it clear)
I can do 2:30. If not, tomorrow morning works; otherwise, let’s keep Friday.
Before → After (compact examples)
Before (choppy, unclear):
I applied last week, also I didn’t get a reply, however I need confirmation. Due to the fact that I’m traveling, so I need it fast.
After (cohesive, calm):
I applied last week. Since I’m traveling on Monday, I need confirmation by Friday. Could you confirm the status?
Before (missing logic):
The technician came. The internet still drops.
After (relation signaled):
The technician inspected the line; however, the connection still drops in the evening. As a result, we’d like to schedule a follow-up visit.
Quick build kit (copy these bones)
- Reason → Result: Because ____, as a result ____.
- Concession → Ask: Although ____, could you ____?
- Timeline: First ____. Next ____. Finally ____.
- Condition: If ____, we’ll ____; otherwise ____.
- Summary → Action: In short, ____. Therefore, we ____ by [date].
Use one clear relation per sentence, keep references precise, and let your paragraphs do the gentle guiding. That’s cohesion that scores.