When Clio Draft Conditionals Keep Breaking Your Formatting (2026)

If you use Clio Draft and your conditionals keep mangling the formatting, broken numbered lists, spacing that doubles up or vanishes, numbering that jumps, you are in good company. It is one of the most common frustrations attorneys raise about conditional drafting, and it is frustrating precisely because the logic is right and the document still comes out looking wrong.

This is a practical look at why it happens, what tends to help, and how to tell when the problem is the tool rather than something you did. One note for transparency: we make DocuWright, a document automation tool, so we have a horse in this race. We will keep the advice useful first and save our pitch for the end, where you can take it or leave it.

Why conditionals break formatting

Conditional logic works by turning blocks of text on and off. You mark a section as "include this only if," and the tool drops it in or leaves it out based on the answers. That part usually works fine. The trouble starts where those on-and-off boundaries cut across things that depend on staying continuous.

Three usual suspects:

• Numbered lists. When a conditional block sits inside a numbered list and gets switched off, the numbering on either side can jump, restart, or skip. The list does not know the missing item was optional; it just sees a gap.
• Paragraph spacing. Where an optional section drops out, the space it used to occupy can collapse or double up, so you get two blank lines in one place and none in another.
• Cross-references and continuations. Anything that refers to "the section above" or continues a thought across a conditional boundary can end up pointing at the wrong thing when the boundary moves.

None of this means you set it up wrong. It is the nature of splitting a formatted document with on-off switches, and every conditional system wrestles with it to some degree.

What tends to help

A few habits reduce the damage, in most conditional tools:

• Keep conditional boundaries at whole-paragraph or whole-section level. Switching text on and off in the middle of a sentence or a list item is where the worst breakage lives. Whole clean blocks behave better.
• Be deliberate with numbered lists. If a list has optional items, check whether the tool can keep the numbering continuous across a dropped item, and if it cannot, consider restructuring so the list is not split by a condition in the first place.
• Test the extremes. Build one test client who triggers every optional section, and one who triggers none. Formatting almost always breaks at the extremes, not in the middle, so those two runs catch most of it.
• Mind the seams. Look closely at the spacing right where a section drops out, because that seam is where doubled or missing blank lines hide.
• Keep your styles consistent. Documents that mix manual formatting with proper paragraph styles break in more places, because the tool has more kinds of formatting to reconcile.

When it is the tool, not you

Here is the honest part. You can do all of the above and still hit breakage, because some of it is baked into how a given conditional system handles formatting. Attorneys have described spending real time cleaning up after conditionals, editing the same templates over and over as a small change breaks something three pages down. If you have kept your boundaries clean, tested the extremes, and it still comes out wrong, it is fair to conclude the approach is fighting you, not the other way around.

That does not automatically mean you should switch. If Clio Draft works for the rest of your practice and this is a manageable annoyance, the cost of moving may not be worth it. But if the cleanup is eating hours you do not have, it is worth knowing there is a different way to approach the same problem.

A different approach: work from your own document

This is where DocuWright comes in, and we will be straight about what it does and does not do.

Most conditional tools rebuild your document inside their own editor, which is one reason formatting drifts: the tool is reconstructing the layout, not preserving it. DocuWright takes the other path. It works from your own Word document, marking up the parts that change in place, so your formatting stays your formatting rather than being rebuilt. The aim is to remove one of the main sources of the breakage above, by not reconstructing the document in the first place.

We are not going to claim this makes conditional logic effortless, because conditional logic is fiddly wherever you do it, and honest tradeoffs are the only kind worth trusting. What we can say is that keeping your own document, rather than rebuilding it, takes one whole category of formatting problems off the table. And the rest of how DocuWright works is deliberately narrow: it never writes legal language of its own, it flags anything it is unsure about for your review, and you approve everything before it goes out. Your language, your judgment.

If you want the wider view of the category, our legal document automation guide covers the options, and if you are weighing Clio Draft overall rather than just this one issue, our Clio Draft alternative guide goes through it.

Quick answers

Why do Clio Draft conditionals break my formatting? Conditional logic turns blocks of text on and off, and where those boundaries cross numbered lists, paragraph spacing, or cross-references, the surrounding formatting can jump or collapse. It is common to conditional drafting generally, not a sign you set it up wrong.

How do I stop numbered lists breaking inside conditionals? Keep conditional boundaries around whole list items rather than parts of them, check whether the tool can keep numbering continuous across a dropped item, and where it cannot, restructure so the list is not split by a condition.

Is there a tool that keeps my own formatting? Some tools, DocuWright among them, work from your own Word document and mark it up in place rather than rebuilding it, which removes one common source of formatting drift. It does not make conditional logic effortless, but it takes that particular problem off the table.

The honest answer

Formatting that breaks every time you touch a conditional is one of the most tiring parts of document drafting, and a lot of it comes down to splitting a formatted document with on-off switches. Clean boundaries, tested extremes, and consistent styles will get you a long way in any tool. If the cleanup is still eating your time, the deeper fix is an approach that does not rebuild your document in the first place, which is the path we took with DocuWright. Whether that is worth a switch is your call, and if Clio Draft is serving the rest of your practice well, staying put is a perfectly good answer too.