-(으)니까: The 'Because' You Use Before a Command

Where -아서 / -어서 reports a cause as plain fact, -(으)니까 hands your listener a reason. It is addressed to someone. That is the whole difference, and everything below falls out of it.

It is the only option before a command

위험하니까 조심하세요.       ✅  It's dangerous, so be careful.
위험해서 조심하세요.         ❌  ungrammatical

Commands, requests and suggestions are all aimed at a listener, so they need the connector that points at one.

• 피곤하니까 일찍 자세요 — You look tired, so go to bed early. (command)
• 시간 없으니까 택시 탈까요? — We’re out of time, shall we take a taxi? (suggestion)
• 바쁘니까 나중에 얘기해요 — I’m busy, let’s talk later. (request)

Check the second half. If it ends in -세요, -ㄹ까요, -읍시다, -지 마세요 or any other form aimed at the listener, you need -(으)니까. For a soft refusal that trails off without commanding, speakers often set background with -는데요 instead of spelling a full reason.

It takes past tense freely

This is the mirror image of the -아서 rule:

• 어제 바빴으니까 오늘은 쉬세요. — You were busy yesterday, so rest today.
• 밥 먹었으니까 이제 나가자. — We’ve eaten, so let’s head out now.

Both are perfectly natural. The equivalent with -아서 would be ungrammatical.

It can stand alone

When someone asks 왜요?, both connectors can carry a short answer:

A: 왜 안 왔어요? — Why didn’t you come?
B: 바빠서요. — Because I was busy. (natural)
B: 바빴으니까요. — Because I was busy. (also fine — and this one can mark the past)

Adding 요 keeps either polite. The difference is tense: -아서요 cannot take 았/었, so it stays 바빠서요. -(으)니까 takes past freely — 바빴으니까요.

A warning: a bare 니까 answer can sound clipped, even a little defensive, depending on tone. If you are explaining yourself to someone senior, a fuller sentence is safer.

Where it goes wrong

Apologies. 늦으니까 죄송합니다 is the classic learner error. It reads as “since I’m late, I guess I’m sorry” — you sound like you are defending yourself. Apologies and thanks always take -아서 / -어서:

늦어서 죄송합니다. ✅
도와주셔서 감사합니다. ✅

ㄹ-final stems. The ㄹ disappears: 살다 → 사니까, 알다 → 아니까, 멀다 → 머니까. Writing 살으니까 is a very common mistake.

Summary