JapanDesk

Practical guides for selling to Japan — written by someone who does the paperwork.

Set a delivery date when your Japanese client has not supplied the inputs

Build a first-quote schedule that separates a requested date, usable client inputs, review time and delivery, with clear branches for missing materials.

Published October 28, 2026 · Updated October 28, 2026 · Checked against 2 primary sources · Drafted and checked by our engine

What happened

A Japanese client asks when you can deliver a website, but the final copy, approved images and site access have not arrived. You are preparing the first quote, so the requested date is an input to planning rather than a date you have already committed to. A calendar entry without dependencies can hide work that neither party has scheduled.

Consider a fictional plan for delivery on 20 November 2026. It assumes usable copy, images and access by 2 November, a first draft on 10 November, consolidated buyer feedback on 12 November and final delivery on 20 November. These are hypothetical planning milestones, not dates for a live project, a standard production duration or a promise based on business-day arithmetic.

Make a dated dependency table before confirming the quote. This article addresses planning before agreement; it does not provide a way to postpone an existing commitment unilaterally. If a date is already agreed or disputed, keep that record and resolve changes through the appropriate process.

What’s going on on the Japanese side

Separate the requested date from a commitment you have actually made

Keep three fields: the buyer’s requested outcome/date, your proposed plan, and any confirmed commitment with its evidence. Ask whether “20 November” means handing over the completed files, making a staging site available, or launching publicly. Those are different outcomes and may require different people or approvals.

In the fictional plan, 20 November means final delivery of the agreed website package, not public launch. Record that definition beside the date. If the buyer needs a launch instead, clarify deployment responsibilities and any separate permission before presenting the same timetable as feasible.

Takeda’s supplier guidance asks suppliers to report delivery-time discrepancies, alongside other PO differences, to their Takeda contact. It illustrates the value of checking the recorded date for that company’s process; it does not establish this article’s dependency schedule or a general right to extend a deadline. Source

List usable inputs instead of treating “materials sent” as readiness

Identify each input, its format, the supplying contact and the person who will check readiness. Receipt is not the same as usability: a copy document may be incomplete, an image may lack a confirmed permitted use, or an access invitation may not grant the required access. Do not mark the entire input bundle ready because one email arrived.

Input for the fictional quoteUsable-state questionProposed owner and readiness point
Final copyIs the copy complete for the agreed pages, in the editable format agreed for this project?Buyer content owner supplies; provider checks by 2 November 2026, 17:00 JST
Approved imagesAre the identified files available in the required format, with the buyer’s confirmation of permitted use?Buyer asset owner supplies; provider checks at the same readiness point
Site accessDoes the named provider account have the access needed for the agreed work?Buyer technical owner arranges; provider checks through the approved route
Review coordinationWho will combine comments and resolve contradictory feedback?Buyer identifies one coordinating contact before the schedule is confirmed

Use readiness states such as not received, received but unchecked, usable, and clarification required. Keep the relevant document or confirmation reference for each state. The example’s readiness point is a planning assumption to discuss, not a newly imposed contractual cutoff.

Arrange receipt early enough for the readiness checks, rather than assuming a file sent at the cutoff can be validated instantly. Specify the necessary checking time after assessing the actual files and access process. Do not put passwords or confidential materials into a widely copied scheduling email.

What to do next

Reserve buyer review and revision time in the same schedule

  1. Plan the whole sequence. Identify production, first-draft delivery, buyer review, revisions and final delivery separately. Confirm the actual review scope and revision allowance in the quote. Do not count only your production time and leave buyer review as an invisible overnight task.
StageRequired inputProposed responsible personFictional proposed timeCurrent status / late-input question
Readiness checkpointUsable copy, images and accessBuyer input owners and provider checker2 November 2026, 17:00 JSTUnconfirmed; which item is missing or unusable?
First draftReadiness confirmed and production capacity availableProvider delivery lead10 November 2026, 17:00 JSTConditional; is the same scope still feasible?
Consolidated reviewFirst draft and agreed review criteriaBuyer coordinating reviewer12 November 2026, 17:00 JSTUnconfirmed; who will combine and approve the response?
Revisions and final deliveryConsolidated feedback within agreed scopeProvider delivery lead20 November 2026, 17:00 JSTConditional; are revision scope and final checks covered?
  1. Check calendars before confirming capacity. Validate holidays, absences, working dates and timezones for the actual participants. The gaps between these milestones are calendar intervals, not allocated working days. Do not infer review speed or availability from the buyer’s nationality.

If several departments review the draft, ask the coordinating contact how conflicts will be resolved before one consolidated response is sent. Identify the backup contact if that person is unavailable. Record an unanswered review as pending; it does not become acceptance when a proposed date passes.

Offer a feasible branch when an input misses the proposed checkpoint

  1. Find the affected work before changing a date. If images arrive but copy remains incomplete, identify which tasks depend on the missing copy. Ask whether the received part is usable and whether starting it would create avoidable rework. Do not assume every task must wait or that every task can proceed.
Planning branchWhat you can proposeWhat needs confirmation
Inputs usable as plannedRetain the proposed sequence after checking capacityScope, review owner, calendars and all milestone dates
Inputs late; full scope still neededReassess production and review slots, then propose new datesActual input readiness and buyer agreement to the revised proposal
Independent portion is readyStart only the clearly identified portionIts boundaries, rework risk, price treatment and effect on remaining work
Smaller deliverable could meet the requestOffer a reduced scope with explicit omissionsBuyer choice, revised price if applicable, and treatment of deferred items
Faster delivery is requestedAssess a separately described acceleration optionFeasibility, resources and agreement to any additional proposed charge

For example, if copy is still unusable at the hypothetical 2 November checkpoint, do not mechanically shift every milestone by the same number of days. Your next available production slot and the buyer’s next review slot may differ. Ask for a realistic input date, then rebuild the sequence and state which dates remain proposals.

Give every milestone a timezone and a responsible contact

  1. Write unambiguous handoff times. Use full dates, a time and a timezone for milestones that require a handoff. For this example, 17:00 JST is 08:00 UTC on the same date. Confirm the other participant’s local display using the actual location and date, including daylight-saving changes where relevant.

JETRO’s business-email examples include a meeting reminder with date, time and a GMT offset, accompanied by a daylight-saving caution. That is an example of clear scheduling communication, not a production-calendar rule or a mandated quote clause. Our owner fields and dependency branches are editorial proposals. Source

  1. Assign the next question. For each unresolved row, record who will supply the missing fact and when you will check again. A provider can assess production capacity; the buyer’s content owner confirms copy readiness. Avoid assigning an unverified responsibility to “the client” as a whole.

Attach the dependency schedule to the first quote and retain its status

  1. Version the proposal. Attach or incorporate the schedule in the first quote with its reference and date. Separate confirmed facts, assumptions awaiting agreement and open questions. When the buyer answers, update the relevant rows and retain the prior proposal instead of rewriting its history.

Use the quotation checklist for the rest of the quote. If the quote is already liked but ordering or start instructions remain unresolved, use the start-readiness guide. For changes to accepted work, use the change record rather than treating this first-quote plan as permission to change existing terms.

Template

Ask for input readiness before confirming the requested delivery

Replace the fictional schedule and owner roles. Both versions request a planning decision; neither confirms delivery or changes an existing obligation.

Subject: Inputs and review dates for the proposed website delivery

To assess the proposed 20 November 2026 delivery, could you confirm
when the final copy, approved images and site access will be usable?
Our draft plan assumes readiness by 2 November at 17:00 JST,
a first draft on 10 November, and consolidated feedback on 12 November,
with the draft, feedback and final-delivery milestones also at 17:00 JST.

Please identify the input owners and the person coordinating review.
These dates remain a proposal pending input, calendar and capacity checks.
If an input will be late, please identify it and its expected readiness date
so we can discuss revised dates, a separate first phase or a smaller scope.

件名:ウェブサイト納品案に必要な入力と確認日程

2026年11月20日の納品案を検討するため、最終原稿、承認済み画像、
サイトへのアクセスがいつ利用可能になるかご確認いただけますか。
日程案は11月2日17:00(日本時間)までの準備完了、11月10日の初稿、
11月12日の取りまとめた確認結果を前提としています。
初稿、確認結果、最終納品の各時刻も17:00(日本時間)の案です。

入力の担当者と確認の取りまとめ担当者をお知らせください。
入力、稼働日程、制作枠の確認前の提案であり、確定日程ではありません。
遅れる入力があれば、対象と利用可能となる見込み日をお知らせください。
日程の再提案、一部先行、範囲縮小の案を相談させてください。

When to bring in a professional

Seek advice if an existing deadline or change right is disputed

Project contacts can confirm input readiness and review arrangements. Seek legal advice if there is disagreement about an existing commitment, an extension, suspension or a proposed additional charge. This planning table does not establish those rights.

Provide the agreed documents, prior date confirmations, input requests and actual responses. Keep the requested date, your proposal and any accepted terms distinct so the adviser can assess the real record.

Kit

Use the free record to resolve the unanswered inputs

The table works in an existing document or spreadsheet without registration. The First-Quote Starter can help organize unanswered quote inputs; it is not a project scheduler and does not confirm these dates. Use the overall selling workflow for context. The next action is to name the missing input, its owner and the question needed to assess readiness.

This guide goes stale when

  • Takeda changes its instruction to report delivery-time discrepancies.
  • JETRO changes its meeting-message example with dates and timezone information.
  • The proposed scope, input readiness, working calendars or review arrangements change.

When one of these happens, the guide goes back into the queue for a re-check against the sources below.

Sources

Publisher Document Checked
other Third-Party Tools and Resources — Purchase Order Review October 28, 2026
jetro Overseas business support — meeting-message examples October 28, 2026

This guide summarizes publicly available information from the sources listed above. It is not tax, legal, or immigration advice. A tax accountant (税理士, zeirishi) or a lawyer licensed in Japan can tell you how it applies to your case.

Was this useful?

More on Selling B2B

Get the next guide by email

Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.

On this page