Run-Ons & Comma Splices

You know that email you fire off at 4:55 on a Friday — the one that starts out perfectly sensible and ends in a bit of a blur?

Thanks for chasing this I'll send the revised draft Monday, the figures still need a check.

It lands fine. Whoever receives it will understand what you mean. But if it were a cover letter, a report going to your director, or an email to a landlord that might get forwarded to a solicitor one day, something about it would feel off. Two complete thoughts are leaning on a join that isn't doing its job — or there's no join there at all. That's a run-on and a comma splice, out in the wild, exactly where they usually live: in writing done fast, under pressure, by someone perfectly capable.

I've spent twenty-two years copy-editing non-fiction and running weekend writing workshops, and here's what I've learned from untangling thousands of sentences like this: nobody's born knowing the names for these faults, and clever people write them constantly when they're tired or rushing. The good news is that they're not mysterious once you see the structure underneath. Two independent clauses, joined either by nothing or by a comma that's too weak for the weight it's carrying. Once you can spot that shape, you've got four reliable ways to rebuild it — every time, in seconds.

This piece sits alongside our earlier work on clauses and sentence-building — if "independent clause" needs a refresher, that's properly covered in [3.1 Independent and Dependent Clauses], and the mechanics of combining sentences live in [2.1 Sentence Types] and [2.2 Combining Sentences]. I won't repeat that ground here. What this article owns is the diagnosis of run-ons and comma splices, and the four structural fixes. The full comma rulebook, and the finer conventions around semicolons, belong to the Punctuation pillar — I'll send you there when we reach the edge of what's covered here.

Before you read on, here's where we're heading. By the end of this article, you'll be able to: - Diagnose a run-on (fused independent clauses) and a comma splice (the same fault, joined by a bare comma). - Apply four structural fixes: split, coordinate, subordinate, or use a semicolon as a structural option. - Choose the restructure that matches meaning and register — a Slack message isn't a client email. - Spot the "however" trap, and know the difference between an accidental splice and a deliberate one.

Beginner (Foundation): Naming the Joint That Failed

An independent clause is a group of words that could stand alone as a complete sentence — subject, verb, finished thought:

• The invoice is ready.
• I'll send it this afternoon.
• The flat needs a repair.

Any one of those is happy sitting on its own with a full stop after it. The trouble starts when you push two of them together without a proper join. There are two ways this goes wrong.

A run-on sentence (also called a fused sentence) fuses two independent clauses with nothing between them — no punctuation, no connecting word:

The invoice is ready I'll send it this afternoon.

Say it aloud and you feel your voice trip somewhere around "ready" — there's a hard boundary there that the sentence gives you no warning about at all.

A comma splice is the same underlying fault, dressed up in a comma that isn't strong enough for the job:

The invoice is ready, I'll send it this afternoon.

It looks tidier, because there's some punctuation sitting in the gap. But a comma alone can't bear the weight of joining two independent clauses. I think of a comma as a paperclip and a full stop as a staple. A paperclip will hold two pages together for a quick glance across a desk; it won't survive being posted.

The test is always the same: can each half stand alone as its own sentence?

• The invoice is ready. — Yes.
• I'll send it this afternoon. — Yes.
• Nothing (or only a comma) joining them?

Two yeses plus a weak or missing join means you've found a run-on or a comma splice.

Common Mistake: Assuming a long sentence is automatically a run-on, and a short one can't possibly be one. "Even though the meeting overran by twenty minutes and the client seemed distracted, we still managed to close on the revised timeline before everyone left the room" is one long, entirely correct sentence, because a subordinate clause is doing its job properly at the front. "The meeting overran we still closed the deal" is a run-on at seven words. The test is structural. It's never about length.

Quick recap: - An independent clause is a complete thought that could stand alone as its own sentence. - A run-on fuses two independent clauses with no punctuation or connector at all. - A comma splice joins two independent clauses with only a comma — too weak to bear that load. - The diagnostic test never changes: can each half stand alone? If yes, and the join is missing or too weak, that's the fault.

Intermediate (Development): Four Structural Restructures

You don't need a flowchart of twenty options — you need four you can trust under deadline pressure. Each does a different job, so it's worth knowing what each one buys you.

We'll use the same broken sentence throughout:

Broken (comma splice): I sent the invoice, I haven't heard back yet.

Fix 1: Split into two sentences

The cleanest, most direct fix. Full stop [US: period] at the crash point, capital letter after it.

I sent the invoice. I haven't heard back yet.

Reach for this when the two ideas deserve equal, separate weight — a status update where you want each fact to land cleanly on its own.

Fix 2: Add a coordinator

A bare comma can't join two independent clauses, but a comma plus a coordinating conjunction (and, but, or, so, yet, for, nor) can:

I sent the invoice, but I haven't heard back yet.

Notice what "but" is doing that the naked comma never could — it tells the reader exactly how the two facts relate. This is the exact mechanism covered fully in [2.2 Combining Sentences]; here, you're using it specifically as a repair.

Fix 3: Subordinate one clause

Demote one of the two independent clauses so it can no longer stand alone — it now depends on the other for its full meaning. Use a word like although, because, since, when, while, even though.

Although I sent the invoice, I haven't heard back yet. or: I haven't heard back yet, even though I sent the invoice on Monday.

This is often your most professional-sounding fix, because it doesn't just connect two facts — it ranks them, signalling which one matters more in the moment. The full landscape of how independent and dependent clauses interact is in [2.1 Sentence Types].

Fix 4: Use a semicolon

There's a fourth structural option available: a semicolon can join two closely related independent clauses directly, without any coordinator at all.

I sent the invoice; I haven't heard back yet.

I'm flagging this purely as a structural choice that exists. The full rules governing exactly when a semicolon is the right punctuation call — and how it behaves next to words like however — belong to the Punctuation pillar, where they get proper treatment. Here, just bank that it's on your list.

Here's all four side by side, applied to a fresh example:

Same facts every time. Different emphasis, different implied relationship. That's the skill worth building at this level — not "which one removes the error" but "which one says what actually happened."

The disguised comma splice

This is the version that trips up even confident writers in professional emails — joining two independent clauses with a comma before however, therefore, moreover, or similar:

❌ The report is finished, however I still need sign-off from Legal.

This looks joined properly — there's a connecting word sitting right there. But however is a conjunctive adverb, not a coordinator, and a comma in front of it isn't strong enough to bridge two independent clauses. You need a full stop or a semicolon:

✅ The report is finished. However, I still need sign-off from Legal. ✅ The report is finished; however, I still need sign-off from Legal.

This exact pattern shows up constantly in work emails, precisely because it looks so tidy on the page.

Pro-Tip: Run the "stop and point" test on anything you're unsure about. Put your cursor at the joining word or mark and ask: does everything to the left read as a complete sentence alone? Does everything to the right? Two yeses means a bare comma isn't going to hold them together — you need something stronger.

Quick recap: - Fix 1 — Split: two sentences, always safe, gives each fact equal weight. - Fix 2 — Coordinate: and/but/so/or shows how equal ideas relate. - Fix 3 — Subordinate: although/because/when ranks one idea against the other. - Fix 4 — Semicolon: a structural option for tightly related, equal clauses (full rules in the Punctuation pillar). - However, therefore, and similar words need a full stop or semicolon before them — never just a comma.

Advanced (Mastery): Meaning, Register, and the Near-Misses

Diagnosis is binary — either the join is doing its job or it isn't. Craft is not binary. Advanced control is about choosing structure on purpose, and recognising the lookalikes that bully people into "fixing" sentences that were never broken.

Structure as a meaning choice

Take this comma splice from a performance-review draft:

Results improved in Q3, the team finally stabilised.

All four fixes are grammatically fine. They make different claims.

• Results improved in Q3. The team finally stabilised. — two facts, sitting side by side; cool, managerial distance.
• Results improved in Q3, and the team finally stabilised. — parallel achievements, equal footing.
• Results improved in Q3 after the team finally stabilised. / …because… — a causal claim. Don't reach for this unless you actually mean it — a careless because can quietly rewrite what happened.
• Results improved in Q3; the team finally stabilised. — an implicit pairing, confident, slightly more polished than a plain split.

In workplace writing, this is the real danger of over-fixing on autopilot: accidental causality. A hasty because asserts a link you never intended. A clean split refuses to invent one.

What is not a comma splice

Some sentences look broken but aren't, and over-correcting them is its own error.

Compound predicate (one subject, two verbs):

She reviewed the contract and signed it.

One subject, two verbs sharing it. No second independent clause — nothing to splice.

A dependent opener plus main clause:

If the payment clears, we'll dispatch tomorrow.

If the payment clears can't stand alone. It's not independent, so there's nothing to fix.

A relative clause:

The report that I submitted was rejected.

That I submitted modifies "report" — dependent, not a second sentence.

The test never changes: are both halves genuinely independent? If one can't stand alone, you're not looking at a fault.

Register: Slack versus the permanent record

Let's be honest — nobody is policing comma splices in a three-line Slack message to a colleague. "Sent the invoice, haven't heard back yet" is completely natural there, and flagging it would be a bit much. Occupational writing is really graded by risk. Internal chat can breathe. Client-facing copy, cover letters, CVs [US: resumes], complaint emails, formal reports — anything that might be re-read later, quoted, or forwarded — should show clean clause joints. An unintended splice in one of those contexts doesn't read as casual; it reads as careless, and that can genuinely cost you credibility.

Published writers bend this rule constantly, and it's worth understanding why, because it clarifies what the rule is actually for. Julius Caesar's "I came, I saw, I conquered" is, structurally, three spliced independent clauses — and it works precisely because the brevity and repetition are doing the connecting work a conjunction would normally do. You'll see the same trick in marketing copy and punchy opening lines. The blanket "never splice" rule most of us were taught at school is training wheels for a more nuanced truth: a splice becomes a legitimate stylistic choice once you're clearly choosing it, rather than stumbling into it by not noticing the crash.

Common Mistake: Reaching for "and" every time, because it's the fastest patch available. "I sent the invoice and I haven't heard back and now I need to follow up again" is grammatically sound and reads flat — exactly the tone you don't want in a client email. Vary your fixes. It's the difference between writing that's merely correct and writing that sounds considered.

Pro-Tip: Before you send anything with real stakes — a client email, a cover letter, a report going to your boss — read it aloud once, slowly. Wherever your voice wants to pause and the punctuation doesn't back it up, that's almost always where a splice or run-on is hiding. Worth catching before you hit send.

Quick recap: - Choose your fix for meaning and implied relationship, not just to clear the error. - Compound predicates, dependent openers, and relative clauses aren't splices — always check both halves are genuinely independent. - Register matters: casual chat is forgiving; client-facing and formal writing is not. - "And" is the fastest fix but often the flattest — don't default to it out of habit.

UK vs US Note

There's no structural difference between UK and US practice here — a run-on is a run-on in Chicago just as much as in Bristol, and all four fixes work identically on both sides of the Atlantic. The only shift you'll ever see is spelling inside the example sentences themselves: a UK writer might say "I finished organising the report, so I can send it over now," while a US reader would see organizing rather than organising, and full stop [US: period]. The underlying comma splice, and the fix applied to it, is exactly the same structure either way. This is one corner of grammar you genuinely don't need to second-guess by audience.

Key Takeaways

• An independent clause is a complete thought that could stand alone as its own sentence.
• A run-on fuses two independent clauses with no punctuation or connector at all.
• A comma splice joins two independent clauses with only a comma — too weak to bear that load.
• Four fixes: split into two sentences, coordinate with and/but/so/or, subordinate with although/because/when, or use a semicolon as a structural option.
• However, therefore, and similar words need a full stop or semicolon before them, never a comma alone.
• Sentence length is never the diagnostic test — short sentences can run on; long ones can be flawless.
• Comma splices can be a deliberate professional style choice once mastered, but they're a genuine risk in formal or client-facing writing.

Check Your Understanding

1. Identify the problem: "The client called I missed the meeting."
2. Identify the problem: "I updated the spreadsheet, I sent it to the team."
3. Rewrite the sentence in Question 2 using subordination.
4. Explain in one sentence why this is wrong, and fix it: "The budget was approved, however we still need the director's sign-off."
5. Is this a run-on, a comma splice, or correct? "Although the client called during the meeting, we managed to finish the presentation on schedule."

Answer Key

1. Run-on — two independent clauses fused with no punctuation or connector.
2. Comma splice — two independent clauses joined by a comma alone.
3. "After I updated the spreadsheet, I sent it to the team." (any correct subordination is acceptable)
4. It's wrong because however needs a full stop or semicolon before it, not a comma — a comma can't join two independent clauses on its own. Fix: "The budget was approved. However, we still need the director's sign-off."
5. Correct — the opening is a subordinate clause, not a second independent clause, so there's no splice or run-on here.

Internal Links

• [5.0 Sentence Structure Diagnosis: How to Tell If a Sentence Is Actually Working]
• [5.1 Sentence Fragments: Structural Diagnosis and How to Fix Them]
• [3.1 Independent and Dependent Clauses: How to Tell Them Apart]
• [2.1 Sentence Types]
• [2.2 Combining Sentences]
• Forward to: Punctuation pillar — full comma-rule system and semicolon conventions