Your Japanese client will not give you a date. Give them one to correct.
Why pressing for a deadline stalls a live deal, and what to write instead.
One-line answer: A Japanese client who stays vague about timing usually does not have a date to give you. The date belongs to an internal approval process they cannot speed up or predict. Stop asking for the date. Ask about the process, and put a date of your own on the table for them to correct.
The misread
You ask when they can confirm. You get 「社内で検討します」 (we will review it internally) or 「もう少しお時間をいただけますか」 (could you give us a little more time). You ask again, more politely, and the same phrase comes back.
The natural conclusion is that they are dodging you, or that the answer is no and nobody wants to say it. Sometimes that is true. But in the deals that are actually alive, pressing for the date is the move that stalls them. You are asking a person to promise something that is not theirs to promise.
Why the vagueness is usually accurate
In a Japanese company of any size, a purchase that commits budget is rarely decided by the person you are emailing. It moves on a circulated approval document, the 稟議書 (ringisho), which collects sign-off from the people above and beside your contact.
How long that takes depends on things your contact cannot control from where they sit: when the next approval meeting is, whether another department has to see it, whether a manager is travelling, whether someone higher up asks a question that sends it back a step.
So when you ask for a date, you are asking them to guess in writing. A guess in writing becomes a commitment, and a missed commitment is their problem internally, not yours. The soft phrase is the safe answer, and often the true one: I do not know yet, and I cannot find out by myself.
I have been on that side of it. I sold door to door in Japan, and I was also the person vendors called on. I said 「検討します」 to those vendors when nothing had been decided at all. I said it to get through the moment. Pressing me for a date would not have produced one. There was no date to produce.
Stop asking for the date. Ask about the process.
Replace “when can you confirm” with questions your contact can actually answer. Each of these asks for a fact they already have, and none of them asks for a commitment.
1. Who else needs to see this?
差し支えなければ、社内ではどなたにご確認いただく流れになりますでしょうか。
“If you do not mind my asking, who inside your company will need to review this?” You learn how many steps the proposal has left, and whether a department you have never spoken to is involved.
2. When is the next point where this gets decided?
次に社内でご検討いただく会議は、いつ頃のご予定でしょうか。
“Roughly when is the next internal meeting where this will be considered?” Many companies approve spending at regular meetings. If the next one is on the first Tuesday of the month, you now have the date you were trying to extract, without anyone having to promise it.
3. What can I prepare for them?
社内でご説明いただく際に、こちらでご用意できる資料はございますか。
“Is there any material I can prepare to help when you explain this internally?” This one does more than it looks. It gives your contact something to carry upward, and the answer tells you whether a case is being built. A contact who says “a one-page summary would help” is writing something. A contact who says “no, nothing needed” may not be.
Give them a date to correct
In writing, the stronger move is the reverse of asking. You state a date yourself and make it easy to push back.
〇〇の件、〇月〇日までは今回のお見積り条件でお取り置きいたします。
社内でのご確認がそれ以降になりそうでしたら、お知らせいただければ延長いたします。
In English, roughly: “Regarding the 〇〇 matter, we will hold the current quoted terms until [date]. If your internal review is likely to run past that, just let us know and we will extend it.” Put the project name where the 〇〇 is, and a real calendar date a couple of weeks ahead where the 〇月〇日 is.
This works because it changes what you are asking them to do. Volunteering a date is a commitment. Correcting your date is not. “That date will be difficult, probably the middle of next month” is an easy sentence to send, and it is the timeline you wanted.
Three details are doing the work:
- お取り置き (holding it for you) frames the date as a favour to them, not a deadline you are imposing.
- 延長いたします (we will extend it) removes the threat. The date is a reference point, not an ultimatum.
- A real calendar date, not “two weeks”. A specific date is something to react to. A duration is something to ignore.
What to avoid is the direct version, 「ご回答期限は〇月〇日です」 (your response deadline is such-and-such a date). It asks for the same thing, but it asks for a commitment, and a contact who cannot commit will reach for the safest reply available.
Read what the reply tells you
- They give you a later date. The deal is alive and you now have a timeline. Plan around it.
- They say your date is fine. Something is moving inside. Expect a request for material or a new name soon.
- They come back with a request (a different quote format, a spec sheet, a question from someone you have not met). That is the clearest sign of all. Internal movement generates requests.
- Nothing comes back, and your date passes. Vague with nothing attached for two or three weeks usually means it stalled, and nobody wants to be the one to tell you. The words in a live deal and a stalled one look identical. What is attached to them does not.
The honest limit
Getting a date is not getting a yes. A timeline tells you when a decision will be made, not which way it will go. The deals I can trace to a decision were settled on price and specification, not on how well anyone read the timing.
What this does is stop you guessing. In person I used to read faces to tell whether someone meant it. In email there is no face at all. What you have is what comes attached to the message, and the questions above are how you get something attached.
Nobody taught me any of this. It came gradually. The point of writing it down is that you should not have to wait for it to come.
FAQ
How do I get a timeline from a Japanese client who stays vague?
Ask three process questions: who else needs to review it, when the next internal meeting that considers it is, and what material you can prepare. Then state a date yourself, offer to hold your terms until then, and offer to extend it if their review runs longer.
Is it rude to ask a Japanese client for a deadline?
Not rude, usually just unproductive. Your contact often does not control the date, so the question produces a softer version of the same non-answer. Ask about the approval process instead, or state a date they can correct.
What if they ignore the date I set?
Let it pass once without pressure, then check what has been asked of you since. If two or three weeks go by with no reply and no request of any kind, treat the deal as stalled for planning purposes.
Should I write these sentences in Japanese if we normally use English?
If your contact will pass your message upward, a Japanese sentence saves them translating it and keeps your wording intact. The body of the email can stay in English.
Does this work with small companies that have no ringi?
The process questions still apply, and often the answer to “who else needs to see this” is “nobody, it is my decision”. That is useful to know. It means the delay is the person, not the process.
One signal at a time
New decodes go out by email. No schedule promises, no filler. Read the archive and subscribe here.