This page in your language

فارسی

العربية

Deutsch

Español

Français

日本語

한국어

Português

中文

हिन्दी

Home
Learn
Korean
Vocabulary
품의서

A2 noun 11 min read

품의서

pumuiseo

Practice it Examples Notes & Tips 품의서 in 30 Seconds

Explanation 품의서 in your Level:

At the A1 level, you don't need to know how to write a '품의서' (Pum-ui-seo), but it's helpful to recognize it as a 'Work Paper.' Think of it as a special note you give to your teacher or boss to ask for something. In Korea, you cannot just do things at work; you have to write it down first. For example, if you want a new pen, you write a '품의서.' It is a very formal word. You might see it in a picture of an office or hear it in a simple story about a person working in a big building. Just remember: 품의서 = Office Request Paper.

At the A2 level, you should understand that '품의서' is a formal noun used in business. It refers to a 'Proposal for Approval.' In Korean culture, hierarchy is important. You cannot spend company money or start a new project without asking your boss. The '품의서' is the document you use to ask. You will often see it with verbs like '작성하다' (to write) or '내다' (to submit). For example: '품의서를 내세요' (Submit the proposal). It's a key word for understanding 'Office Korean.' If you watch K-dramas, you will hear characters talking about this document when they are stressed at work.

At the B1 level, you should be able to use '품의서' in sentences describing office routines. You need to know that it's different from a '보고서' (report). A '품의서' asks for permission *before* you do something. You should also learn the verb '상신하다' (to submit to a superior), which is the professional way to say you are sending a '품의서' up the chain of command. For example, '부장님께 품의서를 상신했습니다' (I submitted the proposal to the department manager). You might have to explain why a '품의서' was rejected (반려되다) or accepted (승인되다) using simple reasons like budget or timing.

At the B2 level, you should understand the administrative and legal implications of a '품의서.' It is a document that creates a paper trail for accountability. You should be able to discuss the components of a '품의서,' such as the '개요' (overview), '필요성' (necessity), and '기대 효과' (expected effects). You should also be comfortable using the word in complex sentences involving conditional clauses, like '품의서가 승인되지 않으면 프로젝트를 진행할 수 없습니다' (If the proposal is not approved, we cannot proceed with the project). You should also know related terms like '전자 결재' (electronic approval).

At the C1 level, you should have a nuanced understanding of '품의서' within corporate governance. You can discuss the '품의 제도' (approval system) and its pros and cons, such as how it ensures careful decision-making but can also slow down business processes. You should be able to draft a formal '품의서' using appropriate 'Munjang-che' (written style) and professional vocabulary. You should also understand how '품의서' relates to auditing (감사) and financial transparency. At this level, you can distinguish between '품의서' and '기안서' or '지출결의서' in a professional consulting or management context.

At the C2 level, you have mastered the use of '품의서' in all its complexities. You can analyze historical and cultural reasons why the '품의' system is so deeply rooted in East Asian corporate structures. You can participate in high-level debates about reforming administrative systems to move away from traditional '품의서' toward more agile decision-making models. You understand the subtle linguistic differences in how '품의서' are drafted across different industries (e.g., public sector vs. private tech) and can use the word in academic or legal discourse regarding organizational behavior and administrative law.

Practice it Examples Notes & Tips

품의서 in 30 Seconds

A formal document used in Korean offices to seek official approval from superiors for actions or spending.
Essential for the 'Gyeol-jae' (approval) process in hierarchical organizations.
Usually includes the purpose, plan, budget, and expected results of a proposal.
Different from a report (보고서) because it focuses on future permission rather than past results.

The Korean word 품의서 (Pum-ui-seo) is a cornerstone of Korean corporate culture, representing a formal document used to seek approval or authorization for a specific course of action, purchase, or project. In the hierarchical structure of traditional and even many modern Korean companies, decisions are rarely made in isolation. Instead, they follow a rigorous process known as 'Gyeol-jae' (결재), where a subordinate proposes an idea and it moves up the chain of command for signatures. The pum-ui-seo is the physical or electronic manifestation of this request. It is more than just a 'proposal'; it is a commitment to a specific plan that requires the backing of superiors to proceed. Understanding this word is essential for anyone looking to work in a Korean office environment or understand the dynamics of Korean business dramas (K-dramas like 'Misaeng' or 'Search: WWW').

Etymological Breakdown: The word is composed of three Hanja characters: 품 (Pum) meaning 'to ask' or 'to inform a superior', 의 (Ui) meaning 'deliberation' or 'opinion', and 서 (Seo) meaning 'document' or 'book'. Together, it literally translates to a 'document for asking for deliberation.'
Contextual Usage: You will encounter this word primarily in administrative, financial, and management contexts. If an employee needs to buy new office chairs, they write a pum-ui-seo. If a marketing team wants to launch a new social media campaign, they draft a pum-ui-seo. It serves as an internal record that justifies the expenditure of company resources.

신규 프로젝트를 시작하기 위해 품의서를 작성하고 있습니다. (I am writing a proposal for approval to start a new project.)

In a broader sense, the pum-ui-seo acts as a safety net for employees. Once the document is signed off by a manager (부장님) or director (이사님), the responsibility for the action is shared with the organization. It is a formal way of saying, 'I have thought this through, here are the costs and benefits, do you agree?' In modern tech companies (startups), the term might be replaced by 'Proposal' or 'Draft' (기안), but the underlying principle of seeking documented consensus remains a vital part of the work culture. The document usually includes the purpose, the current situation, the proposed plan, expected effects, and a detailed budget breakdown.

비품 구매 품의서가 아직 결재되지 않았습니다. (The approval request for purchasing office supplies has not been signed yet.)

Cultural Nuance: The 'Red Stamp': Historically, the 품의서 would travel physically from desk to desk, collecting red ink stamps (Dojang). While most companies now use electronic systems (E-approval), the term 'Gyeol-jae' and the structure of the 'Pum-ui-seo' remain unchanged.

Furthermore, the pum-ui-seo is a tool for accountability. If an audit occurs, these documents are the first things checked to ensure that company funds were spent according to protocol. For a learner, mastering this word signifies an transition from basic conversational Korean to professional, 'Business Korean.' It implies an understanding of how power and communication flow within a Korean organization. You don't just 'ask' for something; you 'pum-ui' it.

이번 행사의 예산 사용을 위해 품의서를 상신했습니다. (I have submitted the approval request for the budget usage of this event.)

Using 품의서 correctly involves pairing it with specific business verbs that describe the lifecycle of a document. In a Korean office, you don't just 'give' a document to your boss; you 'up-send' or 'submit' it. The most common verb is 상신하다 (sang-sin-ha-da), which specifically means to submit a proposal to a superior for approval. Another common verb is 결재를 받다 (gyeol-jae-reul bat-da), meaning to receive final approval. When you are in the process of creating the document, you use 작성하다 (jak-seong-ha-da). If the document is rejected, the verb is 반려되다 (ban-ryeo-doe-da).

Common Verb Pairings: 1. 품의서를 작성하다 (To write a proposal)
2. 품의서를 상신하다 (To submit a proposal for approval)
3. 품의서를 반려하다 (To reject/return a proposal)
4. 품의서를 승인하다 (To approve a proposal)

부장님, 지난번에 말씀드린 품의서 결재 부탁드립니다. (Manager, please approve the proposal I mentioned last time.)

The sentence structure for using 품의서 often reflects the polite and formal nature of the office. You will frequently see it used with the honorific suffix -시- or formal endings like -습니다. Because a pum-ui-seo is a formal request, the language surrounding it should be precise. For example, instead of saying 'I want to buy this,' you would say 'I am submitting a pum-ui-seo for the purchase of equipment.' This shifts the focus from personal desire to organizational necessity.

예산 부족으로 인해 품의서가 반려되었습니다. (The proposal was rejected due to a lack of budget.)

In a sentence, 품의서 can act as the subject or the object. When it's the object (ending in -를/-을), it's something you are acting upon (writing, submitting). When it's the subject (ending in -가/-이), it's usually the thing being approved or rejected. Advanced learners should also be aware of the term 전자품의 (e-approval), which is often used interchangeably with the physical document in modern digital workflows.

Sentence Patterns: [Target/Purpose] + 에 대한 + 품의서 + [Verb]
Example: 광고비 지출에 대한 품의서를 올렸습니다. (I uploaded/submitted a proposal for the advertising expenditure.)

팀장님께서 품의서 내용을 수정하라고 하셨습니다. (The team leader told me to revise the contents of the proposal.)

Finally, it is important to distinguish between a pum-ui-seo and a bogoseo (보고서 - report). A report informs about something that has happened or the current state, while a pum-ui-seo asks for permission for something to happen in the future. In a professional setting, mixing these up can lead to confusion. If you are asking for money or permission, always use 품의서.

워크숍 비용 처리를 위해 품의서를 작성해 주세요. (Please write a proposal for processing the workshop expenses.)

You will hear 품의서 most frequently in a professional office setting. It is the 'daily bread' of administrative work. If you are an intern or a junior employee in Korea, one of your first tasks will likely be learning how to fill out the company's pum-ui-seo template. You'll hear it in the morning meetings, in the hallways when colleagues discuss their pending approvals, and in emails from the accounting department asking for missing documentation. It is a word that carries the weight of bureaucratic procedure.

Workplace Scenarios: In the accounting office: '이 품의서는 증빙 서류가 부족합니다.' (This proposal is missing supporting documents.)
During a project launch: '품의서 승인 나면 바로 발주 넣으세요.' (As soon as the proposal is approved, place the order.)

어제 올린 품의서가 아직 대기 중이네요. (The proposal I submitted yesterday is still pending.)

Beyond the physical office, 품의서 is a staple of 'Office Dramas.' In shows like 'Misaeng' (Incomplete Life), the tension often revolves around whether a pum-ui-seo for a risky business deal will be signed by the executive board. It represents the struggle between innovative ideas and rigid corporate structure. Hearing this word in a drama usually signals a moment of conflict or a hurdle that the protagonist must overcome using their persuasive writing and strategic thinking skills.

You might also hear it in government contexts. Public officials spend a significant portion of their time drafting pum-ui-seo to justify the use of taxpayer money. In these cases, the standards for the document are even higher, requiring precise legal and regulatory citations. If you are reading news articles about government spending or corporate scandals, the word 품의서 often appears when discussing how funds were authorized or if they were diverted through falsified documents.

정부 지원금을 받으려면 상세한 품의서가 필요합니다. (A detailed proposal is needed to receive government subsidies.)

Social Media and Blogs: On platforms like LinkedIn (or its Korean equivalents like Wanted/Remember), experts often share tips on 'How to write a 품의서 that gets approved on the first try.' This shows that the word is deeply embedded in the professional self-improvement culture of Korea.

Lastly, in educational settings, students studying business administration or public policy will learn about the pum-ui-seo as part of organizational behavior and administrative law. It is treated as a fundamental unit of organizational communication. When you hear this word, think of 'official permission' and 'accountability.'

비즈니스 한국어 수업에서 품의서 작성법을 배웠어요. (I learned how to write a proposal in my Business Korean class.)

One of the most common mistakes learners make is confusing 품의서 (Pum-ui-seo) with 보고서 (Bo-go-seo). While both are office documents, their purposes are polar opposites. A 보고서 is a 'Report'—it tells your boss what you *did* or what the current status *is*. A 품의서 is a 'Request for Approval'—it asks your boss what you *can do* in the future. If you submit a report when you should have submitted a proposal, you might end up spending money without authorization, which is a major faux pas in Korean business.

Pum-ui-seo vs. Bo-go-seo: 품의서: Future-oriented. Purpose is to get permission and budget. (e.g., 'Can I buy this computer?')
보고서: Past/Present-oriented. Purpose is to inform. (e.g., 'I bought the computer and here is the receipt.')

'보고서'를 올리는 것과 품의서를 올리는 것은 목적이 다릅니다. (Submitting a report and submitting a proposal for approval have different purposes.)

Another error is using the wrong verb with 품의서. Learners often use generic verbs like '주다' (to give) or '보내다' (to send). In a formal Korean office, these sound too casual and somewhat disrespectful. You should use 상신하다 (to submit to a superior) or 제출하다 (to submit). Using the correct verb demonstrates your cultural competence and respect for the workplace hierarchy.

There is also confusion between 품의서 and 기안서 (Gi-an-seo). While they are very similar and often used interchangeably, a 기안서 is a more general term for any draft or proposal, whereas a 품의서 specifically emphasizes the act of 'asking for permission' from a superior. In some companies, 기안서 is used for internal departmental matters, while 품의서 is used for matters involving external spending or cross-departmental impact.

품의서 대신 단순한 이메일로 허락을 받으려고 하면 안 됩니다. (You shouldn't try to get permission via a simple email instead of a formal proposal.)

Formatting Mistakes: A common professional mistake is failing to include the 'Expected Effect' (기대 효과). Superiors in Korea want to know *why* they should approve the request. If the pum-ui-seo only lists costs without benefits, it is likely to be rejected.

Lastly, pay attention to the particles. Beginners often forget that 품의서 is a noun and requires the object marker -를 when you are writing or submitting it. Also, when referring to the *content* of the proposal, use 품의서 내용, not just '품의서' alone. For example, 'The content of the proposal is good' should be '품의서 내용이 좋습니다.'

품의서를 '결재' 받는 것이지 '결제' 하는 것이 아닙니다. (You receive 'gyeol-jae' (approval) for a proposal, not 'gyeol-je' (payment/settlement). These two words sound identical but have different Hanja and meanings.)

In the ecosystem of Korean business vocabulary, several words orbit around the concept of a 품의서. Understanding the nuances between them will make your Korean sound much more professional and precise. The most frequent 'cousin' of 품의서 is 기안서 (Gi-an-seo). While 품의서 is specifically for requesting permission, 기안서 is a broader term for 'drafting' a plan. Often, a pum-ui-seo is a type of 기안서.

Comparison: 품의서 vs. 기안서: 품의서 (Pum-ui-seo): Focuses on 'Permission.' Usually involves spending money or changing a policy. It's 'asking up.'
기안서 (Gi-an-seo): Focuses on 'Planning.' It's the initial draft of an idea that will eventually become an action. It's more about the 'what' and 'how.'

회사의 규정에 따라 품의서와 기안서를 구분해서 사용해야 합니다. (According to company regulations, you must distinguish between a proposal for approval and a planning draft.)

Another important alternative is 제안서 (Je-an-seo). A 제안서 is a 'Proposal' in a more creative or external sense. If you are trying to win a contract from another company, you send them a 제안서. If you have a brand-new idea for a product that doesn't exist yet, you write a 제안서. In contrast, a 품의서 is strictly internal and follow a standard template for administrative approval.

For financial matters, you might hear 지출결의서 (Ji-chul-gyeol-ui-seo). This is a 'Disbursement Resolution' or an 'Expense Request.' While a pum-ui-seo asks for permission to spend money in the future, a 지출결의서 is often the final document that actually triggers the payment after the pum-ui-seo has been approved. Think of it as the 'check-writing' phase of the process.

마케팅 품의서가 통과되었으니 이제 지출결의서를 작성합시다. (Since the marketing proposal has passed, let's now write the expense request.)

Other Related Terms: 신청서 (Sin-cheong-seo): A simple 'Application Form' (e.g., for vacation or a library card). Less formal than a 품의서.
협조문 (Hyeop-jo-mun): A 'Request for Cooperation' sent between departments.

Finally, in very casual or startup environments, people might just use the English loanword 프로포절 (Proposal) or simply 기획안 (Gi-hwek-an - Project Plan). However, even in these environments, if you are dealing with the legal or financial department, 품의서 remains the standard terminology for the official record of approval. Mastering these distinctions will help you navigate the complexities of the Korean workplace with confidence.

외부 업체에는 제안서를 보내고, 내부적으로는 품의서를 올립니다. (We send a proposal to external companies and submit an internal approval request internally.)

How Formal Is It?

Fun Fact

The '품' (Pum) in '품의서' is the same character used in '품질' (Quality) and '물품' (Product), but here it takes an older meaning of 'reporting to a higher authority'.

Pronunciation Guide

UK /pʰum.i.sʰʌ/

US /pʰum.i.sʰɔ/

The stress is even, but the first syllable '품' (pum) is slightly more emphatic as it carries the core meaning.

Rhymes With

합의서 (Hab-ui-seo - Agreement) 건의서 (Geon-ui-seo - Suggestion paper) 동의서 (Dong-ui-seo - Consent form) 보고서 (Bo-go-seo - Report) 계획서 (Gye-hwek-seo - Plan) 신청서 (Sin-cheong-seo - Application) 설명서 (Seol-myeong-seo - Manual) 확인서 (Hwak-in-seo - Confirmation)

Common Errors

Pronouncing '의' (ui) as 'we'. In this word, it is usually pronounced as 'i' (ee) by native speakers.
Making the 'p' in 'pum' too soft. It should be a strong, aspirated 'pʰ'.

Difficulty Rating

Reading 3/5

Recognizing the word is easy, but reading a real one involves difficult Hanja-based business terms.

Writing 5/5

Writing a proper pum-ui-seo requires advanced formal grammar and specific vocabulary.

Speaking 3/5

Using it in a sentence is straightforward once you know the common verb pairings.

Listening 2/5

It is clearly pronounced and distinct in an office setting.

What to Learn Next

Prerequisites

회사 (Company) 서류 (Document) 부장님 (Manager) 결재 (Approval) 작성하다 (To write/compose)

Learn Next

상신하다 (To submit up) 반려하다 (To reject) 지출결의서 (Expense resolution) 기안 (Drafting) 협조 (Cooperation)

Advanced

전결 규정 (Proxy approval regulations) 품의 제도 (The approval system) 감사 (Audit) 증빙 (Evidence/Proof)

Grammar to Know

-기 위해 (In order to)

승인을 받기 위해 품의서를 꼼꼼히 썼습니다.

-아/어 놓다 (To do something in advance)

품의서를 미리 작성해 놓았습니다.

-ㄴ/은 결과 (As a result of)

품의서를 제출한 결과, 예산이 승인되었습니다.

-에 대하여 (About/Regarding)

이번 행사에 대하여 품의를 올렸습니다.

-지 않으면 안 되다 (Must - double negative)

이 건은 품의서를 쓰지 않으면 안 됩니다.

Examples by Level

이것은 품의서입니다.

This is a proposal for approval.

Simple Noun + 입니다 (to be) structure.

품의서를 써요.

I write a proposal.

Object marker -를 used with the verb 쓰다 (to write).

품의서가 어디에 있어요?

Where is the proposal?

Subject marker -가 used with the location question.

품의서를 주세요.

Please give me the proposal.

Polite request using -주세요.

품의서가 많아요.

There are many proposals.

Adjective 많다 (to be many) describing the subject.

이 품의서는 중요해요.

This proposal is important.

Demonstrative 이 (this) + Noun.

선생님, 품의서 여기 있습니다.

Teacher, the proposal is here.

Formal ending -습니다.

품의서를 읽어요.

I read the proposal.

Object marker -를 + 읽다 (to read).

오늘 품의서를 작성해야 해요.

I have to write a proposal today.

-해야 하다 (must/have to) pattern.

부장님께 품의서를 드렸어요.

I gave the proposal to the manager.

Honorific verb 드리다 (to give to a superior).

품의서 승인을 기다리고 있습니다.

I am waiting for the proposal approval.

-고 있다 (progressive tense).

컴퓨터를 사기 위해 품의서를 썼어요.

I wrote a proposal to buy a computer.

-기 위해 (in order to) purpose clause.

품의서 내용이 조금 복잡해요.

The content of the proposal is a bit complex.

Noun + 내용 (content) as a subject.

이 품의서에 사인해 주세요.

Please sign this proposal.

-아/어 주세요 (request for action).

품의서를 다시 제출하세요.

Please submit the proposal again.

Adverb 다시 (again) + 제출하다 (to submit).

회의 전에 품의서를 읽어 보세요.

Please try reading the proposal before the meeting.

Before (-전에) + Try (-어 보다).

품의서가 반려된 이유를 모르겠어요.

I don't know the reason why the proposal was rejected.

Modifier clause (-ㄴ) + 이유 (reason).

예산 품의서를 상신하기 전에 검토해 주세요.

Please review the budget proposal before I submit it to the superior.

상신하다 (formal submit) + -기 전에 (before).

품의서 작성이 완료되면 알려 드릴게요.

I'll let you know when the proposal writing is complete.

Conditional -면 (if/when) + Future intent -ㄹ게요.

이번 품의서는 팀장님의 승인이 필요합니다.

This proposal needs the team leader's approval.

Noun + 가/이 필요하다 (to need).

품의서에 비용 상세 내역을 포함해야 합니다.

You must include the detailed cost breakdown in the proposal.

포함하다 (to include) + -해야 하다.

어제 올린 품의서가 벌써 결재되었습니다.

The proposal I submitted yesterday has already been signed/approved.

결재되다 (to be authorized/signed).

품의서 양식이 바뀌었으니 확인하세요.

The proposal template has changed, so please check it.

Reason -으니 (so/since).

비품 구매를 위한 품의서를 올렸습니다.

I submitted a proposal for purchasing office supplies.

Noun + 을/를 위한 (for the sake of).

품의서의 기대 효과가 명확하지 않아 반려되었습니다.

It was rejected because the expected effects of the proposal were not clear.

Reason -아/어 (because) + Passive 반려되다.

전자 결재 시스템을 통해 품의서를 상신해 주세요.

Please submit the proposal through the electronic approval system.

Through (-을 통해).

품의서 작성 시 관련 증빙 자료를 반드시 첨부하세요.

When writing a proposal, be sure to attach relevant supporting documents.

When (-시) + Adverb 반드시 (surely).

이 품의서는 사장님의 최종 결재가 있어야 진행 가능합니다.

This proposal can only proceed with the CEO's final approval.

Possibility -ㄹ 수 있다 / 가능하다.

품의서 내용 중 예산 산출 근거를 보완해야 할 것 같습니다.

It seems like the basis for budget calculation in the proposal needs to be supplemented.

Guessing -ㄴ 것 같다.

신규 사업 추진을 위한 품의서가 이사회를 통과했습니다.

The proposal for promoting a new business has passed the board of directors.

Object + 을/를 통과하다 (to pass).

품의서에 적힌 추진 일정이 너무 촉박한 것 아닙니까?

Isn't the implementation schedule written in the proposal too tight?

Negative question -ㄴ 것 아닙니까?

과거의 품의서 사례를 참고하여 작성해 보세요.

Try writing it by referring to past proposal cases.

Referring to (-를 참고하여).

품의서 작성은 단순한 행정 절차를 넘어 의사결정의 핵심입니다.

Writing a proposal is more than a simple administrative procedure; it is the core of decision-making.

Beyond (-를 넘어).

품의서의 논리적 타당성이 부족하면 승인을 얻기 어렵습니다.

If the logical validity of the proposal is insufficient, it is difficult to obtain approval.

Conditional -면 + difficult to -기 어렵다.

해당 품의서는 경영진의 전략적 판단에 따라 보류되었습니다.

The proposal in question has been put on hold according to the strategic judgment of the management.

According to (-에 따라).

품의서 상의 수치 오류는 기업의 신뢰도에 치명적인 영향을 줄 수 있습니다.

Numerical errors in a proposal can have a fatal impact on the company's credibility.

Impact on (-에 영향을 주다).

품의 제도를 간소화하여 업무 효율성을 높이려는 시도가 이어지고 있습니다.

Attempts to increase work efficiency by simplifying the proposal system are continuing.

Intent -려는 + Noun.

기안자와 결재자 간의 원활한 소통이 품의서 통과를 좌우합니다.

Smooth communication between the drafter and the approver dictates the passage of the proposal.

Between (간의) + Influences/Dictates (좌우하다).

품의서에 명시된 예산 집행 계획을 철저히 준수해야 합니다.

The budget execution plan specified in the proposal must be strictly adhered to.

Specified (-에 명시된) + Adhere to (준수하다).

이번 품의서는 부서 간 이해관계가 얽혀 있어 신중한 검토가 요구됩니다.

This proposal requires careful review because the interests of different departments are intertwined.

Intertwined (얽혀 있다) + Passive (요구된다).

품의서의 형식적 완결성보다는 실질적인 사업 타당성에 집중해야 합니다.

We should focus on the actual business feasibility rather than the formal completeness of the proposal.

Rather than (-보다는).

전사적 자원 관리 시스템과 연동된 품의 프로세스가 도입되었습니다.

An approval process linked with the Enterprise Resource Planning (ERP) system has been introduced.

Linked with (-와 연동된).

품의서의 소급 적용 여부를 두고 법무팀과 협의 중입니다.

We are consulting with the legal team regarding whether the proposal can be applied retroactively.

Regarding whether (여부를 두고).

관행적으로 작성되던 품의서의 폐단이 조직의 유연성을 저해하고 있습니다.

The evils of proposals written conventionally are hindering the flexibility of the organization.

Hindering (저해하고 있다).

품의서에 기재된 허위 사실로 인해 징계 위원회가 소집되었습니다.

A disciplinary committee was convened due to false facts recorded in the proposal.

Due to (-로 인해).

디지털 전환 시대에 품의서의 정의와 역할은 재정립될 필요가 있습니다.

In the era of digital transformation, the definition and role of the proposal need to be redefined.

Need to be (-ㄹ 필요가 있다).

품의서 상의 기대 효과를 계량화하여 보고하는 것이 설득력이 높습니다.

Quantifying and reporting the expected effects in the proposal is more persuasive.

Quantifying (-를 계량화하여).

품의서의 결재 경로를 다각화하여 의사결정의 투명성을 확보해야 합니다.

The approval path of the proposal should be diversified to ensure transparency in decision-making.

To ensure/secure (확보해야 한다).

Common Collocations

품의서를 작성하다

품의서를 상신하다

품의서를 반려하다

품의서 승인을 받다

전자 품의

품의서 양식

지출 품의서

품의를 올리다

결재 라인

품의서 내용

Common Phrases

품의서를 올리다

— To submit a proposal for approval. '올리다' (to raise) is used to show respect to the hierarchy.

부장님께 비품 구매 품의서를 올렸습니다.

품의가 나다

— To get the final approval. Literally 'the approval came out.'

아직 품의가 안 나서 기다리고 있어요.

사후 품의

— Submitting a proposal for approval after the action has already been taken (usually discouraged).

급한 건이라 사후 품의로 처리하기로 했습니다.

품의를 득하다

— To obtain/gain approval. A very formal, somewhat archaic business expression.

본 건에 대하여 이미 품의를 득하였습니다.

품의 절차

— The procedure or steps required to get a proposal approved.

품의 절차가 너무 복잡해서 시간이 오래 걸려요.

품의서 반려

— The rejection of an approval request.

품의서 반려 사유를 확인해 보세요.

구매 품의서

— A specific type of proposal for buying items or services.

소프트웨어 라이선스 구매 품의서를 작성하세요.

품의서 검토

— The act of reviewing a submitted proposal.

이사님께서 지금 품의서 검토 중이십니다.

품의 시스템

— The software or organizational system used for approvals.

품의 시스템 점검으로 인해 결재가 늦어지고 있습니다.

품의 근거

— The evidence or reasoning provided in the proposal.

품의 근거가 확실해야 승인받기 쉽습니다.

Often Confused With

품의서 vs 보고서 (Report)

A report states what has happened, while a pum-ui-seo asks for permission for what will happen.

품의서 vs 기안서 (Draft)

A gi-an-seo is more focused on the plan/draft, while a pum-ui-seo is focused on the official request for approval.

품의서 vs 영수증 (Receipt)

A receipt is proof of payment, whereas a pum-ui-seo is the request to make that payment.

Idioms & Expressions

"도장을 찍다"

— To sign off or finalize a deal. While literally 'to press a stamp,' it refers to the final step of a 품의서.

사장님이 드디어 품의서에 도장을 찍으셨어.

Informal/Idiomatic

"서류를 꾸미다"

— To prepare or 'fix up' documents. Sometimes implies making them look better than they are.

품의서를 그럴싸하게 꾸며서 제출했다.

Informal/Nuanced

"입을 맞추다"

— To coordinate stories before submitting a proposal so everyone says the same thing.

품의서를 올리기 전에 팀원들과 입을 맞췄다.

Informal

"결재를 올리다"

— Similar to '품의를 올리다', focusing on the act of seeking the signature.

이번 주 내로 결재를 올릴 계획입니다.

Formal

"반려 딱지를 맞다"

— To get a 'rejection sticker' (idiomatically meaning to have your proposal rejected).

이번에도 품의서가 반려 딱지를 맞았어요.

Slangy/Informal

"윗선에 보고하다"

— To report to the 'upper line' (higher management) regarding a proposal.

품의 내용을 윗선에 보고드려야 합니다.

Business Neutral

"발목을 잡다"

— To hold someone back. Used when a pending 품의서 stops a project from moving.

품의서 승인이 안 나서 프로젝트 발목을 잡고 있다.

Idiomatic

"뜬구름 잡다"

— To catch floating clouds. Used to describe a 품의서 that is too vague or unrealistic.

이 품의서는 너무 뜬구름 잡는 소리만 하네요.

Idiomatic

"판을 짜다"

— To set the stage or design the plan (often the stage before writing the pum-ui-seo).

기획팀에서 이미 품의를 위한 판을 다 짜 놓았다.

Informal

"눈치 보며 올리다"

— To submit a proposal while carefully watching the boss's mood.

부장님 기분이 좋을 때 품의서를 눈치 보며 올렸다.

Informal

Easily Confused

품의서 vs 결재 vs 결제

They sound identical (Gyeol-jae vs. Gyeol-je).

결재 (Gyeol-jae) is approval/signature from a boss. 결제 (Gyeol-je) is payment/settlement (like with a credit card). You get '결재' for your '품의서'.

부장님께 결재(approval)를 받고, 카드로 결제(payment)를 했습니다.

품의서 vs 품의 vs 건의

Both involve suggestions.

품의 is a formal request for approval within the system. 건의 is a suggestion or recommendation, often less formal or directed towards improvement rather than specific spending.

제도 개선을 건의했고, 비품 구매를 품의했습니다.

품의서 vs 상신 vs 제출

Both mean to submit.

제출 is general (submitting homework, a report). 상신 is specific to business hierarchy, meaning to submit 'up' for approval.

과제를 제출하고, 품의서를 상신했습니다.

품의서 vs 반려 vs 취소

Both mean the action stops.

반려 is the boss rejecting the document. 취소 is the person who wrote it deciding to pull it back.

품의서가 반려당해서 제가 기안을 취소했습니다.

품의서 vs 공문 vs 품의서

Both are official documents.

공문 is an official document sent between different organizations. 품의서 is an internal document within one organization.

교육청에서 공문이 왔으니 내부 품의서를 작성합시다.

Sentence Patterns

[Object]를 위해 품의서를 써요.

새 의자를 위해 품의서를 써요.

[Superior]님께 품의서를 상신했습니다.

이사님께 품의서를 상신했습니다.

품의서가 [Reason](으)로 인해 반려되었습니다.

품의서가 예산 부족으로 인해 반려되었습니다.

품의서 내용 중 [Part]를 보완해야 합니다.

품의서 내용 중 기대 효과를 보완해야 합니다.

전자 결재 시스템으로 품의서를 올리세요.

품의서의 타당성을 입증하는 것이 관건입니다.

해당 건은 사후 품의 처리가 불가합니다.

품의 제도의 경직성이 효율성을 저해하고 있습니다.

Word Family

Nouns

품의 (The act of asking for deliberation)

결재 (Authorization/Approval)

상신 (Submission to a superior)

기안 (Drafting a plan)

Verbs

품의하다 (To ask for deliberation)

결재하다 (To approve/sign)

상신하다 (To submit up)

반려하다 (To reject a document)

서류 (Document)

공문 (Official document)

직인 (Official seal)

전결 (Approval by proxy)

합의 (Consensus/Agreement)

How to Use It

frequency

Extremely high in corporate, government, and educational administration.

Common Mistakes

Using '품의서' for a report of completed work. → Use '보고서' (Bo-go-seo).
A '품의서' is for getting permission *before* starting. If you've already finished the work, you are reporting results, not asking for permission.
Using the verb '주다' (to give) with '품의서'. → Use '상신하다' or '제출하다'.
'주다' is too casual for a formal office document. '상신하다' shows respect for the organizational hierarchy.
Spelling it as '결제' when referring to approval. → Spell it as '결재'.
'결제' (je) is for paying bills. '결재' (jae) is for the boss's signature. This is a critical distinction in business writing.
Forgetting to include 'Expected Effects' (기대 효과). → Always include a section on the benefits of the proposal.
In Korean business culture, justifying *why* an expense is necessary is just as important as the expense itself.
Using '품의서' in a casual text message to a friend. → Use '부탁' (favor) or '허락' (permission).
'품의서' is a strictly professional, administrative term. Using it in personal life sounds robotic or sarcastic.

Tips

Be Concise

Managers in Korea are busy. Keep the 'Purpose' and 'Expected Effect' of your 품의서 short and to the point. Use bullet points instead of long paragraphs.

Use Noun Endings

In the body of a 품의서, it is common to end sentences with nouns or nominalized verbs (e.g., '-함', '-임') to sound more objective and formal.

Check the Hierarchy

Before submitting, make sure the '결재 라인' (approval line) is correct. Skipping a manager in the chain is a major social error in Korean business.

Learn Related Verbs

Master '상신' (submit up), '반려' (reject), and '승인' (approve). These three words cover 90% of the conversations about a 품의서.

Attach Proof

Always attach '증빙 서류' (supporting documents) like quotes (견적서) or research data. A 품의서 without proof is rarely approved.

Pre-consultation

In Korea, it's often good to 'Heop-ui' (consult) with your boss verbally before submitting the formal 품의서. This prevents unexpected rejections.

Master E-systems

If your company uses a system like 'Douzone' or 'Hancom,' learn the specific '품의' interface. Each system has its own quirks.

Watch the Budget

Always check if the requested amount fits within the department's remaining budget for the quarter before writing the 품의서.

Practice with Templates

Search for '품의서 양식' (pum-ui-seo template) on Korean search engines to see real-world examples of how they are structured.

Don't confuse Gyeol-jae and Gyeol-je

Remember: 'Jae' (재) for the Boss's sign, 'Je' (제) for the Money you spend. This is the most common spelling mistake even for Koreans.

Memorize It

Mnemonic

PUM (Pump) + UI (We) + SEO (Saw). 'We pumped the boss to sign what we saw in the proposal.'

Visual Association

Imagine a red stamp (Dojang) hitting a paper with a big 'OK' on it. That paper is the 품의서.

Word Web

Office Approval Boss Budget Stamp Paperwork Hierarchy Permission

Challenge

Try to say 'I am writing a proposal for a new computer' in Korean: '새 컴퓨터를 위해 품의서를 쓰고 있어요.'

Word Origin

Derived from Sino-Korean (Hanja).

Original meaning: 품(品) - to inform/ask + 의(議) - to discuss/deliberate + 서(書) - document.

Sino-Korean roots.

Cultural Context

Be aware that '품의서' is strictly a work term. Don't use it in personal life (e.g., asking your spouse for permission to buy a game).

In Western companies, an email or a Slack message often suffices for small approvals. In Korea, even small expenditures often require a formal 품의서 for audit purposes.

Drama 'Misaeng': Shows the intense pressure of drafting perfect proposals. Drama 'Chief Kim': A comedy about an accountant who manipulates 'pum-ui-seo' and 'gi-an-seo'. The term 'Gyeol-jae-pan' (approval folder) often appears in news about government decisions.

Practice in Real Life

Real-World Contexts

Office Budgeting

예산 품의서를 올렸습니다.
금액이 너무 큽니다.
견적서를 첨부하세요.
승인이 났습니다.

Human Resources

채용 품의서가 통과되었습니다.
인원 보충이 필요합니다.
연봉 협상 품의입니다.
교육 참가를 신청합니다.

IT/Equipment

노트북 교체 품의서를 썼어요.
수리 비용이 많이 듭니다.
신규 소프트웨어가 필요해요.
비품 목록을 확인하세요.

Events/Marketing

행사 기획 품의서입니다.
광고 집행을 승인해 주세요.
기대 효과를 적어주세요.
마케팅 예산이 부족해요.

Legal/Administration

계약 체결 품의서입니다.
법무팀 검토를 받았습니다.
규정에 따라 작성하세요.
최종 결재권자가 누구죠?

Conversation Starters

"이번 프로젝트 품의서 작성하셨나요?"

"부장님이 품의서를 반려하셨는데 이유를 아세요?"

"품의서에 어떤 내용을 더 넣어야 할까요?"

"결재 라인에 이사님도 포함되나요?"

"품의서 승인이 언제쯤 날까요?"

Journal Prompts

오늘 회사에서 작성한 품의서에 대해 써보세요.

한국의 품의서 문화와 본국(또는 미국)의 업무 문화 차이를 비교해 보세요.

내가 사장이라면 어떤 품의서를 바로 승인해 줄지 상상해서 적어보세요.

품의서가 계속 반려된다면 어떻게 대처할 것인지 써보세요.

비즈니스 한국어를 공부하면서 품의서라는 단어가 왜 중요한지 생각해 보세요.

Frequently Asked Questions

10 questions

While often used interchangeably, a '기안서' (Gi-an-seo) is a broader term for any document that initiates a plan or draft. A '품의서' (Pum-ui-seo) specifically refers to a document requesting permission or approval from a superior, often involving budget or policy changes. In many companies, a 'pum-ui-seo' is considered a specific type of 'gi-an-seo'.

Yes, but it might feel a bit formal. Startups often use terms like '제안서' (proposal), '기획안' (plan), or even English words like 'Proposal.' However, for official accounting or HR purposes, '품의서' is still the standard term for the record of approval.

If a '품의서' is '반려' (ban-ryeo), it means your superior has returned it without approval. Usually, they will provide a '반려 사유' (reason for rejection). You should read the comments, fix the issues (like clarifying the budget or the purpose), and then '재상신' (re-submit) the document.

No. While very common for budget requests, it is also used for seeking approval on new policies, hiring new employees, changing work procedures, or starting any project that requires official organizational backing.

The 'Gyeol-jae' (결재) system, of which the '품의서' is a part, reflects Korea's Confucian-influenced hierarchical culture. It ensures that responsibility is shared and that every action is aligned with the goals of the leadership. It also provides a clear audit trail for the organization.

The most professional way to say 'submit a proposal' to a superior is '품의서를 상신하다' (pum-ui-seo-reul sang-sin-ha-da). In a slightly less formal but still professional context, you can say '품의서를 올리다' (pum-ui-seo-reul ol-li-da).

'사후 품의' (Sa-hu pum-ui) is 'post-approval.' This happens when an employee takes an action or spends money first due to an emergency and then submits the paperwork later. This is generally avoided because it carries the risk of the expense not being reimbursed if the approval is denied.

In the past, yes. Every '품의서' needed a physical 'dojang' (stamp) from every manager in the chain. Today, most Korean companies use '전자 결재' (electronic approval) systems where you just click a button, but the digital icon often still looks like a traditional red stamp.

A standard '품의서' includes: 1. Subject (제목), 2. Drafter (기안자), 3. Date (일자), 4. Purpose (목적/개요), 5. Details (상세 내용), 6. Budget (예산), and 7. Expected Effects (기대 효과).

Absolutely. It is perhaps even more critical in government offices (Gong-mu-won culture) where every cent of the public budget must be meticulously documented and approved through a formal '품의' process.