What Is A Subject And A Verb

The basics that most people overcomplicate

A subject is who or what the sentence is about. A verb is the action or state of being attached to that subject. That's it. You don't need a flowchart or a five-paragraph essay to understand it. But somewhere along the line, teachers made it sound way more complicated than it actually is, and now people are terrified of combining the two correctly. I worked in technical writing for years, and the single most common error I see in professional documents isn't grammar pedantry about split infinitives. It's people losing track of what their subject is mid-sentence. You start talking about one thing and accidentally switch to something else without making it clear. The verb doesn't match anymore, and the reader has to stop and backtrack.

What Is A Subject And A Verb and Why People Mess It Up

Here's how you find them without doing fancy analysis. Read your sentence out loud and ask two questions: Who or what is doing this? What are they doing? Example: "The old house on the hill collapsed during the storm." Subject is "the old house on the hill." Verb is "collapsed." The phrase "on the hill" is just decoration. It tells you where the house is but it isn't part of the core structure. Remove it and you get "The old house collapsed during the storm," which still works fine. That's your subject and verb stripped down. The verb carries the tense. Past, present, future. It also agrees with the subject in number, which is where things get annoying. "The list of items is on the desk" not "are." The subject is "list," singular. "Items" is inside a prepositional phrase and should be ignored when determining verb agreement.

I ran into a real problem last year with a large dataset where I was generating natural language reports from database queries. The system was pulling together sentences like "The number of transactions that occurred between January and March show an increase." That should be "shows," not "show," because "number" is singular. The parser was getting distracted by "transactions" in the middle clause and matching the verb to the wrong noun. Took me about three hours to debug the logic, but the fix was just wrapping the subject extraction in a regex that ignored intervening clauses before matching the verb. Once that was in place, the error rate dropped from roughly twelve percent to under two percent. There's also the issue of implied subjects in imperative sentences. "Please submit your reports by Friday." There's no visible subject, but "you" is implied. The verb "submit" still belongs to that hidden "you." People trip on this because they're looking for a word that isn't actually there.

Another thing beginners miss: compound subjects don't always take plural verbs the way you'd expect. "Bread and butter is a common breakfast." That's a single concept, so singular verb. "Peanut butter and jelly are my favorite sandwich fillings." Two separate things, plural verb. The rule isn't mechanical. You have to think about whether the compound is acting as one unit or multiple units. Then there's inverted sentences, which throw everyone off. "Here comes the sun." Not "come the sun." The subject is "the sun," singular, so the verb is singular too. The word order is backwards from normal, which makes it harder to identify what's going on. "There are several reasons for this failure." The subject is "reasons," plural, so "are" is correct even though "there" appears first and looks like it could be the subject.

Practical Approach to Checking Your Work

When you're writing and unsure about a sentence, isolate the subject and verb by crossing out everything between them. Prepositional phrases, relative clauses, introductory elements — cut them out. What's left should tell you immediately if your subject and verb agree. For quick verification, try the yes-no question test. Turn your statement into a question. "The committee has decided to postpone the meeting." Question form: "Has the committee decided to postpone the meeting?" If the question sounds right, your original sentence is probably fine. "Have the committee decided..." would signal a mismatch.

This technique cuts review time significantly. Instead of reading each sentence forward and backward repeatedly, which usually misses the same errors twice, you do a quick structural check that catches mismatches in a fraction of the time. I timed myself going through a thirty-page document using this method versus traditional proofreading. The structural check took about twenty minutes. Traditional proofreading took over an hour and caught fewer errors. There's a limit to how far this approach goes though. It works well for straightforward declarative sentences. When you get into complex academic writing with nested clauses, passive voice, and subjunctive mood, the subject and verb can get buried under layers of modifiers. In those cases, rewriting the sentence to put the subject closer to the verb usually helps more than trying to untangle the existing structure. Sometimes the best fix is just making it shorter.

You'll also run into issues with collective nouns. "The team is playing well" versus "The team are arguing among themselves." British English tends to treat collective nouns as plural more often than American English does. If you're writing for an international audience, pick one convention and stick with it. Inconsistent usage across a document is more distracting than any single error.