A list can look tidy and still feel awkward to read. Its bullets align, its spacing is generous, and every item seems relevant. Yet one item names a task, another gives an instruction, and a third describes a result. Readers must keep adjusting how they interpret the words.
Parallel structure addresses that grammatical mismatch. Instead of making every item identical, it gives related items a consistent shape. The examples below are hypothetical editing exercises, not reports of measured improvements. They show how small changes to verbs, nouns, and introductory wording can make the purpose of a list clearer.
Choose what each item is meant to do
Before changing individual words, finish this sentence: “Each item in this list is a…” Possible answers include action, document, question, benefit, or completed task. That decision gives you a useful starting point for the grammar.
Consider this rough list for someone preparing a project handover:
- Update the project summary.
- A folder containing the final files.
- Checking outstanding questions.
The first item tells someone to act. The second names an object. The third names an activity without directly instructing the reader. If these are all responsibilities, rewrite them as instructions:
- Update the project summary.
- Create a folder containing the final files.
- Check outstanding questions.
This revision also reveals a question that grammar alone cannot answer: should the reader create the folder or locate an existing one? Choose the verb that reflects the actual task. Never introduce a new responsibility merely to make the wording match.
Use nouns for things and verbs for actions
A list of materials does not need to sound like a set of commands. For a hypothetical workshop, an uneven draft might say “Bring a notebook,” “A pen,” and “Your registration confirmation.” The writer has mixed an instruction with two objects.
One solution is to introduce the list with “Bring these items:” and use noun phrases throughout:
- A notebook
- A pen
- Your registration confirmation
Alternatively, a list of preparation tasks could say “Pack a notebook,” “Find a working pen,” and “Download your registration confirmation.” Both versions are grammatically coherent, but they serve slightly different purposes. The first identifies belongings; the second asks the reader to do things.
Purdue OWL’s guide to parallel structure explains that matching patterns can operate at the word, phrase, or clause level. Its list guidance recommends keeping the grammatical forms consistent, rather than mixing different constructions.
Test every item against the introduction
A list introduction is more than a label when its wording begins a sentence that the items complete. Read that opening together with each item, including the last one. The combination should make sense without silently inserting or removing words.
Suppose a draft begins “The editor is responsible for:” and continues with “reviewing headings,” “checking links,” and “the introduction is clear.” The last combination becomes “The editor is responsible for the introduction is clear,” which exposes the problem immediately.
A repaired version would read:
- Reviewing headings
- Checking links
- Ensuring the introduction is clear
There is another valid repair: change the opening to “The editor has these responsibilities:” and write three complete instructions. The best choice depends on the surrounding page. What matters is testing the entire construction, rather than approving each bullet in isolation.
Keep the time frame and viewpoint consistent
Parallel wording can break even when every item begins with a verb. Imagine a weekly update containing “Finished the outline,” “Review the draft,” and “Will send the images.” Those phrases refer to different times and different kinds of information.
If the section reports completed work, the revised list might be:
- Finished the outline.
- Reviewed the draft.
- Sent the images.
Only use that revision if all three tasks really are finished. If the original timing is accurate, separate completed work from upcoming work instead. Editing for rhythm must not turn a plan into an accomplishment.
Viewpoint deserves the same attention. A list beginning “You can save drafts” should not unexpectedly switch to “Administrators approve requests” unless that change of actor matters. When several roles genuinely have different duties, name each role explicitly and give every item a similar role-plus-action structure.
Make questions behave like questions
Review prompts often become uneven during collaborative editing. One contributor writes “Is the opening clear?” Another adds “Check the examples.” A third contributes “The conclusion.” All three may concern the same document, but they ask the reader to respond in different ways.
For a discussion guide, turn them into questions:
- Does the opening explain the topic?
- Do the examples support the advice?
- Does the conclusion identify a next step?
For an editing assignment, commands may work better: “Clarify the opening,” “Check the examples,” and “Add a next step to the conclusion.” Notice that these versions are not interchangeable. The questions invite evaluation; the commands assume work is needed. Preserve that distinction when revising someone else’s draft.
Check meaning as well as grammar
Three noun phrases can be grammatically parallel without belonging together. A hypothetical list labeled “Files to upload” might contain “A profile photo,” “A project summary,” and “Friday afternoon.” The final phrase matches the others loosely in shape, but it names a time, not a file.
Move the deadline into a separate sentence and leave the upload list for files. Google’s technical writing lesson on lists and tables treats logical category, grammar, capitalization, and punctuation as separate checks. That distinction is useful: matching the surface pattern does not guarantee that the items answer the same question.
Likewise, avoid combining a feature with its explanation as though they were equivalent choices. “Shared folders,” “Version history,” and “So colleagues can find older drafts” need a meaning-level edit before they need matching punctuation.
Allow useful differences in length
Parallel structure does not require a fixed word count. “Check the title” and “Check the contact details against the approved directory” can share a grammatical pattern despite their different lengths. Removing the verification detail solely to make the bullets look balanced would weaken the instruction.
Similarly, do not force every item to start with the same verb. “Review the summary,” “Confirm the date,” and “Attach the agenda” are parallel commands. Their different verbs help distinguish the actions. Repetition is useful when it clarifies a relationship, not when it hides the specific work.
If a list feels awkward because the ideas need explanation rather than comparison, reconsider the format. The related guide to choosing bullet points or paragraphs addresses that broader decision. Here, the narrower goal is to make the grammar support the format you have chosen.
Finish with a focused grammar pass
Review the opening words of each item, then read each item with its introduction. Check that actions remain actions, questions remain questions, and time frames reflect reality. Finally, confirm that no wording change has altered ownership, requirements, or meaning.
You do not need elaborate terminology to make this edit. Ask whether every item answers the same kind of question in the same grammatical way. When the answer is yes, the reader can concentrate on the information instead of working out how each new bullet fits.
Photo: Lucas George Wendt / Unsplash. Illustrative stock photograph.