Business Proficiency Test Jobpass (B検ジョブパス) common mistakes
Business Proficiency Test Jobpass (B検ジョブパス) · Understand the traps and how to avoid them.
Writing 敬語 that is grammatically polite but socially wrong-for example saying 「ご苦労様です」 to a supervisor or 「お疲れ様です」 to a customer, or double-honorifics like 「お伺いさせていただきます」.
Candidates memorize honorific verb lists (いらっしゃる, 伺う, 申し上げる) without attaching each to the direction of the relationship (目上/目下, 社内/社外), so they pick the form that sounds most polite rather than the one correct for the addressee.
What to do instead
Build a two-axis table: rows = 相手 (上司, 同僚, 取引先, 顧客), columns = 動作 (行く, 来る, 言う, 見る, 食べる). Fill in the correct 尊敬語/謙譲語/丁寧語 cell for each and drill until choosing is automatic. Mark 社外 communication as always using 謙譲語 for your own side and 尊敬語 for theirs.
Answering ビジネスマナー scenario questions by choosing the most deferential option-e.g. standing to bow deeply and immediately apologizing on the phone before identifying the purpose of the call, or handing a 名刺 with both hands while the other party is still speaking.
The exam's distractor design rewards the instinct that 'more polite = more correct,' and candidates who have only abstract politeness knowledge cannot rank actions by appropriateness in context (first contact, apology, internal vs external).
What to do instead
Learn the standard sequences as ordered steps: 名刺交換 (receive with both hands, read the name, place on the 名刺入れ), 電話応対 (identify self and company first, then confirm the other party's name and用件), 訪問 (受付, 取り次ぎ, 応接室での席次). For each scenario question, eliminate any option that skips a step in the sequence or reverses the order of self-introduction.
Treating 敬語 transformation as a one-to-one mapping and producing wrong or non-existent forms, such as 「お分かりになられますか」, 「ご覧になられました」, or using 「させていただく」 for actions that need no permission.
Candidates learn 'add お/ご + になる' as a rule and apply it mechanically, including to verbs that already have a dedicated 尊敬語 (見る→ご覧になる, 食べる→召し上がる), and they overuse させていただく as a universal softener.
What to do instead
Memorize the closed set of special honorific verbs and their 謙譲 counterparts as pairs, and treat the お/ご+になる pattern as a fallback only for verbs outside that set. Ban させていただく unless the speaker is actually receiving permission or benefit; replace with いたします or plain ます form in the drill.
In ビジネス文書 questions, selecting a letter or email whose 頭語 and 結語 do not match (拝啓 paired with 敬具 is correct; 拝啓 with 草々 is not), or omitting the 時候の挨拶 and 記書き structure in a 社外文書.
Candidates remember isolated vocabulary items rather than the fixed scaffolding of a formal document, and they underestimate how heavily the exam tests structural conventions (頭語・時候の挨拶・本文・結語・記書き・以上) as a single unit.
What to do instead
Memorize the 頭語–結語 pairs (拝啓–敬具, 前略–草々, 謹啓–謹言) and the required order of elements for 社外文書. When reviewing a sample, number each structural element in the margin; in the exam, scan the candidate options for a missing or mismatched element and eliminate on that basis before judging content.
Confusing 社外文書 register with 社内文書 register-writing a 稟議書 or 報告書 to an internal reader in full 敬語 letter format, or writing a 取引先 email in casual です・ます with no 時候の挨拶.
Candidates learn 'business writing = formal' as a single style and never separate the two document families, so they misapply the conventions of one to the other.
What to do instead
Classify every document type you study as 社外 (挨拶状, 通知, 依頼, 詫び状) or 社内 (稟議書, 報告書, 議事録, 始末書) and note the register rule for each. Drill by converting one short message between the two registers and checking which elements appear and disappear.
Getting 割合・損益・損益分岐点 calculations wrong by computing on the wrong base-e.g. applying a 20% 値引き and then a 20% 値上げ and assuming the price returns to the original, or adding a 利益率 to a 原価 instead of dividing by (1 − 利益率).
Candidates apply percentage operations additively and treat the base amount as constant, when each successive percentage applies to a new base; they also confuse 原価基準 and 売価基準 for markup.
What to do instead
Before calculating, write down the base explicitly (定価, 原価, 売価) next to each percentage. Memorize 売価 = 原価 ÷ (1 − 利益率) for 売価基準 and 売価 = 原価 × (1 + 利益率) for 原価基準, and always test a discount-then-markup problem with concrete numbers to confirm the result does not return to the start.
Misreading 損益分岐点 problems by mixing 固定費 and 変動費, or forgetting that 限界利益 = 売上 − 変動費, leading to a break-even quantity computed as 固定費 ÷ 売上高 instead of 固定費 ÷ 一単位あたり限界利益.
Candidates memorize the formula symbolically without a cost-classification step, and the exam supplies costs (荷造運賃, 減価償却費, 人件費) that must be sorted before any formula applies.
What to do instead
Adopt a fixed two-step procedure: first list every cost and label it 固定 or 変動 with a one-line reason; only then compute 限界利益率 and 損益分岐点売上高 = 固定費 ÷ 限界利益率. Practice sorting the same cost list under different business assumptions (e.g. 出来高払い vs 月給).
Answering 労働法 and コンプライアンス items from gut instinct about fairness rather than the statutory rule-e.g. assuming 試用期間 exempts an employer from 解雇予告, or that 残業代 can be waived by agreement, or missing that 36協定 is required before 時間外労働.
Candidates rely on general impressions of what seems reasonable and have not encoded the specific thresholds (14日以上の解雇予告, 45時間/月 and 360時間/年 の 36協定 上限, 有給休暇 の 付与日数), so plausible-sounding distractors win.
What to do instead
Build a one-page numeric fact sheet: 解雇予告 30日前 (or 30日分以上の平均賃金), 試用期間14日超で予告必要, 法定労働時間 1日8時間・週40時間, 36協定 上限, 有給休暇 付与 (6か月10日). For each practice item, cite the rule before choosing the answer, and mark any option that contradicts a numeric threshold.
Confusing マーケティング用語 that sit close together-mixing up 3C and 4P, calling セグメンテーション the same thing as ターゲティング, or labeling a 市場浸透価格 strategy as 上澄み価格.
Candidates learn the frameworks as acronym lists without the logical order (STP precedes 4P) or the defining contrast between paired terms (浸透 vs 上澄み, 差別化 vs 集中), so they cannot discriminate between two plausible labels.
What to do instead
For each framework, write the sequence and the question each step answers (Segmentation = who, Targeting = which group, Positioning = why us; Product/Price/Place/Promotion). For paired terms, write a one-line discriminating test (浸透 = low initial price to gain share fast; 上澄み = high initial price to skim early adopters) and drill only the pairs.
In 経営組織 and リーダーシップ questions, choosing an answer based on personal preference for a management style rather than matching the style to the situational variables the question states (team maturity, task structure, time pressure).
Candidates have not internalized contingency models and default to 'participative leadership is always best,' which the exam deliberately tests against situations where directive or 指示型 is correct.
What to do instead
Learn each theory with its contingency variable named: 状況適応理論 (リーダー行動 × 状況), SL理論 (メンバーの成熟度 → 教示/説得/参加/委任), PM理論 (P機能とM機能). For each scenario, underline the stated situational cue first, then select the style that cue maps to, ignoring your own preference.