Case Study 1 — The Patchwrite That Got Caught

A composite, fictional-but-realistic scenario assembled from the kinds of cases writing centers and advisors see constantly. The student and the specifics are invented; the pattern is not.

The situation

Priya Anand is six weeks into her first literature review — the opening chapter of her environmental-engineering thesis on stormwater filtration. She's read forty papers. It's 1:00 a.m., the section on membrane fouling is due to her advisor in the morning, and one source says exactly what she needs. The source is a real, citable review article. She has it open in one window and her draft in the other. She reads the source's sentence, then writes her own — confident she's paraphrasing, because she's changing the words as she goes.

Here is the source, and what Priya wrote.

SOURCE (a real review article; cite as Author et al., year):
"Membrane fouling remains the primary obstacle to the widespread
adoption of membrane filtration in stormwater treatment, as the
accumulation of particulate matter, organic compounds, and biological
growth on the membrane surface progressively reduces permeate flux and
increases the energy required to maintain throughput."

PRIYA'S DRAFT (no citation on this sentence):
"Membrane fouling continues to be the main barrier to the broad
adoption of membrane filtration in stormwater treatment, since the
buildup of particulate matter, organic compounds, and biological growth
on the membrane surface gradually decreases permeate flux and raises the
energy needed to maintain throughput."

She submits it inside a four-page section. Two days later, her advisor returns it with that one sentence highlighted and the source's sentence printed beneath it.

What went wrong

Set the two sentences side by side and the problem is undeniable. The structure is identical — same main clause, same "as/since" subordinate clause, same three-item list (particulate matter, organic compounds, biological growth) in the same order, same two consequences (reduces flux, increases energy) in the same order. The only changes are one-for-one synonym swaps:

This is textbook patchwriting (§11.3). Priya genuinely believed that changing the words made the sentence hers. It didn't — because she borrowed the expression: the sentence's architecture and its distinctive sequencing of ideas. And there was no citation, so even the idea was uncredited. Two failures in one sentence.

The deeper cause is the one the chapter keeps returning to. Priya patchwrote because she was working with the source's words in front of her. Her brain reached for the most available material — the phrasing on the screen — and "paraphrased" by nudging it. Worse, membrane fouling was still a topic she only half-understood; she clung to the source's language precisely because she couldn't yet restate the idea on her own. The patchwriting was a thinking problem wearing the costume of a writing problem.

The fix

Her advisor walked her through the close-the-source method (§11.3), and Priya redid the sentence. First, she made herself actually understand the mechanism: fouling is stuff building up on the membrane, which clogs it, which means you get less clean water out and have to spend more energy pushing water through. Then she closed the source — minimized the window — and wrote the idea from memory, explaining it as if to a labmate. Finally she reopened the source to check her facts and added the citation.

❌ Before (patchwriting, uncited): "Membrane fouling continues to be the main barrier to the broad adoption of membrane filtration in stormwater treatment, since the buildup of particulate matter, organic compounds, and biological growth on the membrane surface gradually decreases permeate flux and raises the energy needed to maintain throughput."

✅ After (honest paraphrase, cited): "The main reason membrane filtration hasn't been widely adopted for stormwater is fouling: as particles, organics, and microbial growth coat the membrane, less water passes through and more energy is needed to keep throughput up (Author et al., 2019)."

Why it works: The idea is preserved and credited, but the architecture is now Priya's. She led with the consequence ("the main reason it hasn't been adopted") instead of the source's "remains the primary obstacle"; she compressed the formal three-item list into a quick "particles, organics, and microbial growth"; she explained the mechanism in plain cause-and-effect ("coat the membrane → less water → more energy"). You could not reconstruct the source's sentence from hers — which is the test of a real paraphrase. And the citation tells the reader exactly where the claim comes from.

Notice what the honest version also accomplished: it's clearer than the source (Chapter 3's lesson, surfacing again). Forcing the idea through her own understanding didn't just protect Priya from plagiarism — it produced better prose, because she finally understood what she was saying.

The takeaways

1. Synonym-swapping is not paraphrase. Changing the words while keeping the structure is patchwriting, and patchwriting is plagiarism — with or without a citation, with or without intent.
2. Close the source. The single change that fixed Priya's problem was writing from her understanding instead of from the source's screen. If she could have written it from memory the first time, she'd never have patchwritten.
3. Patchwriting is a comprehension signal. When you find yourself clinging to a source's wording, that's the source telling you that you don't understand it yet. Reread until you can say it yourself — then say it yourself.
4. The honest version is usually the better version. Priya's cited paraphrase is shorter, plainer, and clearer than the source. Integrity and quality pointed the same direction, as they almost always do.

One sentence to remember: If a reader could rebuild the original's wording from your "paraphrase," you haven't paraphrased — you've patchwritten.