Combining Sentences: Fixing Choppy Writing

Picture the email you've just drafted at 4:55 on a Friday. Every fact's in there. Nothing's misspelled. And yet you read it back and it sounds like a telegram:

The numbers improved this quarter. Sales were still below target. The team worked hard. We might need new strategies.

Nobody could red-pen a single one of those sentences. They're all correct. And they still read stiff — like someone tapping you on the shoulder four separate times instead of just having a conversation with you. If you've ever worried your writing sounds a bit basic, a bit robotic, this is usually why: too many short, separate sentences standing where a couple of well-chosen joins should be.

Here's the thing. Nobody's born knowing how to make sentences flow — it's not a talent you either have or don't, it's a toolkit, and a fairly small one. The good news is, once you know the moves, you'll start seeing choppy writing everywhere — in reports, CVs, LinkedIn posts, texts to landlords — and fixing it becomes almost automatic.

This piece isn't going to re-teach clause types or run-ons from scratch — those live elsewhere in the library, and I'll point you there when it's genuinely relevant. What we're doing here is the craft: which sentences to join, how, and where confident writers go wrong.

Before you read on, here's where we're heading. By the end you'll be able to: - Spot where your writing is choppy and understand why it reads that way. - Combine short sentences using conjunctions, lists, and punctuation. - Choose between combining methods based on what you actually want to emphasise. - Avoid turning everything into one breathless run-on sentence. - Use sentence combining to make emails, reports, and applications sound confident rather than stilted.

Beginner (Foundation): From Bitty to Smooth

Let's start small — with a typical "before" version, the sort of thing that goes out on Slack without a second thought:

I've finished the draft. I'm not sure about the introduction. I'll send it now.

Readable? Sure. Smooth? Not really. It's three separate taps on the shoulder where one clear sentence would do. You fix that by bringing the related ideas into the same sentence — and you've got three basic tools that do most of the work.

Tool one: and/but/or/so — for equal ideas.

I've finished the draft, but I'm not sure about the introduction, so I'll send it now.

That's three short sentences turned into one clean, useful one. (For the full definitions of what makes a sentence "complete" in the first place, that's covered over at Sentence Types — I won't repeat it here.)

Tool two: because — for reasons.

I'll send the draft now because I'm not sure about the introduction.

Because I'm not sure about the introduction is now leaning on the rest of the sentence — a dependent clause, in the proper terminology (see Dependent Clauses if you want the full picture).

Tool three: turn small related sentences into a list, which does wonders for a CV bullet:

Choppy: I managed a team of five. I set monthly targets. I ran weekly check-ins. Combined: I managed a team of five, set monthly targets, and ran weekly check-ins.

Same content. Considerably more professional.

Common Mistake: Treating "because" as if it can open a brand-new sentence on its own. ❌ I'm not coming to the meeting. Because I'm ill. ✅ I'm not coming to the meeting because I'm ill. ✅ Because I'm ill, I'm not coming to the meeting.

Pro-Tip: When you proofread, highlight any run of three or four short sentences in a row and ask: could any of these live together? Try joining one pair, read it aloud, and only keep the change if it genuinely sounds better — not just shorter.

Quick recap: - Short, separate sentences make writing feel choppy and less confident, even when every one is correct. - And/but/or/so join equal ideas — with a comma before the joining word. - Because/when/although/if join ideas where one supports or explains another. - Lists roll several related short sentences into one clean line. - "Because" needs a partner clause — it can't open a sentence on its own.

Intermediate (Development): Making Smart Choices, Not Just Joining Everything

Once you're comfortable joining sentences, the trick becomes choosing how — and that choice changes what your reader actually understands. Take this chunk from an email to a manager:

The client pushed the deadline forward. We had to rush. The team stayed late three nights this week. We still delivered on time.

There's more than one honest way to improve this.

Option A — balanced, with emphasis held back for the last line:

The client pushed the deadline forward, so we had to rush, and the team stayed late three nights this week. We still delivered on time.

Option B — cause-and-effect, more compact:

Because the client pushed the deadline forward, we had to rush and the team stayed late three nights this week, but we still delivered on time.

More economical, though there's a fair amount packed in — some readers will find that heavy in an email.

Option C — use a list for the middle:

The client pushed the deadline forward, so we had to rush: the team stayed late three nights this week, cut some optional features, and still delivered on time.

None of these is "the rule." You're choosing based on rhythm and what you want the reader to notice first.

Equal ideas vs. dependent ideas

Ask two simple questions about any pair of sentences you're thinking of joining:

1. Are these ideas equally important? Use a coordinating conjunction: Sales increased, but profits fell.
2. Is one idea clearly supporting the other — reason, time, condition? Use a subordinating conjunction: We missed the deadline because the spec kept changing.

This is how you build genuinely confident complex sentences without them sounding overdone or forced.

Avoiding run-ons and comma splices

As soon as you're comfortable combining, a new risk shows up: sticking sentences together with whatever punctuation is nearest to hand. Two complete sentences separated only by a comma is a comma splice:

❌ The client pushed the deadline forward, we had to rush.

Both halves stand alone as full sentences — the comma isn't strong enough to carry that weight on its own. Fix it by:

• Adding a conjunction: ✅ The client pushed the deadline forward, so we had to rush.
• Using a full stop: ✅ The client pushed the deadline forward. We had to rush.
• Using a semicolon: ✅ The client pushed the deadline forward; we had to rush.

There's a full guide on this at Run-Ons and Comma Splices if this is a repeat offender for you.

Common Mistake: Believing "longer = more professional." A sixty-word sentence crammed with three ideas and five commas is harder to read than two crisp ones. Combine where it helps the reader. Stop the moment it starts to feel crowded.

Keeping lists parallel

When you fold several short sentences into a list, keep the parts matching in shape:

✅ I wrote the proposal, updated the budget, and chased the client for feedback. ❌ I wrote the proposal, updating the budget, and chased the client for feedback.

That second version trips the reader because the items don't match — wrote / updating / chased. Parallelism (Parallelism) matters more than most people give it credit for; it's a big chunk of what makes a sentence feel tidy rather than lopsided.

Quick recap: - Decide whether ideas are equal (and/but/or/so) or dependent (because/when/if/although) before choosing a join. - Combining is a choice, not an obligation — pick the version that's clearest for the reader, not the shortest. - Never join two full sentences with a bare comma — that's a comma splice. - Longer isn't automatically better; clarity beats length every time. - Keep list items in matching grammatical shape so the sentence doesn't lurch.

Advanced (Mastery): Rhythm, Emphasis, and Professional Tone

If you're still with me, we can get into the subtler stuff — the part that makes writing feel polished rather than just correct.

When not to combine

Sometimes the sharper move is refusing to combine at all. Compare two lines from a personal statement:

A. I dropped out of university because my father was ill. B. My father was ill. I dropped out of university.

Version A explains neatly. Version B lands harder — each fact gets its own beat, almost like a confession. In a cover letter, you'd probably want A. In a personal essay, B might do more work. Short sentences are a genuine tool, not a fallback for people who can't write longer ones — used sparingly, they're powerful. This is what Sentence Variety is really about: a page of long sentences is just as dreary as a page of short ones.

Semicolons and colons — subtler joins

A semicolon (;) joins two closely related full sentences without a joining word at all:

The app crashed repeatedly; we had to delay the launch.

It suggests the two ideas are tightly linked — almost balanced — without the slightly conversational feel of "and."

A colon (:) introduces an explanation, example, or result:

We only had one option left: postpone the release.

Common Mistake: Using semicolons as "fancy commas" anywhere you'd normally use one. Semicolons only belong between full sentences (barring complex lists, which is its own topic entirely).

Embedding — folding detail into the sentence itself

Instead of adding another clause at the end, sometimes the sharper move is to tuck information inside the sentence:

Choppy: I've attached the report. It was prepared by our external auditor. It covers Q1 and Q2. Embedded: I've attached the report, prepared by our external auditor, covering Q1 and Q2.

You can nest this fairly deeply in formal writing:

The proposal, which was revised after the initial feedback the board gave in March, has now been approved.

Perfectly grammatical — and you can feel it start to sag if you push it further. The full mechanics of nesting live at Embedded and Nested Clauses; for everyday work writing, the rule of thumb is: embed selectively, and cut wherever you can.

Matching your context

• Everyday emails and Slack: keep it fairly short, with light combining where it genuinely helps: I've updated the document and added comments on sections 2 and 4, but I'd like your thoughts on the conclusion.
• Reports and formal documents: can carry more complex sentences, especially tying evidence to conclusions: Because the initial pilot showed a 20% increase in engagement, and costs remained within budget, we recommend expanding the programme next quarter.
• Applications and statements: want to sound controlled and reflective: During my time at the charity, where I coordinated a small team of volunteers and managed the events calendar, I developed strong organisational skills and a calm approach to problem-solving.

In all three, combining sentences well signals that you can see the relationships between your ideas — cause, contrast, condition — not just list facts. That's what reads as mature, professional writing, whatever the context.

Pro-Tip: On any important document — CV, statement, big report — highlight every sentence over thirty words and ask whether it can be safely split. Then highlight any run of three or more very short sentences and ask whether any can be joined. That one scan usually delivers eighty per cent of the improvement for about twenty per cent of the effort.

Quick recap: - Whether you combine or separate sentences changes rhythm and emphasis — and both are legitimate tools. - Semicolons and colons offer more formal ways to join closely related sentences. - Embedded clauses let you tuck extra detail into the middle of a sentence rather than tacking it on at the end. - Don't over-nest clauses — clarity is more impressive than complexity, every time. - Match your sentence style to the context: email, report, application, or essay.

UK vs US Usage

For combining sentences, UK and US English follow the same underlying rules — the joining words, the logic of coordination and subordination, and the comma-splice problem are identical on both sides of the Atlantic. The one genuine, narrow difference is a comma habit: UK writing tends to place a comma before a coordinating conjunction joining two full sentences (We reviewed the draft, and we sent the final version), while American style guides are, on the whole, a touch more insistent that this comma "should" be there in formal writing. Neither is wrong — it's house style, not grammar law — so match whichever style sheet you're writing for. Beyond that, the only differences you'll meet are ordinary spelling swaps elsewhere in the library, like colour [US: color]; nothing that touches how sentences actually combine.

Key Takeaways

• Short, choppy sentences make writing feel basic, even when the ideas underneath are genuinely good.
• Combine with conjunctions, lists, or punctuation (semicolons, colons) to show how ideas relate, not just that they're related.
• Decide whether ideas are equal (and/but/or/so) or dependent (because/when/if/although) before choosing a join.
• Never join two full sentences with a bare comma — that's a comma splice, and readers notice.
• Use a mix of shorter and longer sentences on purpose to control rhythm, emphasis, and tone.
• In professional writing, well-combined sentences signal maturity and confidence — badly-combined ones signal the opposite.

Check Your Understanding

1. Combine using "although": The event was well organised. Attendance was lower than expected.
2. Fix the comma splice (several correct answers exist): The system went down, we had to process all orders manually.
3. Turn these into one sentence with a parallel list: I answered customer emails. I updated the FAQ page. I spoke to the product team about common issues.
4. Combine so the second part clearly gives the reason for the first: I've decided not to apply for the promotion. I don't want to move to London.
5. Rewrite these three sentences as two, using separation for emphasis: I checked my bank account. The payment hadn't arrived. I called the finance department.

Internal Links

• 2.1 Sentence Types — for definitions of simple, compound, and complex sentences
• 3.0 Clauses (routing only)
• 3.1 Dependent Clauses — for what makes a clause unable to stand alone
• 3.2–3.4 Specific Clause Types — for adverb, relative, and noun clauses in detail
• 3.6 Embedded and Nested Clauses — for deeper nesting inside a single sentence
• 4.4 Fronting — for moving a clause to the front of a sentence for emphasis
• 5.2 Run-Ons and Comma Splices — for the full troubleshooting guide
• 5.4 Faulty Parallelism — for list and pattern problems when combining
• 6.1 Parallelism — for building balanced compound and complex sentences
• 6.4 Sentence Variety — for controlling rhythm and flow across a whole piece

Back to: Pillar 2 — Coordinating and Correlative Conjunctions; Subordinating Conjunctions