[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:shanai-mail":3},{"meta":4,"markdown":74},{"type":5,"articleId":6,"slug":7,"title":8,"titleEn":9,"category":10,"summary":11,"publishedAt":12,"image":13,"vocabulary":14},"article","bj-shanai-mail","shanai-mail","社内メールの書き方 — 件名から結びまで","How to Write Internal Email — From Subject Line to Closing","business-japanese","Templates and conventions for internal Japanese business email. Subject-line\nprefixes ([依頼], [共有], [要返信]), the \"Otsukaresama\" greeting that only\nbelongs inside the company, CC\u002FBCC etiquette, attachment naming rules, and\nready-to-adapt templates for status reports, meeting requests, and escalations.\n","2026-04-27T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fbj-shanai-mail.png",[15,20,25,29,33,37,41,45,49,53,57,61,65,69],{"word":16,"reading":17,"meaning":18,"level":19},"社内メール","しゃないめーる","internal email","N3",{"word":21,"reading":22,"meaning":23,"level":24},"件名","けんめい","subject line","N2",{"word":26,"reading":27,"meaning":28,"level":24},"依頼","いらい","request",{"word":30,"reading":31,"meaning":32,"level":24},"共有","きょうゆう","sharing",{"word":34,"reading":35,"meaning":36,"level":24},"要返信","ようへんしん","reply required",{"word":38,"reading":39,"meaning":40,"level":19},"お疲れ様です","おつかれさまです","standard internal greeting",{"word":42,"reading":43,"meaning":44,"level":24},"添付","てんぷ","attachment",{"word":46,"reading":47,"meaning":48,"level":24},"宛先","あてさき","recipient",{"word":50,"reading":51,"meaning":52,"level":24},"写し","うつし","copy (CC)",{"word":54,"reading":55,"meaning":56,"level":24},"報告書","ほうこくしょ","report document",{"word":58,"reading":59,"meaning":60,"level":24},"議事録","ぎじろく","meeting minutes",{"word":62,"reading":63,"meaning":64,"level":24},"結び","むすび","closing",{"word":66,"reading":67,"meaning":68,"level":24},"署名","しょめい","signature",{"word":70,"reading":71,"meaning":72,"level":73},"エスカレーション","えすかれーしょん","escalation","N1","\n::heading\n[社内メール]{しゃないめーる::N3}は[速]{はや::N3}さと[分]{わ::N5}かりやすさが[全]{すべ::N3}て\n\n#en\nInternal email is all about speed and clarity\n::\n\n::para\n[社内メール]{しゃないめーる:internal email:N3}は[社外メール]{しゃがいめーる:external email:N4}とは[全]{まった::N3}く[異]{こと::N1}なる[文化]{ぶんか:culture:N3}を[持]{も::N4}ちます。[相手]{あいて:counterpart:N3}は[同僚]{どうりょう:colleagues:N1}や[上司]{じょうし:bosses:N1}なので、[長]{なが::N5}い[挨拶]{あいさつ:greetings:N1}や[拝啓]{はいけい:opening salutation:N1}は[不要]{ふよう:unnecessary:N3}です。[最重要]{さいじゅうよう:most important:N3}なのは[件名]{けんめい:subject line:N3}を[見]{み::N5}ただけで[内容]{ないよう:content:N3}と[緊急度]{きんきゅうど:urgency:N1}が[分]{わ::N5}かることです。\n\n#en\nInternal email has a totally different culture from external email. Since recipients are colleagues and bosses, long greetings and \"Haikei\" openings are unnecessary. The most important thing is that the subject line alone communicates content and urgency.\n::\n\n::heading\n[件名]{けんめい::N3}の[基本ルール]{きほんるーる::N1}\n\n#en\nSubject-line basics\n::\n\n::para\n[件名]{けんめい:subject line:N3}には[必]{かなら::N3}ず[アクション種別]{あくしょんしゅべつ:action category:N3}の[タグ]{たぐ:tag}を[先頭]{せんとう:beginning:N3}に[付]{つ::N3}けます。[受信箱]{じゅしんばこ:inbox:N3}が[100通]{ひゃくつう:hundred messages:N4}を[超]{こ::N2}える[多忙]{たぼう:busy:N3}な[管理職]{かんりしょく:managers:N2}は、[タグ]{たぐ:tag}で[優先順位]{ゆうせんじゅんい:priority:N2}を[即決]{そっけつ:decide instantly:N1}します。\n\n#en\nThe subject line must always begin with an action-category tag. Busy managers whose inboxes exceed 100 messages decide priority on the tag alone.\n::\n\n::callout\n[頻用]{ひんよう:frequently used:N1}される[件名タグ]{けんめいたぐ:subject tags:N3}：\n- [[依頼]{いらい:request:N2}] — [作業]{さぎょう:work:N4}を[頼]{たの::N3}む[時]{とき::N5}\n- [[共有]{きょうゆう:sharing:N3}] — [情報展開]{じょうほうてんかい:info dissemination:N1}のみ\n- [[要返信]{ようへんしん:reply needed:N3}] — [返信必須]{へんしんひっす:must reply:N1}\n- [[要確認]{ようかくにん:please confirm:N3}] — [内容確認]{ないようかくにん:content confirmation:N3}を[依頼]{いらい:request:N2}\n- [[至急]{しきゅう:urgent:N1}] — [当日中]{とうじつちゅう:within today:N3}の[対応]{たいおう:response:N1}\n- [[FYI]{えふわいあい:for your information}] — [参考情報]{さんこうじょうほう:reference info:N3}（[返信不要]{へんしんふよう:no reply needed:N3}）\n- [[報告]{ほうこく:report:N3}] — [完了報告]{かんりょうほうこく:completion report:N2}\n\n#en\nFrequent subject tags: [Request], [Share], [Reply needed], [Please confirm], [Urgent], [FYI], [Report].\n::\n\n::heading\n[本文構成]{ほんぶんこうせい::N3} — [挨拶]{あいさつ::N1}・[用件]{ようけん::N3}・[結]{むす::N1}び\n\n#en\nBody structure — greeting, business, closing\n::\n\n::para\n[社内メール]{しゃないめーる:internal email:N3}の[冒頭]{ぼうとう:opening:N1}は「[お疲]{おつか::N3}れ[様]{さま::N3}です。[〇〇部]{まるまるぶ:〇〇 division:N3}の[山田]{やまだ::N4}です」が[標準]{ひょうじゅん:standard:N1}です。「[お疲]{おつか::N3}れ[様]{さま::N3}です」は[社内専用]{しゃないせんよう:internal-only:N2}の[挨拶]{あいさつ:greeting:N1}で、[社外]{しゃがい:external:N4}の[人]{ひと:person:N5}には[絶対]{ぜったい:absolutely:N3}に[使]{つか::N4}いません。[本文]{ほんぶん:body:N4}は[結論]{けつろん:conclusion:N1}を[最初]{さいしょ:first:N3}に[書]{か::N5}き、[詳細]{しょうさい:details:N1}は[箇条書]{かじょうが::N1}きで[補足]{ほそく:supplement:N2}するのが[現代的]{げんだいてき:modern:N3}な[書]{か::N5}き[方]{かた::N4}です。\n\n#en\nInternal email standardly opens with \"Otsukaresama desu. Yamada from the OO division.\" \"Otsukaresama desu\" is an internal-only greeting and must never be used with outsiders. Modern style is to put the conclusion first and supplement with bullet-point details.\n::\n\n::callout\n[基本構造]{きほんこうぞう:basic structure:N1}：\n1. [挨拶]{あいさつ:greeting:N1} + [名乗]{なの::N3}り（1行）\n2. [用件要約]{ようけんようやく:summary of business:N3}（1-2行）\n3. [詳細]{しょうさい:details:N1}（[箇条書]{かじょうが::N1}き）\n4. [依頼事項]{いらいじこう:request items:N1} or [次]{つぎ::N3}のアクション\n5. [結]{むす::N1}びの[一言]{ひとこと:one phrase:N4}（「よろしくお[願]{ねが::N3}いします」）\n6. [署名]{しょめい:signature:N2}\n\n#en\nBasic structure: 1) Greeting + name, 2) Summary of business, 3) Bulleted details, 4) Request items \u002F next action, 5) Closing line (\"Yoroshiku onegaishimasu\"), 6) Signature.\n::\n\n::heading\n[CC]{しーしー}と[BCC]{びーしーしー}の[使]{つか::N4}い[分]{わ::N5}け\n\n#en\nUsing CC and BCC correctly\n::\n\n::para\n[CC]{しーしー}は「[念]{ねん::N3}のため[共有]{きょうゆう:shared:N3}」で、[受信者]{じゅしんしゃ:recipient:N3}に[アクション]{あくしょん:action}を[求]{もと::N3}めません。[BCC]{びーしーしー}は[他]{た::N3}の[受信者]{じゅしんしゃ:recipients:N3}に[宛先]{あてさき:addresses:N1}を[隠]{かく::N1}したい[時]{とき::N5}に[使]{つか::N4}います。[社内]{しゃない:internal:N3}では[BCC]{びーしーしー}を[多用]{たよう:overuse:N4}すると[隠蔽体質]{いんぺいたいしつ:cover-up culture:N1}と[誤解]{ごかい:misunderstood:N3}されるため[極力避]{きょくりょくさ::N1}けます。\n\n#en\nCC means \"shared just in case\" and asks no action of the recipient. BCC is for hiding addresses from other recipients. Heavy internal use of BCC is read as a cover-up culture, so avoid it as much as possible.\n::\n\n::callout\n[CCの作法]{しーしーのさほう:CC etiquette:N3}：[上司]{じょうし:boss:N1}を[CC]{しーしー}に[入]{い::N5}れる[時]{とき::N5}は「[CC]{しーしー}：[田中]{たなか::N4}[部長]{ぶちょう:division manager:N3}」と[本文冒頭]{ほんぶんぼうとう:body opening:N1}に[明記]{めいき:clearly state:N3}し、[読]{よ::N5}み[手]{て::N4}に[誰]{だれ::N3}が[見]{み::N5}ているかを[伝]{つた::N3}えるのが[親切]{しんせつ:considerate:N4}です。\n\n#en\nCC etiquette: When CC'ing a boss, write \"CC: Tanaka-buchou\" at the top of the body to let the reader know who else is watching. It's a thoughtful touch.\n::\n\n::heading\n[添付ファイル]{てんぷふぁいる::N1}の[命名規則]{めいめいきそく::N2}\n\n#en\nAttachment naming conventions\n::\n\n::para\n[添付ファイル]{てんぷふぁいる:attachment file:N1}の[ファイル名]{ふぁいるめい:filename:N5}には[日付]{ひづけ:date:N3}・[内容]{ないよう:content:N3}・[版数]{はんすう:version:N2}を[必]{かなら::N3}ず[含]{ふく::N2}めます。[多]{おお::N4}くの[企業]{きぎょう:companies:N1}で「20260426_[四月度報告書]{しがつどほうこくしょ:April monthly report:N3}_v2.xlsx」のような[書式]{しょしき:format:N3}が[暗黙]{あんもく:tacit:N1}の[ルール]{るーる:rule}になっています。\n\n#en\nAttachment filenames must include the date, content, and version. The convention \"20260426_April-monthly-report_v2.xlsx\" is the unwritten rule at most companies.\n::\n\n::callout\n[命名]{めいめい:naming:N3}の[原則]{げんそく:principles:N2}：\n- [年月日]{ねんがっぴ:date:N5}は[YYYYMMDD]{わいわいわいわいえむえむでぃーでぃー:YYYYMMDD}[形式]{けいしき:format:N3}\n- [スペース]{すぺーす:space}は[使]{つか::N4}わずアンダースコア\n- [社外秘]{しゃがいひ:confidential:N1}は[ファイル名]{ふぁいるめい:filename:N5}に「[Confidential]{こんふぃでんしゃる:Confidential}」を[追加]{ついか:add:N3}\n- [改訂]{かいてい:revised:N1}は[v2]{ぶいに:v2}, [v3]{ぶいさん:v3}と[版数]{はんすう:version number:N2}を[更新]{こうしん:update:N3}\n\n#en\nNaming principles: dates in YYYYMMDD; underscores not spaces; mark confidential files \"Confidential\"; bump v2, v3 for revisions.\n::\n\n::heading\n[テンプレート1]{てんぷれーといち} — [進捗報告]{しんちょくほうこく::N1}\n\n#en\nTemplate 1 — Status report\n::\n\n::callout\n[件名]{けんめい:subject:N3}：[[報告]{ほうこく::N3}] [Aプロジェクト]{えーぷろじぇくと:Project A} [週次進捗]{しゅうじしんちょく:weekly progress:N1}（[4月26日]{しがつにじゅうろくにち:April 26:N5}）\n\n[本文]{ほんぶん:body:N4}：\nお[疲]{つか::N3}れ[様]{さま::N3}です。[開発部]{かいはつぶ:development division:N3}の[山田]{やまだ::N4}です。\n\n[A][プロジェクト]{ぷろじぇくと:project}の[今週]{こんしゅう:this week:N4}の[進捗]{しんちょく:progress:N1}を[報告]{ほうこく:report:N3}します。\n\n■ [完了]{かんりょう:completed:N2}\n　・[ログイン機能]{ろぐいんきのう:login function:N3}の[実装]{じっそう:implementation:N2}\n　・[テスト環境]{てすとかんきょう:test environment:N1}の[構築]{こうちく:setup:N2}\n\n■ [進行中]{しんこうちゅう:in progress:N3}\n　・[決済]{けっさい:payment:N3}[API連携]{えーぴーあいれんけい:API integration:N1}（[達成度]{たっせいど:completion rate:N3} 70%）\n\n■ [課題]{かだい:issues:N2}\n　・[外部API仕様変更]{がいぶえーぴーあいしようへんこう:external API spec change:N3}により[二日遅延]{ふつかちえん:two-day delay:N2}の[見込]{みこ::N3}み\n\n[来週中]{らいしゅうちゅう:within next week:N4}にAPI[連携]{れんけい:integration:N1}を[完了]{かんりょう:complete:N2}し、[統合テスト]{とうごうてすと:integration testing:N1}に[入]{はい::N5}る[予定]{よてい:plan:N3}です。\n\nよろしくお[願]{ねが::N3}いいたします。\n\n#en\nSubject: [Report] Project A weekly progress (April 26)\n\nBody: Otsukaresama desu, Yamada from the Development Division. Reporting Project A progress this week.\n\nCompleted: login function implementation; test environment setup.\nIn progress: payment API integration (70%).\nIssues: two-day delay expected due to external API spec change.\n\nPlan to finish API integration next week and enter integration testing.\n\nYoroshiku onegaiitashimasu.\n::\n\n::heading\n[テンプレート2]{てんぷれーとに} — [会議依頼]{かいぎいらい::N2}\n\n#en\nTemplate 2 — Meeting request\n::\n\n::callout\n[件名]{けんめい:subject:N3}：[[要返信]{ようへんしん:reply required:N3}] [来週]{らいしゅう:next week:N4}の[設計レビュー]{せっけいれびゅー:design review:N2}[日程調整]{にっていちょうせい:schedule coordination:N1}\n\n[本文]{ほんぶん:body:N4}：\nお[疲]{つか::N3}れ[様]{さま::N3}です。[山田]{やまだ::N4}です。\n\n[新機能]{しんきのう:new feature:N3}の[設計レビュー]{せっけいれびゅー:design review:N2}を[来週]{らいしゅう:next week:N4}[実施]{じっし:hold:N1}したく、[ご都合]{ごつごう:availability:N3}を[伺]{うかが::N2}います。\n\n■ [候補日時]{こうほにちじ:candidate dates:N2}\n　・5月7日（[木]{もく:Thu:N5}）14:00-15:30\n　・5月8日（[金]{きん:Fri:N5}）10:00-11:30\n\n■ [所要時間]{しょようじかん:duration:N3}：90分\n■ [場所]{ばしょ:place:N3}：[会議室B]{かいぎしつびー:meeting room B:N3} or Zoom\n■ [参加者]{さんかしゃ:attendees:N3}：[佐藤]{さとう::N1}[部長]{ぶちょう:dept manager:N3}、[鈴木]{すずき::N1}[リーダー]{りーだー:leader}、[山田]{やまだ::N4}\n\n[4月30日]{しがつさんじゅうにち:April 30:N5}（[水]{すい:Wed:N5}）までに[ご返信]{ごへんしん:reply:N3}いただけますと[幸]{さいわ::N3}いです。\n\nよろしくお[願]{ねが::N3}いいたします。\n\n#en\nSubject: [Reply Required] Schedule coordination for next week's design review\n\nBody: Otsukaresama desu, Yamada here. I'd like to hold the design review for the new feature next week — could you share availability?\n\nCandidate slots: May 7 (Thu) 14:00-15:30; May 8 (Fri) 10:00-11:30.\nDuration: 90 minutes. Location: Meeting Room B or Zoom. Attendees: Sato-buchou, Suzuki-leader, Yamada.\n\nPlease reply by April 30 (Wed). Yoroshiku onegaiitashimasu.\n::\n\n::heading\n[テンプレート3]{てんぷれーとさん} — [エスカレーション]{えすかれーしょん}\n\n#en\nTemplate 3 — Escalation\n::\n\n::callout\n[件名]{けんめい:subject:N3}：[[至急]{しきゅう:urgent:N1}][[要判断]{ようはんだん:decision needed:N3}] [本番環境]{ほんばんかんきょう:production:N1}[障害発生]{しょうがいはっせい:incident occurred:N1}に[関]{かん::N3}する[対応方針]{たいおうほうしん:response policy:N1}\n\n[本文]{ほんぶん:body:N4}：\nお[疲]{つか::N3}れ[様]{さま::N3}です。[山田]{やまだ::N4}です。\n\n[本日]{ほんじつ:today:N5}13:00より[本番環境]{ほんばんかんきょう:production:N1}で[決済機能]{けっさいきのう:payment function:N3}に[障害]{しょうがい:incident:N1}が[発生]{はっせい:occurred:N4}しております。[判断]{はんだん:decision:N3}を[仰]{あお::N1}ぎたく[ご連絡]{ごれんらく:contact:N2}いたします。\n\n■ [現状]{げんじょう:current status:N3}\n　・[決済成功率]{けっさいせいこうりつ:payment success rate:N1}が60%まで[低下]{ていか:dropped:N2}\n　・[原因]{げんいん:cause:N3}は[外部決済]{がいぶけっさい:external payment:N3}サービスの[応答遅延]{おうとうちえん:response delay:N1}と[特定]{とくてい:identified:N3}\n\n■ [対応案]{たいおうあん:response options:N1}\n　A. [代替決済経路]{だいたいけっさいけいろ:alternative payment route:N2}に[切替]{きりかえ:switch:N2}（[復旧]{ふっきゅう:recovery:N2}30分）\n　B. [メンテナンスモード]{めんてなんすもーど:maintenance mode}に[移行]{いこう:transition:N2}し[原因]{げんいん:cause:N3}が[解消]{かいしょう:resolved:N3}するまで[停止]{ていし:halt:N2}\n\nA案[推奨]{すいしょう:recommended:N1}です。[15時]{じゅうごじ:3pm:N5}までに[ご判断]{ごはんだん:decision:N3}いただきたく[お願]{おねが::N3}いいたします。\n\n#en\nSubject: [URGENT][Decision Needed] Response policy for production incident\n\nBody: Otsukaresama desu, Yamada here. Since 13:00 today there's been a payment incident in production. Requesting your decision.\n\nStatus: payment success rate dropped to 60%; cause identified as external payment service response delay.\nOptions: A) Switch to alternative payment route (30 min recovery). B) Move to maintenance mode until resolved.\n\nRecommend option A. Please decide by 15:00.\n::\n\n::heading\n[結]{むす::N1}びの[定型句]{ていけいく::N1}\n\n#en\nClosing set phrases\n::\n\n::para\n[結]{むす::N1}びの[一言]{ひとこと:phrase:N4}は[依頼]{いらい:request:N2}・[報告]{ほうこく:report:N3}・[共有]{きょうゆう:sharing:N3}で[少]{すこ::N4}しずつ[変]{か::N3}わります。「よろしくお[願]{ねが::N3}いいたします」が[万能]{ばんのう:all-purpose:N3}ですが、[報告]{ほうこく:report:N3}には「[ご確認]{ごかくにん:please confirm:N3}のほどよろしくお[願]{ねが::N3}いいたします」、[共有]{きょうゆう:share:N3}のみなら「[取]{と::N3}り[急]{いそ::N4}ぎ[ご共有]{ごきょうゆう:fyi:N3}まで」と[使]{つか::N4}い[分]{わ::N5}けると[洗練]{せんれん:refined:N2}された[印象]{いんしょう:impression:N2}になります。\n\n#en\nClosing phrases vary slightly by request, report, or share. \"Yoroshiku onegaiitashimasu\" works universally, but \"Go-kakunin no hodo yoroshiku onegaiitashimasu\" for reports and \"Toriisogi go-kyouyuu made\" for FYI shares feel more polished.\n::\n\n::callout\n[NG例]{えぬじーれい:bad examples:N3}：\n- [絵文字]{えもじ:emoji:N3}や[感嘆符]{かんたんふ:exclamation marks:N1}の[多用]{たよう:overuse:N4}（!!!）\n- [全角英数字]{ぜんかくえいすうじ:full-width alphanumerics:N2}の[混在]{こんざい:mixing:N2}\n- [署名忘]{しょめいわす::N2}れ\n- [TO]{とぅー:To}に[全員]{ぜんいん:everyone:N3}を[入]{い::N5}れて[誰]{だれ::N3}に[依頼]{いらい:request:N2}しているか[不明]{ふめい:unclear:N4}にする\n\n#en\nBad examples: heavy emoji and exclamation marks (!!!); mixing full-width alphanumerics; forgetting the signature; putting everyone in To: so it's unclear who's being asked.\n::\n"]