The Three Constraints: Tense, Subject & Mood

Once you know that Korean fuses clause-links into verb endings, the next shock is that you can't swap those endings freely. Two endings might both translate as "because," yet one of them makes your sentence ungrammatical in a context where the other is perfect. That's because every connective ending comes with a hidden contract — a set of rules about what it will and won't allow around it. Getting these wrong is the number-one source of sentences that are grammatically broken rather than merely awkward. There are three clauses in the contract: tense, subject, and mood.

Why "and / but / because" aren't interchangeable

An English speaker naturally treats -아서 and -(으)니까 as two words for "because" and picks whichever comes to mind. Korean speakers don't — they pick the one whose contract fits the sentence. Learn the three constraints and you can predict which ending is legal, instead of guessing.

Constraint 1: Tense — can the ending carry 았/었?

Some connective endings refuse a tense marker on themselves. The big ones are -아/어서, -자마자 ("as soon as"), and -(으)러 ("in order to"): you never attach 았/었 to them. The pastness of the whole sentence is expressed once, on the final verb.

The event is firmly in the past, but 가서 stays tenseless — 만났어요 carries the past for the entire sentence. Saying ×갔어서 (past + 서) is simply wrong; the ending won't take it. Contrast that with endings that freely take tense — -고, -지만, -(으)니까, -기 때문에. On these, a past marker is not only allowed but often necessary:

Here 먹었지만 and 왔으니까 wear their own past tense — and they need it, because the eating and the raining happened before the main clause. So tense is the first thing to check: is this an ending that blocks 았/었 (put the tense on the final verb only) or one that carries it?

Constraint 2: Subject — shared or switchable?

The second clause of the contract governs who does what in the two clauses. Endings fall into two camps.

Same-subject endings demand that both clauses have the same actor. The purpose ending -(으)러, the intention ending -(으)려고, the "busy doing" -느라고, and -아/어서 in its sequential sense ("do X and then Y") all require it — one person does both actions.

You cannot go to the market and have someone else buy the fruit under this 가서 — ×제가 가서 동생이 샀어요 breaks the same-subject rule for sequential -아서. Subject-switching endings, by contrast, happily let the actor change: -고, -지만, -(으)니까, -는데.

A crucial subtlety: causal -아/어서 (as opposed to sequential -아서) does allow different subjects. "It rained, so the roads jammed" has two different subjects and is perfectly fine:

So the same-subject rule for -아서 applies to the sequential "and-then" use, not the causal "because" use — a distinction worth keeping straight. A few endings even prefer different subjects: -길래 typically reports someone/something else's situation as the trigger for your own action.

Constraint 3: Mood — can a command or suggestion follow?

This is the most practically important constraint, and the one that decides a choice Koreans make dozens of times a day. Cause -아/어서 and -기 때문에 cannot be followed by a command or a suggestion. The final clause must be a statement or a question — never an imperative (-(으)세요) or a propositive (-자, -읍시다). So ×배고파서 먹읍시다 ("let's eat because we're hungry") is broken.

-(으)니까, on the other hand, licenses commands and suggestions. This single split is the reason Koreans reach for 니까 the moment they want to give an instruction or make a proposal:

Compare the two "because"s doing opposite jobs. When you're stating an objective reason — especially in a fixed, deferential apology or thanks — -아서 is idiomatic:

But the instant the final clause becomes a directive, -아서 is off the table and -(으)니까 takes over:

If you find yourself wanting to say "…so do X" or "…so let's X," that's your cue: the reason clause must end in -(으)니까, not -아서. The full head-to-head is on -아서 vs -(으)니까.

Reference table

Common Mistakes

1. Putting 았/었 on a tense-blocking ending. -아서 refuses it; the past lives on the final verb.

2. Following cause -아서 with a suggestion. Use -(으)니까 for any following command or proposal.

3. Following -아서 with a command. Same rule — a directive final clause needs -(으)니까.

4. Putting tense on -자마자. Like -아서, it blocks 았/었.

Key Takeaways

• Every connective ending is a contract with three clauses; violating one is ungrammatical, not just unnatural.
• Tense: -아/어서, -자마자, -(으)러 block 았/었 (tense goes on the final verb); -고, -지만, -(으)니까, -기 때문에 carry it.
• Subject: -(으)러, -(으)려고, -느라고, and sequential -아서 demand a shared subject; -고, -지만, -(으)니까, -는데 allow a switch — and causal -아서 allows a switch too.
• Mood: cause -아/어서 and -기 때문에 cannot precede a command or suggestion; -(으)니까 can — the reason Koreans pick 니까 whenever a directive follows.
• Objective apologies/thanks take -아서 (늦어서 죄송합니다); instructions take -(으)니까 (시간 없으니까 서두르자).