Send a final delivery manifest that identifies the right version
Make a mixed-version delivery reproducible with a ten-file manifest, explicit replacements and separate receipt and acceptance records.
What happened
You delivered ten images in version 3 and later revised two. Your Japanese client now refers to “the ten v4 images,” while the folder contains several files labeled final. You need a record that lets the recipient identify the intended set without guessing which names or versions supersede others.
This fictional example uses images 02 and 07 at v4, with the other eight remaining at v3. A manifest is a dated list identifying that set and its status. The filenames and review states below are fictional metadata, not evidence that actual images were created, opened, tested or accepted by a client.
“Final” describes the proposed delivery set here, not blanket acceptance, permission to publish or a transfer of rights. Keep those decisions in their appropriate records. The useful outcome is that another reader can reconstruct the same ten-file list and identify precisely which confirmations are missing.
What’s going on on the Japanese side
Identify the exact file set being delivered
Use a stable item ID and an exact filename for each deliverable. A folder called v4 cannot explain a set containing both v3 and v4. Give the manifest its own identifier and revision so an answer can refer to the list as well as the files.
The Agency for Cultural Affairs’ copyright contract manual explains specifying creative work, delivery timing and method, and inspection arrangements. It also contains example contract clauses; this guide uses its explanation of those subjects, not its sample acceptance clauses. Do not insert a deemed-acceptance provision from the manual into an existing international agreement. Source
The following manifest is an editorial example, not an official required form. It identifies exactly ten PNG filenames, each with quantity one. It does not provide file sizes, hashes or technical test results because no underlying image files were measured for this example.
Show which files replaced earlier versions
Fictional manifest M-10 Rev2 identifies the intended current set below. For this scenario only, the earlier record explicitly accepted the unchanged eight v3 items; the revised 02 and 07 files have not yet received a receipt or acceptance confirmation. These states illustrate separate fields, not a conclusion drawn from a version number.
| ID | Prior filename / version | Current filename / version | Change | Qty | Current-file receipt | Current-file acceptance |
|---|---|---|---|---|---|---|
| 01 | image-01-v3.png / v3 | image-01-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 02 | image-02-v3.png / v3 | image-02-v4.png / v4 | Caption correction | 1 | Unconfirmed | Pending review |
| 03 | image-03-v3.png / v3 | image-03-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 04 | image-04-v3.png / v3 | image-04-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 05 | image-05-v3.png / v3 | image-05-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 06 | image-06-v3.png / v3 | image-06-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 07 | image-07-v3.png / v3 | image-07-v4.png / v4 | Crop correction | 1 | Unconfirmed | Pending review |
| 08 | image-08-v3.png / v3 | image-08-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 09 | image-09-v3.png / v3 | image-09-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
| 10 | image-10-v3.png / v3 | image-10-v3.png / v3 | Unchanged | 1 | Previously confirmed | Prior acceptance retained |
The current set contains two v4 files plus eight v3 files: ten files in total. The old image-02-v3.png and image-07-v3.png are outside that current set, even if retained in an archive. Copy only the current-filename column to reconstruct the intended list.
Confirm the buyer’s retention policy before deleting or moving old files. Preserve replacement relationships and prior decisions instead of relying on an overwrite. Keep archive permissions restricted and make the current-set location distinguishable from the historical record.
What to do next
Describe changes without reopening unrelated approvals
-
Describe each replacement narrowly. For image 02, record the caption correction and its agreed reference; for image 07, record the crop correction and reference. Identify the exact area requiring another review. The fictional table does not claim the changes meet a real specification.
-
Carry forward only evidenced decisions. In this example, the eight unchanged files keep their recorded earlier acceptance. In your project, use the actual prior decision and confirm whether the agreed process requires a whole-set check after replacement. An unchanged file with no acceptance evidence remains unconfirmed; “unchanged” is not a substitute for that evidence.
If a requested change goes beyond the agreed work, keep the version question separate from scope, price and schedule. Use the additional-work record to resolve the proposed change. Do not silently make “v4” mean an expanded obligation.
Check names, formats and counts against the agreed delivery
- Reconcile the intended list with the actual package. Check for missing IDs, duplicate IDs, unintended older files and incorrect formats. Compare the exact names against the manifest after uploading, not only in your local working folder. An extra archived version inside the current-set folder is an ambiguity to resolve, even if all ten intended names are present.
| Check | Evidence to retain when actually performed | What it does not establish |
|---|---|---|
| IDs and quantities | Compared list, missing/duplicate results, checker and time | Artistic or specification approval |
| Names and formats | Actual names and formats against agreed requirements | That every file opens |
| Openability | Named files, application/context, result and time | Buyer acceptance or publication rights |
| Recipient access | Recipient’s scoped response through approved channel | Completion of content review |
| Content review | Reviewer, criteria, IDs/versions and result | Approval of unrelated files or uses |
- Report tests truthfully. Run the applicable checks on actual files before describing them as tested. If a file has not been opened, record that gap rather than copying a “passed” value from this example. A successful local open does not demonstrate that the buyer has permission to access the shared copy.
Use only actual measured values if you add sizes or hashes. Explain which file each value identifies and keep it consistent with the delivered copy. Such metadata can assist identification, but it does not establish content suitability or replace the buyer’s review.
Send one authoritative manifest with a clear status
- Identify one current manifest. Send M-10 Rev2 through the agreed route with the current-set location, the two replacement relationships and the pending states. Identify which earlier manifest it supersedes for file selection. Preserve the earlier manifest as history rather than leaving two unlabeled lists competing for use.
The word authoritative means the designated file-selection list for this handoff; it does not confer legal authority on the sender. If the buyer requires approval before using revised files, describe this as the proposed set pending that approval. The message below asks for receipt and separately acknowledges the unresolved review.
Use an existing approved channel. Do not make a private folder public to simplify a handoff, or repeat access credentials in a broadly copied message. If the buyer cannot open a file, resolve access separately using the receipt and acceptance guide.
Record the recipient’s confirmation and archive the manifest
- Tie the reply to a list revision. Save the recipient’s exact answer, date and timezone alongside M-10 Rev2. If the answer says only “got the update,” ask whether it refers to the manifest, both replacement files, or completion of review. Update receipt and acceptance independently.
| Reply or issue | Record and follow-up |
|---|---|
| Manifest received, files not checked | Manifest receipt confirmed; file access and review remain open |
| Both v4 files received; review pending | Update receipt for 02/07 only; retain pending acceptance |
| “All ten are v4” | Restate 02/07 at v4 and the other eight at v3; request confirmation |
| Only 02 approved | Save the decision for 02 v4; keep 07 v4 pending |
| Both replacements accepted | Save scoped decisions; confirm any separate use or publication instruction |
Archive the exact manifest sent and the response under your established retention rules. Reuse the manifest in the project closeout record, with unresolved items visible. The next small action is to copy the ten current filenames into a separate list and verify that it includes only 02 and 07 at v4.
Template
Use this only after replacing the fictional identifiers and verifying that your records support the stated prior acceptance. It asks for receipt of the proposed set without claiming that the two revisions are approved.
Subject: Current delivery set — manifest M-10 Rev2
Please use M-10 Rev2 to identify the proposed delivery set:
images 02 and 07 are version 4, while the other eight remain version 3.
The current-set location is [approved location].
M-10 Rev2 replaces the earlier manifest for file selection.
Can you confirm receipt of this manifest and both v4 files?
Our record retains prior acceptance of the unchanged eight v3 files.
Review of images 02 and 07 at v4 remains pending.
Please identify any access problem and confirm the review status
of those two replacements separately.
件名:現行の納品セット — 一覧 M-10 Rev2
納品予定セットの特定には、M-10 Rev2をご参照ください。
画像02と07はv4で、残る8点はv3のままです。
現行セットの保存先は[承認済みの保存先]です。
ファイル選定用の一覧は、以前の版からM-10 Rev2に差し替えます。
この一覧とv4の2ファイルの受領をご確認いただけますでしょうか。
当方の記録では、変更のないv3の8点は以前の承認を維持しています。
画像02と07のv4は確認待ちです。
アクセスの問題があればお知らせいただき、この2点の差し替え版の
確認状況は受領とは別にお知らせください。
When to bring in a professional
Your project team can reconcile names and ask about missing confirmations. Seek legal advice if the parties disagree about acceptance, required revisions, retention, permitted use or rights. A manifest identifies files; it does not amend those terms or grant publication permission.
Provide the applicable agreement, previous approvals, replacement history and exact buyer replies. Do not copy the manual’s example contract clauses into a delivery email as though they already govern the engagement.
Kit
Use the manifest and checks in an existing spreadsheet or document; no kit or registration is needed. Keep the file-selection record with the selling-to-Japanese-companies workflow. Preserve the actual evidence behind each state so the next handoff can identify the same set without relying on memory.
This guide goes stale when
- The Agency for Cultural Affairs changes its explanation of work specification, delivery or inspection.
- Your agreed file set, naming scheme or review process changes.
- Your buyer changes its delivery channel or retention requirements.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | Copyright Contract Manual — specifying creative work, delivery and inspection | October 27, 2026 |
Was this useful?
More on Selling B2B
-
Japanese Client Requests Extra Work After Accepting Your Quote: Agree on the Change
Preserve accepted scope, price a requested addition, and ask your Japanese client to approve the work, delivery conditions and purchasing record.
-
Give a budget estimate without presenting it as a final quote
Build a defensible budget range from named uncertainties, show assumptions and exclusions, and identify what is needed for a final proposal.
-
Three buyer contacts give different instructions: map who owns each approval
Record conflicting project, procurement and onboarding instructions, ask the buyer to name a coordinating owner, and preserve one traceable answer.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.