Must Should Have To

Choosing between must, should, have to and to in English

People mess this up constantly, even native speakers who teach English for a living. The difference isn't complicated once you stop treating them as interchangeable synonyms and start seeing what each one actually signals. I've been grading essays and doing translations for years. The patterns are predictable.

must should have to — how they actually differ

Must carries internal obligation. The speaker themselves decides something is necessary. It's about your own judgment, not someone else's rule. Should is advice or expectation. It sits somewhere between what's a good idea and what's required. You can violate a should without being wrong, just suboptimal.

Have to is external obligation. Something outside you — a law, a boss, a contract — forces it. You don't get a vote. To is not a modal verb at all. It's the infinitive marker or a preposition. Mixing it into the same category as the other three is a common beginner error that shows up in everything from email subject lines to legal documents.

I ran into a specific problem last year translating a construction contract where the original used "you must to complete" instead of "you must complete." The author was clearly a Spanish speaker conflating the infinitive marker with the modal. I flagged it, corrected it, and moved on. But it got me thinking about how often this exact error repeats itself in professional writing. The fix is simple — drop the "to" after must, should, or have to when they're followed directly by a base verb. "You must finish" not "you must to finish." The same rule applies to should and have to. Here's what most guides don't tell you: have to and must overlap significantly in practice, but they diverge in the past tense. Must has no past form. You say "had to" instead. This creates a gap that trips people up when they try to backshift in reported speech. "She said she must go" becomes technically incorrect in formal writing. The correct version is "She said she had to go." I see this mistake in business correspondence all the time.

Another nuance beginners miss: should can express surprise or criticism, not just advice. "You should think before you speak" isn't a suggestion. It's an accusation wrapped in modal softening. The sentence works because should adds plausible deniability. Remove it and you're just being rude directly. There's also the issue of mustn't versus don't have to. They mean opposite things. Mustn't is prohibition. Don't have to is absence of obligation. "You mustn't smoke here" means smoking is banned. "You don't have to smoke here" means smoking is optional. Confusing these two can get you fired or sued depending on the context.

The biggest limitation of teaching this framework is that it breaks down with certain verbs and contexts. "I must agree" uses must differently than "I must go." In the first case, must expresses strong conviction rather than obligation. In the second, it's closer to necessity. Native speakers handle this intuitively. Learners don't always see the distinction. If you're trying to sound natural in professional English, the practical shortcut is this: use must for your own firm conclusions, should for recommendations where you want to stay diplomatic, and have to when citing external requirements. When you're talking about the past, default to had to rather than searching for a must form that doesn't exist.

For to, keep it separate. It appears after modals only in specific constructions like "have to," "use to," or "be used to." It never follows must or should directly before a verb. That's the simplest rule in the whole system, and also the one most people violate. Learning these distinctions won't take more than a few focused sessions. Reading examples in context helps more than memorizing tables. Find documents in your field and notice which modal each author chose and why. The pattern reveals itself quickly enough.