Separate included revisions from new requests after client feedback
Classify scattered feedback against the agreed scope, resolve conflicting comments and record review rounds before discussing additional work.
What happened
You are designing sales slides from outside Japan for a Japanese client. Several contacts send feedback on different days: one changes a colour, another requests more slides, and a third reports a typo. Your agreement mentions two feedback rounds but does not define whether a round means one consolidated response or each person’s message.
In this fictional project, the accepted scope is eight slides for USD 1,200, with two feedback rounds. Contact A requests a colour change on 6 November 2026, contact B requests three new slides on 7 November, and a typo is reported on 8 November. The dates, price, identifiers and comments below are invented; two rounds are this project’s wording, not a Japanese standard.
Your immediate task is to classify requests and identify unresolved decisions. Pricing an addition comes later. A useful log preserves the actual comments without treating every email as a consumed round or every correction as new paid work.
What’s going on on the Japanese side
Find the agreed revision terms before deciding what a round includes
Collect the accepted quote, specification, supplied copy and subsequent confirmations. Extract the number of rounds, deliverables covered, method of consolidating feedback, review dates and treatment of errors. Distinguish a written term from your recollection of a call; if the accepted version is uncertain, ask the existing contact to identify it.
| Term to find | Fictional record | Question still open |
|---|---|---|
| Deliverable | Eight sales slides; review copy v2 | Are the requested three slides outside this set? |
| Price | USD 1,200 for the accepted scope | No additional amount has been proposed or approved |
| Revision allowance | Two feedback rounds | What counts as one round? |
| Consolidation | Not defined | Who will reconcile conflicting comments? |
| Errors and timing | No separate counting rule recorded | How will verified errors and later comments be handled? |
Do not fill gaps by retrospectively declaring the allowance exhausted. Propose a counting method and ask the buyer to confirm how it will apply to comments already received as well as future feedback. Keep the earlier wording visible alongside the new clarification.
JFTC Q59 explains improper changes and rework under the relevant Freelance Act provision, including cases where the supplier is not responsible and the buyer does not bear resulting costs or losses. It does not establish our categories, a two-round allowance or an automatic entitlement to an extra fee. Whether the rule applies to an overseas provider’s transaction is not determined here. Source
Turn scattered comments into a log that preserves duplicates and conflicts
Use a stable comment ID, sender role, date, target slide and version, requested action, proposed category and decision owner. Link to the original message in your private project record. A brief description is enough for a shared review sheet; do not copy confidential slide content into a public example or an unapproved AI service.
The following five fictional comments all concern v2 of the eight-slide deck. They are an exercise in classification, not evidence of testing with a real buyer. A and C disagree about one colour, while B’s addition is separate from that disagreement.
| ID / date in 2026 | Sender / target | Request | Working classification and next decision |
|---|---|---|---|
| C01 / 6 November | A, sales / slide 3 v2 | Change the accent to blue | Preference within the existing design; conflicts with C04 |
| C02 / 7 November | B, project / deck v2 | Add three competitor-comparison slides | Candidate new deliverable; confirm scope before pricing |
| C03 / 8 November | A, sales / slide 5 v2 | Fix a transposed word against the agreed copy | Verified provider error in this example; correction listed separately |
| C04 / 8 November | C, brand / slide 3 v2 | Use green rather than blue | Preference conflict; coordinator must resolve C01/C04 |
| C05 / 8 November | B, project / deck v2 | Make the presentation more persuasive | Unclassified; ask for target slides and an observable change |
Five comments are not five rounds. C01 and C04 remain two evidence rows but point to one unresolved colour decision. If the same typo is reported again, link the later message to C03 instead of counting a second correction; preserve the second sender’s report without adding duplicate work.
What to do next
Distinguish an error, a preference and a new deliverable using the baseline
-
Test the requested difference against the agreed input. For C03, compare slide 5 with the accepted copy: this fictional example assumes the provider introduced the transposition. Record the evidence and correction without presenting that provider error as an upsell. If the supplied copy itself changed, preserve both versions and investigate instead of using the same label automatically.
-
Separate a design choice from an added output. C01/C04 ask for a colour choice within the agreed design; that does not settle how the review allowance applies. C02 asks for three additional slides: eight plus three would make eleven if agreed, but neither their price nor delivery date follows from that count. Do not divide USD 1,200 by eight and assume the resulting average is an agreed rate for new slides.
-
Keep an unclear comment unclassified. Ask B which slide, audience problem and proposed change C05 refers to. It might mean changing a heading within the existing deck, or developing a new narrative requiring additional work. Until that distinction is supported, leave category, price and work plan unresolved.
These are operational labels for a conversation, not legal findings about liability or chargeability. A disagreement about the accepted specification belongs in the log with both positions and their evidence, rather than being resolved by your preferred category name.
Ask a buyer-confirmed coordinator to resolve contradictory instructions
- Request one consolidated answer through the existing contact. For C01/C04, ask which colour should be used and who will provide that answer after checking with sales and brand. Do not infer decision-making authority from a title or decide that the latest email overrides the earlier one.
Ask for a response date tied to the actual production plan, including timezone where a handoff time matters. Distinguish the date you request from one the buyer confirms. If the answer arrives late, discuss the affected schedule; do not automatically postpone an existing commitment or treat silence as approval.
Keep independent, settled items separate from the pending decision. For example, the verified typo can have a correction plan while the colour remains unresolved, subject to the actual agreed process. Coordinating feedback is a proposed communication arrangement, not an assignment of the buyer’s internal legal authority.
Record the remaining round after confirming the unit and completed work
- Agree what the counter means before updating it. In the fictional project, propose that the buyer’s first consolidated list for v2 becomes round one once its boundaries and treatment are confirmed. Do not mark a completed round merely because the list was received; record the agreed completion point and the provider’s response or revised version as well.
| Review record | Before clarification | Illustrative later state, only after agreement and completion |
|---|---|---|
| Unit | Undefined in the original wording | One identified consolidated list and its agreed implementation/check cycle |
| First list | C01–C05 contain unresolved items | List reference and included items explicitly confirmed; addition and unclear item tracked separately |
| Completed rounds | Not established from message count | One completed round, with revised version and completion evidence |
| Remaining allowance | Unconfirmed | Two agreed rounds minus one completed round = one remaining |
| Later feedback | Treatment unresolved | Record whether it corrects an implementation error, belongs to the next round or needs separate discussion |
This later state is a conditional example, not what the five incoming messages already prove. If the parties have not agreed the unit, keep the remaining allowance unconfirmed. Record how C03’s error correction is treated rather than silently deducting it from the allowance.
Send the resolved list and move only confirmed additions into a change proposal
- Return a decision log with a visible work plan. Add confirmation source, respondent, response date, status and planned action to each row. Use pending, clarified, agreed for action, implemented and checked as distinct states; receiving a reply is not evidence that a change was implemented correctly.
After C02 is confirmed as a proposed addition, use the accepted-work change record to discuss scope, price, schedule and purchasing confirmation. Keep C03’s correction separate. For delivery review status, use receipt versus acceptance; a classified feedback list is not final acceptance.
If a decision is only partial, state the confirmed items and the specific question still open. Preserve the original messages, previous log version and subsequent clarification. Do not replace the historical record with a cleaned-up list that makes all requests appear agreed from the outset.
Template
Ask for a consolidated decision without asserting that rounds are exhausted
Replace the fictional identifiers. The English and Japanese versions request the same clarification, not approval of an additional price.
Subject: Consolidated feedback for deck v2
Could you consolidate the feedback for version 2 and confirm whether
the three new slides in C02 are an additional deliverable?
I have listed the typo correction C03 separately.
C01 requests blue and C04 requests green for slide 3.
Please identify who will confirm the colour decision and when.
For C05, please identify the target slides and the specific changes.
Our record says two feedback rounds but does not define the unit.
Could we confirm the consolidated list, how it counts as a round,
and how corrections and later comments will be handled?
The remaining round count is not yet confirmed. Any addition's price
and schedule will be discussed separately before agreement.
件名:デッキv2のフィードバック取りまとめ確認
バージョン2のご意見を取りまとめ、C02の新しい3枚が追加成果物か
ご確認いただけますか。誤字修正C03は別項目として記載しました。
スライド3について、C01は青、C04は緑の指定です。
色の決定を回答する担当者と回答時期をお知らせください。
C05は対象スライドと具体的な変更内容をご確認ください。
記録にはフィードバック2回とありますが、回の単位は未定義です。
統合する一覧、回数への数え方、誤り修正や後着コメントの扱いを
確認させてください。残りの回数はまだ確定していません。
追加分の金額と日程は、合意前に別途相談させてください。
When to bring in a professional
Seek advice when scope, responsibility or change rights are disputed
Your project contact can clarify comments and identify a coordinating owner. Ask a qualified legal adviser if the parties dispute the scope, responsibility for rework, extra payment, suspension or the effect of a revision limit. Provide the accepted documents, versions, original feedback and dated responses; this classification does not determine applicable law.
Kit
Start with one unresolved comment in your existing project record
Copy the log into your existing document or spreadsheet; no purchase or registration is needed. Identify the relevant version, compare the request with the agreement and name the next question. The overall selling workflow provides context, but the immediate outcome is a supported classification, not a sale of additional work.
This guide goes stale when
- JFTC changes its Q59 explanation of improper changes or rework.
- The agreed revision scope, review unit or coordinating contact changes.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | JFTC Freelance Act Q&A — Q59 | October 29, 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.