This page in your language

فارسی

العربية

Deutsch

Español

Français

日本語

한국어

Português

中文

हिन्दी

Home
Learn
Korean
Vocabulary
기획서

A2 noun 12 min read

기획서

gihoekseo

Practice it Examples Notes & Tips 기획서 in 30 Seconds

Explanation 기획서 in your Level:

At the A1 level, you just need to know that '기획서' is a word for a 'plan' or 'paper for a project.' You might not use it yourself yet, but you should recognize it as a noun. Think of it as 'Project Paper.' You can use it in very simple sentences like '이것은 기획서입니다' (This is a planning document). At this stage, focus on the fact that it ends in '서,' which often means a document or a piece of paper in Korean. It is a formal word, so you will see it in textbooks or hear it in office-themed cartoons. You don't need to worry about the complex business nuances yet; just remember it as a 'big plan on paper.'

At the A2 level, you should be able to use '기획서' with basic action verbs. You are learning how to describe your daily life or work routine. You can say things like '기획서를 써요' (I write a planning document) or '기획서가 어려워요' (The planning document is difficult). You should also be able to understand that it's different from a simple '계획' (plan). A '기획서' is something you can hold or email. You might encounter this word when talking about school projects or small tasks at work. You should start to recognize it in the context of '제출하다' (to submit) or '읽다' (to read). It is a key word for anyone hoping to use Korean in a professional or academic setting.

At the B1 level, you should understand the structure and purpose of a '기획서.' You can explain what is inside the document using more complex grammar. For example, '기획서를 작성하기 위해 회의를 했어요' (We had a meeting to draft the planning document). You should also be familiar with the different types of planning documents, such as '사업 기획서' (business plan) or '마케팅 기획서' (marketing proposal). At this level, you begin to see the word in news articles or more realistic drama dialogues. You should be able to discuss the status of a document—whether it is being reviewed, revised, or completed—using verbs like '검토하다' or '수정하다.'

At the B2 level, you can use '기획서' in professional discussions and debates. You can critique a document's content, saying things like '이 기획서는 현실성이 떨어집니다' (This planning document lacks feasibility). You understand the nuance between '기획서' and '제안서' and can choose the correct one based on the audience (internal vs. external). You are also comfortable with the formal approval process vocabulary, such as '결재' (approval) and '반려' (rejection). You can write a short '기획서' yourself, using appropriate formal endings like '-습니다' or '-ㄴ/는다.' You understand that a '기획서' is a strategic tool, not just a list of tasks.

At the C1 level, '기획서' is a word you use with high precision. You can discuss the 'strategic alignment' (전략적 정렬) within a planning document or the 'expected ROI' (기대 효과). You are sensitive to the stylistic choices in a '기획서,' such as the use of bullet points, formal vocabulary, and logical flow. You can lead a meeting about a '기획서' and provide detailed feedback to subordinates. You understand the historical and cultural weight of '기획' in the Korean corporate world, where thorough documentation is often prioritized. You can read complex, multi-page government planning documents and summarize their core arguments perfectly.

At the C2 level, you have a near-native grasp of '기획서.' You can analyze the rhetorical strategies used in high-level corporate proposals. You might even write academic papers or professional articles about the 'art of the 기획서' in Korean business culture. You understand the subtle social dynamics involved when a '기획서' is submitted—how it reflects the hierarchy and the interpersonal relationships within a team. You can use the word in metaphors or high-level professional jargon without any hesitation. To you, a '기획서' isn't just a document; it's a comprehensive representation of a professional's vision and strategic thinking capability.

Practice it Examples Notes & Tips

기획서 in 30 Seconds

A formal written document used to propose and outline a project's strategy, goals, and execution steps in Korean professional and academic settings.
Commonly paired with verbs like 'draft' (작성하다), 'submit' (제출하다), and 'review' (검토하다) to describe the project lifecycle.
Distinguished from a general 'plan' (계획) by its formal, documented nature and from a 'report' (보고서) by its future-oriented focus.
A central element of Korean office culture, often requiring hierarchical approval (결재) and serving as a measure of professional competence.

The Korean word 기획서 (gi-hwek-seo) is a fundamental term in the Korean professional and academic landscape. It translates most accurately to a 'planning document,' 'proposal,' or 'project plan.' While a simple 'plan' might be called '계획' (gye-hwek), the addition of '서' (seo), meaning document or book, elevates it to a formal, written piece of work. This word is the lifeblood of Korean office culture, often depicted in 'K-Office' dramas where characters spend late nights perfecting their slides to get approval from their superiors. It represents the transition from a mere idea to a structured, actionable strategy that details the 'who, what, when, where, why, and how' of a project.

Professional Context: Used when proposing new marketing campaigns, product launches, or event schedules to a manager or a client.

Academic Context: Students use this term when submitting a project proposal for a research paper or a group presentation.

Creative Industry: In media and entertainment, a 기획서 outlines the concept for a new TV show, movie, or game design.

내일까지 신규 프로젝트 기획서를 완성해야 합니다. (I must finish the new project planning document by tomorrow.)

In Korea, the quality of your 기획서 is often seen as a direct reflection of your competence. It isn't just about the information; it is about the logical flow, the visual presentation, and the feasibility of the ideas presented. When you hear this word, think of a multi-page document, likely created in PowerPoint or Hancom Word (the Korean equivalent of MS Word), filled with charts, budget tables, and timelines. It is the bridge between a dream and reality in a corporate setting.

부장님께서 기획서의 내용을 아주 마음에 들어 하셨어요. (The department manager liked the content of the planning document very much.)

Furthermore, the term is highly versatile. You might encounter a '사업 기획서' (business plan), a '광고 기획서' (advertising proposal), or even a '여행 기획서' (travel itinerary/plan) if someone is being particularly formal about their vacation. The nuance is always 'structured preparation in written form.' Unlike a report (보고서), which usually describes what has already happened, a 기획서 is forward-looking, describing what *should* happen and why it is worth investing time or money into.

이 기획서에는 구체적인 예산안이 포함되어야 합니다. (A specific budget plan must be included in this planning document.)

팀원들과 함께 밤을 새워 기획서를 작성했습니다. (I stayed up all night with my team members to write the planning document.)

그의 기획서는 창의적이지만 현실성이 부족하다는 평을 받았습니다. (His planning document was criticized for being creative but lacking feasibility.)

Using 기획서 correctly involves pairing it with the right verbs and particles. Since it is a noun representing a physical or digital object, it often takes the object marker '-를' or '-을'. Common verbs associated with it include '작성하다' (to write/compose), '제출하다' (to submit), '검토하다' (to review), and '수정하다' (to revise). Understanding these pairings allows you to describe the entire lifecycle of a project proposal from conception to final approval.

To Write/Draft: 기획서를 작성하다 (To draft a planning document). This is the most common way to say you are working on the document.

To Submit: 기획서를 제출하다 (To submit a planning document). Used when handing it over to a boss or client.

어제 제출한 기획서 보셨어요? (Did you see the planning document I submitted yesterday?)

When discussing the content of the document, you might use the particle '-의' (possessive) or '-에' (location/inclusion). For example, '기획서의 내용' (the content of the planning document) or '기획서에 적힌 대로' (as written in the planning document). These structures help you refer back to specific details without repeating the entire context. In professional settings, clarity is key, so using these specific grammatical markers ensures everyone knows exactly which document you are discussing.

이번 이벤트 기획서는 누가 담당하나요? (Who is in charge of this event's planning document?)

Another important aspect is the 'result' of the document. Verbs like '통과되다' (to be passed/approved) or '반려되다' (to be rejected/sent back) are frequently used with '기획서'. If your proposal is successful, you say '기획서가 통과되었어요' (The planning document was passed). If it needs more work, you might hear '기획서가 반려되었으니 다시 작성하세요' (The planning document was rejected, so please rewrite it). Mastering these verbs will make you sound much more natural in a Korean work environment.

완벽한 기획서 덕분에 프로젝트가 승인되었습니다. (Thanks to the perfect planning document, the project was approved.)

팀장님께서 기획서 수정을 요청하셨습니다. (The team leader requested revisions to the planning document.)

To Review: 기획서를 검토하다. This suggests a careful, detailed reading to find errors or improvements.

보내주신 기획서를 꼼꼼히 검토해 보겠습니다. (I will carefully review the planning document you sent.)

Lastly, when you are presenting the document, you use '발표하다' (to present). '기획서 발표' (presentation of the planning document) is a high-pressure moment in many Korean companies. You might say, '오늘 오후에 기획서 발표가 있어요' (I have a planning document presentation this afternoon). This context combines the written document with the verbal act of explaining it, showing how '기획서' is central to the entire communication cycle of a project.

이 기획서의 핵심 전략은 무엇인가요? (What is the core strategy of this planning document?)

You will encounter 기획서 in almost any environment where organization and future planning are required. Most commonly, it is heard in office settings, from small startups in Gangnam to massive conglomerates like Samsung or Hyundai. If you work in Korea, you will hear it daily. Managers will ask for it, colleagues will collaborate on it, and clients will demand it. It is the standard term for any formal proposal or project outline.

TV Dramas (K-Dramas): In dramas like 'Misaeng' (Incomplete Life) or 'Start-Up,' characters are constantly shown wrestling with '기획서.' It's a plot device used to show a character's growth or a major conflict at work.

University Life: Professors often require a '팀 프로젝트 기획서' (team project proposal) before students begin their actual work. It teaches students how to structure their thoughts professionally.

드라마에서 주인공이 기획서를 제출하는 장면이 나왔어요. (A scene where the protagonist submits a planning document appeared in the drama.)

Beyond the office and school, you will hear it in news reports about government initiatives. The government releases '정책 기획서' (policy planning documents) to outline new laws or public works. In the tech industry, developers and product managers talk about '서비스 기획서' (service planning documents) to define the features of a new app. Even in the world of YouTubers and influencers, many successful creators use a '영상 기획서' (video planning document) to organize their content before filming.

정부는 새로운 도시 개발 기획서를 발표했습니다. (The government announced a new urban development planning document.)

In recruitment, job seekers often have to submit a '자기 기획서' (self-planning proposal) or a portfolio that includes past '기획서' they have written. This is especially true for roles in marketing, PR, and management. If you are applying for a job in Korea, being able to say you have experience in '기획서 작성' (writing planning documents) is a major plus. It shows that you understand the formal requirements of the Korean workplace.

면접 때 제가 작성한 기획서를 보여드렸습니다. (I showed the planning document I wrote during the interview.)

유튜브 채널 운영을 위해 매주 기획서를 씁니다. (I write a planning document every week to run my YouTube channel.)

Freelance Work: Freelancers use '기획서' to pitch their services to potential clients, outlining the scope of work and the expected results.

클라이언트에게 보낼 기획서를 마무리하고 있어요. (I'm finishing the planning document to send to the client.)

In summary, '기획서' is not just a word; it's a pillar of Korean societal organization. From the highest levels of government to the smallest personal projects, it represents the Korean value of thoroughness and preparation. Whether you are reading a news article, watching a drama, or working in an office, keep an ear out for this word—it always signals that something important is being planned.

이 기획서가 우리 회사의 미래를 바꿀 수도 있습니다. (This planning document could change our company's future.)

For English speakers, the most common mistake is confusing 기획서 with similar-sounding or related words like '계획' (plan), '제안서' (proposal), or '보고서' (report). While they all deal with information and documents, their usage is quite specific in Korean. Using the wrong one can lead to confusion about whether you are talking about an idea, a formal document, an external pitch, or a summary of past events.

Mistake 1: 기획서 vs. 계획: '계획' is a general 'plan' (mental or informal). '기획서' is the formal 'document.' You don't '제출' (submit) a '계획' in a formal meeting; you submit a '기획서.'

Mistake 2: 기획서 vs. 제안서: '제안서' (Proposal) is usually used for external pitches to other companies. '기획서' is more commonly used for internal project planning. While they overlap, '기획서' implies a more detailed execution plan.

❌ 저는 오늘 계획를 작성했어요. (Incorrect for 'I wrote a project plan document.')
✅ 저는 오늘 기획서를 작성했어요. (Correct.)

Another mistake involves the verb choice. Some learners try to use '쓰다' (to write) in all contexts. While '기획서를 쓰다' is grammatically correct and used in casual conversation, '작성하다' (to draft/compose) is much more appropriate in a professional setting. Using '쓰다' in a business meeting might make you sound slightly childish or less professional. It's a small difference that has a big impact on your perceived 'register' or level of politeness.

❌ 이 기획서는 이미 끝난 일이에요. (Incorrect: A planning document is for future work.)
✅ 이 보고서는 이미 끝난 일에 대한 거예요. (Correct: A report is for past work.)

Furthermore, learners often forget the subject-object markers. Because '기획서' is a long word, it's easy to trip over '기획서가' (subject) vs. '기획서를' (object). If the document is doing something (like 'being difficult' or 'being approved'), use '-가'. If you are doing something to the document (like 'writing' or 'reading'), use '-를'. This is a basic rule, but in the stress of a professional conversation, it's a frequent point of error.

❌ 기획서를 아주 좋아요. (Incorrect.)
✅ 기획서가 아주 좋아요. (Correct: The planning document is very good.)

❌ 기획서가 제출했어요. (Incorrect.)
✅ 기획서를 제출했어요. (Correct: I submitted the planning document.)

Mistake 3: Overuse of Konglish: Some learners might try to say '프로젝트 플랜' (Project Plan). While understood, '기획서' is the standard, natural term used by 99% of Koreans in a professional context.

Finally, watch out for the distinction between '기획서' and '품의서' (pum-ui-seo). A '품의서' is a very specific type of internal document used to ask for formal permission or spending. If you are just outlining a project, use '기획서.' If you are asking for money to buy a new laptop, use '품의서.' Mixing these up in a Korean office can lead to administrative headaches!

기획서와 제안서의 차이를 명확히 아는 것이 중요합니다. (It is important to clearly know the difference between a planning document and a proposal.)

To truly master the use of 기획서, you need to understand its neighbors. Korean has several words for documents and plans, and choosing the right one shows your level of fluency. The nuances often depend on whether the document is internal or external, whether it's for a new idea or a report on an old one, and how formal the situation is.

제안서 (Je-an-seo): Translation: Proposal. Usage: Usually external. When Company A wants to work with Company B, they send a '제안서.' It's more of a pitch. '기획서' is the internal blueprint for how to actually do it.

계획서 (Gye-hwek-seo): Translation: Plan/Schedule document. Usage: Focuses more on the timeline and steps. A '기획서' includes the 'why' and the 'strategy,' whereas a '계획서' might just be a list of dates and tasks.

보고서 (Bo-go-seo): Translation: Report. Usage: Backward-looking. You write a '보고서' after a project is finished or to update someone on current status. You write a '기획서' before a project starts.

기획서는 전략을 담고, 계획서는 일정을 담습니다. (A planning document contains strategy, while a plan document contains the schedule.)

In some contexts, you might also hear '초안' (cho-an), which means a 'draft.' You could say '기획서 초안' to mean the first draft of your planning document. This is useful when you want to manage expectations, signaling that the document isn't finished yet. Another related word is '사양서' (sa-yang-seo), which means 'specifications document,' mostly used in engineering and manufacturing to describe technical details.

이것은 최종 기획서가 아니라 단순한 초안입니다. (This is not the final planning document, but just a draft.)

For more casual settings, you might use '아이디어 보드' (idea board) or '메모' (memo), but these lack the professional weight of '기획서.' If you are in a meeting and you want to sound like you have a solid, well-thought-out plan, always use '기획서.' It commands more respect and attention than the other alternatives. Even if your '기획서' is only two pages long, using that specific word frames it as a serious professional contribution.

제안서와 기획서를 모두 준비했습니다. (I have prepared both the proposal and the planning document.)

Summary Table

기획서: Internal, Strategy-focused, Future.
제안서: External, Pitch-focused, Future.
보고서: Internal/External, Result-focused, Past.
계획서: Internal, Timeline-focused, Future.

어떤 문서를 작성해야 할지 모를 때는 기획서라는 용어를 먼저 떠올려 보세요. (When you don't know which document to write, think of the term 'planning document' first.)

How Formal Is It?

Fun Fact

The character 企 (gi) originally depicted a person standing on tiptoe, looking into the distance, which perfectly captures the forward-looking nature of a '기획서.'

Pronunciation Guide

UK /ɡi.ɦwek̚.sʌ/

US /ɡi.hwɛk̚.sɔ/

Stress is relatively even across all three syllables, as is typical in Korean, but the first syllable '기' may feel slightly more prominent.

Rhymes With

비서 (bi-seo - secretary) 독서 (dok-seo - reading) 문서 (mun-seo - document) 이력서 (i-ryeok-seo - resume) 보고서 (bo-go-seo - report) 제안서 (je-an-seo - proposal) 계약서 (gye-yak-seo - contract) 증명서 (jeung-myeong-seo - certificate)

Common Errors

Pronouncing 'hwek' as two syllables 'hwe-keu.' It should be one sharp syllable.
Making the 'g' in 'gi' too aspirated like a 'k.'
Confusing the 'eo' sound with a long 'o' like 'so.'
Failing to pronounce the 'h' in 'hwek' clearly.
Over-emphasizing the 'seo' at the end.

Difficulty Rating

Reading 2/5

The word is easy to read, but documents containing it often use complex Hanja-based business vocabulary.

Writing 3/5

Writing the word is simple, but producing a high-quality '기획서' in Korean is very difficult for learners.

Speaking 2/5

The pronunciation of 'hwek' can be a bit tricky for beginners to say quickly.

Listening 2/5

It is a very distinct word and usually easy to catch in office or school contexts.

What to Learn Next

Prerequisites

계획 (plan) 문서 (document) 쓰다 (to write) 회사 (company) 회의 (meeting)

Learn Next

제안서 (proposal) 보고서 (report) 결재 (approval) 검토 (review) 전략 (strategy)

Advanced

타당성 (feasibility) 기대 효과 (expected effect) 수행 (execution) 반려 (rejection) 품의서 (internal request document)

Grammar to Know

Noun + 을/를 (Object Marker)

기획서를 제출했습니다.

Noun + 에 (Location/Inclusion)

기획서에 예산이 포함되어 있습니다.

Noun + 의 (Possessive)

기획서의 내용이 좋습니다.

Verb stem + 기 위해 (In order to)

기획서를 작성하기 위해 조사했습니다.

Verb stem + ㄴ/은/는 것 같다 (It seems that)

기획서가 잘 된 것 같아요.

Examples by Level

이것은 기획서입니다.

This is a planning document.

이것 (this) + 은 (topic marker) + 기획서 (noun) + 입니다 (is).

기획서가 있어요.

There is a planning document.

기획서 (noun) + 가 (subject marker) + 있어요 (exists/there is).

기획서를 봐요.

I look at the planning document.

기획서 (noun) + 를 (object marker) + 봐요 (look/see).

기획서가 커요.

The planning document is big.

기획서 (noun) + 가 (subject marker) + 커요 (is big).

기획서가 어디에 있어요?

Where is the planning document?

어디 (where) + 에 (location marker) + 있어요 (is/exists)?

선생님 기획서입니다.

It is the teacher's planning document.

선생님 (teacher) + 기획서 (noun) + 입니다 (is).

기획서를 주세요.

Please give me the planning document.

주세요 (please give).

기획서가 좋아요.

The planning document is good.

좋아요 (is good).

오늘 기획서를 써요.

I am writing a planning document today.

오늘 (today) + 기획서 (noun) + 를 (object marker) + 써요 (write).

내일 기획서를 제출해요.

I will submit the planning document tomorrow.

내일 (tomorrow) + 제출해요 (submit).

기획서가 조금 어려워요.

The planning document is a bit difficult.

조금 (a bit) + 어려워요 (is difficult).

누가 기획서를 만들었어요?

Who made the planning document?

누가 (who) + 만들었어요 (made).

기획서를 다 읽었어요.

I finished reading the planning document.

다 (all/completely) + 읽었어요 (read).

새로운 기획서가 필요해요.

We need a new planning document.

새로운 (new) + 필요해요 (is needed).

기획서를 이메일로 보냈어요.

I sent the planning document by email.

이메일 (email) + 로 (by/via) + 보냈어요 (sent).

기획서를 다시 작성하세요.

Please rewrite the planning document.

다시 (again) + 작성하세요 (please write/draft).

기획서의 내용을 확인해 보세요.

Please check the contents of the planning document.

-의 (possessive marker) + 내용 (content) + 확인해 보세요 (please check).

이 기획서는 아주 잘 정리되어 있네요.

This planning document is very well organized.

정리되어 있다 (to be organized).

회의 전에 기획서를 미리 읽어 오세요.

Please read the planning document in advance before the meeting.

회의 (meeting) + 전에 (before) + 미리 (in advance).

기획서에 오타가 몇 개 있어요.

There are a few typos in the planning document.

오타 (typo) + 몇 개 (a few).

기획서를 수정하는 데 시간이 걸려요.

It takes time to revise the planning document.

-는 데 (in doing something) + 시간이 걸리다 (to take time).

마케팅 기획서를 준비하고 있습니다.

I am preparing a marketing planning document.

마케팅 (marketing) + 준비하고 있다 (is preparing).

기획서가 통과되면 바로 시작합시다.

If the planning document passes, let's start immediately.

-면 (if) + 통과되다 (to pass/be approved).

이 기획서는 예산이 너무 많이 들어요.

This planning document costs too much budget.

예산 (budget) + 들다 (to cost).

기획서의 타당성을 검토할 필요가 있습니다.

We need to review the feasibility of the planning document.

타당성 (feasibility/validity) + 검토할 필요가 있다 (need to review).

기획서가 반려된 이유를 설명해 주세요.

Please explain the reason why the planning document was rejected.

반려되다 (to be rejected/returned) + 이유 (reason).

이번 기획서는 창의적인 아이디어가 돋보입니다.

This planning document stands out with creative ideas.

돋보이다 (to stand out).

기획서 초안을 팀장님께 보고했습니다.

I reported the draft of the planning document to the team leader.

초안 (draft) + 보고하다 (to report).

기획서 작성을 위해 시장 조사를 수행했습니다.

I conducted market research to write the planning document.

시장 조사 (market research) + 수행하다 (to conduct).

기획서의 목표가 명확하지 않은 것 같습니다.

It seems the goal of the planning document is not clear.

목표 (goal) + 명확하다 (to be clear).

이 기획서를 바탕으로 프로젝트를 진행하겠습니다.

We will proceed with the project based on this planning document.

-를 바탕으로 (based on).

기획서에 구체적인 실행 방안을 추가하세요.

Please add specific implementation plans to the planning document.

실행 방안 (implementation plan/measure).

기획서의 기대 효과를 수치로 제시해 주십시오.

Please present the expected effects of the planning document in numerical terms.

기대 효과 (expected effect) + 수치 (numerical value).

본 기획서는 중장기적인 관점에서 작성되었습니다.

This planning document was written from a mid-to-long-term perspective.

중장기적 (mid-to-long-term) + 관점 (perspective).

기획서의 논리적 허점을 보완해야 합니다.

We must supplement the logical loopholes in the planning document.

논리적 허점 (logical loophole) + 보완하다 (to supplement).

경쟁사의 기획서와 차별화된 전략이 필요합니다.

A strategy differentiated from the competitor's planning document is needed.

경쟁사 (competitor) + 차별화되다 (to be differentiated).

기획서 승인을 위한 최종 프리젠테이션을 준비하세요.

Prepare the final presentation for the approval of the planning document.

승인 (approval) + 프리젠테이션 (presentation).

기획서에 명시된 예산 범위를 초과해서는 안 됩니다.

The budget range specified in the planning document must not be exceeded.

명시되다 (to be specified) + 초과하다 (to exceed).

이 기획서는 조직의 핵심 가치를 잘 반영하고 있습니다.

This planning document well reflects the core values of the organization.

핵심 가치 (core value) + 반영하다 (to reflect).

기획서의 완성도를 높이기 위해 외부 자문을 받았습니다.

We received external consultation to increase the quality of the planning document.

완성도 (degree of completion/quality) + 자문 (consultation).

기획서의 담론이 거시적인 시장 변화와 맞물려 있습니다.

The discourse of the planning document is intertwined with macro market changes.

담론 (discourse) + 거시적 (macro) + 맞물리다 (to be intertwined).

기획서에 내포된 전략적 함의를 분석할 필요가 있습니다.

It is necessary to analyze the strategic implications inherent in the planning document.

내포되다 (to be inherent/implied) + 함의 (implication).

기획서의 설득력은 데이터의 객관성에 기반합니다.

The persuasiveness of the planning document is based on the objectivity of the data.

설득력 (persuasiveness) + 객관성 (objectivity).

기획서가 지향하는 바는 지속 가능한 성장입니다.

What the planning document aims for is sustainable growth.

지향하다 (to aim for/be oriented toward).

기획서의 구성이 다소 산만하여 가독성이 떨어집니다.

The structure of the planning document is somewhat distracting, so the readability is low.

산만하다 (to be distracting/unfocused) + 가독성 (readability).

이 기획서는 혁신적인 패러다임의 전환을 제안하고 있습니다.

This planning document proposes an innovative paradigm shift.

혁신적 (innovative) + 패러다임의 전환 (paradigm shift).

기획서의 파급 효과를 다각도로 검토해야 합니다.

The ripple effects of the planning document must be reviewed from various angles.

파급 효과 (ripple effect) + 다각도 (various angles).

기획서에 기술된 리스크 관리 방안이 매우 치밀합니다.

The risk management measures described in the planning document are very meticulous.

리스크 관리 (risk management) + 치밀하다 (to be meticulous).

Common Collocations

기획서를 작성하다

기획서를 제출하다

기획서를 검토하다

기획서가 통과되다

기획서가 반려되다

기획서 초안

기획서 발표

기획서 수정

완벽한 기획서

기획서 내용

Common Phrases

기획서 좀 보여주세요

— Please show me the planning document. Used among colleagues.

작성하신 기획서 좀 보여주세요.

기획서 다 썼니?

— Did you finish writing the planning document? (Informal).

민수야, 기획서 다 썼니?

기획서대로 진행합시다

— Let's proceed according to the planning document.

회의 결과, 기획서대로 진행합시다.

기획서가 엉망이에요

— The planning document is a mess. Used in harsh feedback.

이 기획서는 내용이 엉망이에요.

기획서에 다 적혀 있어요

— It's all written in the planning document.

질문하신 내용은 기획서에 다 적혀 있어요.

기획서 보완이 필요합니다

— The planning document needs supplementation/improvement.

데이터가 부족해서 기획서 보완이 필요합니다.

기획서 승인 부탁드립니다

— Please approve the planning document. Formal request to a boss.

검토 후 기획서 승인 부탁드립니다.

기획서 마감일

— The deadline for the planning document.

기획서 마감일이 오늘까지예요.

기획서 샘플

— A sample of a planning document.

참고할 만한 기획서 샘플이 있나요?

기획서 양식

— The format or template of a planning document.

우리 회사의 표준 기획서 양식을 사용하세요.

Often Confused With

기획서 vs 계획서

Focuses on the 'schedule' and 'steps,' whereas 기획서 focuses on the 'strategy' and 'concept.'

기획서 vs 보고서

A report on past actions, while a 기획서 is a proposal for future actions.

기획서 vs 제안서

Often external pitches, whereas 기획서 is typically an internal execution plan.

Idioms & Expressions

"기획서가 발이 달렸다"

— Literally 'the document grew feet.' Used when a plan spreads quickly through the office.

기획서가 발이 달렸는지 벌써 사장님이 아신대요.

Colloquial

"기획서로 승부를 보다"

— To decide the outcome based on the quality of the planning document.

이번 프로젝트는 기획서로 승부를 봐야 합니다.

Professional

"기획서에 영혼을 갈아 넣다"

— To put one's soul into the planning document (work extremely hard on it).

이번 기획서에 영혼을 갈아 넣었어요.

Slang/Common

"종이 기획서"

— A plan that only exists on paper and isn't actually being executed.

이건 그냥 종이 기획서일 뿐이에요.

Critical

"기획서만 번드르르하다"

— The planning document looks fancy but has no substance.

기획서만 번드르르하고 실속이 없네요.

Critical

"기획서를 엎다"

— To completely scrap and restart a planning document.

팀장님이 기획서를 엎으라고 하셨어요.

Professional Slang

"기획서가 산으로 가다"

— The planning document is losing its point or going in the wrong direction.

회의를 할수록 기획서가 산으로 가네요.

Colloquial

"기획서의 정석"

— The 'textbook' or perfect example of a planning document.

그의 문서는 기획서의 정석입니다.

Praising

"기획서 한 장으로"

— Accomplishing something with just a single planning document.

그는 기획서 한 장으로 투자를 받아냈습니다.

Admiring

"기획서에 뼈를 묻다"

— To devote everything to the planning phase (often hyperbole).

기획서에 뼈를 묻을 각오로 작성했습니다.

Humorous/Exaggerated

Easily Confused

기획서 vs 계획

Both mean 'plan.'

계획 is the abstract idea or simple plan; 기획서 is the formal, written document for a project.

오늘 계획이 뭐예요? (What's your plan for today?) vs. 기획서를 제출하세요. (Submit the planning document.)

기획서 vs 기획사

Only one character difference.

기획서 is a document; 기획사 is an agency or company (like SM, JYP).

기획서를 읽어요. vs. 기획사에 들어가요.

기획서 vs 품의서

Both are internal office documents.

기획서 is for project strategy; 품의서 is specifically for requesting formal approval/spending.

기획서로 프로젝트를 제안하고, 품의서로 예산을 신청합니다.

기획서 vs 명세서

Both are formal documents ending in '서'.

명세서 is a detailed statement or invoice (like a bill), not a plan.

기획서를 작성하고, 나중에 카드 명세서를 받았어요.

기획서 vs 설명서

Both are documents ending in '서'.

설명서 is a manual or instructions for how to use something, not a new proposal.

제품 기획서를 쓰고 나서 사용 설명서를 만들었습니다.

Sentence Patterns

N은/는 N입니다

이것은 기획서입니다.

N을/를 V-아요/어요

기획서를 써요.

N을/를 V-기 위해 N

기획서를 쓰기 위해 회의해요.

N에 따르면

기획서에 따르면 내일 시작해요.

N이/가 V-아/어지다

기획서가 수정되었습니다.

V-는 데 시간이 걸리다

기획서를 작성하는 데 시간이 걸려요.

N을/를 바탕으로

기획서를 바탕으로 분석했습니다.

N에 내포된 N

기획서에 내포된 함의가 큽니다.

Word Family

Nouns

기획 (planning)

기획자 (planner)

기획팀 (planning team)

기획사 (agency/planning company)

Verbs

기획하다 (to plan/design)

Adjectives

기획적인 (planned/strategic)

문서 (document)

계획 (plan)

제안 (proposal)

보고 (report)

설계 (design/blueprint)

How to Use It

frequency

Extremely frequent in professional and academic settings in South Korea.

Common Mistakes

Using '계획' when you mean a formal document. → 기획서
계획 is the idea; 기획서 is the paper. Use 기획서 when you are submitting something.
Saying '기획서를 했어요'. → 기획서를 작성했어요 / 썼어요
You don't 'do' a document; you 'write' or 'draft' it.
Confusing '기획서' with '기획사'. → 기획서
기획사 is a company (agency); 기획서 is a document. Don't say you are 'submitting a company.'
Using '기획서' for a report on last month's sales. → 보고서
Sales results are a report (보고서), not a planning document (기획서).
Incorrect object marker: '기획서가 제출했어요'. → 기획서를 제출했어요
The document is the object being submitted, so use '-를'.

Tips

The 'PPT' Culture

In Korea, a good '기획서' is often judged by its visual design. Learning basic PowerPoint skills is as important as the content if you work in a Korean company.

서 (Seo) Ending

Whenever you see a word ending in '서' in an office context, it's likely a document (e.g., 보고서, 제안서, 계약서).

Verb Pairing

Always pair '기획서' with '작성하다' in emails. It makes you sound like a native professional.

Confidence is Key

When presenting your '기획서,' use the '-ㅂ니다' style to sound authoritative and well-prepared.

Drama Watch

Watch office dramas like 'Misaeng.' You will hear '기획서' in almost every episode, helping you understand the stress associated with it.

Logical Flow

A Korean '기획서' must have a clear 'Why' (Background) before the 'What' (Content). Don't skip the background!

Approval Process

Remember that a '기획서' usually needs '결재' (formal electronic or stamp approval) from multiple people in the hierarchy.

Don't confuse with Report

If the project is already done, it's a '보고서.' If it's a new idea, it's a '기획서.' Using the wrong one shows a lack of professional awareness.

Hanja Root

Remembering that '서' means 'book/document' will help you learn dozens of other Korean words.

Sharing is Caring

Always send your '기획서' in PDF format unless asked otherwise, to ensure the formatting stays perfect for the recipient.

Memorize It

Mnemonic

Think of 'GI' as 'General Idea,' 'HWEK' as 'Wreck' (because you'll wreck your brain writing it), and 'SEO' as 'Series of Output.' A GI-HWEK-SEO is a General Idea you Wrecked your brain for to produce a Series of Output.

Visual Association

Imagine a professional Korean office worker with a 'G' shaped key (GI) opening a 'H' shaped box (HWEK) that contains a 'S' haped scroll (SEO).

Word Web

Project Business Strategy Document Proposal Office Approval Draft

Challenge

Try to describe a plan for your next weekend trip using the word '기획서' to a friend. For example: '이번 주말 여행 기획서를 보여줄게!'

Word Origin

Composed of Hanja (Sino-Korean characters): 企 (기 - gi), 劃 (획 - hwek), and 書 (서 - seo).

Original meaning: 企 means 'to plan' or 'to stand on tiptoe to look forward.' 劃 means 'to draw' or 'to divide.' 書 means 'book' or 'document.'

Sino-Korean (Hanja-based vocabulary).

Cultural Context

Be careful not to dismiss a colleague's 기획서 too harshly; it represents a significant amount of effort and 'face' in the Korean workplace.

In English-speaking offices, 'proposal' or 'project plan' is used, but '기획서' carries a more specific sense of a 'foundational strategy document' in Korea.

The drama 'Misaeng' (Incomplete Life) revolves around interns trying to write the perfect 기획서. The show 'Start-Up' features characters competing with their business 기획서. The variety show 'Infinite Challenge' often had episodes where members had to submit their own 기획서 for new specials.

Practice in Real Life

Real-World Contexts

Office Work

기획서를 작성 중입니다.
기획서 제출 마감일이 언제죠?
기획서가 통과됐어요.
기획서 수정을 부탁해요.

University

팀 프로젝트 기획서예요.
기획서에 이름을 적으세요.
기획서 양식이 있나요?
기획서를 교수님께 드렸어요.

Startup Pitch

투자용 기획서입니다.
기획서의 핵심은 혁신입니다.
기획서를 발표하겠습니다.
기획서에 수익 모델을 넣으세요.

Marketing

광고 기획서를 만들어요.
기획서에 타겟을 명시하세요.
기획서 아이디어가 좋아요.
기획서 예산안을 확인하세요.

K-Drama Viewing

기획서 때문에 혼나고 있어요.
기획서를 밤새워 썼네요.
기획서가 바뀌었어요.
기획서를 뺏겼어요.

Conversation Starters

"이번 프로젝트 기획서는 누가 담당하나요? (Who is in charge of this project's planning document?)"

"제가 작성한 기획서에 대해 피드백을 주실 수 있나요? (Can you give me feedback on the planning document I wrote?)"

"기획서 작성을 위해 어떤 자료가 더 필요할까요? (What more data would be needed to write the planning document?)"

"기획서 승인이 나면 바로 업무를 시작할까요? (Shall we start the work as soon as the planning document is approved?)"

"기획서 양식을 이메일로 보내주실 수 있나요? (Can you send the planning document template by email?)"

Journal Prompts

오늘 내가 한 일 중에서 '기획서'라고 부를 만한 것이 있었나요? (Was there anything I did today that could be called a 'planning document'?)

만약 내가 꿈꾸는 회사를 만든다면, 첫 번째 기획서의 제목은 무엇일까요? (If I were to start my dream company, what would the title of the first planning document be?)

기획서를 작성할 때 가장 어려운 점은 무엇인가요? (What is the most difficult part when writing a planning document?)

한국 드라마에서 본 '기획서'와 관련된 장면을 묘사해 보세요. (Describe a scene related to a 'planning document' that you saw in a Korean drama.)

내 인생의 '행복 기획서'를 쓴다면 어떤 내용을 담고 싶나요? (If you were to write a 'Happiness Planning Document' for your life, what content would you include?)

Frequently Asked Questions

10 questions

Yes, but it sounds very formal or even humorous. Most people would use '여행 계획' or '여행 일정표.' Using '기획서' implies you've made a professional-grade document for the trip.

'기획' (Gi-hwek) is the act of planning or the concept itself (a noun). '기획서' (Gi-hwek-seo) is the physical or digital document that contains that plan. You *do* '기획' and you *write* a '기획서.'

A 'Business Plan' is specifically called '사업 기획서.' '기획서' is a broader term that covers any kind of project proposal, not just business startups.

In casual conversation, '쓰다' is fine. In a professional setting, '작성하다' is much better. For example, '기획서를 작성했습니다' sounds much more professional than '기획서를 썼습니다.'

You can say '기획서 초안' (Gi-hwek-seo cho-an). '초안' means first draft.

Yes, in modern Korean offices, '기획서' almost always refers to a PowerPoint (PPT) or PDF presentation rather than a long text document.

You can add '-들' to make '기획서들,' but usually, the plural is understood from the context or by using numbers like '기획서 두 개' (two planning documents).

It means it was rejected or sent back for revisions. You will need to fix it and submit it again.

Yes, university students often have to submit a '팀 프로젝트 기획서' for their group assignments.

It is made of Hanja: 企 (plan), 劃 (draw/divide), and 書 (document).