Embedded & Nested Clauses

You're halfway through an email to your manager and the sentence on your screen looks like this:

The report, which I started last week and which I've updated with the figures that Finance sent over yesterday which still need checking, should be ready soon.

You read it back and you can't quite work out what "which" is even referring to any more. The thought of your manager trying to untangle it — probably at 8:52 on a Monday, before her coffee's kicked in — makes you wince a bit.

Here's the thing. That sentence isn't a disaster because you can't write. It's a completely natural side effect of trying to sound precise and professional, and of using embedded and nested clauses without quite noticing what you've stacked on top of what. It happens to everyone. I still catch myself doing it in first drafts, and I've been editing other people's sentences for twenty-two years.

Those clauses — little mini-sentences glued onto your main one — are essential if you want to write beyond "See Jane run." They let you add conditions, explanations, side notes, the caveat that matters. Used well, they make you sound clear and across the detail. Used carelessly, they turn your writing into treacle.

We're going to look at how clauses sit inside other clauses, how to spot the moment you've gone one layer too far, and how to keep your sentences doing the one job that actually matters: carrying meaning cleanly from your head into someone else's, without them having to read it twice.

If you want a reminder of what clauses and basic sentence types are, that groundwork's already laid in the Sentence Types article (2.1) — I'm not going over it again here.

Before you read on, here's where we're heading. By the end you'll be able to: - Recognise embedded and nested clauses in your own everyday writing. - See the "spine" of a sentence even when it's wrapped in three layers of extras. - Control how much you embed, so your reader doesn't have to re-read. - Rewrite an over-long, tangled sentence into something clean. - Use complex sentences with confidence in emails, reports, and applications.

Beginner (Foundation): What Are Embedded and Nested Clauses?

Let's keep the jargon down to what's actually useful.

A clause is a group of words with a verb, usually with a subject attached:

• I left.
• The meeting was cancelled.
• When the call ended, we took a break.

Some clauses stand on their own perfectly well — "I left," "The meeting was cancelled." Others can't; they're left dangling, waiting for the rest of the sentence — "Because it was late...", "Which I haven't finished...". Those needy ones are usually the clauses that get embedded.

Embedded clauses: extra information tucked inside

An embedded clause is a clause that lives inside another clause or phrase. It doesn't sit on its own with a full stop; it's dropped into the middle of something else.

Plain: The client approved the design.

With an embedded clause: The client, who had rejected two earlier versions, approved the design.

"Who had rejected two earlier versions" has its own subject and verb — it's a proper clause — but it's sitting inside the main sentence, adding detail about "the client." A few more, straight from the working week:

• My landlord, who lives upstairs, fixed the boiler.
• The email that you sent yesterday went to my spam folder.
• Our office, which is near the station, is being refurbished.

These are usually relative clauses — the who, which, that, where family. There's a dedicated article on relative clauses elsewhere in this pillar; I'll leave the fine detail to that one and stick to what happens when they start stacking.

Nested clauses: boxes inside boxes

Now imagine those embedded clauses starting to nest — one clause sitting inside another, inside the main clause. Russian dolls, basically.

The colleague who said that she knew the answer stayed quiet in the meeting.

• Main clause: The colleague [...] stayed quiet in the meeting.
• Embedded clause: who said that she knew the answer
• Nested inside that: that she knew the answer

Or:

The dog that chased the cat that stole the chicken barked all night.

• Main: The dog [...] barked all night.
• First embedded clause: that chased the cat...
• Second, nested inside it: that stole the chicken

Two layers, still tracking fine. It's the third and fourth that tend to sneak up on you — especially in the kind of sentence you write fast, under pressure, trying to cover every base at once.

Common Mistake: Treating any long descriptive stretch as "just detail" rather than a clause in its own right. If there's a verb with its own subject in there — wearing no full stop, hiding in the middle of the sentence — it's a clause. Full stop or not.

Quick recap: - A clause includes a verb and usually a subject of its own. - Embedded clauses sit inside another clause or phrase. - Many embedded clauses are relative clauses (who, which, that). - Nested clauses are clauses inside clauses — layers, like boxes. - Complex sentences in work and academic writing rely on exactly this machinery.

Intermediate (Development): Using Embedded Clauses Without Losing Control

At this stage the goal isn't to become a grammar analyst — nobody's paying you for that. It's to read your own sentences back and understand why some feel clean and others feel like they're fraying at the edges before you've reached the full stop.

The three most common hiding places

Inside noun phrases, adding detail about a person, document, or thing: - The applicant who impressed the panel most has been offered the job. - The report, which I drafted last week, needs updating.

Inside what someone thinks, says, knows, or believes — the content of a mental or verbal action: - She said she'd email me the details. - I think that we're missing some data.

In speech and casual writing you'll often drop the that — "I think we're missing some data" — and it's still doing the exact same job.

Inside time, reason, and condition phrases: - We cancelled the event because the venue flooded. - If the client agrees, we'll start next week.

All of these clip onto a main clause — the frame everything else hangs off.

Seeing the sentence spine

Take a realistic email sentence:

The proposal, which incorporates the feedback that you and the rest of the team gave me last week, should be ready to send to the client tomorrow, if Legal approves the wording today.

Heavy — but before you touch a word of it, find the spine:

The proposal [...] should be ready to send to the client tomorrow.

Everything else is embedded around that: the relative clause about the feedback (with a nested that-clause tucked inside it), and the condition about Legal at the end. If you can't spot that spine quickly in your own writing, don't assume your reader will manage it either.

Pro-Tip: When a sentence feels wobbly, mentally cross out every which, that, who, when, because, if clause and see what's left standing. If the leftover skeleton doesn't make sense on its own, or it's suspiciously weak ("It is...", "There are..."), that's exactly why the sentence feels fragile.

How many layers is too many?

There's no strict rule here, but for workplace and academic writing: one embedded clause, fine. Two, usually fine — worth a second glance. Three or more layered into a single sentence, and you're probably making life harder than it needs to be, for you and for whoever's reading it.

Look at this from a project document:

The system, which was installed in 2015 and which relies on software that is no longer supported, will need replacing when the current contract, which expires at the end of this year, comes to an end.

Legal, as sentences go. But it's asking a great deal of the reader. Cleaner:

The system will need replacing when the current contract ends this year. It was installed in 2015 and relies on software that's no longer supported.

Same facts. Considerably less brain strain.

Punctuation as a guide rope

Commas, brackets, and dashes flag where an embedded bit begins and ends:

• Our HR manager, who joined us in 2020, is leaving.
• The meeting — which I'd completely forgotten about — has been moved.

The detailed comma rules live in the punctuation pillar of this library, so I'm not going to drown you in them here. For our purposes: punctuation is the guide rope round the side path off your main sentence, not the fix for a badly built one.

Common Mistake: Reaching for a comma every time "which" or "who" turns up, even when the clause is essential to the meaning. "The colleague who sits next to me..." usually doesn't take commas, because it's telling you which colleague. The full rule lives in the relative clauses article — but it's worth knowing it isn't just decoration.

Quick recap: - Embedded clauses cluster inside noun phrases, after verbs like say/think/know, and after words like when, because, if. - Find the main clause — the sentence spine — before you start editing anything. - One or two layers of embedding are usually fine; three or more gets heavy fast. - Punctuation marks off embedded information; it doesn't rescue a structure that's genuinely tangled.

Advanced (Mastery): Deep Nesting, Style, and Strategic Rewriting

If you write reports, essays, or proposals — anything explaining something with moving parts — nested clauses are already part of your toolkit. This section is about wielding them on purpose, rather than backing into them under deadline pressure.

Recognising deep nesting patterns

Stacked relatives in formal prose:

The policy that the committee, which was set up last year, drafted has been approved.

• Main: The policy [...] has been approved.
• Relative 1 (about the policy): that the committee [...] drafted
• Relative 2, nested (about the committee): which was set up last year

Push it further and you get the kind of sentence nobody thanks you for:

The policy that the committee, which was set up last year by the new director, who wanted to improve transparency, drafted has been approved.

Possible. Painful.

Clauses inside content clauses:

We concluded that the approach that the previous team had recommended was no longer viable.

Here the nesting earns its place — it keeps cause and conclusion tightly welded together, which is exactly what you want in a report.

Readability strategies for complex material

The good news is you don't have to choose between baby sentences and these monsters. You can keep the complexity of the thought while being genuinely kind to the reader.

One main idea per sentence. If a sentence contains more than one real decision, action, or conclusion, it's probably doing too much.

Dense original: After we realised that the figures that Finance had sent over, which were based on projections that are now out of date, were unreliable, we decided that the launch, which has already been delayed twice, should be postponed again.

More digestible: We realised that the figures Finance sent over were unreliable — they were based on projections that are now out of date. As a result, we've decided to postpone the launch again. It's already been delayed twice.

You lose a bit of the tight interconnectedness. You gain a reader who actually finishes the paragraph. In most business writing, that's a trade worth making every time.

Shift information into a phrase instead of a clause. Not every detail needs its own clause.

Instead of: The customer who complained that the product that we'd sent her was faulty has now requested a refund.

Try: The customer who complained about the faulty product we'd sent her has now requested a refund.

Play with sentence rhythm. All short: The system failed. The alarms sounded. Nobody reacted. They thought it was a test. All dense: you can imagine it — four clauses deep, exhausting. Balanced: The system had been working smoothly for three years. When it finally failed and the alarms — tested only last week — sounded, nobody reacted. Most people assumed it was just another test.

That mix of lengths is what you're aiming for. Sentence variety proper is covered in article 6.4; nesting is simply one of the tools you'll use once you get there.

Pro-Tip: Read a paragraph out loud when you're editing. If you find yourself dropping in extra breaths where your commas aren't — that's a clear sign the written structure isn't matching the way the sentence actually wants to be read. Nine times out of ten, over-nesting is the culprit.

When deep nesting is actually the right choice

There are moments a fairly heavy, nested sentence is exactly what you want — drawing a careful distinction, tying evidence tightly to a claim, or signalling how ideas depend on one another. In an academic essay:

The study, which was conducted over a ten-year period and which controlled for variables that previous researchers had ignored, provides evidence that supports the hypothesis that early intervention can significantly reduce relapse rates.

Not light reading. But it's doing legitimate work — showing the strength of the study and how tightly it's tied to the hypothesis. In something closer to legal language:

The agreement, which supersedes any prior arrangements that may have been made between the parties, will remain in force until either party provides written notice that they wish to terminate it.

Here the nest of clauses is the precision. Simplify it and you risk quietly changing what the sentence actually means. The trick, always, is to choose the heavy sentence deliberately — not slide into it out of habit because you were in a hurry.

Common Mistake: Equating "sophisticated writing" with "very long sentences full of which and that." Good writing is whatever lets a busy, distracted reader grasp your meaning on the first pass — sometimes that's one carefully built long sentence, but far more often it's a sequence of clear, moderately complex ones.

Quick recap: - Deep nesting shows up in stacked relatives, content clauses inside content clauses, and mixed adverbial/relative patterns. - Heavy nesting isn't automatically bad — but it does raise the reader's processing load, every time. - Split ideas and convert clauses into phrases to improve most dense sentences without losing information. - Use long, nested sentences deliberately, for precision — not as your default setting. - Reading aloud is the simplest way to catch a structure that's fighting you.

UK / US Note

Embedded and nested clauses work exactly the same way in UK and US English — there's no transatlantic grammar divide hiding here. The examples above use UK spelling throughout, so you'll spot things like behaviour [US: behavior] and organise [US: organize], but the sentence structures and the advice apply on both sides of the Atlantic without adjustment.

Key Takeaways

• Embedded clauses are clauses tucked inside other clauses or phrases to add information.
• Nested clauses are layers of embedding — clauses inside clauses — which can quickly become hard to follow.
• In professional and academic writing, one or two levels of embedding is usually plenty.
• You keep control by identifying the main clause first, then checking it still reads cleanly on its own.
• Long, complex sentences have their place — but clarity and variety matter more than sheer length.

Check Your Understanding

1. What's the main clause here? "The report, which includes data that the marketing team collected last quarter, will be shared with the board next week."
2. How many embedded clauses can you find here, and what kind are they? "We decided that the proposal that the consultant had drafted was too expensive."
3. Rewrite this into two or three clearer sentences without losing the important detail: "The client, who had originally said that they were happy with the timeline that we proposed, has now asked for several changes that will delay the launch."
4. Identify one nested clause — a clause inside another clause: "When we realised that the files that had been stored on the old server were corrupted, we contacted IT support."
5. Write a work-style sentence with one main clause and two embedded clauses, keeping it readable.

Answer Key

1. Main clause: The report [...] will be shared with the board next week. (Embedded: "which includes data that the marketing team collected last quarter.")
2. Two embedded clauses: the content clause that the proposal that the consultant had drafted was too expensive, and nested inside it, the relative clause that the consultant had drafted.
3. Sample answer: "The client has now asked for several changes that will delay the launch. They'd originally said they were happy with the timeline we proposed." Any version keeping both facts clear and separate gets full marks.
4. Main: we contacted IT support. Embedded time clause: When we realised that the files that had been stored on the old server were corrupted. Nested relative clause inside that: that had been stored on the old server.
5. Sample: "The manager, who joined the company last year, has approved the budget that we submitted yesterday." (Main clause: "The manager has approved the budget..."; embedded clauses: "who joined the company last year"; "that we submitted yesterday.")

Internal Links

• 2.1 Sentence Types — for the basics of clauses and sentence structures, assumed knowledge here.
• 2.2 Combining Sentences — for practice joining and splitting sentences.
• 3.0 Clause and Sentence Patterns (Routing) — overview of where this piece sits in the pillar.
• 3.2 Main and Subordinate Clauses
• 3.3 Relative Clauses
• 3.4 Noun Clauses / Content Clauses
• 3.5 Adverbial Clauses
• 6.4 Sentence Variety — for shaping style through structure, once nesting's under control.