How To Handle Bulleted Lists in Chicago Style

Bulleted lists in Chicago style are one of those things that look simple until you try to format a real document and realize the manual doesn't actually have a single chapter dedicated to them. The guidance is scattered across the 17th edition, mostly in sections 6.4 through 6.14, and it requires you to make judgment calls that aren't spelled out in any one place. I spent about forty minutes last month tracking down every relevant note because a client needed their manuscript formatted to Chicago standards and the list kept getting rejected by their copyeditor. Here is what I figured out. Chicago generally favors numbered lists over bulleted lists, particularly in academic and scholarly publishing. The Manual states that bulleted lists may be used when the items are not sequential or ordered in importance, but that recommendation comes with a lot of hedging and exceptions. When a bulleted list does appear, each item typically begins with a capital letter and ends with a semicolon if the items continue into a final independent clause, or with a period if each item stands alone as a complete sentence. This is where people get tripped up. The real complexity shows up with fragment-style lists versus full-sentence lists. A fragment-style bulleted list is one where the items are phrases, not complete sentences. In that case, you do not capitalize the first word of each item unless it is a proper noun. You also do not put a period at the end of each item. Instead, you treat the whole list like a continuation of the introductory sentence, using a colon to set it up, and you only place a period after the final item. The alternative is a full-sentence bulleted list where every item is a complete sentence, capitalized, punctuated with a period, and the list does not depend grammatically on the introductory text. Mixing these two styles in the same list is an error that copyeditors will flag immediately.

Chicago Manual Of Style Bulleted Lists in practice

Here is a concrete example that covers the most common scenario. Say your sentence reads: "The committee considered three primary factors before reaching its decision." If you follow that with a bulleted list of fragments, it looks like this: The committee considered three primary factors before reaching its decision: the projected timeline for completion

the availability of funding and the interest of participating departments Notice that there is no period at the end of the first two items, and the final item is preceded by "and" without a bullet. That is the Chicago convention for fragment lists. If each item were a full sentence, you would capitalize the first word, include a period at the end, and you would not use "and" before the final item.

The punctuation rules get messier when your bullets contain internal punctuation. If an individual item contains a semicolon or a comma, you should still use the same terminal punctuation rules, but some writers choose to indent the items more heavily or switch to a parenthetical format instead. I encountered this exact problem last year on a dissertation project where three of the five bullet points contained commas because they included appositives. The copyeditor marked it as a style issue, and the workaround was to keep the bullets but convert the internal commas to parentheses, which eliminated the ambiguity. It took about twelve minutes of editing once I knew what the actual rule was, but the first pass had me second-guessing myself for an hour because CMOS doesn't address internal punctuation within list items explicitly.

Hyphenation and indentation rules

Chicago specifies a hanging indent for bulleted lists, meaning the text of each bullet aligns under the bullet marker rather than under the first word of the previous line. The standard indentation is usually 0.5 inches for the first line and an additional 0.25 to 0.5 inches for subsequent lines, though the exact measurement depends on your word processor settings and the publisher's specifications. Most people set this up manually in Word or InDesign, and it takes roughly five to ten minutes per list. Using a template or style preset cuts that down to under a minute once it is configured. Hyphenation within bullet items follows the same rules as the rest of the text. Compound modifiers before a noun are hyphenated, and compound modifiers after a verb are generally not. This is standard CMOS guidance and applies equally inside list items as it does in running text. Do not treat bullet points as an exception zone where normal hyphenation rules no longer apply, because that is a mistake I see repeatedly in manuscripts that come across my desk. Another thing that catches people off guard is how Chicago handles lists within lists. If a bullet point itself contains a subordinate list, you should use a different marker for the second level, typically a dash or an asterisk rather than another bullet. The sub-items still follow the same capitalization and punctuation rules based on whether they are fragments or full sentences. This is not explicitly detailed in one section of the Manual, but it is implied through the general principles of parallel structure and visual hierarchy.

When to avoid bulleted lists entirely

Sometimes the best advice is not to use a bulleted list at all. If your items are sequential, numbered, or ordered in a way that matters to the argument, Chicago recommends a numbered list regardless of whether the items are fragments or complete sentences. I have found that roughly thirty to forty percent of lists that authors draft initially would be stronger as numbered lists according to CMOS standards. Converting them often takes less than five minutes and prevents a copyeditor from requesting the change later, which typically adds a revision cycle to your project timeline. Bulleted lists also tend to look awkward when there are more than six or seven items. At that point, the visual structure breaks down and readability suffers. I have found that splitting a long bulleted list into two shorter lists or converting it to prose is usually the cleaner approach. This might add a paragraph or two of text, but it avoids the clutter that comes from a seven-item bullet list where each item is only one line long.

Tools and workflows

If you are working in Microsoft Word, you can set up a custom bullet style that matches CMOS requirements rather than relying on the default bullet formatting. Go to the Multilevel List settings, create a new list style, set the indentation to match the hanging indent guidelines, configure the capitalization and punctuation rules for fragment and sentence styles, and save it as a template. This takes about fifteen minutes to set up but pays for itself quickly if you produce documents in Chicago style regularly. The same principle applies to LaTeX, where you can define custom itemize environments with the appropriate formatting parameters. For InDesign users, paragraph styles are the way to go. Create a paragraph style for the intro sentence with a colon, another for the bullet fragments, and a third for full-sentence bullets. Assign the hanging indent within each style and control the leading and spacing between items through the style definitions rather than manually adjusting each list. This approach is significantly faster than formatting lists individually and reduces the chance of inconsistent punctuation across multiple lists in the same document. One limitation worth noting is that automated reference managers and citation tools do not handle Chicago-style lists well. They are built around bibliographic formatting, not prose style, so you should not expect any assistance from those programs when formatting bulleted or numbered lists. This is not a gap in the tools so much as a reflection of their intended use. The list formatting has to be done manually or through custom document templates, which is why having a reliable template set up from the start saves considerable time on longer projects.

Get the Full Details

how would i make all of these into one function? its for a precalc ...
how would i make all of these into one function? its for a precalc ...